![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
We have an off-site database (10g R2, Win2003 Server) that gets bounced twice a week on a schedule. The reason I was told is that our "vendor" (the people taking care of it) recommended it to "flush junk". Is there any real reason to bounce a server twice a week to clear memory (or anything else for that matter) that could/should be handled by having the database actually configured properly? |
#2
| |||
| |||
|
|
We have an off-site database (10g R2, Win2003 Server) that gets bounced twice a week on a schedule. The reason I was told is that our "vendor" (the people taking care of it) recommended it to "flush junk". Is there any real reason to bounce a server twice a week to clear memory (or anything else for that matter) that could/should be handled by having the database actually configured properly? |
#3
| |||
| |||
|
|
We have an off-site database (10g R2, Win2003 Server) that gets bounced twice a week on a schedule. The reason I was told is that our "vendor" (the people taking care of it) recommended it to "flush junk". Is there any real reason to bounce a server twice a week to clear memory (or anything else for that matter) that could/should be handled by having the database actually configured properly? |
#4
| |||
| |||
|
|
We have an off-site database (10g R2, Win2003 Server) that gets bounced twice a week on a schedule. The reason I was told is that our "vendor" (the people taking care of it) recommended it to "flush junk". Is there any real reason to bounce a server twice a week to clear memory (or anything else for that matter) that could/should be handled by having the database actually configured properly? |
![]() |
| Thread Tools | |
| Display Modes | |
| |