Troubleshooting a sql server package configuration

  • Hello,

    I am trying to create a package that stores the configuration information in a sql server table. It seems thought that no matter what I do the package runs and just ignores the values I have in the configuration table. When I run the package with the package execution utility and update the configuration there, then the packages the changes. Does anyone have any suggestions on how I should go about troubleshooting this?

    thanks.

  • Turn package configurations on, create a config file, and use that? I wasn't aware that you could use a 'configuration table'.

  • I am trying to use the package configurate type of sql server.

  • padre (12/10/2009)


    I am trying to use the package configurate type of sql server.

    [font="Comic Sans MS"]

    That is absolutely fine.

    But how did you define the connection of the SQLSERVER your package need to look for rest of the configuration values? That is where did you save configurations of that configuration database? This database should be a predefined database. This is a consideration/call when you save your package configurations in SQL Server.

    Check for more elaboration/reference:

    http://www.sql-server-performance.com/articles/dba/package_configuration_2005_p2.aspx

    OR

    http://rafael-salas.blogspot.com/2007/01/ssis-package-configurations-using-sql.html

    Let me know how it goes.

    [/font]

    [font="Comic Sans MS"]--
    Sabya[/font]

  • Sabya,

    Thanks for the links. It is actually Rafael Salas' solution that I was trying to implement.

    After some more poking at my package I got this error message:

    Warning loading <PackageName> : Table "[dbo].[SSIS Configuration]" does not have any records for configuration This occurs when configuring from a SQL Server table that has no records for the configuration."

    That led me to find this link:

    http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=261584

    Once I changed the collation of the columns in the table to Latin1_General_CI_AS everything started working. :smooooth:

    Thanks,

    Padre

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

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