Choose from several options for complete web, email and data security.
Evaluate Websense products by watching demos and installing evaluation software.
Learn how Websense solutions help keep our customer safe, secure and productive
Get information on product updates, support resources and more.
Get the most out of support in five simple steps.
Find tools and assets to help sell Websense solutions.
Come work for the global leader in unified information security.
We are saving our log database for 40 days and have around 35 databases and they are each 5100MB.
Using SQL 2008 standard and WSS 7.6.2 and a 6000 licens.
If I look at the log database settings we use default configuration.
Today we use, roll over every: 5120. Init size 2048, growth 512.
Any advice to tune the performance for report or SQL server?
Regards Jan Rockstedt
That's an awful lot of data... are you logging full URL? I used to keep 1 year of logs for an environment of about 10000 users and didn't get anywhere near that size.
Yes I am using full URL.
That's your biggest problem. Unless you have a huge need to actually capture full URL I would highly recommend turning that off. It eats up way too much disk space for the amount of users you have and it only ever helps in very specific scenarios. Your space and performance will greatly improve. This way you can keep 6-12 months worth of logs for HR / legal / compliance purposes without buying a SAN for Websense too.
It was websense recommendation to use full logging, as we get an better match for the policies.We have 2,5 TB disk for the database logging, butt I need an recomandation for the database size.
Jan, I don't know who told you that but the Log Server database has NOTHING to do with policy / filtering decisions. They are totally separate from one another. Policy and filtering decisions are made against the full URL before it even makes it to your Log Server database, so whether or not you save it with the full URL is immaterial to filtering. The only reason to have full URL logging on is if you have some need to capture and keep that much detailed information on your users' activity. Some places do, but the majority do not.
You asked for recommendations to increase performance on your database -- turning off full URL logging, unless you have a specific need to save that much information, would result in the largest performance increase you can hope to gain.
Are you logging "Advertisements"? That also eats up space.
I have disable the full logging now.