- You encounter high CMEMTHREAD waits.
- SQL Server is installed on systems with 8 or more cores per socket.
|
T8048 |
- SQL Server 2012 RTM to current Service Pack (SP)/CU
- SQL Server 2014 RTM to SP1
|
- SQL Server 2014 SP2 to current SP/CU
- SQL Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
|
- You encounter high CMEMTHREAD waits.
- SQL Server is installed on systems with 8 or more cores per socket.
|
T8079 |
SQL Server 2014 SP2 to current SP/CU |
- SQL Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
|
- You are using features that rely on log pool cache. (for example, Always On)
- SQL Server is installed on systems with multiple sockets.
|
T9024 |
Cumulative update package 3 for SQL Server 2012 Service Pack 1 to SP2 SQL Server 2014 RTM |
- SQL Server 2012 SP3 to current SP/CUSQL
- Server 2014 SP1 to current SP/CU
- SQL Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
FIX: High "log write waits" counter value on a SQL Server 2012 or SQL Server 2014 instance |
Your instance of SQL Server is handling thousands of connection resets because of connection pooling. |
T1236 |
Cumulative update package 9 for SQL Server 2012 Service Pack 1 to SP2 Cumulative Update 1 for SQL Server 2014 |
- SQL Server 2012 SP3 to current SP/CUSQL
- Server 2014 SP1 to current SP/CUSQL
- Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
|
- Your application workload involves frequent tempdb usage (creation and drop of temp tables or table variables).
- You notice user requests waiting for tempdb page resources because of allocation contention.
|
T1118 |
- SQL Server 2012 RTM to current SP/CU
- SQL Server 2014 RTM to current SP/CU
|
- SQL Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
Concurrency enhancements for the tempdb database
NOTE Enable the trace flag and add multiple data files for the tempdb database. |
- You have multiple tempdb data files.
- The data files at first are set to the same size.
- Because of heavy activity, tempdb files encounter growth and not all files grow at the same time and cause allocation contention.
|
T1117 |
- SQL Server 2012 RTM to current SP/CU
- SQL Server 2014 RTM to current SP/CU
|
- SQL Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
Recommendations to reduce allocation contention in SQL Server tempdb database |
Heavy SOS_CACHESTORE spinlock contention or your plans are being evicted frequently on ad hoc query workloads. |
T174 |
|
None |
|
- Entries in the plan cache are evicted because of growth in other caches or memory clerks
- High CPU consumption due to frequent recompiles of queries
|
T8032 |
- SQL Server 2012 RTM to current SP/CU
- SQL Server 2014 RTM to current SP/CU
|
None |
|
Existing statistics are not frequently updated because of the large number of rows in the table. |
T2371 |
- SQL Server 2012 RTM to current SP/CU
- SQL Server 2014 RTM to current SP/CU
|
None |
|
- Statistics jobs take a long time to complete.
- Cannot execute multiple statistics update jobs in parallel.
|
T7471 |
SQL Server 2014 SP1 CU6 to current SP/CU |
None |
Boosting Update Statistics performance with SQL 2014 & SQL 2016 |
CHECKDB command takes a long time for large databases. |
|
- SQL Server 2012 RTM to current SP/CU
- SQL Server 2014 RTM to current SP/CU
|
None |
|
CHECKDB command takes a long time for large databases. |
T2566 |
- SQL Server 2012 RTM to current SP/CU
- SQL Server 2014 RTM to current SP/CU
|
None |
|
Executing concurrent data warehouse queries that take long compile-time results in RESOURCE_SEMAPHORE_QUERY_COMPILE waits. |
T6498 |
Cumulative update package 6 for SQL Server 2014 to SP1 |
- SQL Server 2014 SP2 to current SP/CUSQL
- Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
|
You are troubleshooting specific query performance issues Optimizer fixes are disabled by default. |
T4199 |
- SQL Server 2012 RTM to SP4
- SQL Server 2014 RTM to latest
|
None |
|
You experience slow performance using query operations with spatial data types. |
|
- SQL Server 2012 SP3 to current SP/CU
- SQL Server 2014 SP2 to current SP/CU
|
- SQL Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
|
- Queries encounter
SOS_MEMORY_TOPLEVELBLOCKALLOCATOR and CMEMTHREAD waits. - There is low available virtual address space for the SQL Server process.
|
T8075 |
- SQL Server 2012 SP2 CU8 to current SP/CU
- SQL Server 2014 RTM CU10 to current SP/CU
|
- SQL Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
FIX: Out of memory error when the virtual address space of the SQL Server process is low in SQL Server |
- SQL Server is installed on a machine with large amounts of memory.
- Creating new databases takes a long time.
|
T3449 |
- SQL Server 2012 SP3 CU3 to current SP/CU
- SQL Server 2014 RTM CU14 to current RTM CU
- SQL Server 2014 SP1 CU7 to current SP/CU
|
- SQL Server 2016 RTM to current SP/CU
- SQL Server 2017 RTM to current SP/CU
|
FIX: SQL Server database creation on a system with a large volume of memory takes longer than expected |