all groups > sql server programming > september 2004 >
You're in the

sql server programming

group:

Persistance Transaction


Persistance Transaction faraz.khan NO[at]SPAM ezdoc.net
9/24/2004 11:40:29 PM
sql server programming:
Here is the scenario. My company uses a table to construct what-if
scenarios. After playing around with different values in the table,
they may want to keep the final table or start over with the table
from the point they start the sessions. These sessions can last for
days or weeks.

Is there a generic way of saving the table at one point in time and
later restoring it to that exact state? Like a transaction roll back.
But this transaction has to continue for several weeks during which a
connection cannot be maintained and several users may alter the data
in the table (insert, update & delete). Other tables in the DB may be
all changing during this time. We must not roll back them.

By generic i mean easy, and quick. I have been doing this by making a
backup of the database and then later restore it to a new db and copy
just the table i need. Is there a better way? An automatic or
Re: Persistance Transaction David Portas
9/25/2004 8:50:55 AM
Why not just add a Scenario column to the table. Keep all the possible
scenarios in there and then delete them when you've finished with them.

--
David Portas
SQL Server MVP
--

Re: Persistance Transaction Roji. P. Thomas
9/25/2004 12:18:48 PM
I suggest you create seperate what-if tables, and when the user
finally decides to save the data, write them to the original tables.

--
Roji. P. Thomas
Net Asset Management
https://www.netassetmanagement.com


[quoted text, click to view]

AddThis Social Bookmark Button