January 5, 2006 at 5:19 pm
Hi,
When having an ActiveX script in SQL2000 DTS you could execute the actual script and if there was an error it would tell you the error and what line the error was on/near.
Is a similar facility available in SSIS because I am having some troubles finding it if there is.
I have found the execution results where the description of the error is, however it doesn't offer any indications as to where the error originated from in the script.
Any ideas?
Thanks in advance.
Troy
January 5, 2006 at 6:02 pm
Hopefully, you're not still using the ActiveX Script Task in SSIS. It's deprecated and should not be used except temporarily for migrating DTS packages.
January 5, 2006 at 6:09 pm
thanks for the response kirk, I didn't realise this (but doesn't surprise me), but will used in the migrations from 2000 as we dont have the resource to dedicate to rebuilding these fully with SSIS.
Bearing this in mind would be it best to simply migrate the DTS packages as DTS packages rather than upgrading/converting to SSIS packages? With a view to recreating within SSIS at a later stage (without ActiveX)
Keen to hear your thoughts.
Cheers
Troy
January 5, 2006 at 6:17 pm
This is definitely one of those "it depends" answers...
So much depends on your resources, commitments, future plans, deadlines and ramp up time.
Some shops just rewrite all their packages. That's one extreme. Some shops don't upgrade at all and plan to migrate one package at a time. Both are viable and valid options.
Some embed the old packages into SSIS packages. This has the distinct advantage of using new features like logging etc. while retaining existing investments in DTS development.
Do a search on the web for upgrade SSIS or something similar, there are several good resources to draw from to help you make your decision.
K
January 6, 2006 at 2:46 am
Troy,
Just to clarify that you can still run DTS packages as is in SSIS. This i s because when you select Integration Services during install, it installs backward compatibility components. You can verify by going to Add or remove programs. If you need to edit those packages later on, you need to install "SQL Server 2000 DTS Designer components" add-on which is freely downloadable from Microsoft download site.
The upgrade options, Kirk has explained already.
Regrads,
Ash
January 8, 2006 at 12:45 pm
Thanks Ash for the response - yeah I was sort of hoping that I could easily just get everything up and running in SSIS but looks as though I will have to use the DTS function for the meantime until we have moved across...
Cheers
Troy
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply