Schema files have blank lines appended after schema compare
After doing a schema compare from the DB to the project, most schema files have a blank line appended. This causes the files to be checked out of source control and then show as changes when they shouldn't
Upvotes: 19<=-=Mar 13 2015 2:44PM=-=>
This is happening for me too; it’s been a long time issue in the SSDT. It creates noise when doing compares, merges, and checkins where these don’t pertain to the real changes of objects.
Microsoft Visual Studio Ultimate 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Installed Version: Ultimate
Scaffolding: A framework for building and running code generators
Server Explorer extensions for Microsoft Azure Websites
NuGet Package Manager 2.8.50926.663
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
SQL Server Data Tools 12.0.50226.0
Microsoft SQL Server Data Tools
Thank you for submitting this feedback. We are investigating this issue and will update when we have more information.
SQL Server Data Tools team
This is one of those issues that convinces me that nobody at MSFT is actually using SSDT.<=-=May 11 2016 2:28AM=-=>
Have same issue. It’s annoying enough. It could be a very-easy-to-fix bug, still alive for several years. So sad…<=-=Aug 10 2016 3:37AM=-=>
I noticed that it doesn’t seem to happen if there are some GRANT instructions on the schema.
This should be a simple fix. Please just do it. Very annoying.
What’s it been, 8 years? 10 years? I know it might seem trivial, but it really wears on a person after so long. Especially if you do a lot of database work like I do.
VS User commented
Still happening with all versions/editions of VS 2019
This has been going on for years, it's a simple fix, why doesn't anyone fix it? It happens on a new project with one table in it (2 schemas)
This is still a problem. SSDT needs to be polished.
Andrew Carmichael commented
Microsoft Visual Studio Community 2019
Steve Martinez commented
Please fix this. From the end user perspective this is productivity robbing and a very annoying bug that has been around for many years in Visual Studio / SSDT / SQL Server Database Projects. What more is needed from the community for Microsoft to actually fix this?
I've just installed Visual Studio 2019 to upgrade from VS2017 and I was hoping this would finally have been fixed. Unfortunately not.
Having the same issue too. This is frustrating and lowering productivity
Steve Martinez commented
I have been dealing with this very annoying bug for many years and want this to be fixed. Having to spend extra time dealing with this during compares, merges, etc..., and having to explain this bug to new developers is quit a waste of time and productivity.
When will this be fixed?
This is extremely annoying.
How long can this go on? I refuse to check in bogus changes, so every time I update a database project I have to go undo pending changes for the schema files. After so many years of this, it has become very very annoying that it is still doing this.
Brian Lawton commented
It's extremely frustrating that I continue having to explain this bug to clients after so many years. Why can't it be fixed?
Nicky van Vroenhoven commented
This is still happening for me. Please adjust it so the blank lines are not added.