Creating DTS packages in SQL Server 2005

  • I have SQL Server 2005 and I need to create DTS packages (not SSIS packages). I installed the DTS add-on but the DTS node only allows me to open or import DTS packages when I'm in SQL Server Management Studio.

    I tried SQL Server Business Intelligence Dev Studio but can't seem to find a way to create DTS packages.

    How can I do this? I need to learn how to create DTS packages because my current client uses DTS packages.

    Thanks !

  • ray 78019 (12/8/2009)


    I have SQL Server 2005 and I need to create DTS packages (not SSIS packages). I installed the DTS add-on but the DTS node only allows me to open or import DTS packages when I'm in SQL Server Management Studio.

    I tried SQL Server Business Intelligence Dev Studio but can't seem to find a way to create DTS packages.

    How can I do this? I need to learn how to create DTS packages because my current client uses DTS packages.

    Thanks !

    You are trying from a wrong tool. Use Enterprise Manager in SQL Server 2000 to create or modify the DTS packages.


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • Bru Medishetty (12/8/2009)


    ray 78019 (12/8/2009)


    I have SQL Server 2005 and I need to create DTS packages (not SSIS packages). I installed the DTS add-on but the DTS node only allows me to open or import DTS packages when I'm in SQL Server Management Studio.

    I tried SQL Server Business Intelligence Dev Studio but can't seem to find a way to create DTS packages.

    How can I do this? I need to learn how to create DTS packages because my current client uses DTS packages.

    Thanks !

    You are trying from a wrong tool. Use Enterprise Manager in SQL Server 2000 to create or modify the DTS packages.

    Yes, agree I do with Bru. You need the SQL Server 2000 client tools, Enterprise Manager to be exact.

  • Bru Medishetty (12/8/2009)


    ray 78019 (12/8/2009)


    I have SQL Server 2005 and I need to create DTS packages (not SSIS packages). I installed the DTS add-on but the DTS node only allows me to open or import DTS packages when I'm in SQL Server Management Studio.

    I tried SQL Server Business Intelligence Dev Studio but can't seem to find a way to create DTS packages.

    How can I do this? I need to learn how to create DTS packages because my current client uses DTS packages.

    Thanks !

    You are trying from a wrong tool. Use Enterprise Manager in SQL Server 2000 to create or modify the DTS packages.

    And if you don't have Enterprise Manager, make a copy of an existing DTS package in SSMS by opening it and saving it with a new name (that is if you already have a package to copy!).

    Greg

  • Hi Greg,

    If I understand correctly, if I open the DTS in SQL Server Management Studio (2005) and save it under a different name, it'll still be saved as a DTS?

  • ray 78019 (12/10/2009)


    Hi Greg,

    If I understand correctly, if I open the DTS in SQL Server Management Studio (2005) and save it under a different name, it'll still be saved as a DTS?

    SQL Server Management Studio is in 2005 or above, it does not exist in SQL 2000.

    Why don't you try it your test system and know it your self?

    Do you want to create DTS packages or edit them only?

    Have you tried using Enterprise Manager as suggested me earlier, and have you looked what options you have?

    Why do you have questions that could be answered by yourself on a test system within an hour?


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • ray 78019 (12/10/2009)


    Hi Greg,

    If I understand correctly, if I open the DTS in SQL Server Management Studio (2005) and save it under a different name, it'll still be saved as a DTS?

    Yes. That does work.

    It comes under the heading of really dumb things to do, but it does work.

    Why would you want to create new DTS packages at this point? SSIS does the job better, is still being supported, and is just plain a better tool.

    Microsoft recommends against using DTS at all any more, and definitely against building new DTS packages. See http://msdn.microsoft.com/en-us/library/cc707786.aspx.

    DTS is specifically problematic on 64-bit systems. See http://msdn.microsoft.com/en-us/library/bb500440.aspx. 64-bit OSes are becoming more common every day, and 32-bit is going away over the next few years.

    Insisting on using DTS at this point is pretty comparable to insisting on using Windows 95.

    If the business insists on staying with DTS, and won't contemplate a move to SSIS, then I recommend educating them on the subject. They probably don't know that DTS is no longer being supported by Microsoft, nor what the consequences of continuing to use it will be.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • ray 78019 (12/10/2009)


    Hi Greg,

    If I understand correctly, if I open the DTS in SQL Server Management Studio (2005) and save it under a different name, it'll still be saved as a DTS?

    That's corrrect.

    Greg

  • Gus,

    Here is my take on this, since it is on a SQL Server 7, 2000 forum and based on the original post. The OP has the SQL Server 2005 Client Tools but his client is still using SQL Server 2000 and he needs to write DTS packages.

    Personally, I ask the client for the SQL Server 2000 install disks, as iirc, SQL Server 2000 personal edition exists on those disks and he could install the personal edition on his PC/Laptop and use the SQL 2000 tools to do the work he needs. This, of course, assumes that the client has the install disks for SQL Server 2000.

  • Are the questions really worthy of asking.

    Someone who has worked at least once with SQL 2000 would surely know how DTS packages can be created and if you worked on SQL 2005, you would have already known what's your options in SSMS with respect to DTS Packages.

    It is like "I am working since couple of years in SQL Server 2008 as a production team lead", but I don't know where is Activity Monitor, can someone show me please please please its urgent, my current client is using SQL Server 2008 and say some activity is running slow.. :w00t: :w00t:


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • The reason why I need to learn DTS is because my client is still using them. I don't have a choice right now. I need to support his current system. Yes, eventually I will try to convince him to move to SSIS. But right now, I need to learn DTS so that I can support him.

    I'm new to both DTS and SSIS. But I need to start somewhere. I was actually hired for something else but the client asked me to try and support the DTS as well.

    Now the problem is that I have SQL Server 2005 at home, so I guess learning DTS is impossible.

    Thanks.

  • << Why do you have questions that could be answered by yourself on a test system within an hour? >>

    Bru, if you look at the left side of the page, you'll see the words "Forum Newbie" which means I don't have all the answers. I thought DTS could still be managed (and created) in SQL Server 2005. After all, there is a DTS designer add-on for SQL Server 2005. So that got me thinking if I missed something. So I searched and couldn't find a way to create a DTS package in SQL Server 2005. Since it is a big product, I thought maybe it's me and I can't find it.

    So I spent "more" than an hour already and decided to leave a message in this forum, to save time.

    Hope that explains it.

    Forget the why's, I want the how's.

  • ray 78019 (12/10/2009)


    << Why do you have questions that could be answered by yourself on a test system within an hour? >>

    Bru, if you look at the left side of the page, you'll see the words "Forum Newbie" which means I don't have all the answers. I thought DTS could still be managed (and created) in SQL Server 2005. After all, there is a DTS designer add-on for SQL Server 2005. So that got me thinking if I missed something. So I searched and couldn't find a way to create a DTS package in SQL Server 2005. Since it is a big product, I thought maybe it's me and I can't find it.

    So I spent "more" than an hour already and decided to leave a message in this forum, to save time.

    Hope that explains it.

    Forget the why's, I want the how's.

    How's, okay.

    Ask your client if they have the SQL Server 2000 install CD's. If they do, since you work for them, ask to borrow them so you can install the SQL Server 2000 Personal Edition on your system to help support them. When you install it, be sure to install the client tools. Then you will be able to create and modify DTS packages.

  • I sympathize with you, Ray. I too have to support some old DTS packages with SQL 2005. Sooner or later, our management will budget the resources to re-build their functionality on a supported platform, but till then, we do what we have to, right?

    As has been mentioned, the add-in designer will let you modify or even save a package to a new DTS file or on a server, but will not create one out of thin air. To make a new one altogether, you need to open an existing package, modify it (which could start with deleting everything in it) and saving under a different name. If saving to a file, be sure to change both the package name and the file name.

    Now, having said that..... Other comments about getting off DTS and using SSIS are right-on. I strongly recommend you reserve using the SQL 2005 add-in DTS 2000 designer ONLY for light maintenance of existing packages for a number of reasons. One is that SSIS is much more flexible and offers programming constructs (like iteration) that have to be kludged together in DTS. Another is that MS has deprecated DTS in both SQL 2005 and 2008, which means "stop using this soon, cuz we may not include it in future releases". Already, SQL 2008 requires run support to be separately installed, as you found with the designer for 2005.

    Finally, my experience has been that the add-in designer can behave in a flakey manner, corrupting a dts file, usually when I hit the [X] to close the designer without first explicitly saving the package. This may be the best reason to try to get a native SQL 2000 environment running if you have to do any significant amount of work with DTS.

    Bottom line: Try to get new work done with SSIS and be very cautious when forced to modify DTS packages with the add-in.

Viewing 14 posts - 1 through 13 (of 13 total)

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