March 13, 2009 at 8:40 am
Hi,
My problem is the following:
I have a sql server 2005 installation in windows 2003 R2 64 bits and I have enabled mirroring service ,but When The mirroring server is working, is no possible to make truncate the database logs when it´s full.
I need to know How to do that kind of maintance
Mi database is 80 compatibility.
Thanks your help.
Oscar
March 13, 2009 at 9:09 am
When you go with mirroring, the logs are moved, which means full recovery mode. If you truncate, you'd break mirroring.
Are you running log backups? You should be doing this to manage the log. You can run them more frequently to lower your requirements for the log. Or you need to increase the size of the log.
March 13, 2009 at 1:34 pm
Thank for your fast answer.
I forgot to tell that it´s happens when "reorganize index database" is running so the log is full fast (3 minutes approx.). I´m using the following sentence;
BACKUP LOG Winblind With TRUNCATE_ONLY
It exists other option to do it without this problem.
Regards,
March 13, 2009 at 4:26 pm
ohernandez (3/13/2009)
Thank for your fast answer.I forgot to tell that it´s happens when "reorganize index database" is running so the log is full fast (3 minutes approx.). I´m using the following sentence;
BACKUP LOG Winblind With TRUNCATE_ONLY
It exists other option to do it without this problem.
Regards,
If database is set for mirroring you should not be able to do that. Because database mirroring relays on T-log for its operation. Only way you'll be able to execute that is if you break mirroring...
WHen you execute it you should get error similar to :
Msg 3048, Level 10, State 1, Line 1
BACKUP LOG WITH TRUNCATE_ONLY cannot operate on database 'dbname' because it is configure for database mirroring.
...
SHould use proper t-log backup and make sure you t-log has enough space to complete its operations.
Thanks.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 14, 2009 at 3:34 am
ohernandez (3/13/2009)
It exists other option to do it without this problem.
BACKUP LOG TO DISK = ....
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 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply