 | |
#11
 
| |||
| |||
|
Re: global synchronization point -
09-19-2008
, 11:47 AM
|
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 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
#12
| |||
| |||
|
|
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 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
#13
| |||
| |||
|
|
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 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
#14
| |||
| |||
|
|
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 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
#15
| |||
| |||
|
|
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 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
#16
| |||
| |||
|
|
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 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
#17
| |||
| |||
|
|
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 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
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.