Hello,
Is it possible to setup replication on mirrored database? Using the naming
‘principal’ and ‘mirror’ for databases involved in mirroring and ‘publisher’
and ‘subscriber’ for replication, what I exactly need is to configure mirror
database as a publisher.
My motivation is as follows:
Currently, I have 2 applications (X and Y), each using its own database (Xdb
and Ydb). Both applications run in the same geographical location (Loc1),
both databases run in the same instance of SQL Server. Some tables are
replicated from Xdb to Ydb.
I need to move Y application to a different geographical location (Loc2) and
in the same time, I want to define some disaster recovery scenario in this
way:
Both applications will be installed in both locations. Y application is
sleeping in Loc1 and X is sleeping in Loc2. Xdb is mirrored from Loc1 to Loc2
and Ydb is mirrored from Loc2 to Loc1. As some data have to be replicated
from Xdb to Ydb I want to save the line between Loc1 and Loc2 and want to
have the replication locally on Loc2 (from mirror of Xdb into Ydb).
Thanks
eXavier
Hello eXavier,
Regarding your question, based on my research, it's not supported to
configure "mirrored" database as the publisher since it's a standby server.
You could only configure publisher in principle database. You may want to
refer to the following article for more details:
Replication and Database Mirroring
http://msdn2.microsoft.com/en-us/library/ms151799.aspx
You could configure snapshot of mirrored database but it's read only and
could not be configured as publisher as well.
Using Database Snapshots with Database Mirroring
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/0bf1be90-7ce4-484c-aaa7-f8a7
82f57c5f.htm
Please rest assure that your feedback on this feature is routed to the
proper channel. Also, I encourage you submit via the link below and our
product team would like to hear your voice:
http://lab.msdn.microsoft.com/productfeedback/default.aspx
If you have any further questions or comments, please feel free to let's
know.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label involved. Show all posts
Showing posts with label involved. Show all posts
Monday, March 26, 2012
Monday, February 20, 2012
Migrating to SQL 2005
I am interested in migrating from SQL 2000 to SQL 2005.
Are there some recommended pointers, sites, or steps involved in the process
that you could provide?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200603/1Robert,
www.microsoft.com/sql is always a good place to look for info such as this.
Here is a link that should get you going.
http://www.microsoft.com/sql/soluti...de/default.mspx
Andrew J. Kelly SQL MVP
"Robert R via droptable.com" <u3288@.uwe> wrote in message
news:5d589ba26f68f@.uwe...
>I am interested in migrating from SQL 2000 to SQL 2005.
> Are there some recommended pointers, sites, or steps involved in the
> process
> that you could provide?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200603/1
Are there some recommended pointers, sites, or steps involved in the process
that you could provide?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200603/1Robert,
www.microsoft.com/sql is always a good place to look for info such as this.
Here is a link that should get you going.
http://www.microsoft.com/sql/soluti...de/default.mspx
Andrew J. Kelly SQL MVP
"Robert R via droptable.com" <u3288@.uwe> wrote in message
news:5d589ba26f68f@.uwe...
>I am interested in migrating from SQL 2000 to SQL 2005.
> Are there some recommended pointers, sites, or steps involved in the
> process
> that you could provide?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200603/1
Labels:
database,
interested,
involved,
microsoft,
migrating,
mysql,
oracle,
pointers,
processthat,
recommended,
server,
sql,
steps
Migrating to SQL 2005
I am interested in migrating from SQL 2000 to SQL 2005.
Are there some recommended pointers, sites, or steps involved in the process
that you could provide?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200603/1
Robert,
www.microsoft.com/sql is always a good place to look for info such as this.
Here is a link that should get you going.
http://www.microsoft.com/sql/solutio...e/default.mspx
Andrew J. Kelly SQL MVP
"Robert R via droptable.com" <u3288@.uwe> wrote in message
news:5d589ba26f68f@.uwe...
>I am interested in migrating from SQL 2000 to SQL 2005.
> Are there some recommended pointers, sites, or steps involved in the
> process
> that you could provide?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200603/1
Are there some recommended pointers, sites, or steps involved in the process
that you could provide?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200603/1
Robert,
www.microsoft.com/sql is always a good place to look for info such as this.
Here is a link that should get you going.
http://www.microsoft.com/sql/solutio...e/default.mspx
Andrew J. Kelly SQL MVP
"Robert R via droptable.com" <u3288@.uwe> wrote in message
news:5d589ba26f68f@.uwe...
>I am interested in migrating from SQL 2000 to SQL 2005.
> Are there some recommended pointers, sites, or steps involved in the
> process
> that you could provide?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200603/1
Labels:
database,
interested,
involved,
microsoft,
migrating,
mysql,
oracle,
pointers,
processthat,
recommended,
server,
sql,
steps
Migrating to SQL 2005
I am interested in migrating from SQL 2000 to SQL 2005.
Are there some recommended pointers, sites, or steps involved in the process
that you could provide?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200603/1Robert,
www.microsoft.com/sql is always a good place to look for info such as this.
Here is a link that should get you going.
http://www.microsoft.com/sql/solutions/upgrade/default.mspx
--
Andrew J. Kelly SQL MVP
"Robert R via SQLMonster.com" <u3288@.uwe> wrote in message
news:5d589ba26f68f@.uwe...
>I am interested in migrating from SQL 2000 to SQL 2005.
> Are there some recommended pointers, sites, or steps involved in the
> process
> that you could provide?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200603/1
Are there some recommended pointers, sites, or steps involved in the process
that you could provide?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200603/1Robert,
www.microsoft.com/sql is always a good place to look for info such as this.
Here is a link that should get you going.
http://www.microsoft.com/sql/solutions/upgrade/default.mspx
--
Andrew J. Kelly SQL MVP
"Robert R via SQLMonster.com" <u3288@.uwe> wrote in message
news:5d589ba26f68f@.uwe...
>I am interested in migrating from SQL 2000 to SQL 2005.
> Are there some recommended pointers, sites, or steps involved in the
> process
> that you could provide?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200603/1
Migrating Systems
I am to be involved in moving 3 clusters soon from one data center in the
Northeast to Texas. The main requirement is to have the shortest cutover
period possible via some kind of replicated technologies.
System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
issue with that one. Stage the new server, restore a backup and put it in
log shipping or use a product like Double-Take to keep things in sync.
System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4. This
instance has over 200 databases on it. Don't think log shipping is an
option here. It's not indexed well enough for replication and because the
environments aren't like I don't think Double-Take will work. Ideas?
System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The SQL
7 cluster is currently on Windows NT. Same scenario as System 2.
Ideas?
I think the fastest way to do this is to migrate all dependencies and
accounts, and then detach and reattach the databases on the new server. Copy
the database don't move them.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Cathy Soloway" <CathySoloway@.discussions.microsoft.com> wrote in message
news:8C4A9E42-D424-4DF9-A5ED-1C3821F2E033@.microsoft.com...
>I am to be involved in moving 3 clusters soon from one data center in the
> Northeast to Texas. The main requirement is to have the shortest cutover
> period possible via some kind of replicated technologies.
> System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
> issue with that one. Stage the new server, restore a backup and put it in
> log shipping or use a product like Double-Take to keep things in sync.
> System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4.
> This
> instance has over 200 databases on it. Don't think log shipping is an
> option here. It's not indexed well enough for replication and because the
> environments aren't like I don't think Double-Take will work. Ideas?
> System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The
> SQL
> 7 cluster is currently on Windows NT. Same scenario as System 2.
> Ideas?
>
Northeast to Texas. The main requirement is to have the shortest cutover
period possible via some kind of replicated technologies.
System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
issue with that one. Stage the new server, restore a backup and put it in
log shipping or use a product like Double-Take to keep things in sync.
System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4. This
instance has over 200 databases on it. Don't think log shipping is an
option here. It's not indexed well enough for replication and because the
environments aren't like I don't think Double-Take will work. Ideas?
System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The SQL
7 cluster is currently on Windows NT. Same scenario as System 2.
Ideas?
I think the fastest way to do this is to migrate all dependencies and
accounts, and then detach and reattach the databases on the new server. Copy
the database don't move them.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Cathy Soloway" <CathySoloway@.discussions.microsoft.com> wrote in message
news:8C4A9E42-D424-4DF9-A5ED-1C3821F2E033@.microsoft.com...
>I am to be involved in moving 3 clusters soon from one data center in the
> Northeast to Texas. The main requirement is to have the shortest cutover
> period possible via some kind of replicated technologies.
> System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
> issue with that one. Stage the new server, restore a backup and put it in
> log shipping or use a product like Double-Take to keep things in sync.
> System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4.
> This
> instance has over 200 databases on it. Don't think log shipping is an
> option here. It's not indexed well enough for replication and because the
> environments aren't like I don't think Double-Take will work. Ideas?
> System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The
> SQL
> 7 cluster is currently on Windows NT. Same scenario as System 2.
> Ideas?
>
Subscribe to:
Posts (Atom)