Database T-Log behaviour in Batch SQL | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Database T-Log behaviour in Batch SQL

Hi to all, I need to add new column with default ‘1’ for existing table of 5 million records.
To avoid transaction problem while adding column with value, I am doing in batch update of 100K to have default value of 1 (after adding column without default). So that it reuses log space. This is working perfectly all right in all servers except in development server.
Is there any potential problem, why the batch SQL did not reuses the Log space in developerment server.
There is no open transaction as well as no user connected to the database.
Error log looks clean. This is kind of surprise as well as curious to me.
I appreciate any thought. Thanks,

Hi,<br />is their something in your SQL Error Log ?! is their some difference in SP , HOT FIXs , MDAC version or Recovery Model ?<br /><br /><br /><img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ /><br />Regards<br /><br />Hemantgiri S. Goswami<br />[email protected]<br />"Humans don’t have Caliber to PASS TIME , Time it self Pass or Fail Humans" – by Hemantgiri S. Goswami<br />
What is the recovery model on this database?
How often you perform transaction log on this databsae?
Run DBCC SQLPERF(LOGSPACE) before and after this procedure. Satya SKJ
Contributing Editor & Forums Moderator
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.