Checkpoints

Hi,
i have a complex database. If a user (database is set to single user)
make changes, and the user want do redo these changes, i need a kind of
manual setted checkpoints. Such a checkpoint is set before changes
made.
The idea is, to set a checkpoint, (store all checkpoints), and when its
necassary you can revert to a checkpoint.
Is this possible or is there another technique to realize this?
Thank you in advance
AlexSQL Server has "database snapshot" that you could potentially use. You can restore from a database
snapshot. But there can only exist *one* snapshot of a database if you want to restore from a (that)
snapshot.
But perhaps it is much cleaner to begin a transaction and rollback?
There's no built-in scheme where many users has many snapshots and you want to revert to some
certain snapshot for one of the users without affecting the other users (unless each user have their
own database). How would SQL Server understand what data that belongs to user A and revert only that
data? Not to speak about relationships between tables.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"alex" <earthquake.de@.freenet.de> wrote in message
news:1157460616.313916.180170@.d34g2000cwd.googlegroups.com...
> Hi,
> i have a complex database. If a user (database is set to single user)
> make changes, and the user want do redo these changes, i need a kind of
> manual setted checkpoints. Such a checkpoint is set before changes
> made.
> The idea is, to set a checkpoint, (store all checkpoints), and when its
> necassary you can revert to a checkpoint.
> Is this possible or is there another technique to realize this?
> Thank you in advance
> Alex
>|||Every change which is made, is encapsulated by an transaction and in
errorcase undone by the rollback or if success with commit.
So i want to set a checkpoint at start of editing the tables, and if
the user want to
undo his changes (created new datarows etc.) so the user can go to the
checkpoint, created at start editing.
So it is a single user instance all changes since last checkpoint
should be reverted.
A case of "higher level transaction"
Alex
Tibor Karaszi schrieb:
> SQL Server has "database snapshot" that you could potentially use. You can restore from a database
> snapshot. But there can only exist *one* snapshot of a database if you want to restore from a (that)
> snapshot.
> But perhaps it is much cleaner to begin a transaction and rollback?
> There's no built-in scheme where many users has many snapshots and you want to revert to some
> certain snapshot for one of the users without affecting the other users (unless each user have their
> own database). How would SQL Server understand what data that belongs to user A and revert only that
> data? Not to speak about relationships between tables.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "alex" <earthquake.de@.freenet.de> wrote in message
> news:1157460616.313916.180170@.d34g2000cwd.googlegroups.com...
> > Hi,
> > i have a complex database. If a user (database is set to single user)
> > make changes, and the user want do redo these changes, i need a kind of
> >
> > manual setted checkpoints. Such a checkpoint is set before changes
> > made.
> >
> > The idea is, to set a checkpoint, (store all checkpoints), and when its
> > necassary you can revert to a checkpoint.
> > Is this possible or is there another technique to realize this?
> >
> > Thank you in advance
> > Alex
> >|||<DIV>"Tibor Karaszi"
<tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
news:e7Mln5O0GHA.772@.TK2MSFTNGP05.phx.gbl...</DIV>> SQL Server has "database
snapshot" that you could potentially use. You can restore from a database
> snapshot. But there can only exist *one* snapshot of a database if you
> want to restore from a (that) snapshot.
> But perhaps it is much cleaner to begin a transaction and rollback?
> There's no built-in scheme where many users has many snapshots and you
> want to revert to some certain snapshot for one of the users without
> affecting the other users (unless each user have their own database). How
> would SQL Server understand what data that belongs to user A and revert
> only that data? Not to speak about relationships between tables.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "alex" <earthquake.de@.freenet.de> wrote in message
> news:1157460616.313916.180170@.d34g2000cwd.googlegroups.com...
>> Hi,
>> i have a complex database. If a user (database is set to single user)
>> make changes, and the user want do redo these changes, i need a kind of
>> manual setted checkpoints. Such a checkpoint is set before changes
>> made.
>> The idea is, to set a checkpoint, (store all checkpoints), and when its
>> necassary you can revert to a checkpoint.
>> Is this possible or is there another technique to realize this?
A "marked transaction" can be your checkpoint. They are all stored in
msdb..logmarkhistory. You can restore a database backup and apply the
transaction log up through a marked transaction.
Using Marked Transactions (Full Recovery Model)
http://msdn2.microsoft.com/en-us/library/ms187014.aspx
David|||Often, the quality of the responses received is related to our ability to
'bounce' ideas off of each other. In the future, to prevent folks from
wasting time on already answered questions, please:
Don't post to multiple newsgroups. Choose the one that best fits your
question and post there. Only post to another newsgroup if you get no answer
in a day or two (or if you accidentally posted to the wrong newsgroup), and
indicate that you've already posted elsewhere.
If you really think that a question belongs into more than one newsgroup,
then use your newsreader's capability of multi-posting, i.e., posting one
occurrence of a message into several newsgroups at once. If you multi-post
appropriately, answers 'should' appear in all the newsgroups. Folks
responding in different newsgroups will see responses from each other, even
if the responses were posted in a different newsgroup.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"alex" <earthquake.de@.freenet.de> wrote in message
news:1157460616.313916.180170@.d34g2000cwd.googlegroups.com...
> Hi,
> i have a complex database. If a user (database is set to single user)
> make changes, and the user want do redo these changes, i need a kind of
> manual setted checkpoints. Such a checkpoint is set before changes
> made.
> The idea is, to set a checkpoint, (store all checkpoints), and when its
> necassary you can revert to a checkpoint.
> Is this possible or is there another technique to realize this?
> Thank you in advance
> Alex
>