SQL Server Soldier :: News from the frontlines of the database wars - All Comments

re: SQLSaturday 26 Session Files

vbabu3 — Fri, 06 Nov 2009 15:16:55 GMT

Was informative with regards to mirroring. Looking forward to future sessions

re: Breaking Up is Easy to Do

Vijayakumar KP — Thu, 05 Nov 2009 05:43:58 GMT

Nice stuff....

re: SQLSaturday 26 Session Files

Robert Davis — Mon, 05 Oct 2009 21:42:39 GMT

Thanks Buck!! Unfortunately, I was not able to atend your sessions that day, but I've attended a couple of your presentations on MSFT campus before, and I hope to attend more of them in the future!!

re: SQLSaturday 26 Session Files

BuckWoody — Mon, 05 Oct 2009 16:40:36 GMT

Great to meet you there, Robert. Hope to see you again soon!

re: Database Mirroring FAQ: How do we handle transaction log maintenance for a mirrored database?

BobAtDBS — Tue, 15 Sep 2009 14:48:59 GMT

If you simply use DBCC ShrinkFile on the principle's log file, the resulting change will be applied to the mirror as well in a very small transaction. The mirror size will normally stay perfectly in synch with the principle's size.

We ran out of disk space on the mirror, so mirroring was suspended and the principle's log grew rather large. After clearing room on the mirror's log drive, resuming mirroring, letting it catch up, and finally letting the next principle log backup take place, we were able to use DBCC ShrinkFile on the principle's log file and the change was instantly reflected on the mirror.

re: I Need a Backup and I Need It Now

dsully — Tue, 18 Aug 2009 19:26:10 GMT

I am getting an error everytime:

Exception calling "SqlBackup" with "1" argument(s): "Backup failed for Server 'myServer'. "

At C:\PowerShell\BackupProdDB.ps1:78 char:18

+ $Backup.SqlBackup( <<<< $Srv)

What am I doing wrong?

This will be very useful if I can get it to work. Thanks in advance.

re: Database Mirroring FAQ: How do we handle transaction log maintenance for a mirrored database?

-- Cranfield — Wed, 05 Aug 2009 10:16:03 GMT

We've seen a problem where if the log file on the Primary autogrows then this growth is not propogated to the mirror. This causes a big problem in that the log file on the primary will not truncate after the log backup. I'm sitting with a tran log of 150GB with 65% used. There are no open transactions and a backup or checkpoint does not truncate the log. My log file on my mirror is only 80GB. the mirror is in synch. This has to be a bug.

re: How many mirrored databases can I have on a server?

Gé Brander — Mon, 15 Jun 2009 10:30:38 GMT

Ok, clear. Maybe adjust your post to Cores. It makes more sense to people. Then you make a clear distinction between processors and cores.

re: How many mirrored databases can I have on a server?

Robert Davis — Mon, 15 Jun 2009 00:00:27 GMT

I use the term "processors" to mean logical processors. It is the number of processors as SQL sees them. So if you have 8 quad core processors, then SQL sees 32 processors. If you have 32 quad core processors, then SQL sees 128 processors.

re: How many mirrored databases can I have on a server?

Gé Brander — Fri, 12 Jun 2009 08:34:43 GMT

When you state 'processors' do you mean cores or processors? Do I need a 32 processor with quad cores ==> 128 cores or 8 processor with each 4 cores ==> 32 cores?

re: Database Mirroring FAQ: How do we handle transaction log maintenance for a mirrored database?

Robert Davis — Fri, 12 Jun 2009 00:31:52 GMT

Hi Bob. I agree about it being a bad thing. That should only be used for extreme cases, in my opinion. Unfortunately, it was required due to a bug if your SQL build was SQL 2005 prior to CU6 for SP2. Fortunately, that bug has been fixed!!

Really, the only way to shrink the log file on the mirror only would be to fail over to the mirror, shrink the file, and then fail back.

re: Database Mirroring FAQ: How do we handle transaction log maintenance for a mirrored database?

Robert Mills — Tue, 09 Jun 2009 21:51:13 GMT

Robert,

The article you referenced from Microsoft Support is a very bad thing for my implementation. I'm dealing with a VERY LARGE DB and it is NOT set to autogrow. I really don't want to shrink it even if that would shrink my mirror transaction log. Is there any way known in SQL 2005 to truncate / shrink a transaction log ONLY on the mirror?

thanks,

Bob Mills

re: Database Mirroring FAQ: How do we handle transaction log maintenance for a mirrored database?

Robert Davis — Thu, 04 Jun 2009 13:45:28 GMT

Hi Amy. Take a look at this KB article if you need to shrink the log file on the mirror: support.microsoft.com/.../937531

Otherwise, if you just need to shrink the log file on the principal, use DBCC ShrinkFile().

re: Database Mirroring FAQ: How do we handle transaction log maintenance for a mirrored database?

Amy Herndon — Wed, 03 Jun 2009 22:14:02 GMT

Database Mirroring FAQ: How do we handle transaction log maintenance for a ... They normally truncate the txn log after a full backup without DB Mirroring. ...

www.sqlservercentral.com/blogs/robert_davis/archive/.../How-do-we-handle-transaction-log-maintenance-for-a-mirrored-database.aspx - Similar pages

I am trying to see what we can do to truncate the logs on the morrroed dbs.

Thanks.

re: Behind Every Great Restore is a Great Backup

v-ranik — Fri, 22 May 2009 09:28:57 GMT

This article was really superb and informative.. I would like to learn more in details on backup & restore terminologies.. Any inputs on this would be of great help.

Thanks