Timeline for Best Setup for Database Cluster
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2011 at 0:32 | comment | added | mrdenny | @Steven, in order for an outage that short you'll want either clustering, or mirroring in sync mode (high safety). The fail over time will be a few seconds to a few minutes depending on the amount of data in the transaction log which needs to be rolled forward and back. SQL Enterprise Edition will help with this as it uses are different recovery procedure than the lower editions. | |
| Feb 18, 2011 at 0:26 | comment | added | mrdenny | @Gaius, no it isn't. It MIGHT be depending on how your storage array is designed. Even if the array stores all the data on all the disks, breaking the databases up into multiple LUNs give you better MPIO options as you are probably using the native Active/Passive MPIO driver that Windows provides, and it will also give Windows multiple disk queues, so that if one IO path stalls for some reason, IO can still be handled over other IO paths for the other LUNs. | |
| Feb 17, 2011 at 15:20 | comment | added | Nodey The Node Guy | thanks for your response. We are storing mostly medical data but also doing things like billing, A/R, etc. So, I would suspect we couldnt be down for too long, maybe a few minutes at max. doctors and dentists submitting claims don't want to be shut out of the system and we don't want them to be either! Thanks again. | |
| Feb 17, 2011 at 7:13 | comment | added | Gaius | If you are using a SAN device then splitting data/indexes/whatever is obsolete advice. | |
| Feb 17, 2011 at 4:47 | history | answered | mrdenny | CC BY-SA 2.5 |