Item 3 of 8 Previous | Next

1
Vote

Fast Load Variable Preventing Load to BIMetadata

description

Issue 1:
Some of my SSIS 2008R2 packages are being read from the file system and loaded to the SQL 2008R2 BIMetadata database with no issues. However, some packages return an error:

Loading file package SSIS_CLAIMS_DEV\bin\SrcFileStgBillHdr_Extr.dtsx'... Error occurred: 'FastLoad variable not yet supported'

Issue 2: 3 branches of a data flow task in one of the packages use and OLEDB Command transform and appears to have caused this error during the same 2008 analyzer process:

Unhandled Statement Type in findIdentifiers(InsertStatement insertStatement) Microsoft.Data.Schema.ScriptDom.Sql.InsertStatement
was raised against query
INSERT FactErrorEvent
VALUES (?,?,?,?,?,0)
Please report to http://sqlmetadata.codeplex.com/WorkItem/List.aspx
The exception
Unhandled Statement Type in findIdentifiers(InsertStatement insertStatement) Microsoft.Data.Schema.ScriptDom.Sql.InsertStatement
was raised against query
INSERT FactErrorEvent
VALUES (?,?,?,?,?,0)
Please report to http://sqlmetadata.codeplex.com/WorkItem/List.aspx
The exception
Unhandled Statement Type in findIdentifiers(InsertStatement insertStatement) Microsoft.Data.Schema.ScriptDom.Sql.InsertStatement
was raised against query
INSERT FactErrorEvent
VALUES (?,?,?,?,?,0)
Please report to http://sqlmetadata.codeplex.com/WorkItem/List.aspx

Any idea of the root cause or how I can prevent these errors from occurring? Thanks.

No files are attached

comments

Mirsky72 wrote Jan 19 at 6:12 PM

Downloaded version 13 @1:00 PM today. Your fix for issue 1 is successful! Thanks.

Let me know when the fix for issue 2 is pushed out.

kmartin wrote Jan 19 at 10:49 AM

Release 13 now has handling for Fast Load Variables. This is available in the Downloads section, but is not the default release, as more work is ongoing within Release 13. (including fixing the Insert statement issues above).

Mirsky72 wrote Jan 18 at 11:09 PM

Thanks, man. You folks do great work. )

kmartin wrote Jan 18 at 11:35 AM

Nope, unfortunately not.
The code currently specifically tests for the following:
case (int)AccessMode.AM_OPENROWSET_FASTLOAD_VARIABLE:
And throws an exception if that is found. ps: it's in SsisEnumerator.cs if you are interested.

I'll change that to a warning, so that the rest of the package will be processed, just without details on the actual underlying statement, and push a new version tomorrow night.

Mirsky72 wrote Jan 17 at 2:42 PM

Regarding issue 1:

If I set the "EvaluateAsExpression" property on all my expression-based variables to "False", do you think that would band-aid the issue for now? Thanks.

kmartin wrote Jan 15 at 12:25 PM

Thanks for the statements. Those packages will have been analysed, but without that particular statements table being determined.

I'll have these both fixed in the next release.

Sign in to add a comment or to set email notifications