SQL 2008R2 Wingate 7

[rebelldtu]

Hi
I have just set up SQL2008R2 as the HTTP caching database. The cache_index is updating nicely . The default is set at 1GB in Wingate Cache settings - is there a recommended value now I have SQL in place or should I stick with the 1GB?

I have noticed however that under Edit Volume the location of the cache is set to C:\Program Files (x86)\WinGate\Packages\HTTPCache\Store\1 and it is receiving updates. Is this normal behaviour once SQL is installed or have I missed something?

I have pointed the System DSN to SQL using the native client 10.0

Many Thanks

[erwin]

Hi

The size in the WinGate HTTP cache settings, sets the size of the cache volume (i.e. the store (location on disk) that holds all the cached files). WinGate uses a database(in your case SQL2008) to store the locations (cache index) of these cached files in the HTTP cache volume.

So the size of the volume will determine how large you want your cache(files in the volume) to be. The location of the cache in the settings refers to the location of the actual cache volume.

Erwin

[rebelldtu]

Thanks Erwin, on another point under cache Settings - Advanced Tab where you set the System DSN there is a max concurrent database connections figure.

Should this figure be upped in accordance with our licence limit or is it simply 1 connection from wingate to the cache index or the amount of files indexed simultaneously?

Or am I way off on all counts?!

Cheers

[erwin]

That setting relates to how many connections WinGate can make to the database to query/update the cache index at anyone time. Often DBMS (database management systems) such as SQL server, Mysql etc, let you specify a limit on the amount of connections can be made to it. So since a DBMS may have various databases running, WinGate is limited in this way so that it wont hog all the connections available and leave some for other applications that may be connecting to those other databases in the DBMS.

Hope that makes it a little clearer.

[rebelldtu]

Hi Erwin,
thanks for the explanation. I have set up SQL solely for Wingate and am trying to tweak settings to gain maximum performance from Wingate as we have heavy usage throughout most of the year. I am using a dedicated server (Two Quad Core Xeons, 8GB Ram and a RAID 5 15k SAS Array. Teamed Gbit NICs in operation) which is more than capable. So any tips on how to maximise throughput and efficiency would be gratefully received.

Cheers

Paul