 | |
being forced to open each transform before running dts pkg
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#31
 
| |||
| |||
|
Re: being forced to open each transform before running dts pkg -
09-22-2008
, 01:43 PM
|
Hi, sorry I know no workaround for this. But... you must do it only the first time and only after you've created the trasform, don't you? As the task is created, DTS designer creates a trasformation on its own basing on... fields' names, type or whatever. And you're expected to at least take a look into it before running package... I don't blame DTS for this feature: I won't even run a trasformation package before knowing how data is moved or deleted... M. thanks matteus, package is stored in msdb, I run it in dts designer by clicking the run button after opening pkg, since posting this question I've learned that if I open and close every transform and then save, I dont need to open and close all over again. *This is painful for large pkgs, and a bit challenging when all of the transforms arent immediately discernable to the naked eye due to their proximity to other transforms. *So if you have a workaround, I'd love to hear it. This seems a little crazy to me.- Hide quoted text - - Show quoted text - |
after I changed some connection info, modified script in a sql task
and modified an activex script in an existing pkg.
#32
| |||
| |||
|
|
Hi, sorry I know no workaround for this. But... you must do it only the first time and only after you've created the trasform, don't you? As the task is created, DTS designer creates a trasformation on its own basing on... fields' names, type or whatever. And you're expected to at least take a look into it before running package... I don't blame DTS for this feature: I won't even run a trasformation package before knowing how data is moved or deleted... M. thanks matteus, package is stored in msdb, I run it in dts designer by clicking the run button after opening pkg, since posting this question I've learned that if I open and close every transform and then save, I dont need to open and close all over again. *This is painful for large pkgs, and a bit challenging when all of the transforms arent immediately discernable to the naked eye due to their proximity to other transforms. *So if you have a workaround, I'd love to hear it. This seems a little crazy to me.- Hide quoted text - - Show quoted text - |
after I changed some connection info, modified script in a sql task
and modified an activex script in an existing pkg.
#33
| |||
| |||
|
|
Hi, sorry I know no workaround for this. But... you must do it only the first time and only after you've created the trasform, don't you? As the task is created, DTS designer creates a trasformation on its own basing on... fields' names, type or whatever. And you're expected to at least take a look into it before running package... I don't blame DTS for this feature: I won't even run a trasformation package before knowing how data is moved or deleted... M. thanks matteus, package is stored in msdb, I run it in dts designer by clicking the run button after opening pkg, since posting this question I've learned that if I open and close every transform and then save, I dont need to open and close all over again. *This is painful for large pkgs, and a bit challenging when all of the transforms arent immediately discernable to the naked eye due to their proximity to other transforms. *So if you have a workaround, I'd love to hear it. This seems a little crazy to me.- Hide quoted text - - Show quoted text - |
after I changed some connection info, modified script in a sql task
and modified an activex script in an existing pkg.
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.