planning for a reporting enviornment ( MS SQL)
Hi Experts
we are planning a reporting enviornment , here is the scenario
We have a database pn primary site that sends logshipping updates to secondary (DR site) . (MS SQL 2005)
The instance on DR site should be cloned (on the same sql server installation) . for example
If database name is "production database" , ideally we need a clone it everynight on the same machine
but with a different name (e.g. ReportingDB).
what's the best method ?
we are planning a reporting enviornment , here is the scenario
We have a database pn primary site that sends logshipping updates to secondary (DR site) . (MS SQL 2005)
The instance on DR site should be cloned (on the same sql server installation) . for example
If database name is "production database" , ideally we need a clone it everynight on the same machine
but with a different name (e.g. ReportingDB).
what's the best method ?
niaz
If you already have a log shipping server, you can use that server for reporting if you don't have a very reporting need that span hours. (depends how do you configure your log shipping). The secondary log shipping server is sitting idle most of the time when its is not applying logs and can be used for (readonly) reporting.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Not sure if using DR site database is okay for reporting , log shipping makes the database read-only but as far as I know it disconnects users when it applies the log.in our enviornment , we receive logs every 30 min. So .. I'd rather have a copy or replica of database for reporting ....
There is no one right answer in this case.
1. Depends on your Service Level Requirement (SLR) you can tune the log ship interval.
2. When setting the log shipping for standby server you can out the option to disconnect the database.
3. Replication is another option to consider (as suggested by "mlmcc").
You pick your option VERY CAREFULLY based on your own particular environment and nature of the database. (eg: DB size, # of Transactions, OLTP, DSS, # of users, # of reports, Time to run those reports, available storage and HW resources to replicate/clone etc.)
1. Depends on your Service Level Requirement (SLR) you can tune the log ship interval.
2. When setting the log shipping for standby server you can out the option to disconnect the database.
3. Replication is another option to consider (as suggested by "mlmcc").
You pick your option VERY CAREFULLY based on your own particular environment and nature of the database. (eg: DB size, # of Transactions, OLTP, DSS, # of users, # of reports, Time to run those reports, available storage and HW resources to replicate/clone etc.)
ASKER
Thanks Niaz
It's a production database , not too huge . It's going to be around 1.5 GB . Intervall is 30 min.
Reporting database can be one day older than production.
It's okay if we can use the same stand-by database for reporting , my only concern is that I dont know for sure if it disconnects users every 30 min. or not ?
Is it possible to backup this standby database while it still receives logshipping updates ? I am thinking about a nightly backup - restore for reporting database.
It's a production database , not too huge . It's going to be around 1.5 GB . Intervall is 30 min.
Reporting database can be one day older than production.
It's okay if we can use the same stand-by database for reporting , my only concern is that I dont know for sure if it disconnects users every 30 min. or not ?
Is it possible to backup this standby database while it still receives logshipping updates ? I am thinking about a nightly backup - restore for reporting database.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.