Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dbalearner
Constraint Violating Yak Guru
272 Posts |
 Posted - 2010-07-29 : 20:09:27
|
| We have Clustered Server boxes and Standalone Server boxes having huge transactions that are taking place on daily basis. Some times the transactions might run into more than 50 GB overall perday.As a result of this, there will be rise in the TEMPDB location which is for reasons not directly known. I know TEMPDB will be impacted for all the Sorting and variables storage etc.But my question is , How often under the prescribed Server practises the Server needs to be started? What would be the frequency of restarting? Or else irrespective of the growth in the TEMPDB whether the server needs to be started or not?Is there any Document Evidence suggesting the Server needs to be started for allowing the latest patches, hot fixes and other generalised practises onto the server to accomodate the latest to be promulgated?Can anyone suggest, thanks All in advance. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
dbalearner
Constraint Violating Yak Guru
272 Posts |
Posted - 2010-07-29 : 21:17:37
|
| Thanks to that, however, I have been recommended by the Experts very long ago due to the scenario explained above. I expect the MS have this one say in its documentation, but couldn't find. Any Help in this regard! Once again thanks. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
dbalearner
Constraint Violating Yak Guru
272 Posts |
Posted - 2010-07-30 : 00:12:44
|
| In General Practises according to the Microsoft SQL Server recommendations the need to start the production server for every 2 Months which otherwise depends on the traffic of the transactions; Hotfixes; patches being uploaded.This I was referred very long back and I dont have any written communication to this, but now I just understand partially you've also supported the idea of hotfixes.TEMPDB issue when it increments either do it database shrink which is not so good idea but simple practise is to restart the server which will automatically fixes its minimum size for it.Now after going through the rough patch of TEMPDB growth I have no other choice but to pull the unwanted transactions inside its files.Perhaps I have given complete problem of mine. Can You please give me the evidence of MSDN or Microsoft Document link to this.Largely thanks to TKizer. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|
|
Server Restart