Database mirroring?

Is database mirroring being delivered as a part of SP1 that is coming out
soon?
Can I setup mirroring with Developer Edition?
OlavAFAIK yes and yes .
MC
"Olav" <x@.y.com> wrote in message
news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
> Is database mirroring being delivered as a part of SP1 that is coming out
> soon?
> Can I setup mirroring with Developer Edition?
> Olav
>|||Yes & Yes
Andrew J. Kelly SQL MVP
"Olav" <x@.y.com> wrote in message
news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
> Is database mirroring being delivered as a part of SP1 that is coming out
> soon?
> Can I setup mirroring with Developer Edition?
> Olav
>|||Yes, but keep in mind it wasn't ready yet when they released 2005, so you'll
be a beta tester without the word "beta". Expect bugs, like everything else
with 2005 so far.
"Olav" <x@.y.com> wrote in message
news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
> Is database mirroring being delivered as a part of SP1 that is coming out
> soon?
> Can I setup mirroring with Developer Edition?
> Olav
>|||That is not a correct statement. Mirroring was fully complete at RTM. MS
simply decided that not enough people fully tested the feature during the
beta period so they wanted to extend it's testing time. In reality it now
has more beta testing than other features that were in RTM to begin with.
Andrew J. Kelly SQL MVP
"AFN" <replywithingroup@.notreal.com> wrote in message
news:g4Q_f.848$543.683@.tornado.socal.rr.com...
> Yes, but keep in mind it wasn't ready yet when they released 2005, so
> you'll be a beta tester without the word "beta". Expect bugs, like
> everything else with 2005 so far.
>
> "Olav" <x@.y.com> wrote in message
> news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
>|||No, that is NOT accurate.
Database Mirroring was feature complete at RTM and had undergone VERY
rigorous testing over a multi-year time frame. The decision was made to not
expose it in the RTM, because not enough customers had tested it against
their applications to ensure that additional problems wouldn't occur due to
all of the different permutations that are possible. It could be enabled
and used when RTM was released and several hundred customers have continued
to beta test it over the last 6 months. It is being enabled in SP1, because
they now have sufficient customer facing testing completed on it.
This is one of the features that has had more testing time than anything
else in the product and is EXTREMELY stable.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"AFN" <replywithingroup@.notreal.com> wrote in message
news:g4Q_f.848$543.683@.tornado.socal.rr.com...
> Yes, but keep in mind it wasn't ready yet when they released 2005, so
> you'll be a beta tester without the word "beta". Expect bugs, like
> everything else with 2005 so far.
>
> "Olav" <x@.y.com> wrote in message
> news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
>

Database mirroring?

Is database mirroring being delivered as a part of SP1 that is coming out
soon?
Can I setup mirroring with Developer Edition?
OlavAFAIK yes and yes :).
MC
"Olav" <x@.y.com> wrote in message
news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
> Is database mirroring being delivered as a part of SP1 that is coming out
> soon?
> Can I setup mirroring with Developer Edition?
> Olav
>|||Yes & Yes
--
Andrew J. Kelly SQL MVP
"Olav" <x@.y.com> wrote in message
news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
> Is database mirroring being delivered as a part of SP1 that is coming out
> soon?
> Can I setup mirroring with Developer Edition?
> Olav
>|||Yes, but keep in mind it wasn't ready yet when they released 2005, so you'll
be a beta tester without the word "beta". Expect bugs, like everything else
with 2005 so far.
"Olav" <x@.y.com> wrote in message
news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
> Is database mirroring being delivered as a part of SP1 that is coming out
> soon?
> Can I setup mirroring with Developer Edition?
> Olav
>|||That is not a correct statement. Mirroring was fully complete at RTM. MS
simply decided that not enough people fully tested the feature during the
beta period so they wanted to extend it's testing time. In reality it now
has more beta testing than other features that were in RTM to begin with.
--
Andrew J. Kelly SQL MVP
"AFN" <replywithingroup@.notreal.com> wrote in message
news:g4Q_f.848$543.683@.tornado.socal.rr.com...
> Yes, but keep in mind it wasn't ready yet when they released 2005, so
> you'll be a beta tester without the word "beta". Expect bugs, like
> everything else with 2005 so far.
>
> "Olav" <x@.y.com> wrote in message
> news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
>> Is database mirroring being delivered as a part of SP1 that is coming out
>> soon?
>> Can I setup mirroring with Developer Edition?
>> Olav
>|||No, that is NOT accurate.
Database Mirroring was feature complete at RTM and had undergone VERY
rigorous testing over a multi-year time frame. The decision was made to not
expose it in the RTM, because not enough customers had tested it against
their applications to ensure that additional problems wouldn't occur due to
all of the different permutations that are possible. It could be enabled
and used when RTM was released and several hundred customers have continued
to beta test it over the last 6 months. It is being enabled in SP1, because
they now have sufficient customer facing testing completed on it.
This is one of the features that has had more testing time than anything
else in the product and is EXTREMELY stable.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"AFN" <replywithingroup@.notreal.com> wrote in message
news:g4Q_f.848$543.683@.tornado.socal.rr.com...
> Yes, but keep in mind it wasn't ready yet when they released 2005, so
> you'll be a beta tester without the word "beta". Expect bugs, like
> everything else with 2005 so far.
>
> "Olav" <x@.y.com> wrote in message
> news:%23mwbVlTXGHA.3448@.TK2MSFTNGP03.phx.gbl...
>> Is database mirroring being delivered as a part of SP1 that is coming out
>> soon?
>> Can I setup mirroring with Developer Edition?
>> Olav
>

