August 12, 2011 at 7:48 am
Hey guys, I have a situation here and Im not sure how to handle it, so any help/suggestions will be greatly appreciated!
Heres the deal:
We have this massive database that we replicate to another server that is used for reporting ONLY...At first we set up transactional replication but for some reason (I cant remember) we ran into issues and could not use transactional replication...So we went with Snapshot....And it works fine...However at least once a week, it wipes the database completely and replication fails due to transaction log gets too big (like 176 GB big)...But my programmers are doing live reporting on this database so this does not need to happen...Sooooo my question is - is there a way around this? Given that its only being replicated to a server to handle our reporting, there is no need for a transaction log...Can I exclude the transaction log from Snapshot Replication? Another possible way is can you truncate the transaction log from the command line where our programmers can write up a little process to take care of that? How I fix this is, I have to go into the Database and change from Full to Simple recovery model, then I use DBCC SHRINKFILE and shrink the transaction log...then switch it back to Full...I may possibly be able to do this in a maintenance plan, Im not sure! So any advice on how to handle this issue will do wonders! Thanks
August 12, 2011 at 8:09 am
Please read through this - Managing Transaction Logs[/url] and this http://www.sqlservercentral.com/articles/Transaction+Log/72488/
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 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply