We have a C# web project authored in Visual Studio 2013 which incorporates a Database Project, and I've set up a number of TeamCity build configurations to do Continuous Integration.
Team City is working well for us at the moment with all of our code checkins going automatically into the integration environment.
SSDT is also working well for us, we are easily able to share and publish database changes within the development team.
What I want to do now is get TeamCity to automatically build the Database Project and deploy it into the integration environment.
We do not have VS2013 on the build server, and would rather not install it there. We are all running SQL Server 2012.
I have read a few questions and articles about "headless" builds of *.sqlproj projects e.g:
How to build .sqlproj projects on a build server?
These approaches seem to be quite manual and fiddly and related to SSDT 2012 - has anyone got a reliable configuration for the versions we're using?
If Visual Studio 2022 is already installed, you can edit the list of workloads to include SSDT. If you don't have Visual Studio 2022 installed, then you can download and install Visual Studio 2022. To modify the installed Visual Studio workloads to include SSDT, use the Visual Studio Installer.
The SQL Server Data Tools (SSDT) is where you'll spend most of your time as an SSIS developer. It is where you create and deploy your SSIS projects. SSDT uses a subset of the full version of Visual Studio 2013.
Click File, New, then Project. In the New Project dialog box, select SQL Server in the left pane. Notice that there is only one type of database project: the SQL Server Database Project. There is no platform-specific project as in previous versions of Visual Studio.
Generally, It is required to install sql server database with visual studio setup. Here are the steps to install sql server database with setup using custom action. 1. In Solution Explorer, select the project.
We've got SSDT working on our build server without requiring a copy of Visual Studio. In our case, we did a full install of SSDT because that will give you the necessary components, including the Visual Studio IDE shell. It was also a bit less fiddly than trying to make the admin install point and install just those bits. We added the folder containing sqlpackage to the path and made sure that we could get to the latest MSBuild executable (part of the .NET framework). There's no need to install a full copy of Visual Studio unless you happen to need it for some other reason on that machine.
This article goes into a bit more detail: http://sqlproj.com/index.php/2012/03/headless-msbuild-support-for-ssdt-sqlproj-projects/
Summarizing that article, here's what you need:
It's been a while, but you might be able to just make sure that machine is connected to the Internet and run the latest SSDT installer to install SSDT and all of the pre-reqs. At that point, you've got the necessary bits to build SQL Projects.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With