SQL Server SSIS: work as a team on the same data flow?
up vote
1
down vote
favorite
I am new to SSIS and I was wondering if it is possible at all to access someone else's work? For instance, if someone created a data flow in SSIS using their user on the server, and I log in as my user, can I access and edit their work?
I know that in other ETL tools like Informatica you need to check in/out the object/data flow you are working on. Is there something similar in place in SSIS?
sql-server ssis ssis-2012 asked Nov 9 at 15:15
vdvaxel
14011
|
show 1 more comment
up vote
1
down vote
favorite
I am new to SSIS and I was wondering if it is possible at all to access someone else's work? For instance, if someone created a data flow in SSIS using their user on the server, and I log in as my user, can I access and edit their work?
I know that in other ETL tools like Informatica you need to check in/out the object/data flow you are working on. Is there something similar in place in SSIS?
sql-server ssis ssis-2012 asked Nov 9 at 15:15
vdvaxel
14011
SSIS has VSTS (Azure DevOps or whatever it was just renamed to last week) and GitHub integration natively. You can certainly import/export projects from your teammates (or SSISDB, or ispac file...) as well, but that's not nearly the same as a repository.
– Jacob H
Nov 9 at 15:24
Ok, but what if you're working in SSIS on the same server, but logged in as different users? Is there no way to open someone else's work?
– vdvaxel
Nov 9 at 15:33
Yes, as I said you can open the packages directly, or import the projects from SSISDB or using an ispac file. It depends on the deployment method. Assuming you have security rights to open them, of course. This is not the same as checking in and checking out a file, which was your question.
– Jacob H
Nov 9 at 15:34
1
Yes, it is possible. Just export and open: mssqlgirl.com/…
– Lukasz Szozda
Nov 9 at 15:35
1
And @LukaszSzozda has presented two ways. One importing from SSISDB (as I mentioned twice) and one by converting the ispac to a zip file and getting the packages directly. This assumes your deployment is in the SSISDB. Which we don't know. Hopefully this information is helping...
– Jacob H
Nov 9 at 15:36
|
show 1 more comment
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am new to SSIS and I was wondering if it is possible at all to access someone else's work? For instance, if someone created a data flow in SSIS using their user on the server, and I log in as my user, can I access and edit their work?
I know that in other ETL tools like Informatica you need to check in/out the object/data flow you are working on. Is there something similar in place in SSIS?
sql-server ssis ssis-2012 asked Nov 9 at 15:15
vdvaxel
14011
I am new to SSIS and I was wondering if it is possible at all to access someone else's work? For instance, if someone created a data flow in SSIS using their user on the server, and I log in as my user, can I access and edit their work?
I know that in other ETL tools like Informatica you need to check in/out the object/data flow you are working on. Is there something similar in place in SSIS?
sql-server ssis ssis-2012 sql-server ssis ssis-2012 asked Nov 9 at 15:15
vdvaxel
14011
asked Nov 9 at 15:15
vdvaxel
14011
asked Nov 9 at 15:15
vdvaxel
14011
asked Nov 9 at 15:15
vdvaxel
14011
asked Nov 9 at 15:15
vdvaxel
14011
14011
SSIS has VSTS (Azure DevOps or whatever it was just renamed to last week) and GitHub integration natively. You can certainly import/export projects from your teammates (or SSISDB, or ispac file...) as well, but that's not nearly the same as a repository.
– Jacob H
Nov 9 at 15:24
Ok, but what if you're working in SSIS on the same server, but logged in as different users? Is there no way to open someone else's work?
– vdvaxel
Nov 9 at 15:33
Yes, as I said you can open the packages directly, or import the projects from SSISDB or using an ispac file. It depends on the deployment method. Assuming you have security rights to open them, of course. This is not the same as checking in and checking out a file, which was your question.
– Jacob H
Nov 9 at 15:34
1
Yes, it is possible. Just export and open: mssqlgirl.com/…
– Lukasz Szozda
Nov 9 at 15:35
1
And @LukaszSzozda has presented two ways. One importing from SSISDB (as I mentioned twice) and one by converting the ispac to a zip file and getting the packages directly. This assumes your deployment is in the SSISDB. Which we don't know. Hopefully this information is helping...
– Jacob H
Nov 9 at 15:36
|
show 1 more comment
SSIS has VSTS (Azure DevOps or whatever it was just renamed to last week) and GitHub integration natively. You can certainly import/export projects from your teammates (or SSISDB, or ispac file...) as well, but that's not nearly the same as a repository.
– Jacob H
Nov 9 at 15:24
Ok, but what if you're working in SSIS on the same server, but logged in as different users? Is there no way to open someone else's work?
– vdvaxel
Nov 9 at 15:33
Yes, as I said you can open the packages directly, or import the projects from SSISDB or using an ispac file. It depends on the deployment method. Assuming you have security rights to open them, of course. This is not the same as checking in and checking out a file, which was your question.
– Jacob H
Nov 9 at 15:34
1
Yes, it is possible. Just export and open: mssqlgirl.com/…
– Lukasz Szozda
Nov 9 at 15:35
1
And @LukaszSzozda has presented two ways. One importing from SSISDB (as I mentioned twice) and one by converting the ispac to a zip file and getting the packages directly. This assumes your deployment is in the SSISDB. Which we don't know. Hopefully this information is helping...
– Jacob H
Nov 9 at 15:36
SSIS has VSTS (Azure DevOps or whatever it was just renamed to last week) and GitHub integration natively. You can certainly import/export projects from your teammates (or SSISDB, or ispac file...) as well, but that's not nearly the same as a repository.
– Jacob H
Nov 9 at 15:24
SSIS has VSTS (Azure DevOps or whatever it was just renamed to last week) and GitHub integration natively. You can certainly import/export projects from your teammates (or SSISDB, or ispac file...) as well, but that's not nearly the same as a repository.
– Jacob H
Nov 9 at 15:24
Ok, but what if you're working in SSIS on the same server, but logged in as different users? Is there no way to open someone else's work?
– vdvaxel
Nov 9 at 15:33
Ok, but what if you're working in SSIS on the same server, but logged in as different users? Is there no way to open someone else's work?
– vdvaxel
Nov 9 at 15:33
Yes, as I said you can open the packages directly, or import the projects from SSISDB or using an ispac file. It depends on the deployment method. Assuming you have security rights to open them, of course. This is not the same as checking in and checking out a file, which was your question.
– Jacob H
Nov 9 at 15:34
Yes, as I said you can open the packages directly, or import the projects from SSISDB or using an ispac file. It depends on the deployment method. Assuming you have security rights to open them, of course. This is not the same as checking in and checking out a file, which was your question.
– Jacob H
Nov 9 at 15:34
1
1
Yes, it is possible. Just export and open: mssqlgirl.com/…
– Lukasz Szozda
Nov 9 at 15:35
Yes, it is possible. Just export and open: mssqlgirl.com/…
– Lukasz Szozda
Nov 9 at 15:35
1
1
And @LukaszSzozda has presented two ways. One importing from SSISDB (as I mentioned twice) and one by converting the ispac to a zip file and getting the packages directly. This assumes your deployment is in the SSISDB. Which we don't know. Hopefully this information is helping...
– Jacob H
Nov 9 at 15:36
And @LukaszSzozda has presented two ways. One importing from SSISDB (as I mentioned twice) and one by converting the ispac to a zip file and getting the packages directly. This assumes your deployment is in the SSISDB. Which we don't know. Hopefully this information is helping...
– Jacob H
Nov 9 at 15:36
|
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228416%2fsql-server-ssis-work-as-a-team-on-the-same-data-flow%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
SSIS has VSTS (Azure DevOps or whatever it was just renamed to last week) and GitHub integration natively. You can certainly import/export projects from your teammates (or SSISDB, or ispac file...) as well, but that's not nearly the same as a repository.
– Jacob H
Nov 9 at 15:24
Ok, but what if you're working in SSIS on the same server, but logged in as different users? Is there no way to open someone else's work?
– vdvaxel
Nov 9 at 15:33
Yes, as I said you can open the packages directly, or import the projects from SSISDB or using an ispac file. It depends on the deployment method. Assuming you have security rights to open them, of course. This is not the same as checking in and checking out a file, which was your question.
– Jacob H
Nov 9 at 15:34
1
Yes, it is possible. Just export and open: mssqlgirl.com/…
– Lukasz Szozda
Nov 9 at 15:35
1
And @LukaszSzozda has presented two ways. One importing from SSISDB (as I mentioned twice) and one by converting the ispac to a zip file and getting the packages directly. This assumes your deployment is in the SSISDB. Which we don't know. Hopefully this information is helping...
– Jacob H
Nov 9 at 15:36