global synchronization point

#1

hey all,

I was wondering if it was possible to do the following -

I would like to set a 'sync point' where

1) transactions could occur on a given database or databases after the
sync point was created in multiple sessions.
2) I could globally 'roll back' the database to the sync point.

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?

Ed

(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..)

#2

horos11 (AT) gmail (DOT) com pisze:

Quote:

[...]
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.

Quote:

(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.

Quote:

select @@version
go

Regards,

--
Marcin Najs

#3

horos11 (AT) gmail (DOT) com pisze:

Quote:

[...]
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.

Quote:

(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.

Quote:

select @@version
go

Regards,

--
Marcin Najs

#4

horos11 (AT) gmail (DOT) com pisze:

Quote:

[...]
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.

Quote:

(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.

Quote:

select @@version
go

Regards,

--
Marcin Najs

#5

horos11 (AT) gmail (DOT) com pisze:

Quote:

[...]
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.

Quote:

(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.

Quote:

select @@version
go

Regards,

--
Marcin Najs

#6

horos11 (AT) gmail (DOT) com pisze:

Quote:

[...]
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.

Quote:

(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.

Quote:

select @@version
go

Regards,

--
Marcin Najs

#7

horos11 (AT) gmail (DOT) com pisze:

Quote:

[...]
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.

Quote:

(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.

Quote:

select @@version
go

Regards,

--
Marcin Najs

#8

horos11 (AT) gmail (DOT) com pisze:

Quote:

[...]
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.

Quote:

(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.

Quote:

select @@version
go

Regards,

--
Marcin Najs

#9

horos11 (AT) gmail (DOT) com pisze:

Quote:

[...]
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.

Quote:

(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.

Quote:

select @@version
go

Regards,

--
Marcin Najs

#10

On Sep 17, 7:17*pm, horo... (AT) gmail (DOT) com wrote:

Quote:

hey all,

I was wondering if it was possible to do the following -

I would like to set a 'sync point' where

1) transactions could occur on a given database or databases after the
sync point was created in multiple sessions.
2) I could globally 'roll back' the database to the sync point.

The "es" after database is the sticky point here. If you mean "within
the same database server" you're OK. If you mean across database
servers I think what you are after is known as an "XA" architecture
and requires additional product for the database vendor [be it Oracle
or Sybase] as well a "transaction monitor" or equivalent (J2EE
Application Server, e.g.) and application support to do it right.
What if your application creates
flat files, for example, or sends pub / sub messages; are actions
required there (external to your database(s)) when you rollback?

Your problem statement is very general and (potentially) very
ambitious at the same time.

Keith