Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2003-02-11 : 07:12:09
|
| Blaine writes "I have successfully used RAM disk software (www.superspeed.com) in various applications and experienced great performance increases. I have been experimenting with using this software in my SQL environment. It is basically a kernel level driver (*.sys) that creates a cache at the block level which should be faster than a file system level cache.Setup:Windows 2000 server, SP3SQL 2000 Standard Edition, SP34 GB RAM4 x 550 Xeon, 1MB L2 Cache.1. I want to turn off the SQL memmory tuning by setting the min and max memmory to 16 mb, effectively turning off SQL caching.2. Locate the databases and log files to dedicated partition.3. Designate this partition to be supercached in the RAMdisk.What this does is create a faster block level cache in RAM as opposed to a byte level or file system level cache for SQL. I also would be able to get my SQL 2000 Standard Edition to access 3GB of RAM for caching at the block level, hence, bypassing the 2GB limitation of this version.Does this reasoning appear sound or am I missing the boat. Does SQL cache more than just the database tables and logs? Thanks." |
|
|
srf
Starting Member
42 Posts |
Posted - 2003-02-11 : 14:37:43
|
| I don't think that there's any way for that to work nor would it be supported by MS; I think SQL even prefers that disk/controller caching be turned off. SQL by design has to load indexes and tables into RAM, and there won't be room to do that if you limit it to 16 megs. Tuning is better left to indexes and the sort, plus you can try caching some information in TempDB and having TempDB reside in RAM:[url]http://www.winnetmag.com/Articles/Index.cfm?ArticleID=4536[/url] |
 |
|
|
|
|
|