![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| ||||
| ||||
|
|
-----Original Message----- Before diving into your issue, I have noticed that when Microsoft creates the target table in a transformation, it |
|
You can change the source table name and the target table name in the disconnected edit menu option to change the |
|
Or you can use an activex script: '************************************************* ******** ************* ' Visual Basic ActiveX Script '************************************************* ******** *************** Function Main() dim myTask set myTask = DTSGlobalVariables.Parent.Tasks("Copy Data from DeclineList to [RussExperimental].[dbo].[DeclineList] |
|
dim sTable dim sDB dim iPos sTable = myTask.CustomTask.DestinationObjectName sDB = DTSGlobalVariables("DestinationDB").Value iPos = instr(1,sTable,".") if iPos > 0 then myTask.CustomTask.DestinationObjectName = sDB & mid (sTable,iPos) end if ' Do the same with the SourceObjectName Main = DTSTaskExecResult_Success End Function Russel Loski, MCSD . |
#4
| |||
| |||
|
|
I would think that simply using TableName or dbo.TableName syntax would allow you to move the package from one database to another by simply changing the connection properties. |
![]() |
| Thread Tools | |
| Display Modes | |
| |