SSIS 2014 Project deployment using TFS

Question

SSIS 2014 Project deployment using TFS

sunil.mvs

Ten Centuries

Points: 1031
More actions
June 15, 2016 at 7:40 pm

#327175

we have started new team of datawarehouse in our company.
Team started working on SQL Server 2014 and TFS .
They developed packages using project deployment instead of package deployment model.
Following are the use cases
1) Now we would like to branch SSIS project as development and production .
When SSIS project is tested successfully , we would like to move/update project to Production folder .
2) Under development folder , if two developers are working on same project but different packages . Then how developers can concurrently work on same project and move projects to production
Thanks
Surya sunil

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

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

Phil Parkin SSC Guru Points: 246686 More actions · Answer 1

What problem are you having?

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Lowell SSC Guru Points: 323504 More actions · Answer 2

sunil.mvs (6/15/2016)
we have started new team of datawarehouse in our company.
Team started working on SQL Server 2014 and TFS .
They developed packages using project deployment instead of package deployment model.
Following are the use cases
1) Now we would like to branch SSIS project as development and production .
When SSIS project is tested successfully , we would like to move/update project to Production folder .

you would simply change the deployment target, right?

2) Under development folder , if two developers are working on same project but different packages . Then how developers can concurrently work on same project and move projects to production

That is the beauty of TFS, or any change control system. i can edit package1 and add package4, and you can edit package2 and add package3 (which is noted in the project) , and since we both mademodifications to the project, it helps you merge those changes.

Thanks

Surya sunil

[/quote]

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

sunil.mvs Ten Centuries Points: 1031 More actions · Answer 3

Hi,

Thanks for looking into my question. I am rephrasing my question to make you to understand

How to use TFS , to manage SQL server Integration Services (SSIS) where deployment mode is project.

How to define branching and merging project packages ,so that we can do smooth transition from Development to release.

Let me know , if you are not clear .

Phil Parkin SSC Guru Points: 246686 More actions · Answer 4

sunil.mvs (6/17/2016)
Hi,
Thanks for looking into my question. I am rephrasing my question to make you to understand
How to use TFS , to manage SQL server Integration Services (SSIS) where deployment mode is project.
How to define branching and merging project packages ,so that we can do smooth transition from Development to release.
Let me know , if you are not clear .

If you have changed package A on branch A and another dev has changed package A on branch B, that is another problem. I do not recommend that you try to merge changes to the same package, rather, I suggest that you treat packages as executable code.

But in the scenario where dev A is working on package A in branch A and

dev B is working on package B in branch B

a merge is perfectly feasible. The one thing to watch when doing such merges is the project file: it needs to reference both packages. If package B in branch B is a new package, the merge will need to include the package file and the modification to the project file.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.