none
How do I deploy SSIS packages when I have SQL Server 2008 and SQL Server 2010 on the same machine?

    Question

  • I have a project in SQL Server 2010.  It is the same project I had in SQL Server 2008.  This project contains about 180 SSIS packages.  Each package uploads a single SQL table with data.  These packages are almost identical in their structure, but each package loads a single different table.  I have Microsoft Visual Studio 2008 and MS Visual Studio 2010 BOTH installed on this same machine.  I am seeking to call all of these VS 2010 packages from a SQL Server Agent Job the same as I called them from a SQL Server 2008 job.  I've created the Deployment Manifest in 2010, yet when I double click it to make it run its wizard, I ultimately get:

    Could not save the package "filepath\goes\here\SSISpkg.dtsx" to SQL Server "(local)"

    Additional Information:

    Storing or modifying packages in SQL Server requires the SSIS runtime and database to be the same version.  Storing packages in earlier versions is not supported.

    These 180 SSIS packages I cited above were converted from VS 2008 to VS 2010.  All of them run fine manually in 2010.  I am trying to get them deployed with this deployment manifest wizard so they can ultimately be incorporated into a SQL Server 2012 Agent Job and run after hours.  The database they load into is on the 2012 version of MS SQL Server Manager.  Can ANYONE help me with this?

    THANKS!


    R. J. Head

    Wednesday, November 21, 2012 7:34 PM

Answers

  • It sounds like you have an instance of SQL 2008 and an instance of SQL 2012 on the same machine.  It also sounds like you are trying to deploy to the default instance.  I am going to assume that your 2012 instance is a named instance and that you need to be deploying to (local)\<instancename> rather than (local)

    Chuck Pedretti | Magenic – North Region | magenic.com

    • Proposed as answer by Devanathan thiru Wednesday, November 21, 2012 10:35 PM
    • Marked as answer by Eileen Zhao Wednesday, November 28, 2012 2:18 AM
    Wednesday, November 21, 2012 8:27 PM

All replies

  • There is no SQL Server 2010, perhaps 2012 is the one you got installed alongside ver 2008? Am I right?

    Seems you need to merely upgrade the SSIS 2008 version packages to SSIS 2012 and the schedule them for execution.

    If SSIS 2012 is installed then VS 2010 can do that. Or you can do the package upgrade wizard.


    Arthur My Blog

    Wednesday, November 21, 2012 7:47 PM
  • It sounds like you have an instance of SQL 2008 and an instance of SQL 2012 on the same machine.  It also sounds like you are trying to deploy to the default instance.  I am going to assume that your 2012 instance is a named instance and that you need to be deploying to (local)\<instancename> rather than (local)

    Chuck Pedretti | Magenic – North Region | magenic.com

    • Proposed as answer by Devanathan thiru Wednesday, November 21, 2012 10:35 PM
    • Marked as answer by Eileen Zhao Wednesday, November 28, 2012 2:18 AM
    Wednesday, November 21, 2012 8:27 PM