Quantcast
Channel: SQLServerCentral » Reporting Services » Reporting Services » Latest topics
Viewing all articles
Browse latest Browse all 2791

Design Question: What is the best practice for reporting on data that spans instances?

$
0
0
We are using SQL Server 2012 SP1, and we have around 30 instances of the database engine installed. We collect performance data throughout the day, and each instance currently stores its own data in its own "dba" database.At some point, we would like to create some Reporting Services reports that display data from the entire database farm, but we are not sure how to proceed. So far, these options come to mind:1) Use dynamic data sources so that a single report can connect to the desired database (via a drop down parameter list) at report runtime (this is what we are currently using, but it is awkward to switch between instances over and over again--it would be great to see the whole database farm represented on a single report run)2) Copy the desired tables from each individual "dba" database to a consolidated database on a daily basis and report on all of the instances using the consolidated data (this sounds like a lot of effort, and I don't want to create something that will be difficult to maintain down the road)3) Potentially use some unknown (to us) Reporting Services feature that allows a report to consume data from multiple instances without creating a maintenance nightmare of managing lots and lots of data setsWhat do other DBAs do for this kind of situation?By the way, Linked Servers are highly discouraged by our Data Security folks, and we cannot use a non-Production Linked Server with a Production server, or Production Linked Server with a non-Production server, which means that Linked Servers will not be able to present the whole database farm to a report for us.J

Viewing all articles
Browse latest Browse all 2791

Trending Articles