Why to Avoid Using the Current Database Name in Object Definitions in SQL Server
I’ve recently published an article, “Why You Shouldn’t Hardcode the Current Database Name in Your Views, Functions, and Stored Procedures,” over on Simple Talk.
In the article, I discuss:
- Why referencing the current database name creates a dependency
- What ‘deferred name resolution’ is, and why the dependency may be more noticeable in views and some functions (rather than stored procedures)
- Which activities are most likely to break if you place dependencies on the current database name