Paul,

SnapDrive for Microsoft SQL Server 2000 is designed using NetApp's Virtual Local Disk technology, which enhances NTFS volume management to provide local disk emulation. With SnapDrive, you get high reliability and is ideal for high-volume transaction environments. In addition, SnapDrive supports front-end application clustering (using Microsoft Cluster Server) and allows the usage of a filer volume as a quorum disk.

If you need more information, please feel free to contact me. My contact number is below.

Thanks.

Narayan Venkat Manager, Windows Marketing Tel: (408) 822-3718 Cell: (408) 221-4297

-----Original Message----- From: Jay Newton (Email) [mailto:jnewton@chkenergy.com] Sent: Friday, March 15, 2002 7:47 AM To: 'Carruthers, Paul A'; 'toasters@mathworks.com' Subject: RE: MS SQL Server

We tried it for several months and had nothing but problems with it. We connected our SQL servers to our F840 Filer using a private GigE backbone as NetApp suggested. Using both NT4 and Windows 2000, the transactions we were making would end up causing the redirector to fail and we would lose connection to the database. This is a flaw with Microsoft and not NetApp. These disconnects caused multiple database corruptions making us restore from older dumps. We have since moved all our SQL and Oracle databases back to local storage due to this problem.

There is a product called SnapDrive (I think) from NetApp. It basically replaces the redirector. You have to be using Win2k and SQL2k with a dedicated volume per database server. Unless you use that, I wouldn't recommend putting SQL databases on a Filer.

-----Original Message----- From: Carruthers, Paul A [ mailto:Paul_Carruthers@AIMFUNDS.COM mailto:Paul_Carruthers@AIMFUNDS.COM ] Sent: Friday, March 15, 2002 8:53 AM To: 'toasters@mathworks.com' Subject: MS SQL Server

Anybody willing to share their experiences running SQL Server against their filers. Good or bad, both appreciated... :)

Cheers -- Paul.