SSDT Schema Compare add blank lines to the schema files
Not really a workaround or a solution, but I remember having this issue on Visual Studio 2017 and the issue stopped arising when I upgraded to Visual Studio 2019.
Not really a workaround or a solution, but I remember having this issue on Visual Studio 2017 and the issue stopped arising when I upgraded to Visual Studio 2019.
According to BOL: Indexed views and indexes on computed columns store results in the database for later reference. The stored results are valid only if all connections referring to the indexed view or indexed computed column can generate the same result set as the connection that created the index. In order to create a table … Read more
I know it is an old thread, but I came across this one when I was facing the same problem.. Someone might still benefit.. Here is what worked for me: When you right click on the DB project in VS you get the ‘Publish Database’ dialog. You setup the target server connection and choose the … Read more
Edit: The old answer below worked for me once but was intermittent on subsequent occasions. I then noticed that I was actually getting an error displayed in the bottom left hand corner of Visual Studio: Exception from HRESULT: 0x80041FE2 The tab has been closed. Searching on the above returned this article: https://connect.microsoft.com/VisualStudio/feedback/details/827417/vs-express-2013-cannot-reopen-any-open-file-tabs-and-silently-closes-them-on-selection So I closed … Read more
It turned out that Visual Studio fooled me with wrong syntax warnings! My setup was perfectly valid. To avoid warnings right click anywhere inside the file and choose “Execution Settings – SQLCMD Mode”. There is also a toolbar button named SQLCMD Mode doing the same thing. Here is the menu item in case you can’t … Read more
Check the Error List if you have any error, I had a non recognized word in VS (but it did in SQL Server), I commented it out, re-compared and it was enabled successfully.
After contacting a friend at Microsoft, he suggested repairing the Data Tools install at https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt And that resolved it. Thanks Chuck!
I’ve been working on this myself, and I can tell you it’s not easy. First, to address the reply by JT – you cannot dismiss “versions”, even with declarative updating mechanics that SSDT has. SSDT does a “pretty decent” job (provided you know all the switches and gotchas) of moving any source schema to any … Read more
You need to install the last version of SQL Server Data Tools: http://msdn.microsoft.com/en-US/data/hh297027 Make sure to restart VS and then build the solution again. This solves the problem!
This is an issue caused by the ESENT engine relied on by SQL Projects adding in a new file. This is a new feature in Windows 10 Anniversary Edition to avoid data loss, but the fact SQL Projects store the .dbmdl cache file under the project root means this locked file is added to the … Read more