![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a package in which I have several Data Pump tasks to copy data from a tables in a Pervasive Database to an SQL Database. I use a dynamic propertice task to change the destination connection (server name and database name). Dynamicall changing the connection works fine for other tasks eg Execute Sql Tasks. However because the Destination Tables are named in the DataPump using the fillowing convention by default [DatabaseName].dbo.[TableName], I am getting errors because the database name in the table definition is different to the new dynamic database name in the destination connection. How can I overcome this problem. Can the destination Tables be defined by their table names only. If so how do I do this using enterprise manager. Paul |
#3
| |||
| |||
|
|
Paul: You can try to set it up as you specify (using just the table name...I'd suggest removing just the database name and leaving the schema name "dbo"). To do this, you will have to use the "Disconnected Edit..." when you right click in the design window for the package. Expand Tasks in the tree and look at the DestinationObjectName property of the data pump(s) in question. Edit it as you specify and try it. If that doesn't work, you will have to modify it using an ActiveX Script, where you can build the name and set the same property during execution. Scott "Paul Say" <saywin (AT) tpg (DOT) com.au> wrote in message news:eSxDp9i8EHA.2608 (AT) TK2MSFTNGP10 (DOT) phx.gbl... I have a package in which I have several Data Pump tasks to copy data from a tables in a Pervasive Database to an SQL Database. I use a dynamic propertice task to change the destination connection (server name and database name). Dynamicall changing the connection works fine for other tasks eg Execute Sql Tasks. However because the Destination Tables are named in the DataPump using the fillowing convention by default [DatabaseName].dbo.[TableName], I am getting errors because the database name in the table definition is different to the new dynamic database name in the destination connection. How can I overcome this problem. Can the destination Tables be defined by their table names only. If so how do I do this using enterprise manager. Paul |
![]() |
| Thread Tools | |
| Display Modes | |
| |