Viewing 15 posts - 76 through 90 (of 93 total)
Thanks. Actually, my system can handle the size, so I really don't need to truncate at this point.
What I'm really wanting is to understand why/how the transaction log can...
August 28, 2008 at 8:37 am
Thanks Paul for your reply. Do you mind telling me what this is going to do? This is a production server and I don't like taking chances 😉
August 28, 2008 at 8:19 am
Also the initial size of the log file was set to 537MB.
August 28, 2008 at 8:12 am
Wow, I can't believe that I forgot about that option...mental lapse! Thanks for pointing that out.
August 12, 2008 at 1:49 pm
tosscrosby (7/25/2008)
My best advice is to monitor growth
Is growth history kept anywhere? Is there a query I can run that will tell me when a growth has occurred?
July 28, 2008 at 8:06 am
GilaMonster (7/24/2008)
Autogrow puts a small overhead on the system and allows the possibility...
July 24, 2008 at 8:01 am
Brandie Tarvin (7/24/2008)
Does this technobabble make sense?
Ok, so it sounds like you should usually restrict the growth (esp. in prod), unless there's a good reason to do otherwise.
Thanks!
July 24, 2008 at 7:48 am
Brandie Tarvin (7/24/2008)
We actually have some DBs with UNRESTRICTED on them, but on the other hand, we also have several Alerts and jobs set up to monitor Hard Drive space....
July 24, 2008 at 7:35 am
So, is it good practice for any database/trans log file to restrict the growth to a little less than what your disk allocation is? (say you have a dedicated disk...
July 24, 2008 at 7:21 am
GilaMonster (7/18/2008)
July 18, 2008 at 7:45 am
GilaMonster (7/17/2008)
July 18, 2008 at 7:21 am
Actually, CAN I do a shrinkfile in a mirrored environment? I was told by our contractor that you should never truncate the logs since you don't know if all...
July 17, 2008 at 12:35 pm
tosscrosby (7/17/2008)
file(s) is truly not recommended. It will lead NTFS fragmentation and will definitely fragment your indexes,...
July 17, 2008 at 12:22 pm
Viewing 15 posts - 76 through 90 (of 93 total)