The Era of The Shared SQL Server Database is Finally Ending
For more than 20 years, many small and medium SaaS companies have built products with complicated business logic and a flexible user experience on the …
Read MoreWhy You Shouldn't Hardcode the Current Database Name in Your Views, Functions, and Stored Procedures
Category:
tsql-programming
, sql-server
I recently published Why You Shouldn’t Hardcode the Current Database Name in Your Views, Functions, and Stored Procedures over on Simple Talk.
What the Article Covers
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
RELATED POSTS
