Re: TimesTen
- From: "Ghassan Salem" <salem.ghassan@xxxxxxxxx>
- To: "Jeremiah Wilton" <jeremiah@xxxxxxxxxxx>
- Date: Fri, 26 May 2006 09:50:05 +0200
Indeed, it's very similar to the 10gr2 addition.
On 5/26/06, Jeremiah Wilton <jeremiah@xxxxxxxxxxx> wrote:
Durable commits set to false in TimesTen sounds a lot like 'commit write
nowait' in Oracle 10g, except that in Oracle you can control it on as
fine-grained a basis as per individual transaction.
http://download-west.oracle.com/docs/cd/B19306_01/appdev.102/b14251/adfns_sq
lproc.htm#sthref182
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14200/statemen
ts_4010.htm
Jeremiah Wilton
ORA-600 Consulting
http://www.ora-600.net
________________________________________
From: Ghassan Salem
Sent: Thursday, May 25, 2006 12:55 PM
In TimesTen, you have much finer control over commits. When you create a
db,
you can specify 'durable commits=true', which means that every commit
insures that redolog is written to disk. You can put it to false, and the
redolog is written asynchronuously from the commit. But you can issue a
redolog sync from your program whenever you want.
- References:
- Re: TimesTen
- From: Ghassan Salem
- RE: TimesTen
- From: Jeremiah Wilton
Other related posts:
- » TimesTen
- » Re: TimesTen
- » Re: TimesTen
- » Re: TimesTen
- » Re: TimesTen
- » RE: TimesTen
- » Re: TimesTen
- » TimesTen - Alex Octan
Durable commits set to false in TimesTen sounds a lot like 'commit write nowait' in Oracle 10g, except that in Oracle you can control it on as fine-grained a basis as per individual transaction.
http://download-west.oracle.com/docs/cd/B19306_01/appdev.102/b14251/adfns_sq lproc.htm#sthref182
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14200/statemen ts_4010.htm
Jeremiah Wilton ORA-600 Consulting http://www.ora-600.net
________________________________________ From: Ghassan Salem Sent: Thursday, May 25, 2006 12:55 PM
In TimesTen, you have much finer control over commits. When you create a db, you can specify 'durable commits=true', which means that every commit insures that redolog is written to disk. You can put it to false, and the redolog is written asynchronuously from the commit. But you can issue a redolog sync from your program whenever you want.
- Re: TimesTen
- From: Ghassan Salem
- RE: TimesTen
- From: Jeremiah Wilton