BIML Question - Copy SSIS-Solution

  • Hi,

    i have searched some times and i doesn't find any solution for my problem.

    Infos: I have a solution which runs perefect. Now we use this solutions to get data from another source.
    But the tables and so on are all indenitcally with the actual package.

    Is it possible to copy the dtsx-files with biml and rename only the connections?

  • PowerUser - Tuesday, July 18, 2017 1:56 AM

    Hi,

    i have searched some times and i doesn't find any solution for my problem.

    Infos: I have a solution which runs perefect. Now we use this solutions to get data from another source.
    But the tables and so on are all indenitcally with the actual package.

    Is it possible to copy the dtsx-files with biml and rename only the connections?

    Did you use BIML to generate the original packages? If not, I don't think so.
    Are your packages deployed to SSISDB? If so, why not just reconfigure the connections using SSISDB environment variables?

    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.

  • Ah - okay. I was not sure if my idea whit BIML is possible 🙂

    SSISDB is a good idea. My last problem is, that the new solution needs a new schema name.
    And the first solution doesn't have the parameter for a schema 🙁

    I think i will edit each package with an editor and rename the solution, or is there another easier solution possible?

  • PowerUser - Wednesday, July 19, 2017 2:12 AM

    Ah - okay. I was not sure if my idea whit BIML is possible 🙂

    SSISDB is a good idea. My last problem is, that the new solution needs a new schema name.
    And the first solution doesn't have the parameter for a schema 🙁

    I think i will edit each package with an editor and rename the solution, or is there another easier solution possible?

    Without knowing how it's all engineered, I can't say for sure.
    If all of the packages were in the same project, for example, they could potentially share the same connection (defined at the project level). Changing such a connection would need to be done only once.
    But if the packages have been developed separately, you'll have to edit them all.

    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.

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

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