sql server - SQL 2008 Encryption Scan -
We have recently upgraded the database server for SQL 2008 64bit from SQL 2005. CPU usage is running 100% on all four processors (it never works on SQL 2005 server). When I run sp_lock, I think there are several processes waiting for a resource called [ENCRYPTION_SCAN]. I am not using any SQL 2008 encryption features Do anyone know that I wait on this resource Why should I have to work? It appears that whenever I have four processes on this resource, the CPU kills 100% on all four processors.
I see this same question crop in some different places. It has not been proven yet, but it seems that long-running bulk INSERT or SORT can be frustrating to hold an ENCRYPTION_SCAN lock to prevent encryption scans from starting operation. In the near future, search for a blog from CSS on this, I will link it back here / when it comes out.
Comments
Post a Comment