SQL Server Performance

Run a package on a different computer in command prompt

Discussion in 'SQL Server 2005 Integration Services' started by WingSzeto, Mar 12, 2008.

  1. WingSzeto Member

    I used SQL server intelligence studio to create a package on my laptop. The package has a connection manager to connect to a SQL server A using a sql login 'Login1' to read some data from a database and export the data to a flat file destination in server B. I ran the package on my laptop using dtsrun command in a command prompt and has no problem. When I copied the same package to server A and run it in the command prompt, I encountered a login failure for the sql login 'login1'. Can someone give me a pointer why i encounter this login error?
  2. ghemant Moderator

  3. satya Moderator

    When you are executing the package from the server then ensure that login has relevant permission as well, also check SQLAgent account relevant permissions to access the other server.
  4. WingSzeto Member

    I am a bit confused but it could be because of my mis-understanding. Do you mean even though I use intelligence Studio (visual studio) to create a package and use a dtsrun command in command prompt to execute the package, SqlAgent account is still involved in the authentication? In my scenerio, I developed the package in my laptop which has SQL 2k5 and intelligence studio installed. The SQLAgent service in my laptop is using Local System as the startup account and it is set to manual startup so it is not running at all. As I indicated in my first email, I am able to execute the package using DTSrun command in the command prompt from my laptop. At this point, does the SQLAgent account really involve in this process? .
    btw, satya, the reason I posted mutiliple copies of this email was because when I posted the first one, your system responded to me that there was some problem in the site and asked me to try later. So I tried later and still encountered the site problem and this happened about four times. I didn't know it actually posted my messages in the beginning.
  5. satya Moderator

    I meant to say on the server as it states login failure, in any case if you are executing the same on server side then ensure SQL server service account has relevant permissions too, that might be required within your package to run.
    Ok, that explains multiple (duplicate) threads, appreciate that.

Share This Page