sql-server-data-tools

问题 I am attempting to install SSDT v15.6.0 into an existing Visual Studio Team Explorer 2017 instance. When I run the SSDT installer, I can select Visual Studio Team Explorer 2017 from this list of existing Visual Studio instances. If I do not choose a any options (other than the required SQL Server Database option). The installation completes successfully. If I however attempt to pick any/all of the other options the installation fails. From looking at the log files, it appears that the

来源： https://stackoverflow.com/questions/57998844/ssis-acquires-connection-at-design-time-but-fails-during-debug-on-same-machine

问题 I am getting an error when using SSDT 2010 (latest updates, v10.3.21208.0) with multiple database projects in a single solution. The error reads the following: SQL71561: View: [dbo].[View] has an unresolved reference to object [OtherDatabase].[dbo].[OtherTable] I've read all the other resources I could find on Stack Overflow and Google. Here are some things I've already tried: Setup Database References to the other projects within the solution. Cleared out the Database variable option to

问题 I am building DacPac file from a database project using Visual Studio. Also, in the Debug Drop tab in Advanced Build Settings , I enabled the following options: Do not drop credentials Do not drop database roles Do not drop database scoped credentials Do not drop logins Do not drop permissions Do not drop role membership Do not drop users Do not drop server role membership Still, I get the following error in CD SQL Deploy: EDIT based on the advice of Krzysztof Madej, I have put the following

问题 I am using SQLPackage.exe utility together with Database project's publish profiles to run changes to the SQL Server database. From my understanding, this is the deployment process: Pre-Deployment Script Main Deployment Post-Deployment Script I have "Include transactional scripts" option checked in the publish profile advanced settings, however, that seems to apply to Main Deployment section only. My questions is: If Main deployment fails, is Pre-Deployment script committed? As well as, if

问题 I have many temporal tables in my SQL Server database project. Today I upgrade my SSDT to the latest version and I got the following errors for temporal tables when building the project. For example, I have a temporal table UseCase which has a history table called UseCase_HISTORY. It looks like a code analysis problem. If I disable the code analysis on build, there will be no errors on build. I am using VS2015 and VS2017. Both have the same problems. C:\Program Files (x86)\Microsoft Visual

问题 I have many temporal tables in my SQL Server database project. Today I upgrade my SSDT to the latest version and I got the following errors for temporal tables when building the project. For example, I have a temporal table UseCase which has a history table called UseCase_HISTORY. It looks like a code analysis problem. If I disable the code analysis on build, there will be no errors on build. I am using VS2015 and VS2017. Both have the same problems. C:\Program Files (x86)\Microsoft Visual

问题 I have a SSIS package that talks to a remote server over HTTP. I execute the SSIS package using a stored procedure in my database (SQL Server 2012), which is called from a web server. The web server connects to the database using Windows Authentication. I now have a need to run the stored procedure (and therefore, the SSIS package) from a client which does not support Windows Authentication. The SSIS package is complicated enough that migrating to a different solution is not feasible. The

问题 We have an SSDT project which includes users, roles and permissions. It was working very nicely, but a recent move to Azure has caused, or possibly highlighted, a problem with deployment. Before Azure, certain project members had a user on the master db with sufficient permissions to publish databases. In Azure SQL Db, there is only one admin user, and those credentials shouldn't be shared around. So instead we thought we'd use sufficiently permissioned contained database users to publish.

问题 We have many SSIS imports in our environment all created with SQL / Visual Studio 2008 version. We run a lot of imports from SharePoint and for that we have been using SharePoint List Adapters that we got from CodePlex long time ago. It works great in SSIS 2008. However we are trying to upgrade all of our jobs to run with newer version and using SQL Server Data Tools 2015. I installed SQL Server Data Tools 2015 on the same machine as SQL Server 2008 Developer Tools. I am still able to use the