A small blog post for anyone who stumbles across this issue (and for my future self, should I forget the solution).
I was working on some tables in SSDT and I tried to publish changes to the database on my local machine. I got a build error because I created a clustered index on the wrong table (which resulted in two clustered indexes on said table). So I fixed the bug and tried to publish. However, even though the build succeeded, I got the following error message:
The script file could not be found.
Well, that’s a first. Rebuilding didn’t work. Re-publishing neither. Eventually, I unloaded the project and removed the .dbmdl file (which seems to be a serialized file of the database model for optimizing deployment performance, as hinted here on Stack Overflow).
Reloading the project into the solution without this file present apparently forces a re-analysis of the project (there used to be a button to reanalyze in previous versions, but I couldn’t find it). Now I could publish the project again.
UPDATE: this might also help if you get the dreaded “null reference not set to an instance of an object” error
It's the second tuesday of the month, which means T-SQL Tuesday time! This month's topic…
It's time for T-SQL Tuesday again! And we're almost to number 200! T-SQL Tuesday is…
A while ago we suddenly had an error while trying to deploy one Fabric workspace…
I've uploaded the slides for my Techorama session Microsoft Fabric for Dummies and my DataGrillen…
I'm doing a small series on indexing basics for SQL Server, and on May 14th…
A short blog post about an issue with Fabric Mirroring (with Azure SQL DB as…
View Comments
You just saved clueless me from total embarrassment