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 |
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2005-07-13 : 10:28:59
|
| I have a user, let's call him "joe" that's giving me issues. I have a production server which log ships a database to another server which we let users run queries against. Joe can see the production server and the database that we want him to see. When Joe connects to the server that is receiving the log shipped server, he can't see the log shipped database. I'm not even sure where to start with this problem. Why can he see it on the production box and not the other? Is there something in one of the system databases like Master that I need to look into? Afraid of really screwing this up too much by playing around and am open to ideas.Mike"oh, that monkey is going to pay" |
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2005-07-13 : 11:08:35
|
| ..some further information. On the destination server that we're log shipping to the database he should have access to is not checked. On production it is checked. Very weird.Mike"oh, that monkey is going to pay" |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-07-13 : 12:57:46
|
| His sid is out of sync. You'll need to drop his login on the secondary server and recreate it using sp_addlogin. Make sure to bring over the sid from the primary. Then he'll have access.Tara |
 |
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2005-07-13 : 13:50:18
|
| I know a SQL Goddess who's going the right way for a hug!Thanks Tara, works great.Mike"oh, that monkey is going to pay" |
 |
|
|
|
|
|