sql-server-data-tools

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

问题 I'm trying to deploy a DACPAC to LocalDB 2012 but it's just not having it: Stack trace is as follows: ================================== Could not deploy package. (Microsoft.SqlServer.Dac) ------------------------------ Program Location: at Microsoft.SqlServer.Dac.DeployOperation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context) at Microsoft.SqlServer.Dac.OperationExtension.Execute(IOperation operation, Action`2 reportStatus, CancellationToken cancellationToken) at Microsoft

问题 I need to be able to publish an SSDT project programmatically. I am looking at using Microsoft.Build to do so but can not find any documentation. It seems pretty simple to create the .dacpac, but how would I either publish to an existing database or at the very least to a .sql file. The idea is to have it do what it does when I right click on the project and select publish. It should compare with a selected database and generate an upgrade script. This is what I have so far to create the

问题 I have a SQL Server Database Project targeting a SQL Server 2012 RC0 database. The project was created in Visual Studio 2010 + SQL Server Data Tools CTP4. The project type is different than the regular Visual Studio 2010 database projects (it's the next version of SQL Developer Tools CTP3 Juneau). It deploys fine in the IDE. How can I deploy it via the command line? I tried VSDBCMD.exe but it expects a .deploymanifest file which is not created by the new project type. 回答1: Use sqlpackage.exe

问题 I am having an issue with the SSDT installation for VS2017. I have ran the installer three times, once basic, once following VS update and the last following some minor windows updates. All 3 times the logs stumble at the same point, anyone know what this .exe it is trying to run is (I am running the installer with Admin...). I read somewhere for a similar error that it might be the SDK but I am able to run this locally, any nice workarounds to having this installed out there? [29BC:A138]

问题 I am running SQL Server 2014 on my machine. I have installed SSDT for Visual Studio 2017, which I also have. Now I am not able to find the SSIS Toolbox in my Visual Studio. Do I need to re-install the SSDT all over again? Please let me know. Thanks in advance. 回答1: If SSDT is installed correctly You can show SSIS toolbox in 3 ways: (1) Visual Studio Menu strip Based on this Microsoft article: If you can't see the toolbox, go to VIEW -> Other Windows -> SSIS Toolbox. (2) From Context Menu

问题 I am working on an SSIS package that loads data from a CSV file into a staging table in SQL Server. The CSV file will be in the following format: FILENAME_YYYYMMDD_HHMMSS.csv The YYMMDD portion will always correspond to yesterday's date, but the HHMMSS piece will vary depending on exactly when the CSV file was created. Is there a way to use a script component in SSIS to do the following: Check to see if there was a file written yesterday (YYYYMMDD = yesterday's date) If so, store the full

问题 I wondered if someone could perhaps help save my sanity by telling me what I'm missing here. The background first. We have 5 database projects in TC, each with a build step and then a deploy step. 4 out of these 5 projects build and deploy perfectly. The 5th however build ok but then raises the following error during deployment to the its SQL Server; "*** An error occurred during deployment plan generation. Deployment cannot continue." The Element or Annotation class

问题 I right-clicked on a column name in a CREATE TABLE script and selected Refactor | Rename. It renamed the column and the expected entry appears in the refactorlog XML file. However, when I run a Schema Comparison from my project to my database and then generate the script, the script contains no mention of a refactoring and wants to drop the existing column name and add it with the new name. I have no _RefactorLog table in this database. The deployment script does not attempt to create one. It

问题 Overall, I am looking for feedback regarding two different design options of running a master package. I have one package that Agent calls that runs a bunch of packages that process data (I think we are up to about 50 now). The original design was to group packages into smaller chunks called directorates which call the actual packages. Sample below: A few perceptions I see (and experienced) with this approach is that: 1. Every package has to open (even if it is unnecessary to run ie no file