Database Mirroring. Asp application (IIS 6.0) does''t forward connections to mirror server

Hi!

I have setup a database mirroring session without witness - ServerA is the principal, ServerB is the mirror,. Each SQL Server instance is hosted on its own machine on sql2005 EE SP2. The mirroring is working correctly. If I submit to server ServerA command:

ALTER DATABASE MYDBNAME SET PARTNER FAILOVER

, ServerB becomes the principal, it means that mirroring works correctly.

My issue is with the SQL Native Client and a front-end ASP application (actually IIS 6.0 site) that needs to make use of this database. I have setup my front-end application to use SQL Native Client and specified the failover server in connection string. Here is the connection string that I am using :

PROVIDER=SQLNCLI.1;Server=ServerA,1433;Failover Partner=ServerB,1433;Database=MYDBNAME;Network=dbmssocn;Integrated Security=SSPI;

Everything works perfectly on my front-end application when ServerA is the principal. If I execute on server ServerA command:

ALTER DATABASE MYDBNAME SET PARTNER FAILOVER

, ServerB becomes the principal, and the failover occurs correctly on the database side. The problem is that my front-end application is not able to query the database on ServerB. The error appears:

Microsoft SQL Native Client error '80004005'

Cannot open database "MYDBNAME" requested by the login. The login failed.

This behavior my appication till I unload IIS 6.0 pool application. After that my front-end application becomes work correctly with ServerB.

When I swap server, I execute on server ServerB command:

ALTER DATABASE MYDBNAME SET PARTNER FAILOVER,

my IIS 6.0 application automaticly turn back to ServerA without any action on my side.

I am using SQL Native Client last version http://download.microsoft.com/download/2/7/c/27c60d49-6dbe-423e-9a9e-1c873f269484/sqlncli.msi (issued in February 2007). Has anyone experienced this issue? I'm thinking that it's a problem in the SQL Native client

Are you using connection pooling>?|||Yes, I think so. I use SQL Native Client settings by default. As I know SQL Native Client uses connection pooling by default.|||

We're having the same problem with this, but we're testing automatic failover with a witness. We're also using classic ASP, native client (Feb2007) and SQL2005 Std with sp2. For some reason, automatic failover doesn't allow the web server connections to failover to the partner server - although we confirmed that the databases DO failover and we are automatically synchronizing sql logins. Manual failover seems to work without problems (again this is with a witness).

Does anyone have any ideas on why this happens? We also tried disabling named pipes on the web server native client settings (as some article suggested), but without luck.

|||

There are different keywords for failover partner. As far as I know there are three keywords that all work in different instances and fail in others. In your situation I am not sure which you would have to use in the connection string.

FailoverPartner=ServerB

Failover_Partner=ServerB

Failover Partner=ServerB

I would just try them and do a manual failover of the database and see which one works and which one fails. I have searched all over trying to find out for sure which ones work where but I can't find a list anywhere.

|||

This also might help. Not sure how accurate the statement is. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=421936&SiteID=1

|||

As already stated, connection pooling will be your issue.

turn it off and try again...

The other thought is, once you have failed over go to lunch and see if your app works afterwards (as if it was connection pooling the connection should be closed by then and hence will start to work)

|||

Been banging my head against this for a few days, have applied Hotfix for Microsoft.Net Framework 2.0 (KB916002) see http://support.microsoft.com/kb/912151 this is meant to fix default timeout in dB driver - didn't help. Just tried your suggestion about connection pooling, added 'Pooling=False;' to connect string - didn't help.

Is it sensible to turn off connection pooling? my understanding was this provides a big boost to site performance so would MS make us sacrifice performance for resilience? Has anyone got this failover working?

sql

Database Mirroring. Asp application (IIS 6.0) does't forward connections to mirror server

Hi!

I have setup a database mirroring session without witness - ServerA is the principal, ServerB is the mirror,. Each SQL Server instance is hosted on its own machine on sql2005 EE SP2. The mirroring is working correctly. If I submit to server ServerA command:

ALTER DATABASE MYDBNAME SET PARTNER FAILOVER

, ServerB becomes the principal, it means that mirroring works correctly.

My issue is with the SQL Native Client and a front-end ASP application (actually IIS 6.0 site) that needs to make use of this database. I have setup my front-end application to use SQL Native Client and specified the failover server in connection string. Here is the connection string that I am using :

PROVIDER=SQLNCLI.1;Server=ServerA,1433;Failover Partner=ServerB,1433;Database=MYDBNAME;Network=dbmssocn;Integrated Security=SSPI;

Everything works perfectly on my front-end application when ServerA is the principal. If I execute on server ServerA command:

ALTER DATABASE MYDBNAME SET PARTNER FAILOVER

, ServerB becomes the principal, and the failover occurs correctly on the database side. The problem is that my front-end application is not able to query the database on ServerB. The error appears:

Microsoft SQL Native Client error '80004005'

Cannot open database "MYDBNAME" requested by the login. The login failed.

This behavior my appication till I unload IIS 6.0 pool application. After that my front-end application becomes work correctly with ServerB.

When I swap server, I execute on server ServerB command:

ALTER DATABASE MYDBNAME SET PARTNER FAILOVER,

my IIS 6.0 application automaticly turn back to ServerA without any action on my side.

I am using SQL Native Client last version http://download.microsoft.com/download/2/7/c/27c60d49-6dbe-423e-9a9e-1c873f269484/sqlncli.msi (issued in February 2007). Has anyone experienced this issue? I'm thinking that it's a problem in the SQL Native client

Are you using connection pooling>?|||Yes, I think so. I use SQL Native Client settings by default. As I know SQL Native Client uses connection pooling by default.|||

We're having the same problem with this, but we're testing automatic failover with a witness. We're also using classic ASP, native client (Feb2007) and SQL2005 Std with sp2. For some reason, automatic failover doesn't allow the web server connections to failover to the partner server - although we confirmed that the databases DO failover and we are automatically synchronizing sql logins. Manual failover seems to work without problems (again this is with a witness).

Does anyone have any ideas on why this happens? We also tried disabling named pipes on the web server native client settings (as some article suggested), but without luck.

|||

There are different keywords for failover partner. As far as I know there are three keywords that all work in different instances and fail in others. In your situation I am not sure which you would have to use in the connection string.

FailoverPartner=ServerB

Failover_Partner=ServerB

Failover Partner=ServerB

I would just try them and do a manual failover of the database and see which one works and which one fails. I have searched all over trying to find out for sure which ones work where but I can't find a list anywhere.

|||

This also might help. Not sure how accurate the statement is. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=421936&SiteID=1

|||

As already stated, connection pooling will be your issue.

turn it off and try again...

The other thought is, once you have failed over go to lunch and see if your app works afterwards (as if it was connection pooling the connection should be closed by then and hence will start to work)

Database Mirroring. Asp application (IIS 6.0) does't forward connections to mirror server

Hi!

I have setup a database mirroring session without witness - ServerA is the principal, ServerB is the mirror,. Each SQL Server instance is hosted on its own machine on sql2005 EE SP2. The mirroring is working correctly. If I submit to server ServerA command:

ALTERDATABASE MYDBNAME SETPARTNERFAILOVER

, ServerB becomes the principal, it means that mirroring works correctly.

My issue is with the SQL Native Client and a front-end ASP application (actually IIS 6.0 site) that needs to make use of this database. I have setup my front-end application to use SQL Native Client and specified the failover server in connection string. Here is the connection string that I am using :

PROVIDER=SQLNCLI.1;Server=ServerA,1433;Failover Partner=ServerB,1433;Database=MYDBNAME;Network=dbmssocn;Integrated Security=SSPI;

Everything works perfectly on my front-end application when ServerA is the principal. If I execute on server ServerA command:

ALTERDATABASE MYDBNAME SETPARTNERFAILOVER

, ServerB becomes the principal, and the failover occurs correctly on the database side. The problem is that my front-end application is not able to query the database on ServerB. The error appears:

Microsoft SQL Native Clienterror '80004005'

Cannot open database "MYDBNAME" requested by the login. The login failed.

This behavior my appication till I unload IIS 6.0 pool application. After that my front-end application becomes work correctly with ServerB.

When I swap server, I execute on server ServerB command:

ALTERDATABASE MYDBNAME SETPARTNERFAILOVER,

my IIS 6.0 application automaticly turn back to ServerA without any action on my side.

I am using SQL Native Client last version http://download.microsoft.com/download/2/7/c/27c60d49-6dbe-423e-9a9e-1c873f269484/sqlncli.msi (issued in February 2007). Has anyone experienced this issue? I'm thinking that it's a problem in the SQL Native client

Are you using connection pooling>?|||Yes, I think so. I use SQL Native Client settings by default. As I know SQL Native Client uses connection pooling by default.|||

We're having the same problem with this, but we're testing automatic failover with a witness. We're also using classic ASP, native client (Feb2007) and SQL2005 Std with sp2. For some reason, automatic failover doesn't allow the web server connections to failover to the partner server - although we confirmed that the databases DO failover and we are automatically synchronizing sql logins. Manual failover seems to work without problems (again this is with a witness).

Does anyone have any ideas on why this happens? We also tried disabling named pipes on the web server native client settings (as some article suggested), but without luck.

