Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. deploying an SSIS package to server

deploying an SSIS package to server

Scheduled Pinned Locked Moved Database
sql-serversysadmintutorialquestion
4 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Alaric_
    wrote on last edited by
    #1

    Hi, I built an SSIS package locally and now I need to deploy it to our development instance of SQLServer...can anyone tell me how to go about doing that?

    "I need build Skynet. Plz send code"

    A T 2 Replies Last reply
    0
    • A Alaric_

      Hi, I built an SSIS package locally and now I need to deploy it to our development instance of SQLServer...can anyone tell me how to go about doing that?

      "I need build Skynet. Plz send code"

      A Offline
      A Offline
      Alaric_
      wrote on last edited by
      #2

      ok...I've got the thing deployed, but I'm trying to run it from a job. If my job is running in a database called "dev" and a package named "foo" is running in Integration Services on "dev", how would I go about referencing it in my job step command? (just a stab)

      EXEC @ReturnCode = msdb.dbo.sp_add_jobstep @job_id=@jobID, @step_name=N'Execute SSIS package',
      @step_id=1,
      @command=N'/FILE "\\dev\MSDB\Maintenance Plans\foo.dtsx" /CHECKPOINTING OFF /SET \Package.Variables[User::Correlator].Properties[Value];' + @Correlator + ' /REPORTING E'

      Looking at my @command assignment, is anything missing? I have the thing deployed to MSDB\Maintenance Plans, but I really don't know if the reference is as simple as this. ..Is it? I'm getting an "XML Parsing error"(<-pseudo) that seems to be a permissions error when trying to open the package. Either the package doesn't exist at the location specified or my account doesn't have access to the file...I'm pretty confident that I have access to the file, so my other logical option is that the context that I have provided in my snippet above is incorrect. Does anyone know how I should go about referencing it?

      "I need build Skynet. Plz send code"

      1 Reply Last reply
      0
      • A Alaric_

        Hi, I built an SSIS package locally and now I need to deploy it to our development instance of SQLServer...can anyone tell me how to go about doing that?

        "I need build Skynet. Plz send code"

        T Offline
        T Offline
        thatraja
        wrote on last edited by
        #3

        Managing and Deploying SQL Server Integration Services[^] Deploying SSIS Packages in SQL Server 2005[^] Deploying SSIS Packages[^]

        thatraja


        **My Tip/Tricks
        My Dad had a Heart Attack on this day so don't...
        **

        A 1 Reply Last reply
        0
        • T thatraja

          Managing and Deploying SQL Server Integration Services[^] Deploying SSIS Packages in SQL Server 2005[^] Deploying SSIS Packages[^]

          thatraja


          **My Tip/Tricks
          My Dad had a Heart Attack on this day so don't...
          **

          A Offline
          A Offline
          Alaric_
          wrote on last edited by
          #4

          Thank you very much for the documentation, but I had already referenced the materials at those links. My specific question was surrounding the command-line reference that I was making to my package after it had been deployed. ...at any rate, I found out what my problem was. I was attempting to reference the package with the FILE switch, but I had not deployed the package to the file system of the database server which I was attempting to reference (I had deployed it directly to the SQL Server instance) ...I still am unsure of how I would go about referencing the package from SQL Server directly, but I repeated my deployment, this time to the file system, and adjusted my reference to the location on the file system, and the package was able to be loaded at run-time. just fyi...anyone referencing a package with the "FILE" switch, make sure your package is deployed to the file system lol ...it'll save you a night's sleep.

          "I need build Skynet. Plz send code"

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups