You can lose transactions in event of a crash.
SQL server will have thought it had written the trx when, in fact, its still sitting in the controllers cache.

When SQL svr restarts it looks in the db log file for uncommitted trx and it wont find them
or will find part of one. Now your DB will probably be marked as 'Suspect'.

At best you'll be missing data at worse you'll be missing data AND the db will be corrupt.

Fun stuff

-----Original Message-----
From: Melissa Faga [mailto:[Email Address Removed] Monday, August 12, 2002 3:16 PM
To: '[Email Address Removed] write-caching disk controller


Can someone explain to me why we shouldn't use a write-caching disk
controller with our SQL Server? I was just reviewing some SQL 7.0
documentation and it includes a CAUTION against write-cashing disk
controllers. Any information you have, would be appreciated.

Melissa


Melissa Faga
GIS/DB Manager
City of Redmond
425-556-2134
[Email Address Removed] unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page