|||

There are different keywords for failover partner. As far as I know there are three keywords that all work in different instances and fail in others. In your situation I am not sure which you would have to use in the connection string.

FailoverPartner=ServerB

Failover_Partner=ServerB

Failover Partner=ServerB

I would just try them and do a manual failover of the database and see which one works and which one fails. I have searched all over trying to find out for sure which ones work where but I can't find a list anywhere.

|||

This also might help. Not sure how accurate the statement is. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=421936&SiteID=1

|||

As already stated, connection pooling will be your issue.

turn it off and try again...

The other thought is, once you have failed over go to lunch and see if your app works afterwards (as if it was connection pooling the connection should be closed by then and hence will start to work)

|||

Been banging my head against this for a few days, have applied Hotfix for Microsoft.Net Framework 2.0 (KB916002) see http://support.microsoft.com/kb/912151 this is meant to fix default timeout in dB driver - didn't help. Just tried your suggestion about connection pooling, added 'Pooling=False;' to connect string - didn't help.

Is it sensible to turn off connection pooling? my understanding was this provides a big boost to site performance so would MS make us sacrifice performance for resilience? Has anyone got this failover working?

Database Mirroring with SQLEXPRESS as witness

I am trying to setup SQLServer 2005 to use Database Mirroring.
The principal and mirror servers are running on Windows2003 64bit edition.
The witness server is running Windows2003 32bit.
I have configured endpoints for both the principal and mirror but when I try
to setup SQLEXPRESS as the witness using...
create endpoint MirroringEndPoint
state=started
as tcp (listener_port=10111)
for database_mirroring (role=all)
I get..
Msg 7878, Level 16, State 4, Line 4
This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this edition
of SQL Server.
SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it
complains about mirroring not being supported in a production environment
which is why I have upgraded to SP2.
Best regards
MarkSorry, I misread. Specify role=witness, which is the only role supported for
Express Edition.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>I am trying to setup SQLServer 2005 to use Database Mirroring.
> The principal and mirror servers are running on Windows2003 64bit edition.
The witness server is
> running Windows2003 32bit.
> I have configured endpoints for both the principal and mirror but when I t
ry to setup SQLEXPRESS
> as the witness using...
> create endpoint MirroringEndPoint
> state=started
> as tcp (listener_port=10111)
> for database_mirroring (role=all)
> I get..
> Msg 7878, Level 16, State 4, Line 4
> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this editio
n of SQL Server.
> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it
complains about
> mirroring not being supported in a production environment which is why I h
ave upgraded to SP2.
> --
> Best regards
> Mark
>|||You need standard or enterprise edition for mirroring. By the name of your i
nstance to judge, it is
express edition.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>I am trying to setup SQLServer 2005 to use Database Mirroring.
> The principal and mirror servers are running on Windows2003 64bit edition.
The witness server is
> running Windows2003 32bit.
> I have configured endpoints for both the principal and mirror but when I t
ry to setup SQLEXPRESS
> as the witness using...
> create endpoint MirroringEndPoint
> state=started
> as tcp (listener_port=10111)
> for database_mirroring (role=all)
> I get..
> Msg 7878, Level 16, State 4, Line 4
> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this editio
n of SQL Server.
> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it
complains about
> mirroring not being supported in a production environment which is why I h
ave upgraded to SP2.
> --
> Best regards
> Mark
>|||Thanks, that seems to have sorted the problem out but I have another issue
with security now - still I shall leave that to another thread
Best regards
Mark
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OzTxF%23VmHHA.4768@.TK2MSFTNGP05.phx.gbl...
> Sorry, I misread. Specify role=witness, which is the only role supported
> for Express Edition.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
> news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>

Database Mirroring with SQLEXPRESS as witness

I am trying to setup SQLServer 2005 to use Database Mirroring.
The principal and mirror servers are running on Windows2003 64bit edition.
The witness server is running Windows2003 32bit.
I have configured endpoints for both the principal and mirror but when I try
to setup SQLEXPRESS as the witness using...
create endpoint MirroringEndPoint
state=started
as tcp (listener_port=10111)
for database_mirroring (role=all)
I get..
Msg 7878, Level 16, State 4, Line 4
This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this edition
of SQL Server.
SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it
complains about mirroring not being supported in a production environment
which is why I have upgraded to SP2.
--
Best regards
MarkSorry, I misread. Specify role=witness, which is the only role supported for Express Edition.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>I am trying to setup SQLServer 2005 to use Database Mirroring.
> The principal and mirror servers are running on Windows2003 64bit edition. The witness server is
> running Windows2003 32bit.
> I have configured endpoints for both the principal and mirror but when I try to setup SQLEXPRESS
> as the witness using...
> create endpoint MirroringEndPoint
> state=started
> as tcp (listener_port=10111)
> for database_mirroring (role=all)
> I get..
> Msg 7878, Level 16, State 4, Line 4
> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this edition of SQL Server.
> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it complains about
> mirroring not being supported in a production environment which is why I have upgraded to SP2.
> --
> Best regards
> Mark
>|||You need standard or enterprise edition for mirroring. By the name of your instance to judge, it is
express edition.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>I am trying to setup SQLServer 2005 to use Database Mirroring.
> The principal and mirror servers are running on Windows2003 64bit edition. The witness server is
> running Windows2003 32bit.
> I have configured endpoints for both the principal and mirror but when I try to setup SQLEXPRESS
> as the witness using...
> create endpoint MirroringEndPoint
> state=started
> as tcp (listener_port=10111)
> for database_mirroring (role=all)
> I get..
> Msg 7878, Level 16, State 4, Line 4
> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this edition of SQL Server.
> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then it complains about
> mirroring not being supported in a production environment which is why I have upgraded to SP2.
> --
> Best regards
> Mark
>|||Thanks, that seems to have sorted the problem out but I have another issue
with security now - still I shall leave that to another thread
--
Best regards
Mark
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OzTxF%23VmHHA.4768@.TK2MSFTNGP05.phx.gbl...
> Sorry, I misread. Specify role=witness, which is the only role supported
> for Express Edition.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mark Baldwin" <sWozzi3@.community.nospam> wrote in message
> news:uBslxtVmHHA.3736@.TK2MSFTNGP03.phx.gbl...
>>I am trying to setup SQLServer 2005 to use Database Mirroring.
>> The principal and mirror servers are running on Windows2003 64bit
>> edition. The witness server is running Windows2003 32bit.
>> I have configured endpoints for both the principal and mirror but when I
>> try to setup SQLEXPRESS as the witness using...
>> create endpoint MirroringEndPoint
>> state=started
>> as tcp (listener_port=10111)
>> for database_mirroring (role=all)
>> I get..
>> Msg 7878, Level 16, State 4, Line 4
>> This "ROLE=PARTNER/ALL ENDPOINT" statement is not supported on this
>> edition of SQL Server.
>> SQLEXPRESS is SP2. I have tried the initial SQLEXPRESS release but then
>> it complains about mirroring not being supported in a production
>> environment which is why I have upgraded to SP2.
>> --
>> Best regards
>> Mark
>

Database mirroring technical matters

Hello,
I would like to setup SQL 2005 database mirroring. Prior to this, I would
like to know if there are some technical prerequisites? For example, to do a
transactional replication, all tables need to have a primary key... Is there
the same kind of troubles with database mirroring?
How are handled the identity columns with mirroring when we make a recovery
after failure?
How are handled the triggers? Are they desactivated on the backup database?
Thanks a lot,
Eric.Mirroring doesn't work in the same way as replication. It is based on replic
ating the log records,
not re-generating the SQL statements from the log, like transaction replicat
ion does). Since *the
effect* of every modification is mirrored to the mirror database, it will be
in the very same shape
as the principal database. (Well, if you go async, you could lose some commi
tted transactions, but
that is a trade-off you have to think about.)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"itparis" <itparis@.discussions.microsoft.com> wrote in message
news:842CEE8B-29E4-4A38-BA9F-7881406C8E97@.microsoft.com...
> Hello,
> I would like to setup SQL 2005 database mirroring. Prior to this, I would
> like to know if there are some technical prerequisites? For example, to do
a
> transactional replication, all tables need to have a primary key... Is the
re
> the same kind of troubles with database mirroring?
> How are handled the identity columns with mirroring when we make a recover
y
> after failure?
> How are handled the triggers? Are they desactivated on the backup database
?
> Thanks a lot,
> Eric.

Database mirroring technical matters

Hello,
I would like to setup SQL 2005 database mirroring. Prior to this, I would
like to know if there are some technical prerequisites? For example, to do a
transactional replication, all tables need to have a primary key... Is there
the same kind of troubles with database mirroring?
How are handled the identity columns with mirroring when we make a recovery
after failure?
How are handled the triggers? Are they desactivated on the backup database?
Thanks a lot,
Eric.Mirroring doesn't work in the same way as replication. It is based on replicating the log records,
not re-generating the SQL statements from the log, like transaction replication does). Since *the
effect* of every modification is mirrored to the mirror database, it will be in the very same shape
as the principal database. (Well, if you go async, you could lose some committed transactions, but
that is a trade-off you have to think about.)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"itparis" <itparis@.discussions.microsoft.com> wrote in message
news:842CEE8B-29E4-4A38-BA9F-7881406C8E97@.microsoft.com...
> Hello,
> I would like to setup SQL 2005 database mirroring. Prior to this, I would
> like to know if there are some technical prerequisites? For example, to do a
> transactional replication, all tables need to have a primary key... Is there
> the same kind of troubles with database mirroring?
> How are handled the identity columns with mirroring when we make a recovery
> after failure?
> How are handled the triggers? Are they desactivated on the backup database?
> Thanks a lot,
> Eric.

Database mirroring setup without downtime

Does anyone know if you can mirror a database while users are banging away on
it? I can't see how I'd get the log backups in sync on the mirror server,
it's pretty busy with transactions. I've done some small scale testing and it
seems like you can apply a log backup while the data on the primary is being
changed and it still sets up the mirror ok. It's a 24/7 system and we have to
schedule some downtime otherwise.
Thanks in advance.
Hi
How do you know that log backups are ansync?
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:98F90C89-B307-4FB3-85D1-ACA8CA2D2297@.microsoft.com...
> Does anyone know if you can mirror a database while users are banging away
> on
> it? I can't see how I'd get the log backups in sync on the mirror server,
> it's pretty busy with transactions. I've done some small scale testing and
> it
> seems like you can apply a log backup while the data on the primary is
> being
> changed and it still sets up the mirror ok. It's a 24/7 system and we have
> to
> schedule some downtime otherwise.
> Thanks in advance.

Database mirroring setup without downtime

Does anyone know if you can mirror a database while users are banging away o
n
it? I can't see how I'd get the log backups in sync on the mirror server,
it's pretty busy with transactions. I've done some small scale testing and i
t
seems like you can apply a log backup while the data on the primary is being
changed and it still sets up the mirror ok. It's a 24/7 system and we have t
o
schedule some downtime otherwise.
Thanks in advance.Hi
How do you know that log backups are ansync?
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:98F90C89-B307-4FB3-85D1-ACA8CA2D2297@.microsoft.com...
> Does anyone know if you can mirror a database while users are banging away
> on
> it? I can't see how I'd get the log backups in sync on the mirror server,
> it's pretty busy with transactions. I've done some small scale testing and
> it
> seems like you can apply a log backup while the data on the primary is
> being
> changed and it still sets up the mirror ok. It's a 24/7 system and we have
> to
> schedule some downtime otherwise.
> Thanks in advance.

Database mirroring setup without downtime

Does anyone know if you can mirror a database while users are banging away on
it? I can't see how I'd get the log backups in sync on the mirror server,
it's pretty busy with transactions. I've done some small scale testing and it
seems like you can apply a log backup while the data on the primary is being
changed and it still sets up the mirror ok. It's a 24/7 system and we have to
schedule some downtime otherwise.
Thanks in advance.Hi
How do you know that log backups are ansync?
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:98F90C89-B307-4FB3-85D1-ACA8CA2D2297@.microsoft.com...
> Does anyone know if you can mirror a database while users are banging away
> on
> it? I can't see how I'd get the log backups in sync on the mirror server,
> it's pretty busy with transactions. I've done some small scale testing and
> it
> seems like you can apply a log backup while the data on the primary is
> being
> changed and it still sets up the mirror ok. It's a 24/7 system and we have
> to
> schedule some downtime otherwise.
> Thanks in advance.

Database Mirroring Setup Document.

Hi:

I am looking for a Step-by-Step document for setting up and configuring of database mirroring if one is available. I have gone through BOL and found some related documentation but want to see if a step-by-step document is available. If so can any one please direct me to the resource.

Thank you

AK

Please look at the How-to section in the BOL.

http://msdn2.microsoft.com/en-us/library/ms175059.aspx

Database Mirroring in SQL Server 2005

I have been trying to setup a mirror database using the instructions in the
doc and have not had much success. I either get a message that a service is
not running or that the database mirror is busy. Has any had any luck with
this. If so please let me know the exact sequence of steps that I need to
follow.
Thanks
There's an extremely comprehensive article here
http://www.microsoft.com/technet/pro.../dbmirror.mspx
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raji" <Raji@.discussions.microsoft.com> wrote in message
news:174EA9C2-9A9B-4123-A395-95E488A0B14C@.microsoft.com...
>I have been trying to setup a mirror database using the instructions in the
> doc and have not had much success. I either get a message that a service
> is
> not running or that the database mirror is busy. Has any had any luck with
> this. If so please let me know the exact sequence of steps that I need to
> follow.
> Thanks
>

Database Mirroring in SQL Server 2005

I have been trying to setup a mirror database using the instructions in the
doc and have not had much success. I either get a message that a service is
not running or that the database mirror is busy. Has any had any luck with
this. If so please let me know the exact sequence of steps that I need to
follow.
ThanksThere's an extremely comprehensive article here
http://www.microsoft.com/technet/pr...5/dbmirror.mspx
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raji" <Raji@.discussions.microsoft.com> wrote in message
news:174EA9C2-9A9B-4123-A395-95E488A0B14C@.microsoft.com...
>I have been trying to setup a mirror database using the instructions in the
> doc and have not had much success. I either get a message that a service
> is
> not running or that the database mirror is busy. Has any had any luck with
> this. If so please let me know the exact sequence of steps that I need to
> follow.
> Thanks
>

Database Mirroring in SQL Server 2005

