Re: Is msdb transactional???

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Gregory A. Larsen (greg.larsen_at_netzero.com)
Date: 06/28/04 

Date: Mon, 28 Jun 2004 11:28:25 -0700

By default the msdb database is not transactional. Meaning the recovery
mode is "Simple". Although you can change the recovery mode to "Full" if
you desire. If you do this then you might need to backup the transaction
logs. If your recovery mode is "Simple" you will not be able to do
transaction log backups. Whereas if it is "Full" or "Bulk Logged" you can
perform transaction log backups.

All data is eventually stored in the data portion of the database. The
transaction log uses write-ahead. Meaning all changes to the database are
first written to the transaction log, before they are written to data
portion of the database. Updates are not directly written to data portion
of the database, but instead they are written to the buffer cache. Until a
data block is flushed from the buffer cache the change is not actual
writting to the data portion of the database. 

-- 
----------------------------------------------------------------------------
----------------------------------------------------------------------------
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Mary Kerrigan" <mkerrigan@ktoys.com> wrote in message
news:652faee5.0406281001.3562189e@posting.google.com...
> Once and for all, is the msdb database transactional?  I am getting
> conflicting answers searching for this in the newsgroup.  Do I need to
> backup the msdb transaction log?  One poster says that the backup
> history, jobs, etc. are kept in the msdb transaction log, another says
> they're kept in the database and NOT the log.

Relevant Pages

  • Re: Help - Timing Logic
    ... server application, both of which ran on the same box. ... the client applications and 'lodging' them in the database. ... Another part of the server application was dedicated to retrieving messages ... commit transaction ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help - Timing Logic
    ... put a trigger on the database table. ... Transaction and Database Locking - look at isolation levels / settings ... Maybe implement a message broker ... ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help - Timing Logic
    ... build a trigger on the database .. ... Transaction and Database Locking - look at isolation levels / settings ... If you need to implement a locking mechanism / or / logging mechanism / or / a checking mechanism to avoid duplicate messages caused by multi-threading ... ... message broker gets all the necessary messages or message id's from the database to be sent ... ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help - Timing Logic
    ... put a trigger on the database table. ... Transaction and Database Locking - look at isolation levels / settings ... Maybe implement a message broker ... ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help - Timing Logic
    ... If you need to implement a locking mechanism / or / logging mechanism / or / a checking mechanism to avoid duplicate messages caused by multi-threading ... ... Is it the READ from the database ... ... Perhaps a stored proc may be faster to execute and return the values as opposed to building the transaction in the code. ... implement as above locking only the records you retrieve / update - need to watch out here for table locking ... ...
    (microsoft.public.dotnet.languages.vb)