 | |
mirroring database user account problem
microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools
 |
| | Thread Tools | Display Modes |
#21
 
| |||
| |||
|
Re: mirroring database user account problem -
09-02-2008
, 09:15 PM
|
... and also make sure that the SID number for the login you create is the same between the instances. One option is to use sp_help_revlogin (Google). -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Ekrem Önsoy" <ekrem (AT) compecta (DOT) com> wrote in message news:397F6677-E0BD-4CEE-AB28-D4846A1F221F (AT) microsoft (DOT) com... 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 in message news:evFylMRDJHA.4824 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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. |
#22
| |||
| |||
|
|
... and also make sure that the SID number for the login you create is the same between the instances. One option is to use sp_help_revlogin (Google). -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Ekrem Önsoy" <ekrem (AT) compecta (DOT) com> wrote in message news:397F6677-E0BD-4CEE-AB28-D4846A1F221F (AT) microsoft (DOT) com... 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 in message news:evFylMRDJHA.4824 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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. |
#23
| |||
| |||
|
|
... and also make sure that the SID number for the login you create is the same between the instances. One option is to use sp_help_revlogin (Google). -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Ekrem Önsoy" <ekrem (AT) compecta (DOT) com> wrote in message news:397F6677-E0BD-4CEE-AB28-D4846A1F221F (AT) microsoft (DOT) com... 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 in message news:evFylMRDJHA.4824 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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. |
#24
| |||
| |||
|
|
... and also make sure that the SID number for the login you create is the same between the instances. One option is to use sp_help_revlogin (Google). -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Ekrem Önsoy" <ekrem (AT) compecta (DOT) com> wrote in message news:397F6677-E0BD-4CEE-AB28-D4846A1F221F (AT) microsoft (DOT) com... 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 in message news:evFylMRDJHA.4824 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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. |
#25
| |||
| |||
|
|
... and also make sure that the SID number for the login you create is the same between the instances. One option is to use sp_help_revlogin (Google). -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Ekrem Önsoy" <ekrem (AT) compecta (DOT) com> wrote in message news:397F6677-E0BD-4CEE-AB28-D4846A1F221F (AT) microsoft (DOT) com... 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 in message news:evFylMRDJHA.4824 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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. |
#26
| |||
| |||
|
|
... and also make sure that the SID number for the login you create is the same between the instances. One option is to use sp_help_revlogin (Google). -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Ekrem Önsoy" <ekrem (AT) compecta (DOT) com> wrote in message news:397F6677-E0BD-4CEE-AB28-D4846A1F221F (AT) microsoft (DOT) com... 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 in message news:evFylMRDJHA.4824 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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. |
#27
| |||
| |||
|
|
... and also make sure that the SID number for the login you create is the same between the instances. One option is to use sp_help_revlogin (Google). -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Ekrem Önsoy" <ekrem (AT) compecta (DOT) com> wrote in message news:397F6677-E0BD-4CEE-AB28-D4846A1F221F (AT) microsoft (DOT) com... 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 in message news:evFylMRDJHA.4824 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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. |
#28
| |||
| |||
|
|
... and also make sure that the SID number for the login you create is the same between the instances. One option is to use sp_help_revlogin (Google). -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Ekrem Önsoy" <ekrem (AT) compecta (DOT) com> wrote in message news:397F6677-E0BD-4CEE-AB28-D4846A1F221F (AT) microsoft (DOT) com... 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 in message news:evFylMRDJHA.4824 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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. |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.