I have been trying to setup a mirror database using the instructions in the
doc and have not had much success. I either get a message that a service is
not running or that the database mirror is busy. Has any had any luck with
this. If so please let me know the exact sequence of steps that I need to
follow.
ThanksThere's an extremely comprehensive article here
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raji" <Raji@.discussions.microsoft.com> wrote in message
news:174EA9C2-9A9B-4123-A395-95E488A0B14C@.microsoft.com...
>I have been trying to setup a mirror database using the instructions in the
> doc and have not had much success. I either get a message that a service
> is
> not running or that the database mirror is busy. Has any had any luck with
> this. If so please let me know the exact sequence of steps that I need to
> follow.
> Thanks
>

Database Mirroring : How to find the TCP port being used for mirroring?

Hi,

I am interested in finding the TCP port which has been setup on a principal/witness/mirror server.

I have queried the sys.database_mirroring_endpoints and sys.endpoints system views but nowhere does it specify the TCP port.

I think the only way to find out is to go to one of the mirrored databases and to right click properties-->Mirroring. I think this is ugly way to find out the TCP port, so if anyones found a better way to find this do tell....
Cheers,
Priyanga
select * from sys.tcp_endpoints

may be what you're looking for...

-Keith.|||Thanks Keith.

database mirroring

Does anyone know if you can read the mirror database after installing sql
2005 sp1.
I did setup mirror config before sp1 came out, but at that time the mirror
db was not avilable to read, but I heard then in sp1 it was going to be
fixed, so you can read the mirror db.
Thank you.Check out this thread in this forum: SQL 2005 Architecture Question -
Active Secondary Database?|||Nope. You cannot read the mirror database. You can create a DB Snapshot of
the mirror database and read the snapshot, which has worked since the first
CTPs. For true reporting consider using replication.
Mark Wistrom [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"john" <john@.discussions.microsoft.com> wrote in message
news:89921180-B433-40F0-AB00-13185B8C115C@.microsoft.com...
> Does anyone know if you can read the mirror database after installing sql
> 2005 sp1.
> I did setup mirror config before sp1 came out, but at that time the mirror
> db was not avilable to read, but I heard then in sp1 it was going to be
> fixed, so you can read the mirror db.
> Thank you.|||This is a NNTP newsgroup. What "forum" are you talking about?
*mike hodgson*
http://sqlnerd.blogspot.com
sterillo@.hotmail.com wrote:

>Check out this thread in this forum: SQL 2005 Architecture Question -
>Active Secondary Database?
>
>|||You cannot read from nor update a database involved in a mirroring session
while is acting as the 'mirror' role, but you can create a snapshot at any
moment and read from the snapshot. See this link:
http://msdn2.microsoft.com/en-us/library/ms175511.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"john" <john@.discussions.microsoft.com> wrote in message
news:89921180-B433-40F0-AB00-13185B8C115C@.microsoft.com...
> Does anyone know if you can read the mirror database after installing sql
> 2005 sp1.
> I did setup mirror config before sp1 came out, but at that time the mirror
> db was not avilable to read, but I heard then in sp1 it was going to be
> fixed, so you can read the mirror db.
> Thank you.sql

database mirroring

Does anyone know if you can read the mirror database after installing sql
2005 sp1.
I did setup mirror config before sp1 came out, but at that time the mirror
db was not avilable to read, but I heard then in sp1 it was going to be
fixed, so you can read the mirror db.
Thank you.Check out this thread in this forum: SQL 2005 Architecture Question -
Active Secondary Database?|||Nope. You cannot read the mirror database. You can create a DB Snapshot of
the mirror database and read the snapshot, which has worked since the first
CTPs. For true reporting consider using replication.
--
Mark Wistrom [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"john" <john@.discussions.microsoft.com> wrote in message
news:89921180-B433-40F0-AB00-13185B8C115C@.microsoft.com...
> Does anyone know if you can read the mirror database after installing sql
> 2005 sp1.
> I did setup mirror config before sp1 came out, but at that time the mirror
> db was not avilable to read, but I heard then in sp1 it was going to be
> fixed, so you can read the mirror db.
> Thank you.|||This is a multi-part message in MIME format.
--020800020103060408080900
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
This is a NNTP newsgroup. What "forum" are you talking about?
--
*mike hodgson*
http://sqlnerd.blogspot.com
sterillo@.hotmail.com wrote:
>Check out this thread in this forum: SQL 2005 Architecture Question -
>Active Secondary Database?
>
>
--020800020103060408080900
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>This is a NNTP newsgroup. What "forum" are you talking about?</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:sterillo@.hotmail.com">sterillo@.hotmail.com</a> wrote:
<blockquote
cite="mid1146764469.171645.227080@.j33g2000cwa.googlegroups.com"
type="cite">
<pre wrap="">Check out this thread in this forum: SQL 2005 Architecture Question -
Active Secondary Database?
</pre>
</blockquote>
</body>
</html>
--020800020103060408080900--|||You cannot read from nor update a database involved in a mirroring session
while is acting as the 'mirror' role, but you can create a snapshot at any
moment and read from the snapshot. See this link:
http://msdn2.microsoft.com/en-us/library/ms175511.aspx
--
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"john" <john@.discussions.microsoft.com> wrote in message
news:89921180-B433-40F0-AB00-13185B8C115C@.microsoft.com...
> Does anyone know if you can read the mirror database after installing sql
> 2005 sp1.
> I did setup mirror config before sp1 came out, but at that time the mirror
> db was not avilable to read, but I heard then in sp1 it was going to be
> fixed, so you can read the mirror db.
> Thank you.

Database Mirror or Log Shipping?

We are going to setup a new secondary server for reporting purpose. A group
of users will use the secondary database for data modeling, analysis, etc.
We have already setup two log shipping secondary servers for the primary,
one is over WAN. The logs are backup and restore on every 15 minutes. For
the past several years, log shipping has been working fine.
I would like to hear some opinion about database mirror, especially from
those who are using database mirror now. Is there any complication after
use database mirror?
Thanks!
Lijun
You cannot use a DB that is the target of log shipping. However, you can
create a DB snapshot on a DB mirror and report off of that.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Lijun Zhang" <sonyzhang00@.yahoo.com> wrote in message
news:O%23Zoc8NiHHA.4300@.TK2MSFTNGP05.phx.gbl...
We are going to setup a new secondary server for reporting purpose. A group
of users will use the secondary database for data modeling, analysis, etc.
We have already setup two log shipping secondary servers for the primary,
one is over WAN. The logs are backup and restore on every 15 minutes. For
the past several years, log shipping has been working fine.
I would like to hear some opinion about database mirror, especially from
those who are using database mirror now. Is there any complication after
use database mirror?
Thanks!
Lijun
|||Are there any issues with the mirror staying updated while there is a
snapshot of it?
I seem to remember something like this, but I think it was more an issue
with log shipping. For example, logshipping to another server -- and putting
a snapshot on the destination -- causes problems with log shipping restores
being able to be applied. probably not an issue with mirroring but i
couldn't remember.
If you would ever failover to the reporting server if the live OLTP went
down, remember that if it is a corruption -- the mirrored box might become
corrupted as well -- but with a log shipping box that is slightly delayed you
might be able to stop the corrupted log from being applied if you catch it
ahead of time.
Robert
"Tom Moreau" wrote:

> You cannot use a DB that is the target of log shipping. However, you can
> create a DB snapshot on a DB mirror and report off of that.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Lijun Zhang" <sonyzhang00@.yahoo.com> wrote in message
> news:O%23Zoc8NiHHA.4300@.TK2MSFTNGP05.phx.gbl...
> We are going to setup a new secondary server for reporting purpose. A group
> of users will use the secondary database for data modeling, analysis, etc.
> We have already setup two log shipping secondary servers for the primary,
> one is over WAN. The logs are backup and restore on every 15 minutes. For
> the past several years, log shipping has been working fine.
> I would like to hear some opinion about database mirror, especially from
> those who are using database mirror now. Is there any complication after
> use database mirror?
> Thanks!
> Lijun
>
>
|||There are no issues with the mirror being updated by the primary while there
is a snap shot. Indeed, this is a means of using the primary as a reporting
server, thus off-loading work from the primary.
I don't believe that you can log ship to a destination and mirror off of
that.
You can take a belt and suspenders approach and use mirroring, plus log ship
to another destination. As long as you keep all logs and not the time of
the corruption, you can stop the restores just prior to the corruption.
Also, take snapshots frequently, you can revert to a snapshot.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"sql411@.nospam.com" <sql411nospamcom@.discussions.microsoft.com> wrote in
message news:C9685BFA-7131-40F7-AB41-2D23E1FFF592@.microsoft.com...
Are there any issues with the mirror staying updated while there is a
snapshot of it?
I seem to remember something like this, but I think it was more an issue
with log shipping. For example, logshipping to another server -- and
putting
a snapshot on the destination -- causes problems with log shipping restores
being able to be applied. probably not an issue with mirroring but i
couldn't remember.
If you would ever failover to the reporting server if the live OLTP went
down, remember that if it is a corruption -- the mirrored box might become
corrupted as well -- but with a log shipping box that is slightly delayed
you
might be able to stop the corrupted log from being applied if you catch it
ahead of time.
Robert
"Tom Moreau" wrote:

> You cannot use a DB that is the target of log shipping. However, you can
> create a DB snapshot on a DB mirror and report off of that.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Lijun Zhang" <sonyzhang00@.yahoo.com> wrote in message
> news:O%23Zoc8NiHHA.4300@.TK2MSFTNGP05.phx.gbl...
> We are going to setup a new secondary server for reporting purpose. A
> group
> of users will use the secondary database for data modeling, analysis, etc.
> We have already setup two log shipping secondary servers for the primary,
> one is over WAN. The logs are backup and restore on every 15 minutes. For
> the past several years, log shipping has been working fine.
> I would like to hear some opinion about database mirror, especially from
> those who are using database mirror now. Is there any complication after
> use database mirror?
> Thanks!
> Lijun
>
>