September 28, 2004 at 12:57 pm
Hi
I have a scheduled job that runs on my server everyday from 2100, and it ends about 2330. I have noticed that the database increase in size during this job, not to mention that it allocates alot of free space and it keeps holding that free space after the job ends.
Thus I have to shrink the database after this job. No problem, but there has to be away around this?
I use scheduled shrink right after the job ends, but can I shrink while the job run?
My shrink settings:
- max free space in files after shrink: 99%
- shrink file to [minimum]
Should I use some other settings? i.e. truncate free space from the end of file.
ps! cross post to forums: general and performance tuning
Best regards
Dan
September 29, 2004 at 6:54 am
Why do you need to shrink it? It would be best just to leave it at the larger size. Your job will run more efficiently and you will have less file fragmentation. If your application is transactional, allowing for online updates, you should probably have some free space in your database to allow space for the new records. Otherwise, the database will be expanding while the user is doing their update, and he/she will experience long waits.
Steve
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply