Databases
Another area about which you should think carefully before refactoring is in production databases. When you refactor a database design, you incur the burden of porting data from the old design to the new one. This may be more trouble than it's worth, particularly if the database is already in production. Then again, you may find that it's an absolute necessity. It depends on the situation. If you're going to refactor a database, do so as early in the development process as possible. As with any type of software, the cost of changing a database on which applications are already based rises exponentially over time, the aspirations of Extreme Programming (XP) notwithstanding.
To Rename or Not to Rename?Is renaming worth the effort? Some ... |
Get Guru's Guide to SQL Server™ Stored Procedures, XML, and HTML, The now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
