Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Chinwa
Starting Member
20 Posts |
 Posted - 2005-12-15 : 08:51:53
|
| I thought I read somewhere that you can suspend writing to the transaction log for performance issues.I have a really big table insert with gov. data and each time I flush out the table and then write all the data received into the table. I do not need the transaction log to record all this. If the job fails I simply flush the table and re-write from the CD again. I do not want to totally stop the transaction log; I just want this one job to run with out making entries.I am sure I saw a command for this somewhere. Anyone know? |
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2005-12-15 : 09:17:08
|
| Set the recovery model to BULK_LOGGED.See ALTER DATABASE in BOL.How do you enter the data?rockmoose |
 |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2005-12-15 : 09:17:58
|
| 1. As long as this action is the ONLY DB activity in effect during this time period, and you may wish to make the DB single-user for the duration to ensure it stays that way, you can set the recovery model to simple, load the data backup the DB and then set the recovery model back to regular.2. If the raw data is external to SQL, you could BCP the data which operates (or can operate) in non-logged mode.3. You could load the data in batches, to minimise the working size of the T-Log. |
|
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2005-12-15 : 09:42:48
|
| How about...Put the table with gov data in a separate database, simple recovery model.rockmoose |
|
|
|
Chinwa
Starting Member
20 Posts |
Posted - 2005-12-19 : 08:53:32
|
| I thought there was some sp or DBCC or something command that would simply halt the transaction log from recording the bluk insert of just this one query.Thank you for your help. |
|
|
|
|
|
|
Halting the transaction log