April 4, 2011 at 10:49 pm
Can you have this mirroring scenario.
Principal sql server 2008 standard engine
Mirror sql server 2008 R2 enterprise engine
Thanks!
April 4, 2011 at 11:50 pm
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, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 5, 2011 at 12:04 am
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!
April 5, 2011 at 1:22 am
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, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 5, 2011 at 1:26 am
why do you think the log shipping needs same versions of sql? Is it for the same reason?
April 5, 2011 at 1:47 am
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, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 5, 2011 at 5:43 am
For our reporting database, we use log shipping with the standby option and only restore logs at night. It works real well.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply