I have a SQL Server database which has data for several customers/devices. We are changing the prefix of our website (asp.net) and our application dynamically loads the proper connection string based on the first part of the URL. Is it safe for me to change the name of my database accordingly, or should I simply put a conditional statement in the connection string logic to make the new URL point to the old database? Thanks!
-
1Hard to answer without more detail. Why wouldn't it be safe?– theglauberFeb 28, 2012 at 20:30
-
voted to close - too localized...you say you have a system to map the url to the connection string...so why would you want to go around that system?– dotjoeFeb 28, 2012 at 20:31
-
As long as your connection strings and any data that relies on knowing the database name are changed, then this should be safe.– Justin PihonyFeb 28, 2012 at 20:31
-
That's the point - I don't want to circumvent the logic there. Just wondering if it's a bad practice to change the database name or if there are other ramifications I'– Joshua SmithFeb 28, 2012 at 20:54
-
Which DBMS are you using? "SQL database" does not describe a specific product.– user1822Feb 28, 2012 at 23:00
|
Show 1 more comment
1 Answer
If you have queries that reference the full database name (which you likely will have if you have cross database queries), they will break. If you have Imports or reports that reference the full database name those will break. If you have linked servers (SQL server), those will break. If you have other applications that hit the same database backend, those will likely break.
If you have none of those situations, you may be OK. However, you will still want to do this only if you have a full test suite to be able to verify that nothing broke. Keeping the database name and changing how the application connects is a far safer choice if you don't have a good test suite.
