My Variable doesn't like my Object any more - FIXED!

THIS LIMITATION HAS BEEN FIXED AND REMOVED FOR SQL SERVER 2008 RTM. Object of any type can now be passed through package variables of type Object, and consumed within Script task code.

No, wait. Maybe it's "My Object doesn't like my Variable." Anyway, we just had to remove one of the Integration Services package samples ("SmoTablesDBCC") for Katmai because of this issue that affects the Script task.

There are many Types that you will no longer be able to pass into a Script task by way of a package Variable. In the case that I mentioned just above, we were passing an SMO Table object in the variable.

Here is the summary of this issue:

The Script task can store and retrieve objects in package variables of type Object only when those objects (or more properly, their types) are defined in one of the following assemblies:

  • mscorlib;
  • System;
  • System.Data;
  • System.Data.OracleClient;
  • System.Xml;
  • System.Messaging;
  • System.Configuration;
  • System.Runtime.Remoting;
  • System.Drawing;
  • System.Runtime.Serialization.Formatters.Soap;
  • System.Security;
  • System.Web;

User-defined objects cannot be passed to or from the Script task through package variables of type Object.

This restriction applies only to the Script task and not to the Script component.


Comments (1) -

Matt Masson

Note that we are currently working hard to solve this problem for RTM!!

Pingbacks and trackbacks (1)+