Ramdisk Plus Non-Cluster-Ramdisk

Ramdisk Plus has been designed as a hybrid that offers a combination of features from our plain RamDisk product, and our SuperSpeed product, plus additional functionality.

The user creates and configures either an NTFS, FAT or FAT32 volume from main memory using the configuration tool built-in to the software.

Ramdisk Plus creates a RamDisk Plus device of the specified size and format. The drive looks just like a real drive to the user and the operating system, except it's blistering fast....

In fact, Ramdisk performance is white hot... faster than any disk device in the World. The user may now install any application desired onto RamDisk Plus. That's all there is to it.

Boost server performance with Ramdisk Plus software - in less than 10 minutes !

• Microsoft SQL Server
• Microsoft Internet Information Server
• Web Servers
• Microsoft Terminal Server
• Microsoft Exchange
• DB2
• CITRIX
• Mimesweeper
• Navision
• MailMarschall

How to Implement the tempdb Solution on a Machine that Is Not Part of a Cluster

Preliminary considerations:

• Examine the size of the tempdb file and the amount of available free memory. If the tempdb file is 100 MB or less, a RAM disk is unlikely to improve performance. If the tempdb file is greater than available physical memory, add more RAM to the system.



• Consider the impact of reallocating system memory to the RAM disk. Sufficient memory resources must be available for SQL and other processes.



• On a production machine, determine a convenient time when SQL Server can be stopped. SQL must be stopped to change the tempdb path, and, possibly, to reduce its memory allocation limit.

1. Install the latest version of RamDisk or RamDisk Plus.



2. Stop SQL Server.



3. Add a RAM disk to the system.



1. Select a size large enough to contain the tempdb file.
2. Select an appropriate drive letter.
3. Select "NTFS" file system, without compression.



4. Configure MS SQL Server to place the tempdb file on the RAM disk. If necessary, reduce the SQL Server's system memory allocation limit.



5. Start SQL Server.