Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-09-03 : 20:40:52
|
| Matt Again writes "SQL 2000, windows 2000 server, 4 * CPUSituation - We have three servers with replication happening between them - srv a - srv b, srv a - srv c, srv b - c. All the servers are connected as remote servers. All servers use a common password and login to start them. We have custom stored procs which we execute on srv a & srv c which connect and get rows counts from replicated DB's by executing a remote stored proc. This allows us to see table/row counts on the replicated and local databases/tables, across servers which are party to the replication. From this we can tell if replication is in sync or running behind. There is a DBA group which has SA rights to all servers/DB's. We use Query analyser and trusted connections to connect and run queries.Problem - This situation use to work in our old 6.5 environment, since moving to 2k enviroment it no longer works. The only way we can execute remote stored procs is by making a connection through Query Analyser as "SA", our trusted connections as our ourselves do no loneger appear to be sufficient to run the remote stored procs.Can you help? " |
|
|
|
|
|
Remote server problems