Mirroring and Replication

I'm using replication and want to mirror my publisher to get high availability. As I understand the documentation the principal and the mirror must both use the same distributor instance. So if the distributor fails the replication fails. This seem like a big weakness. Maybe I'm missing some thing. Is there a way to set it up so that replication continues if a distributor fails -- some mechanism that will switch in a "back-up" distributor? I'm looking for a configuration that will continue to run in the event of any single failure. This means that both the publisher and the distributor must be covered by mechanisms that keeps them going in the event of a failure. Mirroring covers the failure of the publisher but I don't see a mechanism that will conver the failure of the distributor.

My application is developed in .net / c#. Data is accessed through .net sql server data provider etc.

The only solution right now is clustering, there's way too hard-coded server names at the publisher/distributor that makes it difficult to get mirroring to work. We're looking at developing other solutions, but they won't be available until after the next SQL Server release. But for now, clustering is your answer.

mirror as a publisher

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.

mirror as a publisher

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
eXavierHello 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.|||Hello Peter,
Thanks for your response.
eXavier
""Peter Yang[MSFT]"" wrote:
> 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.
>|||Hello eXavier,
My pleasure. Please feel free to let's know if you have any further
concerns. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
=====================================================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Minimum AD Rights for LAN Based RS

I understand that one must have certain rights in their role as publisher in
reporting services.
Does anyone know the minimum rights needed to allow a developer to publish
reports? Must they have domain admin rights.
Win 2000 Server running SQL server 2000 and RS on a domain.
Thank you in advance.
P.S. I was hoping to not have to give full Administrator rights to publish
reports.
RichExcept for the fact that members of the local administrators group (note
that I say local) has admin rights to RS, there is no correlation between
the rights / groups someone is in as a member of the domain. Because the
domain adminstrator group is usually a member of the local administrators
group this looks the same. Note that you can definitely give rights to any
domain group you want or to individual users. RS operates based on the role
that the user or group has been given rights to. What I do is create a local
group and then to that group I add the domain groups and users that I want
to have rights. I do this just because it is such a pain to create and
manage a domain group but it can work either way. Here are the roles that
you can assign to a user/group:
Browser May view folders, reports and subscribe to
reports.
Content Manager May manage content in the Report Server. This
includes folders, reports and resources.
My Reports May publish reports and linked reports; manage
folders, reports and resources in a users My Reports folder.
Publisher May publish reports and linked reports to the
Report Server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rich" <rwatson@.brick.net> wrote in message
news:uR60h1MfFHA.3912@.tk2msftngp13.phx.gbl...
>I understand that one must have certain rights in their role as publisher
>in reporting services.
> Does anyone know the minimum rights needed to allow a developer to publish
> reports? Must they have domain admin rights.
> Win 2000 Server running SQL server 2000 and RS on a domain.
> Thank you in advance.
> P.S. I was hoping to not have to give full Administrator rights to publish
> reports.
> Rich
>sql

Million records table

Hi everybody,
I set up a merge replication on Sql2K with one publisher/distributor
and 6 anonymous subscribers that run msde.
The db is growing bigger and bigger and i can't understand why.
I noticed that some of the MS_xxxxx tables are very large: in
particular one is 16.7 millions and another over 770K. Is there a way
to reduce/shrink these tables?
Thanks
Lorenzo
How many rows are being modified (inserted/updated/deleted) in the replicated
articles? I would expect this to be a similar order of magnitude to the
msmerge-contents, msmerge_tombstone tables. These tables will be
automatically cleared down during synchronization as part of the meta data
cleanup naturally run in merge by sp_mergemetadataretentioncleanup so
normally you don't need to do anything - the rows will be removed as they
reach the retention period defined in the publication.
HTH,
Paul Ibison
|||On 17 Mag, 17:32, Paul Ibison <Paul.Ibi...@.Pygmalion.Com> wrote:
> How many rows are being modified (inserted/updated/deleted) in the replicated
> articles? I would expect this to be a similar order of magnitude to the
> msmerge-contents, msmerge_tombstone tables. These tables will be
> automatically cleared down during synchronization as part of the meta data
> cleanup naturally run in merge by sp_mergemetadataretentioncleanup so
> normally you don't need to do anything - the rows will be removed as they
> reach the retention period defined in the publication.
> HTH,
> Paul Ibison
Hi Paul,
i don't know exactly haw many rows are being modified, but i can tell
you that the largest replicated table counts less than 130000 records
and i'm sure only a small part of these are changed/added/deleted
the msmerge_tombstone now counts almost 7 millions rows
i'm having some timeout troubles when i synchronize and i often get
the "can't enumerate changes" error
now i'm checking all my tables and indexes to see if some are missing
(the publication is partitioned with dynamic filtering)
thanks a lot for your help
lorenzo
|||Paul Ibison:
> I'd do a join between the msmerge_tombstone table and sysmergearticles. Make
> it a group by on article name and count the records per article then compare
> this to the rowcounts. It may be that there are other articles/publications
> contributing that you haven't accounted for, but even if not, this should
> clarify the situation a bit.
> HTH,
> Paul Ibison
that was a great idea, Paul
i found that there are over 5 million rows relating to a view that
returns 4800!
now i know what to investigate ;-)

Migration to new cluster enviroment

My production system is on stand alone Server and it is a publisher on the
replication system. I need to Migrate to a new hardware with fail over
cluster and upgrade to SQL 2005 .
I need to do that with out impacting replication. What is my options? Can I
do that Or not
If this was to stand alone new hardware I will have no issue.
Thanks for your help
You can't do it without any impact to replication, but you should be able to
with minimal impact.
Build out your new system and test thoroughly. Once you are confident that
the new system performs adequately, then drop your publication on the
production database and copy it (several options here for you) to the new
system.
You will have to redirect your clients to the new host name and reestablish
replication publication.
This should be doable during a reasonable off hours maintenance window.
Sincerely,
Anthony Thomas

<msnews.microsoft.com> wrote in message
news:ek7ECL6THHA.1552@.TK2MSFTNGP05.phx.gbl...
> My production system is on stand alone Server and it is a publisher on the
> replication system. I need to Migrate to a new hardware with fail over
> cluster and upgrade to SQL 2005 .
> I need to do that with out impacting replication. What is my options? Can
I
> do that Or not
> If this was to stand alone new hardware I will have no issue.
> Thanks for your help
>