Development and production database servers
-
Hello, Our production and development databases are on the same server, due to the complexity of the system. is there a way, that I could not have the production server active, when I open the database server? I do not want to accidently connect to this. Thanks!
-
Hello, Our production and development databases are on the same server, due to the complexity of the system. is there a way, that I could not have the production server active, when I open the database server? I do not want to accidently connect to this. Thanks!
-
Hello, Our production and development databases are on the same server, due to the complexity of the system. is there a way, that I could not have the production server active, when I open the database server? I do not want to accidently connect to this. Thanks!
Depending on what DB server you are using, you can also assign different users to the databases.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Depending on what DB server you are using, you can also assign different users to the databases.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Both instances of databases are on the same server, this is sql2005. Once you add a login, it is by default to all the databases that exists on that server, right?
I'm not an expert on SQL2005, but check the GRANT SQL keyword. You should be able to create a user and grant that user access to only a single DB. I don't think there's any way to restrict the administrator from accessing a db, though.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Both instances of databases are on the same server, this is sql2005. Once you add a login, it is by default to all the databases that exists on that server, right?
You can create a login on a SQL server, but you still need to associate it to a User in a database and grant that user specific rights in that database. For example, I created a user, pm_user, which is valid in the PM database, but has no access to the "Sandbox" database. When I try to execute the following SQL, Use Sandbox GO I get the following error message: The server principal "pm_user" is not able to access the database "Sandbox" under the current security context. This shows that a login is not the same as a user and with a single login, you can restrict the databases the user has access to. Hope this helps. David
-
Both instances of databases are on the same server, this is sql2005. Once you add a login, it is by default to all the databases that exists on that server, right?
vanikanc wrote:
Both instances of databases are on the same server, this is sql2005. Once you add a login, it is by default to all the databases that exists on that server, right?
Wrong. A login to a server does not automatically grant access to databases on that server.
-
Hello, Our production and development databases are on the same server, due to the complexity of the system. is there a way, that I could not have the production server active, when I open the database server? I do not want to accidently connect to this. Thanks!
vanikanc wrote:
Our production and development databases are on the same server, due to the complexity of the system. is there a way, that I could not have the production server active, when I open the database server? I do not want to accidently connect to this.
Obviously the best solution is to use two different servers. That precludes other problems as well such as run away queries that cause CPU overload, or timeouts due to long running processes. Myself I test against the database server which runs on my development box. But as noted by others very careful use of users and permissions would entirely preclude overlap.