Have you ever tried to create an object in SQL Server, but it failed due to a missing table, column, or other dependency? If so, you’ve hit a case where SQL Server doesn’t offer ‘deferred name resolution’.
While these errors can be helpful when you’ve made a typo or accidentally used the wrong database, this can sometimes be a big hassle when you are…
– Deploying database code to set up a partial environment
– Deploying database code from version control to an empty database to ensure the code is valid
In this post, I walk through common scenarios and test whether deferred name resolution works or not.
Check it out for what is probably the most detailed look at the topic I’ve ever seen.