how to deploy a solution created onto different system

Hot Topic

scope and attribute relationships..
Sending SQL Mail
how send the values from stored procedure to triggers?
Upgrade from MSDE 2000 to MSSQL 2005 Workgroup Edition?
Can I filter the data on mining structure, mining model?
Actual and Forecast as One Measure
Fire and forget messages
Access to TaskHost from derived Task class.
Data-Driven Subscriptions
Vertical Line

SQL Server

SQL Server 2005 Analysis Services - disk configuration
fail connect to intergrate services
SSAS minidumps after installing SP2
"Illegal characters in path" while getting varaible values from stored proc
The underlying connection was closed: Could not establish trust relationship with remote server.
Cannot connect
Unable to access the report server
POINTING TO SERVER
sqk 2K asks for a license key why?
Jet.OLEDB.4.0 and Linked Servers (SQL standard 2005 on Win2003 SP1)

how to deploy a solution created onto different system

Hi,

I have a solution with it packages, and the solution is running. Now, I want to deploy the same solution onto other server machine. What would be the best way to do this

Any suggestions regarding this



Answer this question

how to deploy a solution created onto different system

  • Mike Sage

    Well, if your packages are stored as file system files; the only think you have to do is to copy the packages files (.dtsx) onto the new SSIS server along with configuration files (if any). Project, Solution and datasource files do net need to be copied for deployment proposes. I don't know if that is the 'right' way or not but that's how I do it.

    I know the procedure is different if you are storing the packages in a DB.

     

    Update: I just googled 'SSIS deploy' and found some papers...have you read them

    http://www.google.com/search hl=en&q=SSIS+deploy



  • rebeccat

    Use package configuration to change connection strings and other values at run time, so you don't have to re-visit all packages:

    http://msdn2.microsoft.com/en-us/library/ms141682.aspx

    Make sure to check:

    • Protection level property in your packages.
    • Permission of the user running the packages in the new server (if different from current user)
    • Enable package logging so you have a clue if something goes wrong.

  • Dan Mikkelsen

    Hi Manish,

    If you right-click your SSIS project and click Properties, a project properties dialog will display.

    One of the options under Configuration Properties is Deployment Utility. If you select this option, you can set the CreatDeploymentUtility property to True. A Build will then create a file with an *.SSISDeploymentManifest extension in the path specified in the DeploymentOutputPath property.

    Executing *.SSISDeploymentManifest will start the SSIS Package Installation Wizard, which will guide you through the deployment process.

    Hope this helps,

    Andy

  • Sumit Bhatnagar

    Rafael,

    Thanks a lot for you response.

    We are using the package configuration for the details. My query was on how to port the solution, like what would be the best possible solution for porting our application onto different server. Like, I created the solution onto one server, and then after I want to deploy the same application onto the different server, then how should I go for it

    Currently, for our internal use, we directly copy the entire solutions folder to the different server and then change the package configuration details. But, this is not a clean way to do and we wanted to know about how we can deploy the applications onto the different server machine.

    Please suggest.
  • how to deploy a solution created onto different system
Answer this question