Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2004
    Location
    Long Island
    Posts
    696

    Unanswered: sa account with DTS

    If I execute a DTS package as sa, and the DTS package creates a file on a remote server, should it not inherit the permissions of the domain account that starts the SQL Agent Service on the local SQL Host ? The SQL Agent jobs do. The package works fine scheduled via the SQL Agent, but running straight from DTS it fails due to insufficient permissions. I'm not entirely sure what permissions a task run by sa picks up for cross server access, specifically to file system objects.

  2. #2
    Join Date
    Nov 2004
    Location
    on the wrong server
    Posts
    8,835
    Provided Answers: 6
    I am betting the account that runs the sql agent is mapped to a domain account that has rights on the remote drive.

    And I forget because I gave up on DTS and being a DBA, but I would guess that the local administrator or whatever account you are in windows as while running DTS does not.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  3. #3
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    SQL2K SP2 and earlier would use SQL Server Service account when going outside of SQL name space. So when being logged on as SA, you will be using the SQL account of the instance that you're logged on to. I don't remember if this approach was retained all the way to SP4 and later. SQL2K5/8 actually use your windows credentials when you go out of the name space.
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  4. #4
    Join Date
    Jun 2004
    Location
    Long Island
    Posts
    696
    Quote Originally Posted by rdjabarov
    SQL2K SP2 and earlier would use SQL Server Service account when going outside of SQL name space. So when being logged on as SA, you will be using the SQL account of the instance that you're logged on to. I don't remember if this approach was retained all the way to SP4 and later. SQL2K5/8 actually use your windows credentials when you go out of the name space.
    Odd, because the account that starts the SQL Service and Agent has full rights and does indeed go down to the agent jobs running the dts packages, but running the DTS packages themselves it does not (when using sa account in DTSRun). I ended up just granting permissions to a trusted account and using that, but I am still bothered that it did not work for a sql account, particularly one with sysadmin privileges.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •