Subject RE: [ib-support] forced writes off under NT/2K/XP
Author Alan McDonald
it's not a problem, it's just a setting you can choose to make. You're not
"forced" to make this setting but the message outlines what might happen if
you don't. For example, on a website using an ODBC driver, connections are
made and dropped in milliseconds... with forced write set to OFF, there may
be no appreciable difference to setting it ON. In a C/S setup where very
long connection times are maitained, then on NT it would be better to set it
to ON

-----Original Message-----
From: jbperez808 <jbperez808@...> [mailto:jbperez808@...]
Sent: Monday, 17 February 2003 9:51 AM
Subject: [ib-support] forced writes off under NT/2K/XP

Sorry if this has been answered before, but I just
need a clarification. An earlier message states:

"Forced Writes ON will write the data to disk as soon as
there's a change. Forced Writes OFF, by definition, will
write the data to disk when the system is idle, but under
Windows this is performed only when all of the connections
are disconnected. Your database could start with 3MB in
size and insert 3GB and never see the physical size increase
until all connections are disconnected. To my knowledge,
the problem doesn't exist on the other platforms(OS)."

Is this problem still present on Firebird 1.5 for NT?
What about Firebird 1.02? What about Firebird 1.0?

[On a sidenote, for a feature as potentially havoc-ridden
as this, EMS Quickdesk does not issue a proper warning in
the check box to disable it...]

Also, bug entry 447008 at sourceforge,
is very confusing, the summary says:

Win32 Forced Writes Default = ON

With the introduction of IB 6.0 the default settings
for newly created databases, under Win32, was chnaged
to OFF. This change was made to improve database
performance but at the expense of database

So which is the default? ON or OFF?

To unsubscribe from this group, send an email to:

Your use of Yahoo! Groups is subject to