Comments on: Initialize SSIS Variables from a Database Table http://blog.boxedbits.com/archives/8 ( ... more specifically about BI with Microsoft products ) Tue, 06 Jan 2009 00:25:45 +0000 http://wordpress.org/?v=2.7 hourly 1 By: PedroCGD http://blog.boxedbits.com/archives/8/comment-page-1#comment-2409 PedroCGD Tue, 06 Jan 2009 00:11:02 +0000 http://blog.boxedbits.com/archives/8#comment-2409 Dear Friend, Good post and blog. But tell me why you need all this using script, you you have SSIS Package Configurations? Or you can use only SQL Task to get the values to a database table and store in a SSIS variable. Regards, Pedro Dear Friend,
Good post and blog.
But tell me why you need all this using script, you you have SSIS Package Configurations?
Or you can use only SQL Task to get the values to a database table and store in a SSIS variable.
Regards,
Pedro

]]> By: Tom VdP http://blog.boxedbits.com/archives/8/comment-page-1#comment-1653 Tom VdP Fri, 15 Aug 2008 15:42:14 +0000 http://blog.boxedbits.com/archives/8#comment-1653 If you want to assign a value from the database table to an SSIS variable of, say, type Int32 then you will have to cast <i>de.Value</i> in the code above to integer. Otherwise you get an error: <i>Variables may not change type during execution. Variable types are strict, except for variables of type Object</i>. If you want to assign a value from the database table to an SSIS variable of, say, type Int32 then you will have to cast de.Value in the code above to integer. Otherwise you get an error: Variables may not change type during execution. Variable types are strict, except for variables of type Object.

]]> By: red http://blog.boxedbits.com/archives/8/comment-page-1#comment-1632 red Wed, 13 Aug 2008 19:01:22 +0000 http://blog.boxedbits.com/archives/8#comment-1632 Very nice. Just wondering what exactly you mean by "all the parameters are string types". Are you talking about the parameters in database table only or both in the table as well as the variables in SSIS package? Could the package variables be of different datatypes? Very nice. Just wondering what exactly you mean by “all the parameters are string types”. Are you talking about the parameters in database table only or both in the table as well as the variables in SSIS package? Could the package variables be of different datatypes?

]]> By: Tom VdP http://blog.boxedbits.com/archives/8/comment-page-1#comment-1507 Tom VdP Wed, 06 Aug 2008 13:01:30 +0000 http://blog.boxedbits.com/archives/8#comment-1507 It is probably the check for the existence of the variable in the <i>While sqlResult.Read()</i>-loop that returns false. Variable names are case sensitive, so make sure the value of the ParameterName in the table matches the name of the SSIS parameter exactly. If this does not help you will have to resort to adding debugging messageboxes. It is probably the check for the existence of the variable in the While sqlResult.Read()-loop that returns false. Variable names are case sensitive, so make sure the value of the ParameterName in the table matches the name of the SSIS parameter exactly.
If this does not help you will have to resort to adding debugging messageboxes.

]]> By: Kevin http://blog.boxedbits.com/archives/8/comment-page-1#comment-1506 Kevin Wed, 06 Aug 2008 12:34:00 +0000 http://blog.boxedbits.com/archives/8#comment-1506 I have changed the name of the db connection in the script and when I run the script it executes successfully but it does not change the variables to the ones stored within the database (SQL Server 2005). The db schema is below. I figure it is something small, but I have yet to pinpoint it. Let me know what additional information may be useful. [dbo].[SSISCubeAutomationVariables]( [OLAPdbName] [varchar] (100) NOT NULL, [Month] [varchar] (20) NULL, [Year] [varchar] (10) NULL, [ParameterName] [varchar] (100) NOT NULL, [ParameterValue] [varchar] (4000) NULL, [Description] [varchar] (4000) NULL ) ON [PRIMARY] I have changed the name of the db connection in the script and when I run the script it executes successfully but it does not change the variables to the ones stored within the database (SQL Server 2005). The db schema is below. I figure it is something small, but I have yet to pinpoint it. Let me know what additional information may be useful.

[dbo].[SSISCubeAutomationVariables](
[OLAPdbName] [varchar] (100) NOT NULL,
[Month] [varchar] (20) NULL,
[Year] [varchar] (10) NULL,
[ParameterName] [varchar] (100) NOT NULL,
[ParameterValue] [varchar] (4000) NULL,
[Description] [varchar] (4000) NULL )
ON [PRIMARY]

]]> By: Tom VdP http://blog.boxedbits.com/archives/8/comment-page-1#comment-1487 Tom VdP Tue, 05 Aug 2008 20:26:55 +0000 http://blog.boxedbits.com/archives/8#comment-1487 Kevin, I cannot disclose the package in which I use this code. But if you give some more details about the "issues" you are having I will be glad to help. Kevin, I cannot disclose the package in which I use this code. But if you give some more details about the “issues” you are having I will be glad to help.

]]> By: Kevin http://blog.boxedbits.com/archives/8/comment-page-1#comment-1486 Kevin Tue, 05 Aug 2008 18:30:34 +0000 http://blog.boxedbits.com/archives/8#comment-1486 I am having issues making this work. Can you post the SSIS package so that I can see what the issue is? I am having issues making this work. Can you post the SSIS package so that I can see what the issue is?

]]> By: Prasannakumaran Sarasijanayanan http://blog.boxedbits.com/archives/8/comment-page-1#comment-405 Prasannakumaran Sarasijanayanan Thu, 05 Jun 2008 09:56:59 +0000 http://blog.boxedbits.com/archives/8#comment-405 Thanks, Excellent post. Thanks,
Excellent post.

]]> By: Dave Neeley http://blog.boxedbits.com/archives/8/comment-page-1#comment-224 Dave Neeley Thu, 15 May 2008 19:09:43 +0000 http://blog.boxedbits.com/archives/8#comment-224 Thanks for posting this, it's really nice! Thanks for posting this, it’s really nice!

]]>