|
Home > Archive > microsoft.public.exchange2000.admin > October 2002 > When are t-logs committed to the Store
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
When are t-logs committed to the Store
|
|
| Del Pomerinke 2002-10-05, 8:13 pm |
| With E2K, when are tlogs committed, when the database is dismounted or when
the Information Store service is stopped? I know that with 5.5 the
uncommitted tlogs are written to the store when the Information Store
service is stopped.
| |
|
| that is not exactly correct - transaction logs are committed to the
databases when there is time...excerpt from Q271987:
Transaction log files also make writing data more efficient because it is
faster
to update pages sequentially in a log file than to insert pages into the
database. When a change occurs in the database, the database engine updates
the
data in memory. It synchronously writes a record of the transaction to the
log
file, telling it how to redo the transaction if the system fails. Then the
database engine writes the data to the database on disk. To minimize disk
input/output, the database engine transfers pages to disk in batches.
"Del Pomerinke" <del_pomerinke@spamhell.com.NOSPAM.COM> wrote in message
news:OV71BbiSCHA.1652@tkmsftngp09...
> With E2K, when are tlogs committed, when the database is dismounted or
when
> the Information Store service is stopped? I know that with 5.5 the
> uncommitted tlogs are written to the store when the Information Store
> service is stopped.
>
>
| |
| Dave Howe [MS] 2002-10-05, 8:13 pm |
| Actually, if you stop the Information Store service gracefully, all
outstanding transactions will be committed to the database(s).
--
Dave Howe
Microsoft PSS
This posting is provided "AS IS" with no warranties, and confers no rights.
"Susan" <sconkey@mgmmirage.com> wrote in message
news:eJSZofiSCHA.2364@tkmsftngp08...
> that is not exactly correct - transaction logs are committed to the
> databases when there is time...excerpt from Q271987:
>
> Transaction log files also make writing data more efficient because it is
> faster
>
> to update pages sequentially in a log file than to insert pages into the
>
> database. When a change occurs in the database, the database engine
updates
> the
>
> data in memory. It synchronously writes a record of the transaction to the
> log
>
> file, telling it how to redo the transaction if the system fails. Then the
>
> database engine writes the data to the database on disk. To minimize disk
>
> input/output, the database engine transfers pages to disk in batches.
>
> "Del Pomerinke" <del_pomerinke@spamhell.com.NOSPAM.COM> wrote in message
> news:OV71BbiSCHA.1652@tkmsftngp09...
>
> > With E2K, when are tlogs committed, when the database is dismounted or
> when
> > the Information Store service is stopped? I know that with 5.5 the
> > uncommitted tlogs are written to the store when the Information Store
> > service is stopped.
> >
> >
>
>
| |
| Dave Howe [MS] 2002-10-05, 8:13 pm |
| Susan's information IS correct, as long as the Information Store service is
started and the database(s) are mounted.
--
Dave Howe
Microsoft PSS
This posting is provided "AS IS" with no warranties, and confers no rights.
"Susan" <sconkey@mgmmirage.com> wrote in message
news:eJSZofiSCHA.2364@tkmsftngp08...
> that is not exactly correct - transaction logs are committed to the
> databases when there is time...excerpt from Q271987:
>
> Transaction log files also make writing data more efficient because it is
> faster
>
> to update pages sequentially in a log file than to insert pages into the
>
> database. When a change occurs in the database, the database engine
updates
> the
>
> data in memory. It synchronously writes a record of the transaction to the
> log
>
> file, telling it how to redo the transaction if the system fails. Then the
>
> database engine writes the data to the database on disk. To minimize disk
>
> input/output, the database engine transfers pages to disk in batches.
>
> "Del Pomerinke" <del_pomerinke@spamhell.com.NOSPAM.COM> wrote in message
> news:OV71BbiSCHA.1652@tkmsftngp09...
>
> > With E2K, when are tlogs committed, when the database is dismounted or
> when
> > the Information Store service is stopped? I know that with 5.5 the
> > uncommitted tlogs are written to the store when the Information Store
> > service is stopped.
> >
> >
>
>
| |
| Del Pomerinke 2002-10-05, 8:13 pm |
| I understand Tlogs are committed online when there is time.
But when the Store is stopped all uncommitted logs are written to the store.
With E2K does this happen at Information Store stoppage or database
dismount?
"Susan" <sconkey@mgmmirage.com> wrote in message
news:eJSZofiSCHA.2364@tkmsftngp08...
> that is not exactly correct - transaction logs are committed to the
> databases when there is time...excerpt from Q271987:
>
> Transaction log files also make writing data more efficient because it is
> faster
>
> to update pages sequentially in a log file than to insert pages into the
>
> database. When a change occurs in the database, the database engine
updates
> the
>
> data in memory. It synchronously writes a record of the transaction to the
> log
>
> file, telling it how to redo the transaction if the system fails. Then the
>
> database engine writes the data to the database on disk. To minimize disk
>
> input/output, the database engine transfers pages to disk in batches.
>
> "Del Pomerinke" <del_pomerinke@spamhell.com.NOSPAM.COM> wrote in message
> news:OV71BbiSCHA.1652@tkmsftngp09...
>
> > With E2K, when are tlogs committed, when the database is dismounted or
> when
> > the Information Store service is stopped? I know that with 5.5 the
> > uncommitted tlogs are written to the store when the Information Store
> > service is stopped.
> >
> >
>
>
| |
|
| since it is possible to dismount a single database and not need to stop the
instance of store.exe or interrupt service to any other databases, I would
tend to believe that all log files would be committed to the database when
an individual store is dismounted...dismounting would be tantamount to a
graceful shut down...
"Del Pomerinke" <del_pomerinke@spamhell.com.NOSPAM.COM> wrote in message
news:u4PePTuSCHA.1360@tkmsftngp13...
> I understand Tlogs are committed online when there is time.
>
> But when the Store is stopped all uncommitted logs are written to the
store.
> With E2K does this happen at Information Store stoppage or database
> dismount?
>
> "Susan" <sconkey@mgmmirage.com> wrote in message
> news:eJSZofiSCHA.2364@tkmsftngp08...
> > that is not exactly correct - transaction logs are committed to the
> > databases when there is time...excerpt from Q271987:
> >
> > Transaction log files also make writing data more efficient because it
is
> > faster
> >
> > to update pages sequentially in a log file than to insert pages into the
> >
> > database. When a change occurs in the database, the database engine
> updates
> > the
> >
> > data in memory. It synchronously writes a record of the transaction to
the
> > log
> >
> > file, telling it how to redo the transaction if the system fails. Then
the
> >
> > database engine writes the data to the database on disk. To minimize
disk
> >
> > input/output, the database engine transfers pages to disk in batches.
> >
> > "Del Pomerinke" <del_pomerinke@spamhell.com.NOSPAM.COM> wrote in message
> > news:OV71BbiSCHA.1652@tkmsftngp09...
> >
> > > With E2K, when are tlogs committed, when the database is dismounted or
> > when
> > > the Information Store service is stopped? I know that with 5.5 the
> > > uncommitted tlogs are written to the store when the Information Store
> > > service is stopped.
> > >
> > >
> >
> >
>
>
|
|
|
|
|