|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Thursday, February 21, 2013 9:37 AM
Points: 29,
Visits: 129
|
|
Can you have this mirroring scenario.
Principal sql server 2008 standard engine
Mirror sql server 2008 R2 enterprise engine
Thanks!
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 11:45 AM
Points: 37,744,
Visits: 30,023
|
|
Yes, but it's not supported except during an upgrade scenario. (upgrading a 2008 mirror pair to 2008 R2). If you ever fail to the mirror, you will not be able to fail back without upgrading the principal to R2.
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
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Thursday, February 21, 2013 9:37 AM
Points: 29,
Visits: 129
|
|
I'll tell you why we want it - from your explanation seems like we are good to go with that.
We need to replicate a database from one site to another for the sole purpose of reporting. The BI guys insist on a incremental load. I did try transactional replication but had schema issues (schema_binding on functions did not allow replication of table because it could not drop them). Therefore thought this method may be better. Seems to work well when editions on principal and mirror is the same!
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 11:45 AM
Points: 37,744,
Visits: 30,023
|
|
I strongly do NOT recommend mirroring with different versions. The mirror should also be 2008 if the principal is SQL 2008. The setup you described is intended to work only for a short time during the upgrade process.
Have you considered log shipping? Ship with standby (also requires same version) and the database is read only automatically. You could set the restore job to restore after hours only so that there are no disconnects.
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
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Thursday, February 21, 2013 9:37 AM
Points: 29,
Visits: 129
|
|
| why do you think the log shipping needs same versions of sql? Is it for the same reason?
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 11:45 AM
Points: 37,744,
Visits: 30,023
|
|
djordan 4543 (4/5/2011) why do you think the log shipping needs same versions of sql?
Because restore WITH STANDBY does not work in an upgrade scenario (primary lower version than secondary). It'll throw an error when you try to restore. Restore with NORECOVERY does, but that does not allow for reading the secondary server
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
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 5:40 PM
Points: 199,
Visits: 469
|
|
For our reporting database, we use log shipping with the standby option and only restore logs at night. It works real well.
|
|
|
|