Mirror goes down... Affect client transactions?

If the mirror server goes down for any reason, then what happens to client transactions against the principle?

Will any client transactions fail?

Thanks in advance

Quick answer - no, they should not be affected.

However, if you have witness set-up and the principal cannot connect to both the witness and the mirror then it will stop serving the database and the transactions will fail.

Take a look at this article:

http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx#ETPAE

Thanks,

Kaloian.

|||

Thank you. That answers my question.

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
>