September 8, 2010 at 3:52 pm
Dear All,
I have a data migration activity in one of my production database server.this activity takes more that four hours.The script contain lots of insert delete and update statements.so after the activity the size of the log will be more than 100GB.So is there any way to disable sql transaction logging
Please help me
Regards
Denny
September 8, 2010 at 4:58 pm
To answer the specific question: You *can* alter the database restoration method via an Alter Database command before you begin, and thus the logging will only store the transactions that are occurring until they're completed.
Doing this also destroys any chance you have of point in time restoration after that point (although differential backups will work, just not log backups), even when you switch back, until you reset it to full (or bulk-logged) and then perform an entire full backup.
You can also do transaction log backups in your import cycle to help keep the t-log itself to a reasonable level, but you'll obviously need a place to store all those backups.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 8, 2010 at 11:18 pm
You cannot disable logging. You can change when SQL removes inactive log records from the log by changing the recovery model. Before you do that, understand the implications if this is a production DB. Won't help if the entire script is done in a single transaction though.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply