david.edwards 76768 wrote:
Grant Fritchey wrote:
Be careful of autogrowth here. Also, it's a good idea on any drive with auto-growth enabled, create an file called 'deletemeinemergencies' or similar. Make it big enough, say 20 or 50 mb, so that you can use it to easily reclaim a little space when the drive filled by accident. It makes recovery much easier.
OOOOH! I like that idea! Why didn't I think of that! 🙂
For the log file, it's real handy if (for example, you have a 100GB drive just for the log file), to allocate only 10 or 20GB and then setup an alert for when it grows. That way, you can have some time to find out what is causing the log file to grow. You could even make it so the alert runs code to see what's running to help narrow down the candidates or scare up some code that will tell you what everything that's currently running is using for logfile space.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)