How It Works
My recent posts https://blogs.msdn.microsoft.com/bobsql/2016/06/03/sql-2016-it-just-runs-faster-column-store-uses-vector-instructions-sseavx/ https://blogs.msdn.microsoft.com/bobsql/2016/06/03/sql-2016-it-just-runs-faster-bulk-insert-uses-vector-instructions-sseavx/ have generated discussions about the SSE and AVX support
The trace flag 1222 can be very powerful and helpful in tracking down
When executing a query to enumerate the locks, such as select * from sys.dm_tran_locks,
Previous posts have discussed partitioning, for example, a partitioned memory object https://blogs.msdn.microsoft.com/psssql/2011/09/01/sql-server-20082008-r2-on-newer-machines-with-more-than-8-cpus-presented-per-numa-node-may-need-trace-flag-8048/ and how
How It Works: SQL Server Locking WAIT_WITH_LOW_PRIORITY I received a question from Jonathan as
To track the login statistical information, enable the sp_configure value ‘common criteria compliance enabled‘