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 Configuration Files - SQL School Video Expand / Collapse
Author
Message
Posted Thursday, October 30, 2008 12:09 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: Moderators
Last Login: Wednesday, June 4, 2014 12:29 PM
Points: 1,931, Visits: 234
Comments posted to this topic are about the item SSIS Configuration Files - SQL School Video

Brian Knight
Free SQL Server Training Webinars
Post #594102
Posted Thursday, October 30, 2008 8:20 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Friday, October 30, 2009 8:16 AM
Points: 81, Visits: 87
Great video! I'm curious as to how people modify the configuration file when deploying packages to customers. Would you need to write your own program to edit the configuration file based on customer responses? For example, have a program that asks users for server name and database name and then have the program somehow do a search and replace in the configuration file?
Post #594366
Posted Thursday, October 30, 2008 9:00 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, July 17, 2014 10:36 PM
Points: 5,309, Visits: 1,378
Great!!!


Post #594416
Posted Friday, October 31, 2008 9:55 AM


Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 7:05 AM
Points: 16, Visits: 126
Brian,

I have had some issues with the package configuration. We use a hosted vendor for production (on an entirely different network) than our dev server.

When I run packages in the prod environment I get validation errors because the previously used values for my connection managers point to a server that is not accessible in the prod network. In our dtsconfig file we have the correct servers that are in the prod environment but the validation still causes issues. I have tried the delay validation options, but this just changes when the values get checked and doesn't allow you to stop validation entirely. It seems like there is an order of operations problem here. I think SSIS should set the conn mgr values from the dtsconfig file first and then try to validate components.

Have you seen this error? Do you have any suggestions? Maybe I need to put this on the ms connect site.

What I have to do now is manually change all of my connection managers once I migrate packages into prod to point to an accessible server. This obviously defeats the purpose of the package configuration, but some of my other configurations like variable assignments work fine because they don't depend on the validation.

Thanks,
Sean


Cheers,

Sean
Post #595096
Posted Tuesday, December 1, 2009 2:38 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, October 17, 2012 3:17 AM
Points: 3, Visits: 46
Sean Woehrle (10/31/2008)
Brian,

I have had some issues with the package configuration. We use a hosted vendor for production (on an entirely different network) than our dev server.

When I run packages in the prod environment I get validation errors because the previously used values for my connection managers point to a server that is not accessible in the prod network. In our dtsconfig file we have the correct servers that are in the prod environment but the validation still causes issues. I have tried the delay validation options, but this just changes when the values get checked and doesn't allow you to stop validation entirely. It seems like there is an order of operations problem here. I think SSIS should set the conn mgr values from the dtsconfig file first and then try to validate components.

Have you seen this error? Do you have any suggestions? Maybe I need to put this on the ms connect site.

What I have to do now is manually change all of my connection managers once I migrate packages into prod to point to an accessible server. This obviously defeats the purpose of the package configuration, but some of my other configurations like variable assignments work fine because they don't depend on the validation.

Thanks,
Sean


Hi Sean

This post is quite old, but I was wrestling with this exact thing today and have found a solution. I thought I'd post it up here for other people struggling with the same thing.

It turns out, that setting the connection string from configuration is considered setting the connection string at runtime. Go figure. So, SSIS is using the connection string from design time to validate the objects and T-SQL in the package before entering runtime, hence your problem (and mine). Setting "DelayValidation" to TRUE at the package level (or on the object using the connection that is set from configuration), will cause SSIS to first set the connection string from Config and then validate at runtime.

I found this from these posts:
http://sqlserveruniverse.com/content/SSIS0300103262008NuggetsfromMySSISExperience.aspx by Dinesh Priyankara
and
http://www.louisnguyen.info/Home/ssis-best-practices by Louis Nguyen

Hope it helps, it's sorted my problem out.

Mike
Post #826529
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse