November 18, 2024 at 12:00 pm
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
November 18, 2024 at 2:11 pm
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
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply