Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

DB mirroring between SQL 2005 and SQL 2008 R2 Expand / Collapse
Author
Message
Posted Tuesday, May 14, 2013 6:47 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:45 AM
Points: 94, Visits: 319
Is it possible to setup DB mirroring between SQL 2005 as primary and SQL 2008 R2 as Mirror.
Post #1452542
Posted Tuesday, May 14, 2013 7:30 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:16 AM
Points: 40,194, Visits: 36,599
Yes, but it's an exceedingly bad idea and it's only supported as part of a rolling upgrade process.

The mirroring will work, however if that ever fails over then the new principal is 2008 R2 and the mirroring will go suspended and you won't be able to resume without upgrading the 2005 server.
Essentially it's a failover implementation that you can never ever fail over, kinda pointless.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1452566
Posted Tuesday, May 14, 2013 7:49 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, October 20, 2014 2:56 PM
Points: 835, Visits: 1,191
I have never tried that but first prerequisite for that as per MS :-

"For a mirroring session to be established, the partners and the witness, if any, must be running on the same version of SQL Server."

http://msdn.microsoft.com/en-us/library/ms366349.aspx#Prerequisites
Post #1452585
Posted Tuesday, May 14, 2013 8:26 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:16 AM
Points: 40,194, Visits: 36,599
It is possible to have the mirror a higher version, but as I said it's a stupid thing to do and iirc it takes extra work to even set up that way, you can't use the GUI to set it up.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1452619
Posted Tuesday, May 14, 2013 10:18 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 2:28 AM
Points: 151, Visits: 667
GilaMonster (5/14/2013)
It is possible to have the mirror a higher version, but as I said it's a stupid thing to do and iirc it takes extra work to even set up that way, you can't use the GUI to set it up.


The only practical use I can see is to setup a database for upgrade prior to actually implementing the upgrade; saves a bit of time in your maintenance window for the upgrade by not having to perform a full restore?
Post #1452706
Posted Tuesday, May 14, 2013 2:24 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:16 AM
Points: 40,194, Visits: 36,599
About the only use is as part of a rolling upgrade, so install a second SQL instance (same version), configure mirroring, make sure everything works and the app redirects properly, upgrade the mirror (now running higher version mirror than principal), fail the mirroring over, upgrade the principal, fail the mirroring back (or, if you're migrating hardware as well, leave the 'mirror' as the new principal).

Version upgrade with minimal downtime (one or two failovers).

In a rolling upgrade though you wouldn't install the mirroring with mismatched versions, it would just be that way for a brief time during the upgrade.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1452829
Posted Tuesday, May 14, 2013 8:31 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 8:53 AM
Points: 411, Visits: 1,310
GilaMonster (5/14/2013)
It is possible to have the mirror a higher version, but as I said it's a stupid thing to do and iirc it takes extra work to even set up that way, you can't use the GUI to set it up.


Gail,

I don't think it's so stupid, I think it depends.

I "migrated" a huge, very big database, from SQL 2005 to SQL 2008 using mirroring. It took just few seconds of downtime, literally speaking and was just changing the code. It went very well.

Backup and restore was not an option to me, too much downtime.

Of course, I knew going back was not an option, but that was actually part of the initial plan.
Post #1452901
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse