Endpoint Protection

Dear SEPM Admins,

Having configured our two syncronised installations of SEPM to use respective SQL 2005 servers, we thought all was working OK until the other week when our 3rd party SQL developer pointed out that in the space of an hour the jTDS process had made over 200,000 requests to the SQL server. After a bit of investigation we found that the jTDS process is an open source SQL driver used by SEPM to talk with the SQL server.

While it's fair to say that the sum processing time of all of these requests is low, for an installation of less than 300 clients and server, finding that SEPM was making almost 4 times as many SQL requests than our actual SQL application used by about 150 users, was a bit of a surprise to say the least.

A bit of investigation and I came across the previous forum entry: https://www-secure.symantec.com/connect/forums/sep-sql-database-questions, where NickF makes reference to a high number of SQL requests. However, no one appears to pick up on that part of the thread and I've found very little else in direct relation to this. As a result I placed a support call with Symantec who have confirmed that this is considered normal behaviour. While the SEPM developers may consider this normal behaviour I'm not sure NickF and myself think that some 20 - 60 SQL requests per second is exactly normal...

So the point of this post and my question to other SEPM / SQL Server admins is are you seeing a high number of SQL requests from jTDS and have you seen any real impact on your SQL server performance as a result? Also I guess, it would be worth asking did anyone who saw this as an issue, come up with any better solution than simply pointing the SEPM database at a locally installed copy of SQL Server Express? Any thoughts on this will be greatly appreciated.

Cheers

John

Title: 'How to improve Symantec Endpoint Protection 11 Microsoft SQL performances.'
Document ID: 2010041413592148
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2010041413592148?Open&seg=ent


http://support.microsoft.com/kb/298475

Hi Prachand,

Thanks for the prompt reply, however it doesn't really answer the issue. The SQL server is already configured on a DAS box, with seperate spindles for the transaction files / database files / swap file / OS /  program files and was certainly functioning well enough for our database application. However, what I didn't have was a base line to work from so I'm unsure as to whether or not there has been an actual drop in performance since putting the SEPM databases on the SQL servers...

As much as anything, I'm trying to gauge community response as to whether other admins see these somewhat high numbers of SQL requests, which will allow us to determine how best to proceed.

Regards

John

Hello,

Even I have seen the same issue do we have more admins who have seen the similar issue?????????

Same here, however, it's not seeming to impact SQL performance in a negative way. But our SQL admin DID notice the huge number of hits on the database. He says it "doesn't clean up after itself" either, whatever that means.