Just updated server to 2022 - CXSYNC_PORT waits - HELP!
-
Hi
Updated from SQL2014 to SQL2022 today.
Seeing a ton of CXSYNC_PORT waits.
Its as if something is not configured correctly,
What can I check?
This in an on-premise server. SQL22 ENTERPRISE Microsoft SQL Server 2022 (RTM-CU1) (KB5022375)
-
As Ken mentioned CX_PAKKET got subdived in CXSYNC_PORT en CXSYNC_CONSUMER . Related to parallellism. Have you set a maxdop?
Catch up with the latest CU 7 for SQL 2022 https://www.microsoft.com/en-us/download/details.aspx?id=105013
Have you enabled Query Store for easier tracking troublesome queries?
Compatiblity set at 120 ( 2014 ) ?
Updated statistics ?
-
By now I hope you have read about what a CXSYNC_PORT wait is. If not please do so.
The situation described for this wait type did exist in SQL2014, but was not externalised into a specific message. In SQL2022 a specific message now appears. If you are meeting all your performance SLAs than it may be that for your system there is nothing to worry about. If you have performance issues the situation in the message may be part of the problem, or may be just something else that is happening.
As already suggested, investigate how to use Query Store to identify the queries with performance problems, and then fix those with the greatest problem. In other words, do a pareto analysis of your problems. Do not be too worried by the CXSYNC_PORT message until the query causing it gets to the top of your unsolved problem query list.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply