Deploying DTS packages from different environments

  • We have a test server and a production server and I want to be able to make the DTS connections generic to the server.  What is the best way to do this?

    The DTS packages are run from various locations (pcs), including the server where the instance resides as well as remote computers.

    I tried to create an alias but the alias needs to be created on each machine and we dont want anything on remote servers. 

    I have also tried a data link but the files associated with the data link needs to be on the local machine.

    Thanks for the help.

  • There is currently a thread going that may answer your question. Take a look at http://qa.sqlservercentral.com/forums/shwmessage.aspx?forumid=19&messageid=168132

    Let us know if your situation is different and we can help you more.

  • Take a look at this link. It enables you to set source and destination properties at run time. I am guessing that you want portable dts packages. I use this on all my dts packages. That way, I never have to worry where I am running them form and to.

     

    http://www.databasejournal.com/features/mssql/article.php/3073161


    ------------------------------
    The Users are always right - when I'm not wrong!

  • Thank you for your replies.  Jonathan, I dont want to specify a specific drive.  The problem is that we have users (unfortunately) that run the dts packages from their pcs using Enterprise Manager.  This is something that we will be changing, but unfortunately not soon enough.

    What that means is that the file you mention needs to reside on each person's computer.  We dont want to do that.  I actually set up the dts package to use a microsoft data link.  This works fine but again, the file needs to reside on the user's pc.  Is there a way to not do this with a file?  Can you create an alias for the database?  Since the DTS packages are associated with an instance, cant it know somehow what instance it is under?

    Thanks again for the help.

    Jim

  • The problem you're encountering is due to the way DTS works. It's basically a client application and all resources that are referenced in the package need to be local to where the package is executed.

    Best thing I can suggest for the short term is the data link file that you already use, or the INI file approach suggested by Jonathan. In the long term the approach I outlined in this post,

    http://qa.sqlservercentral.com/forums/shwmessage.aspx?forumid=19&messageid=168132

    will solve your immediate problems.

    Once you have those out of the way you can approach the issue of users running Enterprise Manager to execute the packages, which are in fact then running on their workstations.

     

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

  • Hi

    I need to dts an excel. Depending on where the excelfile is stored, this excel is must be dts'ed within the same database. So eg Folder :Track, file : verdeling.xls, it should dts'ed into database : track.

    I am using software that is called automate. This is a service, triggering the file. When the file is saved in a specified drive it can start an executable or even better a stored procedure. I think i can start the dts using a stored procedure (how ?) and i can create a variable using that software. But how will i get my dts that far that he uses that variable to know which excel file and which database to use, so that I not need to create a package per database ?

    Many thx

    J


    JV

Viewing 6 posts - 1 through 5 (of 5 total)

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