Hi. We are contemplating using san (not sql) snapshots temporarily to deal with a very tight month end window in which we normally get one or two shots at extracting certain info from a voluminous database. Later, after we build and maintain incrementally a filtered version of this info, the tight window becomes less of an issue but the san snapshot technology may be incorporated into bringing up quickly qa environments for emergency and normal project purposes.
Anyway, from what I'm hearing, san snapshots can be taken at the server/disk level and leave files visible for sql attachment and other purposes. I'm guessing that if we distribute our dbs strategically on to different disks, some of the overhead associated with san snapshot technology volume can be avoided. I should know for sure in a few days. I do know that we already use san snapshots in certain situations for sql and other software but I dont believe we've used it yet for sql dbs from the same server distributed across multiple disks.
If this is even possible and we ever do something like this, I want to make sure that the database(s) on which things like security and perhaps other necessary server level objects are stored get distributed and isolated on to the smallest number of disks possible.
I'm not sure where this is going but definitely would like to know from the community where (which db(s)) anything having to do with security might be found so that we group our dbs appropriately.
I should point out that we are experimenting with solid state technolgy for RS and engine temp dbs. But either way, I'm guessing that if possible, temp dbs wouldnt be included in a snapshot.