Issues with Jet Databases on Compressed Drives

Do not put files that are managed by extensible storage engine (ESENT or ESE) on a compressed drive. Placing a Microsoft Jet database on a compressed drive may cause write-through delays that can cause Jet database corruption.

To avoid a possible data loss that may be caused by a corrupted database, make sure not to put the following items on a compressed drive. Note that this list includes any Jet-related files such as DIT files, logs, checkpoints, and temporary databases:

• Active Directory (NTDS)
• File Replication service (FRS)
• Windows Internet Name service (WINS)
• DHCP
• Security Configuration Engine (SCE)
• Certificate Server
• Terminal Services Session folder
• Terminal Services Licensing service
• Catalog database
• Help and Support Services
• Directory Synchronization service (MSDSS)
• Remote Storage (RSS)
• Phone Book service
• Single Instance Store (SIS) Groveler
• Windows NT Backup/Restore
• Exchange store
• Microsoft Exchange folder (SRS and DXA)
• Key Management service (KMS)
• Instant Messaging
• Content Indexing

Note Do not install Windows Server 2003, Standard Edition on a compressed drive unless the drive was compressed with the NTFS file system compression utility. Uncompress a DriveSpace or DoubleSpace volume before running Setup on it. For more information about Jet databases and compressed drives, click the following article number to view the article in the Microsoft Knowledge Base: