sql-server-data-tools

How to build .sqlproj projects on a build server?

元气小坏坏 提交于 2019-11-28 03:34:05
I have many .sqlproj projects that need to be built on our build server. I don't want to install all of Visual Studio on the build server just so I can install SSDT to build these. How can I build .sqlproj projects without a full VS install? Here's the raw error I get on the build server when trying to build without SSDT intstalled: C:\MyProject\MyProj.sqlproj (4): The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file

VS 2012 Database Project “unresolved reference to object” Error

与世无争的帅哥 提交于 2019-11-27 21:59:35
问题 I created SQL Server Database Project in VS 2012 & imported our database. When I build the project, I get a lot of "unresolved reference to object" Errors. These errors are only for a few views I have in my database. The syntax for these views are correct & I am not using temp tables. What should I check to solve this issue? UPDATE: This is one example: CREATE view [Factory].[NonStartedOrders] as SELECT "Customers"."CustomerName", "Customers"."CustomerAName", "Customers"."MarketID", "Orders".

Visual Studio 2013 incompatibility with MS SQL Server 2014

做~自己de王妃 提交于 2019-11-27 21:16:34
I downloaded MS SQL Server 2014 Enterprise Edition from MSDN. I want to do a server backend in C# and MS SQL, but the problem is, whenever I want to do something with DB in Visual Studio 2013 Ultimate it just tells me this =================================== An incompatible SQL Server version was detected. (Microsoft.VisualStudio.Data.Tools.SqlEditor) ------------------------------ Program Location: at Microsoft.VisualStudio.Data.Tools.SqlEditor.DataModel.SqlConnectionStrategy.ValidateConnectionForEditor(UIConnectionInfo ci, IServerType server) at Microsoft.SqlServer.Management.UI

Deploy SQL Server database project (SSDT) via command line

久未见 提交于 2019-11-27 19:33:05
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. Keith Use sqlpackage.exe , located in C:\Program Files\Microsoft SQL Server\{version}\DAC\bin or C:\Program Files (x86)

Publish DACPAC to SQL Server 2014 using SqlPackage.exe?

前提是你 提交于 2019-11-27 18:22:26
I've been successfully publishing DACPACs to SQL Server 2008-2012 instances using SqlPackage.exe, as installed by SQL Server Data Tools (and typically found in C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin ). However, in attempting to publish a 2014-targeted DACPAC to a SQL Server 2014 instance using this same SqlPackage.exe, I get the following: *** Could not deploy package. Internal Error. The database platform service with type Microsoft.Data.Tools. Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type

Prevent dropping of users when publishing a DACPAC using SqlPackage.exe

让人想犯罪 __ 提交于 2019-11-27 15:04:17
问题 Is there any way of preventing users being dropped when publishing a DACPAC using SqlPackage.exe, other than changing the setting below, which prevents all objects from being dropped if they're not in the DACPAC. <DropObjectsNotInSource>True</DropObjectsNotInSource> We deploy to a number of environments, each with different users. Current workarounds are to either: Script the users for each environment to recreate them after deploying Use /Action:Script and manually change the deployment

Visual Studio 2017 does not have Business Intelligence Integration Services/Projects

五迷三道 提交于 2019-11-27 13:30:56
问题 I do not see an option to create an SSIS project using Visual Studio 2017. 回答1: VS2017 supports ssis or ssrs projects if you install SSDT for VS2017 here. Click on the newly downloaded file and check SSIS or SSRS components that you required, as show in diagram :- Once you have installed this, try opening ssis / ssrs project. I managed to open ssis developed on vs2010. You should see these component installed. (reboot if you don't see them). Try open your project again. If you get

SSDT installation issue (Failed to execute EXE package.)

ぃ、小莉子 提交于 2019-11-27 07:23:57
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][2017-09-26T09:28:00]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress:

Can SQL Server Data Tools work with SQL Server 2008 SSIS?

我的梦境 提交于 2019-11-27 06:40:03
问题 Can I use the new SQL Server Data Tools that come with SQL Server 2012 to create SSIS packages for SQL Server 2008? I work with both SQL Server 2008 and SQL Server 2012 and I am wondering if I can use SSDT to create and maintain SSIS on both. 回答1: No. See problem with deploying ssis 2010 package It seems that the backward compatibility offered by SSDT does not apply to SSIS. 回答2: Everyone wants a smooth integration process that will allow for proficient system performance. In theory, the SQL

unresolved reference to object [INFORMATION_SCHEMA].[TABLES]

。_饼干妹妹 提交于 2019-11-27 06:31:20
I've created a UDF that accesses the [INFORMATION_SCHEMA].[TABLES] view: CREATE FUNCTION [dbo].[CountTables] ( @name sysname ) RETURNS INT AS BEGIN RETURN ( SELECT COUNT(*) FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = @name ); END Within Visual Studio, the schema and name for the view are both marked with a warning: SQL71502: Function: [dbo].[CountTables] has an unresolved reference to object [INFORMATION_SCHEMA].[TABLES]. I can still publish the database project without any problems, and the UDF does seem to run correctly. IntelliSense populates the name of the view for me, so it doesn't