July 29, 2004 at 3:03 pm
I have a number of maintenance plans that do a optimization on a set of specified databases. My problem is the larger databases (3GB+) the logs are set to autogrow so it can expand automatically as the reindexing occurs. The thing is that they are growing so much they are running the disk out of space. Is there a way to prevent this growth or have the logs automatically shrink when the maintenance plan is done? Any suggestion would be greatly appreciate. This is on a SQL Server 2000 box.
Thanks
Arthur Lorenzini
July 29, 2004 at 6:01 pm
July 29, 2004 at 8:20 pm
My reindexing script looks at the log between tables and will perform a tlog backup if needed is currently in testing. We blow up the tlog doing a index defrag. If you can live with it you may want to set your db the bulk logged option during reindexing. If I remember correctly that will keep the reindex from being logged. I don't think it has an effect on index defrag though.
Wes
August 4, 2004 at 9:00 am
Our recovery mode is full because we need point in time recovery on our production dBs. Could you show me a sample of you reindexing script?
Arthur Lorenzini
August 4, 2004 at 9:21 am
Same here. I won't have a ready script until the end of this week or beginning of next. When it is done it will go into the script library here. I'll be more than happy to bump you a note as soon as its done.
Wes
August 4, 2004 at 9:41 am
That would be great. So actually you are not running maintenance plans you are running some job that executes a script?
Arthur Lorenzini
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply