This question already has an answer here:
We have a large database, with a size of approx 400GB. We are using bulk insert (from upstream system) with the following parameters:
`Driver=/IIS/Appl/Server/branded_odbc/lib/VMsqls24.so` `Description=DataDirect 6.0 SQL Server Native Wire Protocol` `Address=SQLLPB2GBRxxx.xxxxx.COM,14331` `AnsiNPW=Yes` `AuthenticationMethod=4` `Database=DB_PROD` `QuotedId=No` `EnableBulkLoad=1` `BulkBinaryThreshold=32` `BulkCharacterThreshold=-1` `BulkLoadBatchSize=1024` `BulkLoadOptions=0`
The delta changes in the DB represent approx 70GB at month end. The transaction log file is falling over at 800GB (twice the size of the actual DB, where 800GB is the current size of the allocated transaction log drive). Autogrow is enabled on the transaction log, but we are unsure WHY it is becoming so large. Simple recovery is set.
Are there any parameters (either upstream on the bulk insert, or on the transaction log db ) we can fine tune?