Here, we have two cluster nodes ( SQLServerNode01 and SQLServerMode02), and one SQL Server instance ( Server4\SQL01). Having vetted the new ReportServer database, I had to migrate it to the production cluster and my plan had been to use the scale out deployment native to SSRS Enterprise.įigure 1 – Scaling out SSRS, Enterprise solution. For more information, please review the following link on using RS.EXE to migrate objects from one SSRS instance to another. I won’t cover how I merged the reports into a single ReportServer database and prepared it for migration to SQL Server 2016. Merging reports from two ReportServer databases This Staging Server had Developer Edition, which is unbounded feature-wise. In the meantime, I was working in the Staging environment, merging reports from the two existing SQL Server 2008 R2 Enterprise SSRS deployments into a single SQL Server 2016 ReportServer database, on the Staging Server.
SQL SERVER 2008 ENTERPRISE EDITION WINDOWS
The customer was busily building the new production cluster, using Cluster Shared Volumes on Windows Server 2016. When I first joined the project, I confess that “separation of duties” meant that I was blissfully unaware of the need for my solution to work on Standard Edition. The ability to “ scale out” SSRS to multiple frontend Web servers, so that one or more report server instances can share a single report server database, has always been an Enterprise Edition feature, and remains so in SQL Server 2016. It required a bit of creativity, but this article describes my solution, its merits and drawbacks. Sounds straightforward? It was, until I realized the new production cluster would have SQL Server 2016 Standard Edition, not Enterprise Edition. The idea was that should one node go “belly up”, the database instance containing the ReportServer database would failover and be available on the secondary node, and the remaining Report Server Web Portal, also on the secondary node, would continue to render the reports that drove their retail business. We would use a scale out deployment to attach two Report Server Web Portal front ends, one per node, to the clustered ReportServer database. Recently, I worked on a SSRS project where the customer wanted to consolidate over 1000 reports, from two existing SQL Server 2008 R2 Enterprise SSRS deployments, into a single SQL Server 2016 ReportServer database, and then deploy that database to a new 2-node production cluster. Despite its myriad shortcomings, obtuse errors and required hacks to make it work the way I want, it’s always somehow managed to tackle any business reporting requirement that I’ve thrown at it. I have been working with SSRS since its initial release in 2004 and have written about it extensively over the years, mostly favorably. Or I could just use replication with multiple machines, which Standard edition also supports.īasically, what it comes down to, is Enterprise really worth the extra cash ($8487 + CAL vs.Scaling out SSRS on SQL Server Standard Edition - Simple Talk Skip to content If I do, the extra cost of SQL Server Enterprise is going to be negligible. Limited to 4 CPUs - I understand this is number of physical processor sockets, not cores, and I don't plan on needing a server ever that has more than 4 sockets. Table and Index Partitioning - Does this really make a difference if everything is on the same disk/raid array? Parallel index operations - Only matters when you're creating or altering indexes. Based on the information found here, I've only been able to find a few differences. I'm not looking at the management and reporting side of things, which I understand Enterprise is much better at, but just at raw speed point of view. What are the specific advantages that the Enterprise version has over the Standard version in terms of speed. I'm looking into running a single instance web application on SQL Server 2008.
0 kommentar(er)
