авторРассматриваю:

Для каких целей?

автор1)Надёжность

Вам сколько 9ок?

автор2)Требования к рабочей среде

У каждой СУБД в доке раздел "Hardware and Software Requirements"

автор3)Особенности архитектуры и функциональные возможности

Тут, понимаете ли, на кажду из СУБД по книге страниц в 1000 можно написАть.

автор4)Производительность

-Ну, как приборы?
-33
-Что "33"?!
-А что "Ну, как приборы"???!!! ((с) Анекдот)

Хотя во 2 и 4ом случае Вам сюда: http://www.tpc.org/

SiemarglНе соврать бы сильно - AFAIK чексуммы создавались для бэкапов на ленту, где метеоритов поболее.

Отнюдь...

MS SQL:


PAGE_VERIFY { CHECKSUM | TORN_PAGE_DETECTION | NONE }
Discovers damaged database pages caused by disk I/O path errors. Disk I/O path errors can be the cause of database corruption problems and are generally caused by power failures or disk hardware failures that occur at the time the page is being written to disk.

CHECKSUM
Calculates a checksum over the contents of the whole page and stores the value in the page header when a page is written to disk. When the page is read from disk, the checksum is recomputed and compared to the checksum value stored in the page header. If the values do not match, error message 824 (indicating a checksum failure) is reported to both the SQL Server error log and the Windows event log. A checksum failure indicates an I/O path problem. To determine the root cause requires investigation of the hardware, firmware drivers, BIOS, filter drivers (such as virus software), and other I/O path components.

TORN_PAGE_DETECTION
Saves a specific bit for each 512-byte sector in the 8-kilobyte (KB) database page and stored in the database page header when the page is written to disk. When the page is read from disk, the torn bits stored in the page header are compared to the actual page sector information. Unmatched values indicate that only part of the page was written to disk. In this situation, error message 824 (indicating a torn page error) is reported to both the SQL Server error log and the Windows event log. Torn pages are typically detected by database recovery if it is truly an incomplete write of a page. However, other I/O path failures can cause a torn page at any time.

NONE
Database page writes will not generate a CHECKSUM or TORN_PAGE_DETECTION value. SQL Server will not verify a checksum or torn page during a read even if a CHECKSUM or TORN_PAGE_DETECTION value is present in the page header.

kdvЯ помню, в 91 работал на компе с диском в 5 мегабайт.

Ага, ага... 286 ХТ, 640 Кб озу, CGA графика... Во времена были.