Hello We are looking to migrate to SQL 2012 - as part of this process we are wanting to seperate out to two servers, one containing the Application databases, the other being a copy of these databases for reporting, utilising Reporting Services. The issue I have is I am not sure how to make this "copy". my requirments are quite minimal Reporting Services DB to have Stored procedures. Cost of Licensing - e.g. Enterprise is likely to expensive unless I have a very good (water tight) business case. Reporting data can be 24 hours old I have looked at replication and log shipping as possible alternatives to an Enterprise license mirroring solution - but not sure if this will do what I want I am open to any thoughts, please take anything not written here as "not considered" Regards.

I think that having dedicated SSRS server you will need to pay for license but not sure for 100 percent. Are you talking about adding SSRS to HA env.? Like clustering?Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/

Hello. Thanks for responding quickly The additional license has been accounted for - so I have that in the budget :-) We use VMWare which performs the required "company availibility". My question really is focussing on the "how do I make it happen" rather than any Infrastructure/DR issues, although its fair to say that SSRS would not need to be in a HA Env at the moment as this is the first stage to getting the company to understand how reporting can help them.

Just install whole SQL Server (including SSRS) , that's all.Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/

Hi Uri Let me explain a bit clearer. I have SQLServer1 which contains the databases which for arguments sake I will call "Live" I also have SQLServer2 which has reporting services installed, which for arguments sake I will call "Reporting" I want to get the data from "Live" to "Reporting" - with the above conditions inposed. The reason for this is to reduce load on the "Live", when Reports are run. I hope this is a bit clearer.

Hi al00fy, In SQL Server, a high-availability solution masks the effects of a hardware or software failure and maintains the availability of applications so that the perceived downtime for users is minimized. Database mirroring is a solution to increase database availability by supporting almost instantaneous failover. However, this feature will be removed in a future version of Microsoft SQL Server. We recommend that you use AlwaysOn Availability Groups instead. For more information, please see: High Availability Solutions (SQL Server) In Reporting Services, the scale-out deployment provides a way to share a database. If one report server goes down, other servers in the same deployment will continue to work. A scale-out deployment enables us to increase the number of users who concurrently access reports and improve the availability of the report server. For more information about configuring Reporting Services for Scale-Out Deployment, please see: Configure a Native Mode Report Server Scale-Out Deployment Hope this helps. Regards, Mike Yin TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.