sql-server-data-tools

I applied the SQL Server Data Tools patch to Visual Studio 2012 (Premium) and created a SQL Server CLR user-defined function project in C#: public partial class UserDefinedFunctions { [Microsoft.SqlServer.Server.SqlFunction] public static SqlInt32 Add42(SqlInt32 in_param) { SqlInt32 retval = in_param + 42; // Set break point here. return retval; } } In the SQL Server Object Explorer pane, I right-click on the newly published UDF and select "Execute Function..." I am prompted to supply a sample input value, and Visual Studio then publishes the function (again) to my local 2012 SQL Server and

MSBuild 14.0 (the version included with Visual Studio 2015) logs warnings (MSB4078) when building a solution which contains SSDT projects (rptproj or dwproj projects). For example: warning MSB4078: The project file "Reports.rptproj" is not supported by MSBuild and cannot be built. This is fine, MSBuild does not support SSDT projects, and we have to fall back to building them with Visual Studio (i.e. devenv.com ). See, for example, this answer . When using MSBuild 15.0 (the version included with Visual Studio 2017), however, building the same solution file gives the following error : Reports

I'm trying to create a user with a login for a SSDT database project. The login already exists on the target server. With the following SQL: CREATE USER [MyLogin] FOR LOGIN [MyLogin] WITH DEFAULT_SCHEMA = dbo GO I get the error: Error 1 SQL71501: User: [MyLogin] has an unresolved reference to Login [MyLogin]. I've found two solutions, but neither work with 2013: 1) Create a server project to reference the login. This isn't an option in the current version of SSDT / VS2013 2) Disable schema checking. The option is missing in 2013 (I believe it was Options -> Database Tools -> Schema Compare )

When working with a Database Project in Visual Studio 2012, VS defaults to the "Design-View" pane when you add or edit a table. While you can work in split-screen mode, the T-SQL pane defaults to the bottom pane. As I prefer to work with T-SQL directly as opposed to the designer, I constantly am switching to make the T-SQL pane the top-most editor in order to work with the object. Unfortunately, VS does not remember this preference, so each and every time I work with a table I must change to make the T-SQL pane appear on top as opposed to beneath the designer pane. I've looked to see if there

I recently had troubles Importing a Database from a SQL Server Database Project in VS 2015. Just hoping this helps some folks. I will add more pictures when my rep is higher. Error I get: The server version or database compatibility level is not supported. This is the Error I get when I right click on the project and try and Import a Database . Import Error: Right click on the Project and clicking View in Object Explorer . Add and connect to your database next, if needed. Right click on the database you are wanting to import and click Create New Project . Change settings if needed. Then Click

In Visual Studio 2012, we have Schema Compare in SSDT 's SQL Server Database Project (DbProject) project which helps Compare source versus target Update target to make it the same as source Where Source and target can be either a database, a DbProject project, or a .dacpac file Update can be done via an update action or generated script My question is that is it possible to have and where can I get the command-line/API interface to call this feature? SOURCE Database sqlpackage.exe /a:Extract /scs:Server=%Server%;Database=AspBaselineDB; /tf:%DriveSpec%\%DacPath%\%AspBaselineDB%_baseline.dacpac

I'm in the research phase trying to adopt 2012 Database Projects on an existing small project. I'm a C# developer, not a DBA, so I'm not particularly fluent with best practices. I've been searching google and stackoverflow for a few hours now but I still don't know how to handle some key deployment scenarios properly. 1) Over the course of several development cycles, how do I manage multiple versions of my database? If I have a client on v3 of my database and I want to upgrade them to v8, how do I manage this? We currently manage hand-crafted schema and data migration scripts for every version