April 9, 2010 at 5:32 pm
Seems to be a silly question but really the answer requires for me.
I have a small doubt, Generally when I got alert on tempdb log file size 75 % full, I just do these steps
1)Check the current size,
2)If I need shrunk the size
3) Some times I use backup log with truncate_only( I know it is not recomended)
My Question is If I shrunk the log file or used the option release unused space, I have take any precautions before doing these options
I never faced any problem by using these options,
I would really appreciate if any one can answer quickly.
April 9, 2010 at 5:34 pm
rames.net (4/9/2010)
Seems to be a silly question but really the answer requires for me.I have a small doubt, Generally when I got alert on tempdb log file size 75 % full, I just do these steps
1)Check the current size,
2)If I need shrunk the size
3) Some times I use backup log with truncate_only( I know it is not recomended)
My Question is If I shrunk the log file or used the option release unused space, I have take any precautions before doing these options
I never faced any problem by using these options,
I would really appreciate if any one can answer quickly.
No, many systems I have worked on have a job to shrink TempDB on a hourly basis.
Shninking it won't delete any objects in it. It just free's up space on the LUN.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 9, 2010 at 6:03 pm
Shrinking it is not necessarily a bad thing - only because it is Tempdb.
I would recommend that you find what is causing it to fill and see if you can fix that situation.
Here is an article that could help you in determining that.
http://www.sqlservercentral.com/articles/Log+growth/69476/
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 9, 2010 at 10:04 pm
rames.net (4/9/2010)
Seems to be a silly question but really the answer requires for me.I have a small doubt, Generally when I got alert on tempdb log file size 75 % full, I just do these steps
1)Check the current size,
2)If I need shrunk the size
3) Some times I use backup log with truncate_only( I know it is not recomended)
My Question is If I shrunk the log file or used the option release unused space, I have take any precautions before doing these options
I never faced any problem by using these options,
I would really appreciate if any one can answer quickly.
You're actually missing the first step... determine what's causing the problem and fix it.
You also haven't stated what the size of the TempDB log file is. That's kind of import in being able to make a recommendation to you.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2010 at 10:11 pm
Jeff Moden (4/9/2010)
rames.net (4/9/2010)
Seems to be a silly question but really the answer requires for me.I have a small doubt, Generally when I got alert on tempdb log file size 75 % full, I just do these steps
1)Check the current size,
2)If I need shrunk the size
3) Some times I use backup log with truncate_only( I know it is not recomended)
My Question is If I shrunk the log file or used the option release unused space, I have take any precautions before doing these options
I never faced any problem by using these options,
I would really appreciate if any one can answer quickly.
You're actually missing the first step... determine what's causing the problem and fix it.
And, seriously, refer to that article I posted. It is very useful in determining the cause of a growing log file.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 10, 2010 at 10:47 am
place your Tempdb on a separate array and size it appropriately + then some. It shouldn't then get to the point where it needs to grow again. Any file shrinking\growth incurs I\O and this is the unnecessary I\O you want to decrease!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 10, 2010 at 11:37 am
shrinking is definiely not recommended. If tempdb requires that much of space and if tempdb have emplty space, it will use it. If tempdb log is small and if any transaction requires more log it will fire filegrow event everytime to increase the log space which is costly operation.
April 10, 2010 at 1:09 pm
vidya_pande (4/10/2010)
shrinking is definiely not recommended. If tempdb requires that much of space and if tempdb have emplty space, it will use it. If tempdb log is small and if any transaction requires more log it will fire filegrow event everytime to increase the log space which is costly operation.
Tempdb should be properly sized but transactions or poorly written code do get through from time to time and cause problems with tempdb. Occasionally it is necessary to shrink it back to normal operating range. Prior to doing that however, you must find what is causing the problem.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply