I setup a mirroring database, have principal (host A), mirroring (host B),
withness (host C)

i create a user account and login account "usera" can login can retieve data
in principal server (host A)

when occur failover to host B, host B become principal, but i can connect
host B using "usera", i saw host B have a user account "usera" in host B,
but haven't the login account, then i create login account "usera",
but the "usera" login account only can login only, can't access database,
anyone can help,

Many many thanks.

Well, the story was told a little bit confusing...

However, let me tell you that in Database Mirroring, the mirroring process
is performed only at the database level. Principle replicates the
transactions to the Mirror. You should create the Logins at the Principle
and Mirror yourself manually. Database Mirroring would not create the server
level objects (like Logins). So, you better have the same Logins at the
Principle and Mirror SQL Server instances. So that your connections will not
fail when a failover happens and your ex-mirror takes the responsibility of
Principle role.

--
Ekrem Önsoy



"ken" <kenken2 (AT) yahoo (DOT) com.hk> wrote

Well, the story was told a little bit confusing...

However, let me tell you that in Database Mirroring, the mirroring process
is performed only at the database level. Principle replicates the
transactions to the Mirror. You should create the Logins at the Principle
and Mirror yourself manually. Database Mirroring would not create the server
level objects (like Logins). So, you better have the same Logins at the
Principle and Mirror SQL Server instances. So that your connections will not
fail when a failover happens and your ex-mirror takes the responsibility of
Principle role.

--
Ekrem Önsoy



"ken" <kenken2 (AT) yahoo (DOT) com.hk> wrote

Well, the story was told a little bit confusing...

However, let me tell you that in Database Mirroring, the mirroring process
is performed only at the database level. Principle replicates the
transactions to the Mirror. You should create the Logins at the Principle
and Mirror yourself manually. Database Mirroring would not create the server
level objects (like Logins). So, you better have the same Logins at the
Principle and Mirror SQL Server instances. So that your connections will not
fail when a failover happens and your ex-mirror takes the responsibility of
Principle role.

--
Ekrem Önsoy



"ken" <kenken2 (AT) yahoo (DOT) com.hk> wrote

Well, the story was told a little bit confusing...

However, let me tell you that in Database Mirroring, the mirroring process
is performed only at the database level. Principle replicates the
transactions to the Mirror. You should create the Logins at the Principle
and Mirror yourself manually. Database Mirroring would not create the server
level objects (like Logins). So, you better have the same Logins at the
Principle and Mirror SQL Server instances. So that your connections will not
fail when a failover happens and your ex-mirror takes the responsibility of
Principle role.

--
Ekrem Önsoy



"ken" <kenken2 (AT) yahoo (DOT) com.hk> wrote

Well, the story was told a little bit confusing...

However, let me tell you that in Database Mirroring, the mirroring process
is performed only at the database level. Principle replicates the
transactions to the Mirror. You should create the Logins at the Principle
and Mirror yourself manually. Database Mirroring would not create the server
level objects (like Logins). So, you better have the same Logins at the
Principle and Mirror SQL Server instances. So that your connections will not
fail when a failover happens and your ex-mirror takes the responsibility of
Principle role.

--
Ekrem Önsoy



"ken" <kenken2 (AT) yahoo (DOT) com.hk> wrote

Well, the story was told a little bit confusing...

However, let me tell you that in Database Mirroring, the mirroring process
is performed only at the database level. Principle replicates the
transactions to the Mirror. You should create the Logins at the Principle
and Mirror yourself manually. Database Mirroring would not create the server
level objects (like Logins). So, you better have the same Logins at the
Principle and Mirror SQL Server instances. So that your connections will not
fail when a failover happens and your ex-mirror takes the responsibility of
Principle role.

--
Ekrem Önsoy



"ken" <kenken2 (AT) yahoo (DOT) com.hk> wrote

Well, the story was told a little bit confusing...

However, let me tell you that in Database Mirroring, the mirroring process
is performed only at the database level. Principle replicates the
transactions to the Mirror. You should create the Logins at the Principle
and Mirror yourself manually. Database Mirroring would not create the server
level objects (like Logins). So, you better have the same Logins at the
Principle and Mirror SQL Server instances. So that your connections will not
fail when a failover happens and your ex-mirror takes the responsibility of
Principle role.

--
Ekrem Önsoy



"ken" <kenken2 (AT) yahoo (DOT) com.hk> wrote

Well, the story was told a little bit confusing...

However, let me tell you that in Database Mirroring, the mirroring process
is performed only at the database level. Principle replicates the
transactions to the Mirror. You should create the Logins at the Principle
and Mirror yourself manually. Database Mirroring would not create the server
level objects (like Logins). So, you better have the same Logins at the
Principle and Mirror SQL Server instances. So that your connections will not
fail when a failover happens and your ex-mirror takes the responsibility of
Principle role.

--
Ekrem Önsoy



"ken" <kenken2 (AT) yahoo (DOT) com.hk> wrote

Well, the story was told a little bit confusing...

However, let me tell you that in Database Mirroring, the mirroring process
is performed only at the database level. Principle replicates the
transactions to the Mirror. You should create the Logins at the Principle
and Mirror yourself manually. Database Mirroring would not create the server
level objects (like Logins). So, you better have the same Logins at the
Principle and Mirror SQL Server instances. So that your connections will not
fail when a failover happens and your ex-mirror takes the responsibility of
Principle role.

--
Ekrem Önsoy



"ken" <kenken2 (AT) yahoo (DOT) com.hk> wrote