Question:
Must transaction logging be ON while importing large data sets? Can
transaction logging be disabled when making batch updates to a large
database?
Background:
We have been testing with MS SQL server for some time with some large
databases (greater 30 million records per db). This data is completely
static except during infrequent reloads or updates. We are frustrated by
the automatic transaction logging that occurs with MS SQL server and are
seeking out alternatives such as PostgreSQL.
We would much prefer to incorporate our own "transaction" management via the
old-fashioned "backup & restore" mechanism instead of using the high
overhead of transaction logging by DBMSs like MS SQL. In other words, if
things goes wrong in the update process, then we'd rather just restore the
tables and indexes from tape.
Please let me know,
Jonathan Boarman
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
