Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS - copyied original package, changed name, but still reading original dtsConfig file Expand / Collapse
Author
Message
Posted Monday, December 3, 2012 8:23 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 24, 2013 8:34 AM
Points: 5, Visits: 27
I have an SSIS package, that I did not write. It is used to transfer production data from a configurator to a production MRP system. I copied the origin QuoteTransfer.dts to QuoteTransferDEV.dts so that it would flow from development configurator package to development MRP system. However when I did that it still reads from the QuoteTransfer.dtsConfig rather than QuoteTransferDEV.dtsConfig. Does anyone have any suggestions? I checked all the variables, but I just don't see where it points to the file.

Thanks in Advance

Charles

SQL 2008
Post #1391973
Posted Monday, December 3, 2012 8:31 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, December 23, 2014 9:32 AM
Points: 5,490, Visits: 10,354
Charles

The config file is specified by right-clicking on the design surface in BIDS and choosing Package Configurations. You can specify a different config file at run-time when running a package through the command line or a job step (and, I think, with the Package Execution Utility).

John
Post #1391980
Posted Monday, December 3, 2012 8:46 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 24, 2013 8:34 AM
Points: 5, Visits: 27
Thanks John, I will look at that.

I did find that it is using a variable called QTE_XFER_Config. However, when I review the variables it is not in there. When I do the Package Configuration that variable shows up, but has nothing in it. Does it default to a name somehow?

Still looking

Thanks

Charles
Post #1391995
Posted Monday, December 3, 2012 8:52 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, December 23, 2014 9:32 AM
Points: 5,490, Visits: 10,354
Charles

Not sure I understand. If your variable takes its value from the config file, you should have a line something like this in the file:

<Configuration ConfiguredType="Property" Path="\Package.Variables[User::MyVariable].Properties[Value]" ValueType="String">
<ConfiguredValue>MyValue</ConfiguredValue>

Do you have anything like that?

John
Post #1392007
Posted Monday, December 3, 2012 9:14 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 24, 2013 8:34 AM
Points: 5, Visits: 27
John,

I don't have anything in the QuoteTransferDEV.dtsConfig file for that line. That is what is confusing. I would assume that a variable pointing to a dtsConfig file wouldn't be in the dtsConfig file. As this QuoteTransferDEV.dtsConfig is pulling up the QuoteTransfer.dtsConfig, even though I have the appropriate config file.

It is confusing.

Thanks

Charles
Post #1392020
Posted Thursday, December 6, 2012 1:20 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, December 23, 2014 9:32 AM
Points: 5,490, Visits: 10,354
Charles

You're right - you don't set the location of the config file in the config file. See my first post above for how you do that.

John
Post #1393361
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse