Good Article. I wish there was something like it when I first started doing portable DTS work.
Chalk me up as another fan of UDL and INI files.
To add to andyj93's comments, you can write a failirly simple vbscript to chop out the 1st and 2nd parts of the three part name and stick it into an ActiveX script in your package (runs early). That way you do not need to do the editting.
Hey andyj93
How did you get rid of the three part naming in the tranformation?
I have the source from ODBC AS400 and destination is the SQL server. I am able to set the global varible for the connections but not the transformation. Any inmput is appreciated.
THanks.
Once again, the submission is SPOT ON. Good job and thanks for the very well written and easy to understand style!
Hi BankaR,
I added this code in an ActiveX script at the top of my package:
For i = 1 to oPackage.Tasks.Count ' Verify that this task is a transformation task by interrogating for default name If Left(oPackage.Tasks(i).Name, 19) = "DTSTask_DTSDataPump" Then PumpID = i set oTrans = oPackage.Tasks(PumpID) ' Get the Destination tablename and find the 2nd qualifier location oTask = oTrans.CustomTask.DestinationObjectName tst = InStr(1 ,oTask,"dbo") tst2 = tst - 2 ' Use calculated starting point to strip off the table creator and name ' from the server name tempname = Right(oTask,Len(oTask) - tst2) ' Apply stripped name back to destination name oTrans.CustomTask.DestinationObjectName = tempname set oTrans = nothing End If Next
I use this loop to also change other aspects of the Tasks (just add new code to loop) when I have many of them in a single package. It allows you to avoid opening each Task.
