sql server redux

Jay Madren JaysLists at triad.rr.com
Mon Sep 20 15:49:20 EDT 2004


I haven't investigated SQL Server snapshot backups before, but a quick look
through the docs and their web site seems to indicate that there's probably
some API or DMO call used to "freeze" the database at the time of the
snapshot.  The MSDN site refers to some VC++ examples, but I couldn't locate
them.  If you could find them, then you should be able to determine how they
are accomplishing it.

I'm curious, why do you want to do a snapshot backup instead of the normal
backup method.  I understand that it's intended for high availability
scenarios and supposed to have minimal impact on the server, but you have to
have the right equipment to pull it off (3 way mirror or something like
that).  Is this what you're working with?

Jay Madren

-----Original Message-----
From: use-revolution-bounces at lists.runrev.com
[mailto:use-revolution-bounces at lists.runrev.com]On Behalf Of Mark D.
Sent: Monday, September 20, 2004 14:59
To: use-revolution at lists.runrev.com
Subject: sql server redux

"Won't a transaction with appropriate serialization give you the same
result, but without interrupting other users' ability to access the
database during the snapshot process?"

Okay, this is where my nearly perfect ignorance comes to play--I don't
really understand how a transaction with appropriate serialization
would work for a snapshot. If other users are able to access the
database, then the files are open, things are in a cache, and the
snapshot won't be good for backup purposes--unless there is something
here I'm missing (entirely possible!)

I thought that the actual server itself needs to be paused to do a good
snap--much the same as in a backup scenario, just not taking quite so
long (less than one second).


use-revolution mailing list
use-revolution at lists.runrev.com

More information about the use-livecode mailing list