Split SSIS project in to multiple files to avoid merge hellHow to avoid log space error while executing SSIS...

How do I make my single-minded character more interested in the main story?

Was the Spartan by Mimic Systems a real product?

Is Developer Console going to be deprecated?

Multiple null checks in Java 8

Sets which are both Sum-free and Product-free.

What is the reward?

When distributing a Linux kernel driver as source code, what's the difference between Proprietary and GPL license?

Does しかたない imply disappointment?

What sort of grammatical construct is ‘Quod per sortem sternit fortem’?

How can I prep for the Curse of Strahd adventure effectively?

Graphical modeler calculator missing in QGIS3

Expression for "unconsciously using words (or accents) used by a person you often talk with or listen to"?

Why does this quiz question say that protons and electrons do not combine to form neutrons?

What does @ mean in a hostname in DNS configuration?

Identical projects by students at two different colleges: still plagiarism?

How can I give a Ranger advantage on a check due to Favored Enemy without spoiling the story for the player?

What does "don't have a baby" imply or mean in this sentence?

Why don't you get burned by the wood benches in a sauna?

SQL Server Service does not start automatically after system restart

In the Lost in Space intro why was Dr. Smith actor listed as a special guest star?

Why do single electrical receptacles exist?

Is it possible to detect 100% of SQLi with a simple regex?

Why write a book when there's a movie in my head?

Is Screenshot Time-tracking Common?



Split SSIS project in to multiple files to avoid merge hell


How to avoid log space error while executing SSIS packages?Importing Excel files with SSISSQL Server split mdf into multiple filesSSIS FTP Sending Blank FilesSSIS Failed to start projectIntroduce or not introduce SSIS to an ETL projectConditionally move files in SSISExecuting SSIS Package from a stored procedure with different user privilegesHow does SSIS Balanced Data Distributor decide to split records?How to read data from multiple Excel files with SQL Server Integration Services(New Senario)













2















Since SSIS does not like being merged nicely I was wondering how to have a big SSIS package split up. With the idea of having multiple devs working on this simultaneously, and a minimal chance of having merge conflicts.



In SSIS 2016 I found these options:





  • package parts, but apparently they don't share connection managers. I don't want to have 100 different connection managers.


  • subpackages, still this doesn't look very clean and I also wonder if this is what it is intended for. Also, the debugger goes crazy too opening the subpackages while running. Any other drawbacks I should know of?


I can't be the only person with this problem. Is there an other way to achieve this?










share|improve this question
















bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • I suggest that if your package is that big then you need to work out how to logically break it into multiple packages. This doesn't help with deployment but does help with development. You can also break a package up by moving functionality into the database (i.e. calling stored procedures), and this is often faster.

    – Nick.McDermaid
    Jan 23 '17 at 1:35











  • Have you looked at BIDShelper and it's Smartdiff?

    – Tom V
    May 6 '17 at 12:25


















2















Since SSIS does not like being merged nicely I was wondering how to have a big SSIS package split up. With the idea of having multiple devs working on this simultaneously, and a minimal chance of having merge conflicts.



In SSIS 2016 I found these options:





  • package parts, but apparently they don't share connection managers. I don't want to have 100 different connection managers.


  • subpackages, still this doesn't look very clean and I also wonder if this is what it is intended for. Also, the debugger goes crazy too opening the subpackages while running. Any other drawbacks I should know of?


I can't be the only person with this problem. Is there an other way to achieve this?










share|improve this question
















bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • I suggest that if your package is that big then you need to work out how to logically break it into multiple packages. This doesn't help with deployment but does help with development. You can also break a package up by moving functionality into the database (i.e. calling stored procedures), and this is often faster.

    – Nick.McDermaid
    Jan 23 '17 at 1:35











  • Have you looked at BIDShelper and it's Smartdiff?

    – Tom V
    May 6 '17 at 12:25
















2












2








2


1






Since SSIS does not like being merged nicely I was wondering how to have a big SSIS package split up. With the idea of having multiple devs working on this simultaneously, and a minimal chance of having merge conflicts.



In SSIS 2016 I found these options:





  • package parts, but apparently they don't share connection managers. I don't want to have 100 different connection managers.


  • subpackages, still this doesn't look very clean and I also wonder if this is what it is intended for. Also, the debugger goes crazy too opening the subpackages while running. Any other drawbacks I should know of?


I can't be the only person with this problem. Is there an other way to achieve this?










share|improve this question
















Since SSIS does not like being merged nicely I was wondering how to have a big SSIS package split up. With the idea of having multiple devs working on this simultaneously, and a minimal chance of having merge conflicts.



