sql-server-data-tools

问题 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

问题 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

问题 I have an issue with compilation of SSDT SQL Server Database Project by using Visual Studio 2015. I want to use C# 6 features inside my database project, but it seems like it is unsupported. For example, I have added the next class in my db project: namespace Database1 { class ClassFile1 { public string Str { get; } = string.Empty; } } I have tried to compile this, but I got the error: CS1519: Invalid token '=' in class, struct, or interface member declaration I have found out that the reason

问题 One of our build servers has just been updated to the latest "Microsoft SQL Server Update for database tooling" (version 12.0.60629.0) and is now incompatible with the version of SqlPackage.exe we have (in C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\120\SqlPackage.exe). The SQL Server database project (targeting SQL Server 2014) builds without error, but when we attempt to deploy the .dacpac to the target server using SqlPackage.exe, we get

问题 Looking for a workaround for: Error: SQL71609: System-versioned current and history tables do not have matching schemes. Mismatched column: 'XXXX'. When trying to use SQL 2016 System-Versioned (Temporal) tables in SSDT for Visual Studio 2015. I've defined a basic table: CREATE TABLE [dbo].[Example] ( [ExampleId] INT NOT NULL IDENTITY(1,1) PRIMARY KEY, [ExampleColumn] VARCHAR(50) NOT NULL, [SysStartTime] datetime2 GENERATED ALWAYS AS ROW START HIDDEN NOT NULL, [SysEndTime] datetime2 GENERATED

问题 The problem I want to solve is to build different scripts depending on build configuration. Say we have two instances of SQL Server: Enterprise version with connected Linked servers LocalDb version for offline developing and unit tests Enterprise version has views for Linked servers when LocalDB substitues those views with local tables. Those Linked Server views and local tables have the same names and set of fields. So they are not included in build by default (Build Action = None). Instead

问题 I have create a report using visual studio 2015 with SSDT Tools installed from the following link https://msdn.microsoft.com/en-us/mt186501 The database is on SQL Server 2014. The reports work on my machine however when I try to upload a report on customers machine(Which has SQL Server 2014 and not visual studio). I get the following error "The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later

问题 According to this answer, SQL Server Data Tools uses a private LocalDB instance ProjectsV13, which you're not supposed to use for your own applications. Instead, you should use MSSQLLocalDB or your own private instance. Is this documented anywhere? What does SSDT use its private instance for? (I don't see anything in mine.) Is a private LocalDB instance basically spinning up a second copy of SQL Server? On the surface, it sounds rather resource intensive to have a dedicated database engine

问题 This is my first experience with SSIS so bear with me... I am using SSIS to migrate tables from Oracle to SSMS, there are some very large tables I am trying to transfer (50 million rows +). SSIS is now completely freezing up and rebooting VS when I am just trying to save the package (not even running it). It keeps returning errors of insufficient memory, however, I am working on a remote server that has well over the RAM it takes to run this package. Error Message when trying to save The only

问题 Using Visual Studio 2013 I have a set of 8 SSDT projects that can all be deployed to several distinct environments. The advanced publish settings for each project, however, are meant to be identical. At present I have created a distinct publish profile for each environment, meaning I have ~20 publish profiles all using the exact same settings but different connection strings. Tweaking the publish settings (which happens with some regularity as I am still a bit new to SSDT) for my databases is