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-27 : 09:23:31
|
| Paul writes "I have an application that utilizes multiple databases.ALL of the access to the database(s) is via stored procedures. There is no embedded SQL in any app.The application logs in under a user account and is defaulted to a database that is used as a workspace. This user account has been granted execute permsission on all appropriate stored procedures. Most access is via RPC to other stored procedures in the other databases, but there are a few cases where a stored procedure utilizes cross database joins to retrive refrenced data. This works beautifully, until I backup/restore the databases to another server or copy/attach the files. If copy all but the workspace database, I start getting PERMISSION errros when executing the sp's that contain the cross database joins.I have :Rebuilt the master, dropped the user account from all databases, loaded the login, loaded the user, assigned the execute permissions and still have the problem. The only way I seem to clear this is by dumping and restoring the workspace database from the same server as the other databases.Have you seen or heard of this problem? I used to deal with a similar problem in 6.5 using the senerio I listed above, but in SQL 2000 it is not working. This leads me to think that it isn't a SID->UID mismatch, but something else that is new with SQL 2000.Any help would be greatly appreciated." |
|
|
|
|
|