Viewing 15 posts - 91 through 105 (of 1,270 total)
ScottPletcher (2/28/2013)
I have additional space to grow, you prevent it.
So if a task unexpectedly needs, say, 50MB more of tempdb space to complete, you abend it -- perhaps after it...
February 28, 2013 at 11:37 am
ScottPletcher (2/28/2013)
So if tempdb now does need to grow for whatever reason, and it causes a SQL issue because it can't, you've guaranteed that there's no easy way to recover,...
February 28, 2013 at 11:12 am
If you were successfully sizing tempdb to be the size that SQL needs, you wouldn't be using startup procs to check file sizes and be concerned about checking the files...
February 28, 2013 at 11:08 am
ScottPletcher (2/28/2013)
Zero chance. I'd never disable autogrow on tempdb: you could slam your entire instance to a halt -- or worse, perhaps cause it to crash.
If you've pre-sized the...
February 28, 2013 at 10:56 am
ScottPletcher (2/28/2013)
So proportional fill will "ensure" that? I wasn't sure that was guaranteed. I know it wasn't in the past.
Nobody is saying that proportional fill will ensure that...
February 28, 2013 at 10:53 am
ScottPletcher (2/28/2013)
February 28, 2013 at 10:49 am
ScottPletcher (2/28/2013)
How, then, do you become aware...
February 28, 2013 at 10:48 am
GilaMonster (2/28/2013)
I meant exactly what I said. No reboot necessary. A restart of the SQL Server service is very strongly recommended. A reboot of the entire server is not required...
February 28, 2013 at 10:46 am
GilaMonster (2/28/2013)
Regarding point number 4 above. Is a reboot necessary - could i just restart the sql server agent ?
No reboot necessary. Not SQL agent though, restart SQL Server itself
Did...
February 28, 2013 at 9:15 am
Yes, that was the reason for his suggestion of two files at 800MB so that together they would be about 1.5 GB. Personally, I always advocate pre-sizing your tempdb files...
February 27, 2013 at 9:15 pm
ScottPletcher (2/27/2013)
If a tempdb data file is 1.5G when SQL goes down, won't it be 1.5G when SQL comes back up? Isn't it automatically reset to its previous size?...
February 27, 2013 at 2:58 pm
ScottPletcher (2/27/2013)
Then, set up a start up proc to shrink both tempdb files
NEVER manually shrink tempdb files. It can corrupt the tempdb files. Avoid shrinking files of any database if...
February 27, 2013 at 2:03 pm
That's not for SQL Server. It's for the other programs (Like Exchange) that still have the on-site training as a requirement. They are re-introducing on-site training for SQL Server, but...
February 10, 2013 at 4:56 pm
So the difference you're seeing is definitely the difference in collection intervals. You can adjust the collection interval if you need to for troubleshooting a particular issue, but I would...
February 7, 2013 at 11:00 am
Viewing 15 posts - 91 through 105 (of 1,270 total)