Re: same user/login for different databases on same instance
- From: "Russell Fields" <russellfields@xxxxxxxxxx>
- Date: Wed, 4 Feb 2009 17:29:38 -0500
Yes, you have analyzed the problem correctly. So, I am not sure what to tell you to do. You will have to change something about your approach. E.g.
1 - Get 3 SQL Servers, which could mean 3 instances of SQL Server on the same machine. (Providing it can handle the load. Perhaps dev and test could be SQL Server Express.)
2 - Use different logins for each database. (But you already knew that.)
3 - Switch to using an Application Role, which is specific to a database, once your application attaches to the proper database. From that point forward it will be limited to one database. (Separate logins are still better.)
"db" <db@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:CB3F6C99-4D98-41F0-B36B-C938EFE745F0@xxxxxxxxxxxxxxxx
I have a new sql server 2005. Ineed to set up test, production and
development databases on the server. Say the database are test, dev, prod.
I need to create same database user "appuser" on all three databases. I need
same user ("appuser" ) but user on test database should not have access to
anything on development or production environment/database.
Before creating database user, I have to create login (sp_addlogin) and this
login is common for all the databases. So I am stuck in the sence I can not
have same user name but different permission for different databases as that
username is associated with login name and loginname have all the
- Prev by Date: same user/login for different databases on same instance
- Next by Date: Re: Problem with bulk load security.
- Previous by thread: same user/login for different databases on same instance