Post reply

Running DTS packages

  • September 1, 2009 at 3:57 am

    #135290

    Hi,

    I have created some dts packages and have a question about how/where they can be run.

    If another user needs to run the package,do they have to have integration services installed? What permissions do they need set up for this to work?

    Naively, i thought that if i moved the .dtsx file to any folder, it could be executed without the need for such access rights.

  • September 1, 2009 at 7:05 am

    #1047485

    i have now tried setting up a job and uses the start job procedure .

    The packages do seem to start but fail when trying to access folders to pick up/create files.

    Tried one package and got "Cannot open the datafile" error.

    Is this an issue with the permissions that the job is running at? The owner of the job is under my username, so i don't understand why it won't access the various folders.

    Package runs fine from ssis and from integration services.

  • September 1, 2009 at 8:11 am

    #1047553

    Let's get a clearer understanding of why you wish to create a dts package on 2005 when you can use SSIS. As far as the errors you're getting is the file you are trying to grab located locally on the server or at another location. Please give us more details to troubleshoot this.

  • September 1, 2009 at 8:24 am

    #1047561

    Hi,

    I have created the packages on SSIS. when i import onto integration services, the package runs ok.

    When i try to create a sql sever job, the package does not run. Wondering whether it is to due with the sql sever account not having access to certain folders.

    The file i need to get is located on another location to the server.

    The reason that i need to create a sql job is that eventually i will not be running the dts but another user will be. He has sql server installed but does not have integration services installed.

  • September 1, 2009 at 10:17 am

    #1047652

    Any connection in the package that uses Windows authentication will use the credentials of the login executing the package. When the package is executed in a job, the SQL Agent login executes it. So, if that login doesn't have permission for the file location, you'll get that error.

    SSIS packages need to run on a computer that has Integration Services installed. If you save the package on the SQL Server, the user doesn't have to have SSIS installed on his workstation.

    BTW, confusion ensues when you refer to SSIS packages as DTS packages.

    Greg

  • September 1, 2009 at 10:28 am

    #1047663

    thanks for the info. the issue i seemed to be getting was the file location were not recognised by the sql service account

    i.e i had file location such as H:\location\etc...which was fine when running in visual studio

    Since been told that i need to actually put the full UNC path for it be recognised by the sql service

    i have since adjusted my file paths and the sql agent are now working.

    cheers for the replies

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

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