SQL Server configuration table

  • I am getting error as

    "Could not complete wizard actions. (Microsoft Visual Studio)

    ===================================

    Cannot insert configuration information into the configuration table. (Microsoft.DataTransformationServices.Wizards)"

    I am trying to add the

    "Connection String" of an OLEDB connection (with sql authentication) to the Config table.

    Can anyone help on this?

  • How are you trying to do this?

    Do you have write permissions on that database/table?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Koen..Thanks. The issue is with the length of the connection string

    I have altered the config table design to accomodate lengthy strings. Its working

  • Gerbera (3/30/2012)


    Koen..Thanks. The issue is with the length of the connection string

    I have altered the config table design to accomodate lengthy strings. Its working

    Ah yes, I have bumped into that one before.

    Good that you posted back the solution.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • 🙂

  • Could someone please provide me with a script for a Database and Table to Store the Package Configurations?

    Thanks.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • Welsh Corgi (3/30/2012)


    Could someone please provide me with a script for a Database and Table to Store the Package Configurations?

    Thanks.

    When you choose to use the SQL Server package configs SSIS will create the table for you in whatever database you specify (as long as it can connect to it) so a script to create the table is not needed.

    However here is the script for one of the ones I use if you really want..

    SET ANSI_NULLS ON

    GO

    SET QUOTED_IDENTIFIER ON

    GO

    SET ANSI_PADDING ON

    GO

    CREATE TABLE ConfigTable

    (

    [ConfigurationFilter] [nvarchar](255) NOT NULL,

    [ConfiguredValue] [nvarchar](255) NULL,

    [PackagePath] [nvarchar](255) NOT NULL,

    [ConfiguredValueType] [nvarchar](20) NOT NULL,

    [VariableName] [varchar](50) NULL

    ) ON [PRIMARY]

    GO

    SET ANSI_PADDING OFF

    GO

    Andy

    ==========================================================================================================================
    A computer lets you make more mistakes faster than any invention in human history - with the possible exceptions of handguns and tequila. Mitch Ratcliffe

  • Thanks Andy.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • No probs 🙂

    ==========================================================================================================================
    A computer lets you make more mistakes faster than any invention in human history - with the possible exceptions of handguns and tequila. Mitch Ratcliffe

  • I created an environmental variable and a package configuration and it gave me an error when I loaded it.

    It said that the package was corrupt and I saw three errors, one about the environmental variable and the others about the package configuration.

    The package is loading, takes forever , a lot of transformations.

    I followed these steps:

    http://www.mssqltips.com/tipprint.asp?tip=1405

    I will try and fix it or try and remove what it causing the problem.

    I have the package stored in MSDB but I get get the SSIS Service to start so I can't export it to a file.

    I could use the following command to export from MSDB?

    DTUTIL /SQL <PACKAGENAME> /COPY FILE;<DRIVE:\FOLDERNAME\PACKAGENAME.DTSX> /QUIET

    If all else fails I assume that package in the deployment folder is a copy of the package the last time that it was built and I could use that file as an alternative?

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 10 posts - 1 through 9 (of 9 total)

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