Skip to main content
New: Stack Overflow For Agents. The next generation of knowledge exchange. Learn more
Filter by
Sorted by
Tagged with
Filter by Employee ID
0 votes
0 answers
47 views

Without VS 2026 tooling for new SDK-style sqlproj and VS 2022 tooling still being preview and incompatible with legacy SSDT, I am left with having to maintain some legacy old-sqlproj projects. I want ...
Ivan Petrov's user avatar
1 vote
0 answers
110 views

When I run a schema compare in Rider in the new SDK-style .sqlproj format where the [$(DatabaseName)] value is in the *.sql code and the resolved database name is in the database side, it still ...
devlord's user avatar
0 votes
0 answers
71 views

I’m deploying a SQL Server/Azure SQL database using an SSDT .sqlproj (DACPAC) and SqlPackage.exe (DacFx publish). For local dev we require DropObjectsNotInSource=True so schema drift/renames are ...
Rob C's user avatar
0 votes
0 answers
109 views

I'm building a selfhosted github runner image using a docker file. When we run a github actions build on this runner I get the following error: MSBuild auto-detection: using msbuild version '18.0.5....
checkcomparemeerkat's user avatar
1 vote
0 answers
182 views

Is it possible to use non hard-coded values for asserting scalar values in VS SQL Server unit test project? Below I have the variable @ResourceId that I'd like to test against the value of a column ...
user32056484's user avatar
0 votes
0 answers
107 views

We have a SQL Server Data Tools (SSDT) Visual Studio database project, and we deploy the DACPAC output using DacFx + PowerShell scripts. In this project, we enable: Database-level change tracking via ...
Indi's user avatar
0 votes
1 answer
204 views

I am able to create an SSDT solution, with projects, and build in VS Pro 2022 without any issues. However, when I do the same in VS Code, I get the following warning: Restore succeeded with 1 warning(...
J Weezy's user avatar
0 votes
1 answer
86 views

Currently all of our SSDT packages have been created with SQL Server Data Tools 2015 We are looking to upgrade to SSDT 2022. I installed Visual Studio 2022 with the following selected during setup: ...
JetRocket11's user avatar
0 votes
1 answer
87 views

I have a scenario where my SSDT project needs to reference a second database via Dacpac, but the destination schema could change per environment. In the example below I have my primary database with a ...
Sam Alex's user avatar
-1 votes
1 answer
187 views

We have a Visual Studio SQL server data tools solution with multiple databases for an on-premise database server. Our datawarehouse database references many of the source databases which have been ...
Koen van Wielink's user avatar
0 votes
0 answers
170 views

We have hundreds of SSIS packages created with Visual Studio 2015 and currently they all run perfectly fine through batch commands that execute the following: C:\Program Files (x86)\Microsoft SQL ...
JetRocket11's user avatar
0 votes
0 answers
219 views

To create Integration Service packages before, I could set up the development environment without caring about Visual Studio edition. Because the shell copy of Visual Studio 2017 was apparently ...
saya24's user avatar
-1 votes
2 answers
2k views

I am in the process of updating our local instance to SQL Server 2022. I have all of the SQL Server configuration done, but I am having problems getting our SSIS packages to open in Visual Studio and ...
Scotty Smith's user avatar
0 votes
1 answer
192 views

I can't upload the Image to SO for some reason so see the imgur screenshot here#1 and here#2 and here#3. [edit] In 3rd example, the only diff emphasis is on the keyword CREATE (casing problem) while ...
CodeAngry's user avatar
0 votes
1 answer
57 views

I have setup a connection to my local SQL Server, over the "SQL Server Object Explorer" in Visual Studio. Is there a way, built in or maybe with an extension, for setting the focus to a ...
Dom84's user avatar

15 30 50 per page
1
2 3 4 5
139