Package to Project model conversion

Question

Package to Project model conversion

blom0344

SSCrazy

Points: 2235
More actions
November 18, 2024 at 12:00 pm

#4485350

Hi All,
With previous customer range we were always required to work in the traditional package model approach were individual packages were stored in deployment folders and combined with configuration files. (Usually old 2008R2 SQL server versions)
For my current employee I have the liberty to setup everything from scratch using newest versions of everything.
This involves development on a separate development server and I am trying to setup the project model using SSISDB database to store metadata in that repository.
To simplify matters I kept things like naming and paths identical between development and production and now looking for the easiest way to deploy from development to production.
Is there a best practice to follow for this more modern approach?
November 18, 2024 at 12:20 pm

This was removed by the editor as SPAM

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Thom A SSC Guru Points: 99133 More actions · Answer 1

Deploying to your production environment is no different to your development one; you can do this from your project in Visual Studio. Why do you feel it would be different?

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

blom0344 SSCrazy Points: 2235 More actions · Answer 2

I do not feel that it would be different. I have no experience with this type of deployment, hence my question. If development and production would not be identical, then I would imagine that simply deploying would not be enough.

More or less comparable with configuration files being different between development and production when working with the earlyest package model .

Phil Parkin SSC Guru Points: 246979 More actions · Answer 3

Use environment variables to control the values of connection strings and other parameters which vary between environments.

Here is a link to get you started: https://www.mssqltips.com/sqlservertip/4810/setup-environment-variables-in-sql-server-integration-services/

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

Thom A SSC Guru Points: 99133 More actions · Answer 4

You can also make use of Project/Package Parameters and link their values to the configuration you are working in within VS. Coincidentally, I wrote something for Phil on this a few years ago.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk