How to prevent SSDT publishing from dropping tables?
If you are using the “Drop Objects not in Source” option but want to prevent the dropping of just Tables, you can exclude them by: going to “Advanced Deployment Settings” (the “Advanced…” button on the “Debug” tab of “Project Properties”), then going to the “Drop” tab, and enabling the “Do not drop tables” option (in the scrollable list).
How to publish database changes with SSDT in SQL Server?
I have a SQL Server Data Tools (VS2012) project that’s published automatically during the build process. A column was recently updated from an int to decimal (18,4). As a result of this change, the publishing fails with the error (49,1): SQL72014: .Net SqlClient Data Provider: Msg 50000, Level 16, State 127, Line 6 Rows were detected.
Can you use SSDT to push schema changes?
Don’t use SSDT for Schema changes. Just use it to push code (Stored Procedures, Functions, Triggers, SQLCLR Objects, etc). You can write your own schema deployment scripts and include them in the Project.
How to create a new table in SSDT?
The (marginally) less clunky route is to use pre and post deployment scripts to do the work with a rename. Rename the existing table in a pre-deployment script. With the existing table missing the table in focus will be created as per the new schema definition.
Is it possible to exclude a table from a SSDT deploy?
It depends on dbo.a. dbo.a has many columns that are foreign keys to other columns. Someone else (who maintains the default schema) might change dbo.a. I’d like to simple store dbo.a as: So it gets built internally, but not deployed. Is that possible? You can use the AgileSqlClub SqlPackage Deployment Filter.
Can you only manage part of a database with SSDT?
Only managing part of a database with SSDT is difficult. If there were no dependencies then you could simply disallow it to drop objects and not include it in the project. Since there are dependencies, but you don’t want to manage them, I think that you will have to trick the system.