Re: global synchronization point
- From: mnajs <marcinn@xxxxxxxxxx>
- Date: Thu, 18 Sep 2008 13:29:11 +0200
horos11@xxxxxxxxx pisze:
[...]
I'm not thinking of the transaction begin/commit/rollback cycle, I'm
thinking of it truly globally - where users could do multiple commits
and rollbacks, and then do a global rollback to a given point of time.
In oracle, I believe this is done through transaction logs; how do you
set up this in sybase?
Hi,
If you perform database+transaction log dumps for your database
you can 'rollback' the state of database loading database from
the last db dump and loading transactions up to a specified time
(i.e. using 'until_time' option). I'm not an expert but I think
it would work.
(ps - how do you get the version of sybase that you are running
against via isql? I see in my case the binary is old (1999) but I'm
assuming that the database itself is a lot newer..)
For ASE servers, @@verion is a server-wide, global variable that
contains version information.
>select @@version
>go
Regards,
--
Marcin Najs
.
- References:
- global synchronization point
- From: horos11
- global synchronization point
- Prev by Date: global synchronization point
- Next by Date: Re: global synchronization point
- Previous by thread: global synchronization point
- Next by thread: Re: global synchronization point
- Index(es):
Relevant Pages
|