In SSIS 2016 I found these options:





  • package parts, but apparently they don't share connection managers. I don't want to have 100 different connection managers.


  • subpackages, still this doesn't look very clean and I also wonder if this is what it is intended for. Also, the debugger goes crazy too opening the subpackages while running. Any other drawbacks I should know of?


I can't be the only person with this problem. Is there an other way to achieve this?







sql-server ssis visual-studio development






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 6 '17 at 14:10









B.lahm

77




77










asked Jan 19 '17 at 10:47









Sam SegersSam Segers

1114




1114





bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • I suggest that if your package is that big then you need to work out how to logically break it into multiple packages. This doesn't help with deployment but does help with development. You can also break a package up by moving functionality into the database (i.e. calling stored procedures), and this is often faster.

    – Nick.McDermaid
    Jan 23 '17 at 1:35











  • Have you looked at BIDShelper and it's Smartdiff?

    – Tom V
    May 6 '17 at 12:25





















  • I suggest that if your package is that big then you need to work out how to logically break it into multiple packages. This doesn't help with deployment but does help with development. You can also break a package up by moving functionality into the database (i.e. calling stored procedures), and this is often faster.

    – Nick.McDermaid
    Jan 23 '17 at 1:35











  • Have you looked at BIDShelper and it's Smartdiff?

    – Tom V
    May 6 '17 at 12:25



















I suggest that if your package is that big then you need to work out how to logically break it into multiple packages. This doesn't help with deployment but does help with development. You can also break a package up by moving functionality into the database (i.e. calling stored procedures), and this is often faster.

– Nick.McDermaid
Jan 23 '17 at 1:35





I suggest that if your package is that big then you need to work out how to logically break it into multiple packages. This doesn't help with deployment but does help with development. You can also break a package up by moving functionality into the database (i.e. calling stored procedures), and this is often faster.

– Nick.McDermaid
Jan 23 '17 at 1:35













Have you looked at BIDShelper and it's Smartdiff?

– Tom V
May 6 '17 at 12:25







Have you looked at BIDShelper and it's Smartdiff?

– Tom V
May 6 '17 at 12:25












1 Answer
1






active

oldest

votes


















0














I've been using subpackages successfully on multiple projects. The typical scope is one sub-package per target table. I also have a few utility packages eg Disable Indexes, Rebuild Indexes (on a table, passed as a parameter). A single "Master Control Package" is mostly Execute Package tasks.



With the Project Deployment method, devs need to be aware that prematurely checking in their changes to a single package can block the deploy (it wont deploy a project until all the packages validate cleanly).






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "182"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f161584%2fsplit-ssis-project-in-to-multiple-files-to-avoid-merge-hell%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I've been using subpackages successfully on multiple projects. The typical scope is one sub-package per target table. I also have a few utility packages eg Disable Indexes, Rebuild Indexes (on a table, passed as a parameter). A single "Master Control Package" is mostly Execute Package tasks.



    With the Project Deployment method, devs need to be aware that prematurely checking in their changes to a single package can block the deploy (it wont deploy a project until all the packages validate cleanly).






    share|improve this answer




























      0














      I've been using subpackages successfully on multiple projects. The typical scope is one sub-package per target table. I also have a few utility packages eg Disable Indexes, Rebuild Indexes (on a table, passed as a parameter). A single "Master Control Package" is mostly Execute Package tasks.



      With the Project Deployment method, devs need to be aware that prematurely checking in their changes to a single package can block the deploy (it wont deploy a project until all the packages validate cleanly).






      share|improve this answer


























        0












        0








        0







        I've been using subpackages successfully on multiple projects. The typical scope is one sub-package per target table. I also have a few utility packages eg Disable Indexes, Rebuild Indexes (on a table, passed as a parameter). A single "Master Control Package" is mostly Execute Package tasks.



        With the Project Deployment method, devs need to be aware that prematurely checking in their changes to a single package can block the deploy (it wont deploy a project until all the packages validate cleanly).






        share|improve this answer













        I've been using subpackages successfully on multiple projects. The typical scope is one sub-package per target table. I also have a few utility packages eg Disable Indexes, Rebuild Indexes (on a table, passed as a parameter). A single "Master Control Package" is mostly Execute Package tasks.



        With the Project Deployment method, devs need to be aware that prematurely checking in their changes to a single package can block the deploy (it wont deploy a project until all the packages validate cleanly).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 22 '17 at 23:32









        Mike HoneyMike Honey

        24615




        24615






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f161584%2fsplit-ssis-project-in-to-multiple-files-to-avoid-merge-hell%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

            Always On Availability groups resolving state after failover - Remote harden of transaction...

            update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...