Post reply

Problem In ssis Job creation

  • December 7, 2012 at 6:54 am

    #267291

    when i am trying to create a job to execute an ssis package

    then while trying to search for configuration file the job freezes and shows not responding

    than after 10 minutes it comes up with computer drives to choose config for config file.

  • December 7, 2012 at 7:00 am

    #1566600

    And your question is?

    It's best to run SSMS on the computer on which the package resides when you're setting up SSIS jobs. If you run it on a client PC, it will look for the files locally.

    John

  • December 7, 2012 at 7:29 am

    #1566613

    Hi John

    but this does not happen when user have sysadmin permission

    but without this it takes time

  • December 7, 2012 at 7:46 am

    #1566618

    What permission does the user have, if not sysadmin? To manage jobs, membership of certain role(s) in msdb is necessary.

    John

  • December 9, 2012 at 9:57 pm

    #1566906

    the permissions that user have are

    db_ssisadmin

    db_owner

    Sqlagentoperatorrole

    sqlagentreaderrole

    sqlagentuserrole

  • December 10, 2012 at 6:33 am

    #1567003

    hey john

    plz help for the issue

  • December 11, 2012 at 1:52 am

    #1567284

    What happens if you create a new login and make it a member of SQLAgentOperatorRole in msdb?

    John

  • December 11, 2012 at 2:07 am

    #1567292

    hey John its still taking the time but this does not happen when

    i give the user sysadmin permission but i dnt want user to have this permission.

  • December 11, 2012 at 2:27 am

    #1567300

    I don't know what's going on, then. Try running a Profiler trace to see what's happening in the background when you modify the job.

    John

  • December 11, 2012 at 4:45 am

    #1567373

    Thanks

    i have run profiler for sqlagentoperatorrole it is searching through all the drives available on the networkbut for ssisadmin it leaves the network drive

    any method to restrict this.

  • December 11, 2012 at 5:35 am

    #1567395

    Sorry, but I'm lost now. Are we talking about sysadmin on ssisadmin (never heard of that)? What do you mean by "it leaves the network drive"? Could you post the relevant rows from your Profiler trace, please?

    John

  • December 11, 2012 at 6:44 am

    #1567415

    Sorry my fault

    for sysadmin permission it does not search for Drive that are available on my

    organisations network but for SQLAgentOperatorrole it searches for drives on my network.

  • December 11, 2012 at 6:52 am

    #1567421

    OK, I think what I'm about to say is right, but you may want to check it. When you run a job as a login that's a member of sysadmin, it runs in the context of the SQL Server Agent service account. When you run a job as a login that isn't sysadmin, it runs in the context of whatever you're logged in as. That must be why it's scanning the drives you have mapped when you're not sysadmin, but not doing so when you are. You'll need to find a way to provided a list of UNC locations for the job to scan.

    John

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

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