Post reply

MS Technet article for Yukon DTS

  • January 7, 2004 at 3:52 pm

    #161378

    Here is a nice little article on DTS in Yukon

    http://www.microsoft.com/technet/prodtechnol/sql/next/SQLSBDTS.asp?frame=true

     

    --------------------
    Colt 45 - the original point and click interface

  • January 9, 2004 at 9:12 pm

    #489499

    First thought, "Great they improved it!",

    Second thought, "Are all my existing packages going 2 break?"

    Will there be a seamless route to migrate SQL 2000 DTS packages into Yukon or will they need re-writing?

  • February 20, 2004 at 2:28 pm

    #495005

    A very nice article (and I only read half of it).  I second the concern of how well will existing packages transfer to DTS in Yukon.  Microsoft has made a lot of cool changes.  I would hope Microsoft has provided an easy way otherwise they will make a lot of SQL Server DBA's very mad.

    Robert W. Marda
    Billing and OSS Specialist - SQL Programmer
    MCL Systems

  • February 22, 2004 at 1:20 pm

    #495067

    I would say that the developers that have written a lot of VBScript to get around some of DTS's limitations are going to be in for a lot of work upgrading to Yukon

     

    --------------------
    Colt 45 - the original point and click interface

  • February 23, 2004 at 7:46 am

    #495132

    You mean VBScripts won't work anymore.  That won't be good.  We use VBScripts in most of our DTS packages and for the reason you mention to get around DTS limitations.  Is there an article somewhere that describes the changes in how VBScripts will work with DTS in Yukon?  Or is that in the second half of the article sited in the message that started this thread?

    Robert W. Marda
    Billing and OSS Specialist - SQL Programmer
    MCL Systems

  • January 17, 2005 at 5:12 am

    #537639

    Does anyone knows the latest link to the above article? That link doesn't work anymore.

  • January 18, 2005 at 2:10 am

    #537792

    Robert,

    I don't know of any article that describes this but I can tell you what I know.

    First, you have to get your head around a completely new paradigm shift in SSIS*. The flow of data from a source to a destination (i.e. a data flow) has been seperated from the inter-relationship of these data flows (i.e. a control flow). To think of it in DTS 2000 terms, the data pumps are defined in one place and the precedence contraints somewhere else. [N.B. I would recommend that you try and put your DTS 2000 mindset to one side before exploring SSIS. SSIS is a V1 product and not a single line of code has been ported from DTS 2000.]

    It is possible to have script tasks (and "Script Task" is their proper name) in the control flow and these have the closest resemblance to ActiveX scripts in DTS 2000. They will do things like manipulate package variables, pop up message boxes and the like. One thing they WON'T do is directly manipulate other task objects in the package which is something that ActiveX scripts are used for alot in DTS 2000.

    Note also that the script tasks are written in VB.Net, not VBScript, and therefore give you full access to the .Net Framework.

    I hope this is useful to you. Check out my (plug alert SSIS blog for more information http://blogs.conchango.com/jamiethomson/category/71.aspx.

    * SSIS = SQL Server Integration Services = Yukon DTS

    Jamie Thomson
    http://sqlblog.com/blogs/jamie_thomson

  • January 18, 2005 at 2:11 am

    #537793

    The DTS 2000 runtime will be shipped with Yukon so you can still run your packages. However, there is no provision for editing DTS 2000 packages.

    HTH

     

    Jamie Thomson
    http://sqlblog.com/blogs/jamie_thomson

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply