Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
uofmoo
Starting Member
6 Posts |
Posted - 2008-11-07 : 15:56:09
|
Hello, Just wondering everyone's opinion on:Locking down production so only DBAs & processes have access to it... for purposes of having no question of load or quality whatsoever on production... and using mirroring or copying selective data to other servers for users/reporting/etcIs it just a matter of "if u have disk space and network capacity go for it"?Seems like a headache waiting to happen with data becoming out of sync or out of date using selective copying. should one use replication / log shipping / mirroring instead? what is the best practice?thanks. |
|
Elisabeth Redei
Starting Member
15 Posts |
Posted - 2008-11-09 : 11:58:04
|
Hi,For reporting you should be aware that a database mirror is not directly accessible to clients (because it is continously loading transaction). You can use it together with Snapshots to get reporting capabilities, you can read about the concept here: "Database Mirroring and Database Snapshots", http://msdn.microsoft.com/en-us/library/ms175511(SQL.90).aspx.Sort of the same goes for Log Shipping. You can make it somewhat accessible to clients but you have to kick any users out as soon as a transaction log is being restored (and this you set up a schedule for so if you are only loading transactions logs during the night, your Secondary server can be used for reporting during the day).Both Mirroring and Logshipping is on the database level whereas with Replication you can choose to replicate only a subset of your data. A subscriber is always accessible to your clients.You didn't give us much information about the requirements for the reporting but regardless I would say that any of the other options are better than a homegrown copying solution.HTH!/Elisabethelisabeth@sqlserverland.com |
|
|
|
|
|