Hi

I am trying to set the OLE DB destination table name dynamically in an
SSIS package. I have an Execute SQL task which prepares the table name
and sets the name to a variable say var1. Var1 is of data type string.
In the OLE DB destination editor I am using the Data access mode as
"table name or view name variable - fast load" and setting the
table name as variable name var1.



When I execute SSIS package, I get following errors where proxy20051108
is the table that I am dynamically creating. I see this table in the DB
and from what I see in the error the table name is getting padded with
spaces because of which it is failing.



[Proxy20051108 [5908]] Error: An OLE DB error has occurred. Error code:
0x80040E37. An OLE DB record is available. Source: "Microsoft SQL
Native Client" Hresult: 0x80040E37 Description: "Table/view either
does not exist or contains errors.".

[Proxy20051108 [5908]] Error: Failed to open a fastload rowset for
"PROXY20051108








". Check that the object exists
in the database.

Is there anyway to specify the field length in user variables declared
in SSIS? Can someone direct me on how to get rid of those extra spaces
from the variable?

The error code 0x80040E37 talks about
HResults.DTS_E_CANNOTGETIROWSETFASTLOAD , of which I have no clues.

Any input is appreciated!

The variable should be available to you in a dropdown and will take the
form User::NameOfVariable


If there are space in the name of the table make sure the variable value
is wrapped in []

i.e.

If your table name is OLE DB Destination then your variable value should
be [OLE DB Destination]


Allan



"Megan" <meghana.mhaisekar (AT) gmail (DOT) com> wrote

Thanks Allan for the help ! I had to prefix the tablename with the
[dbo]. for it to work properly. Even though I had wrapped the tablename
with [] it wasn't working properly.

-Meghana

Ahhh remember that if you are not the dbo then you will need to
otherwise it will look for something like

[DOMAIN\USER]\TABLENAME

In my example I didn't because I am a sysadmin on my box.

Glad we've sorted things

Allan

"Megan" <meghana.mhaisekar (AT) gmail (DOT) com> wrote