>We are experiencing missing records following BSOD on a Windows 2K Server with Terminal Services. Sometimes we lose 1000's of records and several days of information. Data loss is consistently on one main table (heavily used for lookups, etc.) approximately 260mb in size. No corruption, just missing records from the last entered items. (we must rebuild indexes after this occurs) Other tables are fine, no data loss.
>

ONe of my clients has experienced this twice recently, (Win NT, not Win2K) and I think that what happens is that records created since the table was last opened are gone. WinNT seems to cache writes until the table is completely closed. Not suer if this helps at all, but...

BTW, BSOD is most often (always?) caused by a hardware or driver problem. I would get to the bottom of it as quickly as possible. My client's most recent was caused by a printer driver, but I've seen incompatible video cards and drivers, and bad memory do the same thing. BSOD on a server is very bad news.