Hi,
here's the definition:
SecondLevelDataCache REG_DWORD 0 | 1 ? cache size (in kilobytes)
Default: 0 (256?KB)
Specifies the size of the secondary processor cache, also known as the L2 cache. Data in this entry is used only when the Hardware Abstraction Layer (HAL) cannot detect the L2 cache.
Value Meaning
0 Sets the L2 cache size to 256?KB.
Number of kilobytes Sets the L2 cache size to the value specified.
From: Technical Reference to the Windows NT Registry ? Microsoft Corporation 1985 - 1997
This means: nothing !
Defently you get no Performance boost out their.
With Hardware you can boostup your SQL-Server in the Range between 1% to 100%.
With a new DAtabaseand Apps-design you can boostup performance in the Range between 100% to 2000% (This mean you had a very Performance HW-Platform plus a good definition of the DB-Design for your Application!)
A good implementation and DB-Design is defintly better then a Powermachine with rude implementation of DB and APP.
Some rules for tuning HW:
More CPU's : Take min. two or more CPU's plus a large 2.Level Cache then more MHZ'
A Performant DISK:
Take an RAID-Controller with big Cache and plenty of Disk (the size of each Disk is notso important then the amount of disk). The Rule an RAID-5 Array with 7 disk = 500 I/o's per second. This is more Important then CPU or RAM, since each block has an amount of few Bytes. the Database could access Randomly over the hole disks.
i could wrote a lot, but the goal is to size the Server for an Application, and without understanding the behavior of the App it doesn't make sense.
regards
Frobo
