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.
Yes, there is a new version supporting SQL Server 2005-2016 available and it installs into a different location than the previous (SQL Server 2012 and lower) version. In fact, you’ll have different install locations depending on if you just use SSDT or if you install it as part of SSMS or the standalone installer. SSDT … Read more
To resolve this, I added a reference to the other database, clearing out the “Database variable” field in the dialog. If I didn’t clear this field, when doing a schema compare, SSDT would generate the update script using the database variable name, which would fail. Add a Database Reference to the project. In my case … Read more
You can suppress it at individual file level which contains the code generating the warning if you want. Something like this. <Build Include=”Stored Procedures\X.sql”> <SuppressTSqlWarnings>71502</SuppressTSqlWarnings> </Build>
VS2017 supports ssis or ssrs projects if you install SSDT for VS2017 here. Click on the newly downloaded file and check SSIS or SSRS components that you required, as show in diagram :- Once you have installed this, try opening ssis / ssrs project. I managed to open ssis developed on vs2010. You should see … Read more
SOURCE Database sqlpackage.exe /a:Extract /scs:Server=%Server%;Database=AspBaselineDB; /tf:%DriveSpec%\%DacPath%\%AspBaselineDB%_baseline.dacpac TARGET Database sqlpackage.exe /a:Extract /scs:Server=%Server%;Database=%AspTargetDB-2%; /tf:%DriveSpec%\%DacPath%\%AspTargetDB%.dacpac COMPARE & GENERATE the Delta script sqlpackage.exe /a:Script /sf:%DriveSpec%\%DacPath%\%AspBaselineDB%_baseline.dacpac /tf:%DriveSpec%\%DacPath%\AspNetDb\%AspTargetDB%.dacpac /tdn:aspTargetdb /op:%DriveSpec%\%SqlPath%\AspNetDb\AspDbUpdate.sql EXECUTE the script sqlcmd.exe -S %Server%\aspnetdbAmexDev -i %DriveSpec%\%SqlPath%\AspNetDb\AspDbUpdate.sql I do this in CMD scripting as our IT dept will not allow unsigned PowerShell scripts and they won’t purchase a cert. This … Read more
SQL Server Integration Services, SSIS, covers a whole lot of territory. I’ll discuss what’s relevant to this question of 32 vs 64 bit-ness. Installation As you discovered, the installer is stupid but you typically only need to use it once or twice in a machine’s lifetime. I’m ok with this as I’d rather them spend … Read more
Update 5 Jun. 2023 – general Availability (GA) release Microsoft released Version 1.0 (General Availability (GA) release) of the SQL Server Integration Services extension for Visual Studio 2022. Update 24 Nov. 2022 – Public preview released Microsoft added a public preview of the SQL Server Integration Services Projects 2022 to the Visual Studio marketplace, which … Read more
Answer: Microsoft now has an official NuGet package (see blog post). Old answer, prior to August 2016; provided in case the NuGet package doesn’t work for you: Install dacframework.msi (x86|x64) Install SQLDOM.MSI (x86|x64) Install SQLLS.MSI (x86|x64) Install SQLSysClrTypes.msi (x86|x64) Install SSDTBuildUtilities.msi (from the “Administrator Install Point” as setup in step 3 here) Done! Source: Headless … Read more
One other possibility is that the schema you have used in your view/table etc does not exist in the project. You may need to add the schema to the VS Database Project. Right Click the project and Add > New Item > Schema