Solved

How to deploy ssrs and ssis objects to antoher server

Posted on 2014-03-12
4
595 Views
Last Modified: 2016-02-10
I've developed a set of SSIS DTSX files and associated reports on my development station.   I now need to move them to a production server.  What is the best way to update my objects to point to them to the other database and file systems?   Ideally I want things so I can quickly change them back to my laptop for development.
0
Comment
Question by:canuckconsulting
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 37

Accepted Solution

by:
ValentinoV earned 500 total points
ID: 39926324
You need to look into package configuration.  A method that's used a lot is called indirect package configuration.  In this method you set up an environment variable that points to a configuration XML file or table.  So your development machine can point to a configuration file/table on your PC while the production environment will have an environment variable that points to the production configuration.

Details: Best Practices for Integration Services Configurations [MSDN]
0
 

Author Comment

by:canuckconsulting
ID: 39932427
Thanks...this is going to be very useful.

One problem I have just run into is that I can't seem to deploy to my production server.  I have developing using BIDS on the Visual Studio 2012 shell against a SQL Server 2012 db.  After creating the default catalogue I have no problems deploying.

Our production server is SQL Server 2008 and when I point my SSIS deployment destination to it I get an error advising that the version of SQL Server does not support the selected operation as shown below.  Do I need to configure 2008 in some way to deploy SSIS ?

error
0
 
LVL 37

Assisted Solution

by:ValentinoV
ValentinoV earned 500 total points
ID: 39936947
Ouch!  Packages created with SSIS 2012 are not backwards-compatible and thus cannot be deployed to 2008...  So if you really want to get this to work you either need to develop your packages using BIDS 2008 or install an instance of SSIS 2012 on that production server...
0
 

Author Closing Comment

by:canuckconsulting
ID: 39945935
Thanks
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

My client sends a request to me that they want me to load data, which will be returned by Web Service APIs, and do some transformation before importing to database. In this article, I will provide an approach to load data with Web Service Task and X…
From implementing a password expiration date, to datatype conversions and file export options, these are some useful settings I've found in Jasper Server.
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar. Int…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question