Comments
Sort by recent activity
Unfortunately, I haven't tried what you are talking about and am pretty new at using this tool so I'm unable to provide an answer to your second question. I'm really not sure how this would work because even with a named instance specified in the build, I don't think it would resolve what you are facing. Hopefully someone with more experience can chime in. I will likely face this same issue going forward. / comments
Unfortunately, I haven't tried what you are talking about and am pretty new at using this tool so I'm unable to provide an answer to your second question. I'm really not sure how this would work be...
The answer ended up being pretty simple. In my case, there were references in some functions and stored procedures with the database name listed before the schema. For example, Database1.schema.tablename vs. schema.tablename. Depending on how your build is set up, it either spins up a copy of the DB with a temporary name (this is how mine is set up), or goes against a named instance of the database specified in the build. I wanted to continue down the path using the temp DB that was spun up so I removed the hard coded database name from everything that referenced it. This resolved the issue and the build succeeded. / comments
The answer ended up being pretty simple. In my case, there were references in some functions and stored procedures with the database name listed before the schema. For example, Database1.schema.tab...