May 30, 2006 at 8:33 am
Here's the situation....
DB:SQL Server 2K
Project manager decides we will use select - inserts to load an extraction database (26 tables, 3 with large record counts) from our transaction system. I fought for bcp, but no dice.
So, the Extract db was initially created with 1 meg for t_log, with simple recovery.
Our process to load E_db: Drop indexes in E_db, run proc to load each table, build indexes on E_db.
we have 18 messages in the log
Autogrow of file 'TWIA_Extract_Log' in database 'TWIA_Extract' took 96641 milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file.
The auto growth was set to 10%. I turned off auto shrink, set the file growth on the T_log to 5000 meg increments. thinking it would reduce the number of auto growths.
still getting the message (18 of them, again)
Autogrow of file 'TWIA_Extract_Log' in database 'TWIA_Extract' took 238375 milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file.
I'm armed with the SQL Server Admin 2000 book as my reference, and have no clue where to start to fix this problem.
I think it's shrinking the t_log after each insert, because of the simple recovery model. Any suggestions?
Thanks in advance from a DBA in the making,
Vicki
May 30, 2006 at 11:31 am
How about creating a very large file to reduce autogrowth at least till the file gets there.The autogrowth process consumes useful resources when the extraction process could be better served
Mike
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply