sql-server-data-tools

Having recently upgraded to SSDT 2012 I seem to be missing the option to just generate a T-SQL script instead of deploying the database to a server somewhere. To be more accurate the predecessor to SSDT used to set the Deploy action to 'Generate script', but I cannot locate that option anywhere in the new version. Is it possible? To generate a script from an offline data project in SSDT rather than deploy to a target database, configure the project settings as shown below You may want to look at the SQLPackage command line. You can set the options there to use an action of "script" and specify

I have a database project in a solution which will not deploy from Visual Studio 2013. It fails with an error message "Unable to connect to target server" . The same project, when opened in Visual Studio 2012 deploys without an issue. The database is Sql 2012 hosted in a Sql 2014 engine (express) The deployment settings are thus (with names changed to protect the innocent): <?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="12.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <PropertyGroup> <IncludeCompositeObjects>True</IncludeCompositeObjects> <TargetDatabaseName

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 version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting

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 just for tooling metadata. How resource intensive is this really? Does it have a perf impact on starting

I am new using SSIS and want to create a script to connect to a Mongo DB, for this purpose I am trying to add a reference to a MongoDB driver as explained here Unfortunately I don't see a way to do so, in the solution explorer, there is no Reference node Could you please point how to add a reference to my script in this project? After trying different solutions I tried the following: Uninstall SSDT and Reboot Downloaded this version 15.8.2 from here Install SSDT selecting my version of Visual Studio and finally it worked: Followed some of the steps explained here . 来源： https://stackoverflow

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 most annoying, but I have yet to find a way around this as I am unable to apply transforms to publish

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 thing I can think of is when this package is attempting to run, my Ethernet Kbps are through the roof

After installing Visual Studio 2012 Ultimate on Windows 8, SSDT via SQL Server Object Explorer did not work. The solution was to install the latest version of VS2012 from the MSDN website. All was well. I could see databases, no problem. It did not matter whether I used the EF defaultConnectionFactory or my own connectionString, either way, all of my code first databases showed up in the VS2012 SQL Server Object Explorer. Not long ago, I installed Visual Studio 2013 Ultimate. In VS2013 Ultimate, local db, all I see, via properties, is this connection string: Data Source=(localdb)\Projects;