database mirroring - correction to technet article requested

This is a very informative document:
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
However, I would like to request one correction:
Step 4 under "Setup and Security" indicates that you have to specify the
partner and the witness. It tells you to to issue "ALTER DATABASE...SET
PARTNER..." on the intended principal first. Then you execute the same
command on the intended mirror.
Problem:
I could not get it to work that way. When I set up Mirroring in my
environment (9.0.2153) I had to execute the command on the mirror first then
against the primary.
--
Keith KratochvilHi Keith!
The early revisions of this document, I believe was based on a beta, so it is possible that the
behavior changed between that and production. Did you do a feedback at the bottom of that page?
(I see the same thing, btw, that you have to do mirror before principal...)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
> This is a very informative document:
> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
>
> However, I would like to request one correction:
> Step 4 under "Setup and Security" indicates that you have to specify the partner and the witness.
> It tells you to to issue "ALTER DATABASE...SET PARTNER..." on the intended principal first. Then
> you execute the same command on the intended mirror.
> Problem:
> I could not get it to work that way. When I set up Mirroring in my environment (9.0.2153) I had
> to execute the command on the mirror first then against the primary.
>
> --
> Keith Kratochvil
>
>|||argh. "Please limit comments to 256 characters"
I will try to be more to the point.
--
Keith Kratochvil
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
> Hi Keith!
> The early revisions of this document, I believe was based on a beta, so it
> is possible that the behavior changed between that and production. Did you
> do a feedback at the bottom of that page?
> (I see the same thing, btw, that you have to do mirror before
> principal...)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
>> This is a very informative document:
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
>>
>> However, I would like to request one correction:
>> Step 4 under "Setup and Security" indicates that you have to specify the
>> partner and the witness. It tells you to to issue "ALTER DATABASE...SET
>> PARTNER..." on the intended principal first. Then you execute the same
>> command on the intended mirror.
>> Problem:
>> I could not get it to work that way. When I set up Mirroring in my
>> environment (9.0.2153) I had to execute the command on the mirror first
>> then against the primary.
>>
>> --
>> Keith Kratochvil
>>
>|||> argh. "Please limit comments to 256 characters"
Like a SQL 6.5 varchar?
;-)
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:OxGJasH9GHA.788@.TK2MSFTNGP05.phx.gbl...
> argh. "Please limit comments to 256 characters"
> I will try to be more to the point.
> --
> Keith Kratochvil
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
>> Hi Keith!
>> The early revisions of this document, I believe was based on a beta, so
>> it is possible that the behavior changed between that and production. Did
>> you do a feedback at the bottom of that page?
>> (I see the same thing, btw, that you have to do mirror before
>> principal...)
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
>> news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
>> This is a very informative document:
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
>>
>> However, I would like to request one correction:
>> Step 4 under "Setup and Security" indicates that you have to specify the
>> partner and the witness. It tells you to to issue "ALTER DATABASE...SET
>> PARTNER..." on the intended principal first. Then you execute the same
>> command on the intended mirror.
>> Problem:
>> I could not get it to work that way. When I set up Mirroring in my
>> environment (9.0.2153) I had to execute the command on the mirror first
>> then against the primary.
>>
>> --
>> Keith Kratochvil
>>
>>
>

database mirroring - correction to technet article requested

This is a very informative document:
http://www.microsoft.com/technet/pr...5/dbmirror.mspx
However, I would like to request one correction:
Step 4 under "Setup and Security" indicates that you have to specify the
partner and the witness. It tells you to to issue "ALTER DATABASE...SET
PARTNER..." on the intended principal first. Then you execute the same
command on the intended mirror.
Problem:
I could not get it to work that way. When I set up Mirroring in my
environment (9.0.2153) I had to execute the command on the mirror first then
against the primary.
Keith KratochvilHi Keith!
The early revisions of this document, I believe was based on a beta, so it i
s possible that the
behavior changed between that and production. Did you do a feedback at the b
ottom of that page?
(I see the same thing, btw, that you have to do mirror before principal...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
> This is a very informative document:
> http://www.microsoft.com/technet/pr...5/dbmirror.mspx
>
> However, I would like to request one correction:
> Step 4 under "Setup and Security" indicates that you have to specify the p
artner and the witness.
> It tells you to to issue "ALTER DATABASE...SET PARTNER..." on the intended
principal first. Then
> you execute the same command on the intended mirror.
> Problem:
> I could not get it to work that way. When I set up Mirroring in my enviro
nment (9.0.2153) I had
> to execute the command on the mirror first then against the primary.
>
> --
> Keith Kratochvil
>
>|||argh. "Please limit comments to 256 characters"
I will try to be more to the point.
Keith Kratochvil
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
> Hi Keith!
> The early revisions of this document, I believe was based on a beta, so it
> is possible that the behavior changed between that and production. Did you
> do a feedback at the bottom of that page?
> (I see the same thing, btw, that you have to do mirror before
> principal...)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
>|||> argh. "Please limit comments to 256 characters"
Like a SQL 6.5 varchar?
;-)
Hope this helps.
Dan Guzman
SQL Server MVP
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:OxGJasH9GHA.788@.TK2MSFTNGP05.phx.gbl...
> argh. "Please limit comments to 256 characters"
> I will try to be more to the point.
> --
> Keith Kratochvil
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
>

database mirroring - correction to technet article requested

This is a very informative document:
http://www.microsoft.com/technet/pro.../dbmirror.mspx
However, I would like to request one correction:
Step 4 under "Setup and Security" indicates that you have to specify the
partner and the witness. It tells you to to issue "ALTER DATABASE...SET
PARTNER..." on the intended principal first. Then you execute the same
command on the intended mirror.
Problem:
I could not get it to work that way. When I set up Mirroring in my
environment (9.0.2153) I had to execute the command on the mirror first then
against the primary.
Keith Kratochvil
Hi Keith!
The early revisions of this document, I believe was based on a beta, so it is possible that the
behavior changed between that and production. Did you do a feedback at the bottom of that page?
(I see the same thing, btw, that you have to do mirror before principal...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
> This is a very informative document:
> http://www.microsoft.com/technet/pro.../dbmirror.mspx
>
> However, I would like to request one correction:
> Step 4 under "Setup and Security" indicates that you have to specify the partner and the witness.
> It tells you to to issue "ALTER DATABASE...SET PARTNER..." on the intended principal first. Then
> you execute the same command on the intended mirror.
> Problem:
> I could not get it to work that way. When I set up Mirroring in my environment (9.0.2153) I had
> to execute the command on the mirror first then against the primary.
>
> --
> Keith Kratochvil
>
>
|||argh. "Please limit comments to 256 characters"
I will try to be more to the point.
Keith Kratochvil
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
> Hi Keith!
> The early revisions of this document, I believe was based on a beta, so it
> is possible that the behavior changed between that and production. Did you
> do a feedback at the bottom of that page?
> (I see the same thing, btw, that you have to do mirror before
> principal...)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:u8enyNH9GHA.3820@.TK2MSFTNGP02.phx.gbl...
>
|||> argh. "Please limit comments to 256 characters"
Like a SQL 6.5 varchar?
;-)
Hope this helps.
Dan Guzman
SQL Server MVP
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:OxGJasH9GHA.788@.TK2MSFTNGP05.phx.gbl...
> argh. "Please limit comments to 256 characters"
> I will try to be more to the point.
> --
> Keith Kratochvil
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:es8ewZH9GHA.3348@.TK2MSFTNGP03.phx.gbl...
>

Database logon request

Hi,

I am using CrystalReport from MS Visual Studio .Net. The report was created by the designer. It accesses a MySQL DB by the MyODBC 2.5 driver. Everything works fine on my development machine. I call the form which implements the crystalreportview and the report is displayed. Hoever, if I create an installation and run it on the deployment machine, a dialog is displayed requesting for server name, database, user name and password. Whatever I type in the login fails ("login fails. please retry"). I tried the MyODBC DSN and the MySQL user - without success.

Was anyone facing the same problem? I don't know how to proceed, it is really a strange issue, because the application runs on my development machine...

Thanks in advance.

gbrOkay. Please ignore my posting. I found out that different user accounts were created...