January 19, 2006 at 9:44 am
All,
We have an ongoing debate here at my company on whether or not to include an environment specific identifier in the database name or not.
For example, we have a database called NOVA, and in DEV, Test, Stage & Prod, the db name is the same. For another application we have the "Dialer" database, but it's different across all environments - DLRDEV, DLRTST, DLRSTG & DLRPRD.
I've always been taught to use some sort of identifier in the name whether at the beginning or end, with 1 letter or 2 or whatever, but it makes it less likely for someone to screw up and truncate a table in Prod when they thought they were in DEV.
I'm very interested to hear opinions on this subject.
Thanks.
January 19, 2006 at 10:52 am
At work we currently differ the password the application uses to connect to the various servers. (sql authentication at the moment)
dev: login applicationX password applicationTesting
QA: login applicationX password applicationQA
Prod: ...
So if a developer version tries to connect to QA it gets invalid password.
Pro: we don't have to change the database names used in various stored procedures since a lot of them require 3 part naming.
We plan a kind of welcome message to displayed on screen so the users know if they are testing or not.
Developers don't get access to Prod.
January 19, 2006 at 4:51 pm
I've done it both ways, adding a prefix/suffix in the DB name and using passwords. I prefer using passwords because of what Jo P. points out. He also makes another great point....developers should not have access to production data. If you have a test system, there is no reason for developers to have access to production data.
January 19, 2006 at 5:07 pm
>>We have an ongoing debate here at my company on whether or not to include an environment specific identifier in the database name or not.
I'd say it depends on the complexity of the environment. If the environment/application requires any cross-database joining, then different DB names in DEV/QA/PRD becomes a nightmare. You can't move objects like stored procs & UDF's cleanly between environments, nor can you run tools like SQLDiff to determine differences between DEV,QA & PRD - the diff tools will show every object as different if 3-part naming is required for cross-database joins.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply