Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Best Way for reporting Purpose:In the Same Instance Expand / Collapse
Posted Sunday, June 16, 2013 7:04 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, November 15, 2016 3:33 AM
Points: 26, Visits: 772
In our environment we have sql server 2012 . we need the database in sql server 2012 to be used for reporting services. we hvae already being using it for reporting but we face lot's of blockings in it. Which is the best way to reports fetching. we dont need to replicate to secondary for reporting purpose as it depends on the application settings..
As of now i had taken a snapshot of the database everyday (job) for reporting purpose in live server itself. Disadvantages are there for snapshot as there is a over-head in I/O for the live database. If we consider to schedule a job for backup/restore then i am not sure whether restoration happens without any problem as there would be existing connections to the database as it couldn't be killed . so anyone suggest which type of high availability can be used.Also logshipping and mirorring cannot be done on the same instance.

Anyone could help me in solving this problem.
Post #1463953
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse