Quantcast
Channel: SQL Server Database Engine forum
Viewing all articles
Browse latest Browse all 12963

Design Database for Reports

$
0
0

I am using sql 2008 R2 SE. Currently I have separated out our reports databases that are being used for internal purpose. However these report databases are logshipped secondary databases being hosted on secondary server. The reason I separated reports databases from the transactional databases is I didnt wanted the queries being used for reports causing blocking and deadlocks with queries being used by our apps.

However due to growth in data the queries that I used in the rdl files are taking longer time to run. So some reports are taking very long time to load and output the results. And since I am querying against the standby secondary database I cannot add indexes. But the query execution plan suggests that adding some indexes would improve the performance by almost 90%. If I add these indexes to the primary database then its degrading performance as its causing slowness in the applications. And the applications and the reports built are using different queries.

I want to take experts opinions on how to implement a better strategy for reports in this scenario. Experts please share your valuable thoughts.


Viewing all articles
Browse latest Browse all 12963

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>