none
Non-yielding scheduler on SQL Server 2019 RRS feed

  • Question

  • We are getting a non-yielding scheduler error on our new SQL Server 2019 boxes.  This started when someone ran a query yesterday and in the error log it kicks off a BEGIN STACK DUMP  Looking at this:

    https://support.microsoft.com/en-us/help/4338890/sql-server-appears-unresponsive-and-non-yielding-scheduler-error-occur

    It seems this is due to bugs (subsequently patched) in SQL Server.  Others suggest it could also be an IO problem (IO is very low however, next to nothing). Can anyone advise?

    Error extracted from log is below:

    01/13/2020 10:45:50,Server,Unknown,Process 0:0:0 (0xa08) Worker 0x000001E6034CC160 appears to be non-yielding on Scheduler 8. Thread creation time: 13223301429074. Approx Thread CPU Used: kernel 0 ms<c/> user 192390 ms. Process Utilization 6%. System Idle 93%. Interval: 197693 ms.
    01/13/2020 10:44:50,Server,Unknown,Process 0:0:0 (0xa08) Worker 0x000001E6034CC160 appears to be non-yielding on Scheduler 8. Thread creation time: 13223301429074. Approx Thread CPU Used: kernel 0 ms<c/> user 132140 ms. Process Utilization 6%. System Idle 93%. Interval: 137441 ms.
    01/13/2020 10:43:50,Server,Unknown,Process 0:0:0 (0xa08) Worker 0x000001E6034CC160 appears to be non-yielding on Scheduler 8. Thread creation time: 13223301429074. Approx Thread CPU Used: kernel 0 ms<c/> user 70656 ms. Process Utilization 6%. System Idle 93%. Interval: 70658 ms.
    01/13/2020 10:43:50,Server,Unknown,External dump process return code 0x20000001.<nl/>External dump process returned no errors.
    01/13/2020 10:43:43,Server,Unknown,Stack Signature for the dump is 0x00000000000001B8
    01/13/2020 10:43:43,Server,Unknown,* *******************************************************************************
    01/13/2020 10:43:43,Server,Unknown,*
    01/13/2020 10:43:43,Server,Unknown,* Non-yielding Scheduler
    01/13/2020 10:43:43,Server,Unknown,*
    01/13/2020 10:43:43,Server,Unknown,*   01/13/20 10:43:43 spid 6748
    01/13/2020 10:43:43,Server,Unknown,* BEGIN STACK DUMP:
    01/13/2020 10:43:43,Server,Unknown,*
    01/13/2020 10:43:43,Server,Unknown,* *******************************************************************************
    01/13/2020 10:43:43,Server,Unknown,***Unable to get thread context for spid 0
    01/13/2020 10:43:43,Server,Unknown,Using 'dbghelp.dll' version '4.0.5'
    01/13/2020 10:43:43,Server,Unknown,CImageHelper::Init () Version-specific dbghelp.dll is not used

    Monday, January 13, 2020 11:56 PM

Answers

  • Here is the SQL code to reproduce the issue. I have given you our functions as it may be something in the functions causing the problem:

    Thanks for the repro. And, yes, I was able to reproduce the scenario. I did not get the non-yielding scheduler, but I killed the query after ten minutes.

    Please fix ASAP as we have many functions and quite a few function calling functions in our code and we desperately want the performance enhancements that inlining scalar UDFs will bring.

    This is however not the place to ask for something being fixed ASAP. This is a peer-to-peer forum for SQL assistence.

    If you want something fixed because it is a blocking issue, you will need to open a support case.

    However, in this case I would not really recommend this for a couple of reasons.

    There was a similar thread sometime back, and in this thread Joe Chang relayed that this issue will be fixed in CU2. And to be precise, he talked about the issue in that thread, so it may or not may not fix your case as well.

    There are also some workarounds that are easily applicable. For this particular query, you can do this:

    SELECT *, [dbo].[fn_pack_legal_name](CompanyName,200) as CheckNestedFunc FROM dbo.Function_calling_function
    OPTION (USE HINT('DISABLE_TSQL_SCALAR_UDF_INLINING'))

    There is also a database-scope configuration to turn off UDF inling all over the database.

    I would suggest that you do this for now, and then review the situation when CU2 has been released. Since CUs are monthly for the first year, I would expect CU2 to come out in February.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    • Marked as answer by blobbles Monday, January 20, 2020 7:28 PM
    Friday, January 17, 2020 11:00 PM

All replies

  • It seems this may be fixed in the latest cumulative patch: https://support.microsoft.com/en-us/help/4527376/cumulative-update-1-for-sql-server-2019 - we have not installed this yet.

    I will install this and report back if the problem is fixed.

    Tuesday, January 14, 2020 12:40 AM
  • Hi blobbles,

    Yes, this issue is fixed in Cumulative Update 1 for SQL Server 2019, we can get the information from FIX: Non-yielding scheduler error occurs when you run batch query with sort operation in SQL Server 2017 and 2019.

    If you have resolved your issue, please mark your solution as answer. This can be beneficial to other community members reading the thread.
    Thanks for your contribution.

    Best regards,
    Cathy 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Tuesday, January 14, 2020 2:45 AM
  • No, this hasn't fixed the problem. We are still getting the same error after applying the Cumulative Update.

    This is the dump from the SQL Server Log, since we restarted the instance:

    01/15/2020 15:35:48,Server,Unknown,Process 0:0:0 (0x1e78) Worker 0x00000177FCD6C160 appears to be non-yielding on Scheduler 3. Thread creation time: 13223526711865. Approx Thread CPU Used: kernel 0 ms<c/> user 131546 ms. Process Utilization 7%. System Idle 91%. Interval: 133597 ms.
    01/15/2020 15:34:47,Server,Unknown,Process 0:0:0 (0x1e78) Worker 0x00000177FCD6C160 appears to be non-yielding on Scheduler 3. Thread creation time: 13223526711865. Approx Thread CPU Used: kernel 0 ms<c/> user 70406 ms. Process Utilization 7%. System Idle 91%. Interval: 70405 ms.
    01/15/2020 15:34:47,Server,Unknown,External dump process return code 0x20000001.<nl/>External dump process returned no errors.
    01/15/2020 15:34:45,Server,Unknown,Stack Signature for the dump is 0x00000000000001B8
    01/15/2020 15:34:45,Server,Unknown,* *******************************************************************************
    01/15/2020 15:34:45,Server,Unknown,*
    01/15/2020 15:34:45,Server,Unknown,* Non-yielding Scheduler
    01/15/2020 15:34:45,Server,Unknown,*
    01/15/2020 15:34:45,Server,Unknown,*   01/15/20 15:34:45 spid 6056
    01/15/2020 15:34:45,Server,Unknown,* BEGIN STACK DUMP:
    01/15/2020 15:34:45,Server,Unknown,*
    01/15/2020 15:34:45,Server,Unknown,* *******************************************************************************
    01/15/2020 15:34:45,Server,Unknown,***Unable to get thread context for spid 0
    01/15/2020 15:34:44,Server,Unknown,Using 'dbghelp.dll' version '4.0.5'
    01/15/2020 15:34:44,Server,Unknown,CImageHelper::Init () Version-specific dbghelp.dll is not used
    01/15/2020 14:53:54,spid70,Unknown,Using 'xplog70.dll' version '2019.150.2000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    01/15/2020 14:53:54,spid70,Unknown,Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    01/15/2020 14:51:53,spid12s,Unknown,Recovery is complete. This is an informational message only. No user action is required.

    • Edited by blobbles Wednesday, January 15, 2020 2:41 AM
    Wednesday, January 15, 2020 2:38 AM
  • Hi blobbles,

    Few people in this forums can analysis SQL server dump. Maybe you can ask MS professional engineer for help, and they will deal with your problem separately and confidentially. https://support.microsoft.com/en-us/assistedsupportproducts

    Hope this could help you.

    Best regards,
    Cathy

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Wednesday, January 15, 2020 3:29 AM
  • If you have a location to which you can upload the dump file, assuming you're allowed to, please upload it and link it here.

    -Sean


    The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

    Thursday, January 16, 2020 11:18 AM
    Answerer
  • You guys will be very interested in this...

    We have identified the issue further - I suspect it is due to the new SQL Server feature for inlining scalar UDFs.

    We have a query which calls a scalar function, this function then calls another scalar function.  I suspect this nesting causes issues - it takes a long time to run, even with a simple table with 7 rows.

    Here is the SQL code to reproduce the issue. I have given you our functions as it may be something in the functions causing the problem:

    CREATE FUNCTION [dbo].[fn_remove_nonstandard_characters]
      (
        @p_string_to_cleanse   varchar(1000)
      )
      RETURNS varchar(1000)
      AS
      --===============================================================================
      --   removes nonstandard characters from string (except commas and dashes)
      --===============================================================================
      BEGIN
        DECLARE @v_nonstandard_character_mask   varchar(110)
    
        SET @v_nonstandard_character_mask = '%[!?\"$.;:*#()@\\]%'
    
        WHILE @p_string_to_cleanse LIKE @v_nonstandard_character_mask
          BEGIN
             SET @p_string_to_cleanse = LEFT( @p_string_to_cleanse,
                                              PATINDEX( @v_nonstandard_character_mask,
                                              @p_string_to_cleanse )-1 )
                             + REVERSE( LEFT( REVERSE( @p_string_to_cleanse),
                                              LEN( @p_string_to_cleanse ) -
                                              PATINDEX( @v_nonstandard_character_mask, @p_string_to_cleanse )))
          END
    
      --===============================================================================
      --   removes commas and dashes characters from string
      --===============================================================================
        IF @p_string_to_cleanse LIKE '%,%'
          SET @p_string_to_cleanse = REPLACE( @p_string_to_cleanse, ',', '' )
    
        IF @p_string_to_cleanse LIKE '%-%'
          SET @p_string_to_cleanse = REPLACE( @p_string_to_cleanse, '-', '' )
    
        IF @p_string_to_cleanse LIKE '%''%'
          SET @p_string_to_cleanse = REPLACE( @p_string_to_cleanse, '''', '' )
    
        IF @p_string_to_cleanse LIKE '%~[%' ESCAPE '~'
          SET @p_string_to_cleanse = REPLACE( @p_string_to_cleanse, '[', '' )
    
        IF @p_string_to_cleanse LIKE '%]%'
          SET @p_string_to_cleanse = REPLACE( @p_string_to_cleanse, ']', '' )
    
        IF @p_string_to_cleanse LIKE '%`%'
          SET @p_string_to_cleanse = REPLACE( @p_string_to_cleanse, '`', '' )
                
        RETURN @p_string_to_cleanse
      END
    
    
    
    CREATE FUNCTION [dbo].[fn_pack_legal_name]
    (
      @p_legal_name	      varchar(1000)
    , @p_max_return_length  integer
    )
    RETURNS varchar(1000)
    AS
    
    --===============================================================================
    --	removes the following terms from employer_name
    --	AND, MANAGEMENT, LTD, LIMITED, GROUP, COMPANY, CO, DIVISION, NEW ZEALAND, NZ, MR, MRS
    --===============================================================================
      BEGIN
        SET @p_legal_name = dbo.fn_remove_nonstandard_characters( @p_legal_name )
    
        IF @p_legal_name LIKE '% AND%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' AND', ' ' )
    
        IF @p_legal_name LIKE '% MANAGEMENT%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' MANAGEMENT', ' ' )
    
        IF @p_legal_name LIKE '% LTD%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' LTD', ' ' )
    
        IF @p_legal_name LIKE '% LIMITED%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' LIMITED', ' ' )
    
        IF @p_legal_name LIKE '% GROUP%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' GROUP', ' ' )
    
        IF @p_legal_name LIKE '% COMPANY%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' COMPANY', ' ' )
    
        IF @p_legal_name LIKE '% CO %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' CO ', ' ' )
    
        IF @p_legal_name LIKE '% DIVISION%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' DIVISION', ' ' )
    
        IF @p_legal_name LIKE '%NEW ZEALAND%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, 'NEW ZEALAND', ' ' )
    
        IF @p_legal_name LIKE '% NZ%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' NZ', ' ' )
    
        IF @p_legal_name LIKE '% MRS%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' MRS', ' ' )
    
        IF @p_legal_name LIKE '% MR%'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' MR', ' ' )
    --lbf repair
        IF @p_legal_name LIKE '% AN %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' AN ', ' ' )
    
        IF @p_legal_name LIKE '% AS %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' AS ', ' ' )
    
        IF @p_legal_name LIKE '% AT %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' AT ', ' ' )
    
        IF @p_legal_name LIKE '% BY %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' BY ', ' ' )
    
        IF @p_legal_name LIKE '% FOR %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' FOR ', ' ' )
    
        IF @p_legal_name LIKE '% FROM %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' FROM ', ' ' )
    
        IF @p_legal_name LIKE '% IN %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' IN ', ' ' )
    
        IF @p_legal_name LIKE '% OF %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' OF ', ' ' )
    
        IF @p_legal_name LIKE '% ON %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' OF ', ' ' )
    
        IF @p_legal_name LIKE '% OR %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' OR ', ' ' )
    
        IF @p_legal_name LIKE '% THE %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' THE ', ' ' )
    
        IF @p_legal_name LIKE '% TO %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' TO ', ' ' )
    
        IF @p_legal_name LIKE '% WITH %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' WITH ', ' ' )
    
        IF @p_legal_name LIKE '% COMP %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' COMP ', ' ' )
    
        IF @p_legal_name LIKE '% COMPAN %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' COMPAN ', ' ' )
    
        IF @p_legal_name LIKE '% COMPANIES %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' COMPANIES ', ' ' )
    
        IF @p_legal_name LIKE '% COMPANY %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' COMPANY ', ' ' )
    
        IF @p_legal_name LIKE '% COMPNY %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' COMPNY ', ' ' )
    
        IF @p_legal_name LIKE '% CORP %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' CORP ', ' ' )
    
        IF @p_legal_name LIKE '% PTY %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' PTY ', ' ' )
    
        IF @p_legal_name LIKE '% CORPORATION %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' CORPORATION ', ' ' )
    
        IF @p_legal_name LIKE '% INC %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' INC ', ' ' )
    
        IF @p_legal_name LIKE '% INCORP %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' INCORP ', ' ' )
    
        IF @p_legal_name LIKE '% INCORPORATED %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' INCORPORATED ', ' ' )
    
        IF @p_legal_name LIKE '% PROPRIETARY %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' PROPRIETARY ', ' ' )
    
        IF @p_legal_name LIKE '% LMTD %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' LMTD ', ' ' )
    
        IF @p_legal_name LIKE '% NL %'
    		  SET @p_legal_name = REPLACE( @p_legal_name, ' NL ', ' ' )
    
        SET @p_legal_name = UPPER( LEFT( REPLACE( @p_legal_name, ' ', '' ), @p_max_return_length) )
    
        RETURN @p_legal_name
      END
    
    
    --Now lets run these functions using a simple table:
    
    DROP TABLE IF EXISTS dbo.Function_calling_function
    
    CREATE TABLE dbo.Function_calling_function (
    	ID int IDENTITY(1,1) PRIMARY KEY,
    	CompanyName varchar(300)
    )
    
    INSERT INTO dbo.Function_calling_function (CompanyName)
    VALUES ('Microsoft software LMTD'),('Amazon shopping [.com] limited'),('Gillette, shaving foam limited'),('Facebook.com'),('New Zealand company inc'),('Xero'),('Some [],; Company')
    
    --Try selecting everything, works a-ok
    SELECT * FROM dbo.Function_calling_function
    
    --Try non nested scalar function, works a-ok
    SELECT *, [dbo].[fn_remove_nonstandard_characters](CompanyName) FROM dbo.Function_calling_function
    
    --Try nested scalar function, seems to never end
    SELECT *, [dbo].[fn_pack_legal_name](CompanyName,200) as CheckNestedFunc FROM dbo.Function_calling_function

    After 20 minutes, the last query is still running. Also when we remove the nested function from our previous code, it runs without issue.  If we use only the non-nested UDF function above fn_remove_nonstandard_characters it also works fine.

    The above code does not directly give you the error specified in the title of this thread, but it likely causes the issue.  It may also be cause by the function above called fn_pack_legal_name, however this compiles and runs fine. 

    Please fix ASAP as we have many functions and quite a few function calling functions in our code and we desperately want the performance enhancements that inlining scalar UDFs will bring.

    Friday, January 17, 2020 3:44 AM
  • Here is the SQL code to reproduce the issue. I have given you our functions as it may be something in the functions causing the problem:

    Thanks for the repro. And, yes, I was able to reproduce the scenario. I did not get the non-yielding scheduler, but I killed the query after ten minutes.

    Please fix ASAP as we have many functions and quite a few function calling functions in our code and we desperately want the performance enhancements that inlining scalar UDFs will bring.

    This is however not the place to ask for something being fixed ASAP. This is a peer-to-peer forum for SQL assistence.

    If you want something fixed because it is a blocking issue, you will need to open a support case.

    However, in this case I would not really recommend this for a couple of reasons.

    There was a similar thread sometime back, and in this thread Joe Chang relayed that this issue will be fixed in CU2. And to be precise, he talked about the issue in that thread, so it may or not may not fix your case as well.

    There are also some workarounds that are easily applicable. For this particular query, you can do this:

    SELECT *, [dbo].[fn_pack_legal_name](CompanyName,200) as CheckNestedFunc FROM dbo.Function_calling_function
    OPTION (USE HINT('DISABLE_TSQL_SCALAR_UDF_INLINING'))

    There is also a database-scope configuration to turn off UDF inling all over the database.

    I would suggest that you do this for now, and then review the situation when CU2 has been released. Since CUs are monthly for the first year, I would expect CU2 to come out in February.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    • Marked as answer by blobbles Monday, January 20, 2020 7:28 PM
    Friday, January 17, 2020 11:00 PM
  • Thanks Erland, we will do as you suggest - I didn't realise the feature could be turned off. For now we will be switching it off for our databases and will review later.


    • Edited by blobbles Monday, January 20, 2020 8:03 PM
    Monday, January 20, 2020 7:27 PM
  • Thanks Erland, we will do as you suggest - I didn't realise the feature could be turned off. For now we will be switching it off for our databases and will review later.

    It would be a bad thing to turn it off across the board. This is really a go-faster button.

    What I forgot to mention is that you can also turn off inlining per function:

    CREATE FUNCTION ... WITH INLINE = OFF AS

    That bug appears to be some logical operation bug with the inlining, our bug is related to nested functions. Will test again after CU2 comes out.

    Maybe. However, the nested function has a loop, so it does not qualify for inlining.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Monday, January 20, 2020 10:09 PM
  • We have many functions and some highly time dependent releases.  Until we go through a whole regression test with our important data sets, we will leave the function turned off. This is likely to be 6 months away before we get to it, which should also give plenty of time for us to install a few fixes coming out with the CU's.  Currently we have migrated some data sets that aren't as time sensitive, but still need these to run a-OK.

    Regarding "However, the nested function has a loop, so it does not qualify for inlining.", I cannot see this specified in the documentation here: https://docs.microsoft.com/en-us/sql/relational-databases/user-defined-functions/scalar-udf-inlining?view=sql-server-ver15

    I guess this should be updated, I have asked the question in the comments at the bottom.

    Also - if the function is not inlined, then it should run without issue.  Maybe the problem is the first function CAN be inlined, but the second one cannot?

    Thanks for keeping up with this Erland :-)

    Monday, January 20, 2020 11:06 PM
  • Regarding "However, the nested function has a loop, so it does not qualify for inlining.", I cannot see this specified in the documentation here: https://docs.microsoft.com/en-us/sql/relational-databases/user-defined-functions/scalar-udf-inlining?view=sql-server-ver15

    It follows from the first point:

    The UDF is written using the following constructs:

        DECLARE, SET: Variable declaration and assignments.
        SELECT: SQL query with single/multiple variable assignments1.
        IF/ELSE: Branching with arbitrary levels of nesting.
        RETURN: Single or multiple return statements.
        UDF: Nested/recursive function calls2.
        Others: Relational operations such as EXISTS, ISNULL.

    WHILE is not on that list.

    Also - if the function is not inlined, then it should run without issue.  Maybe the problem is the first function CAN be inlined, but the second one cannot?

    Maybe. Or it is just that the function call takes the optimizer over the brink. The outer function is after all quite long. If I comment out all but the first REPLACE operation in the outer function, it runs smoothly.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Tuesday, January 21, 2020 10:18 PM
  • CU2 came out today and I tested the repro. My expectations that this would be fixed proved to be wrong - the issue still persists.

    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Friday, February 14, 2020 8:31 PM
  • Erland,

    Can you recompile/refresh the function and try again, please?

    EXEC sys.sp_refreshsqlmodule '...'

    -Sean


    The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

    Friday, February 14, 2020 9:25 PM
    Answerer
  • Can you recompile/refresh the function and try again, please?

    EXEC sys.sp_refreshsqlmodule '...'

    Sean, I created everything fresh in tempdb; it was not a leftbehind before the upgrade.

    By the way, I also tried two other repros that I have seen that misbehaved in CU1 and RTM. These two run run fine on CU2.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Friday, February 14, 2020 10:04 PM
  • Hi Erland, Joe Sack sent me an email on cu2 in relation to this post https://social.msdn.microsoft.com/Forums/en-US/b1db7482-57da-44fc-84ee-cebe131dd882/sql-server-2019-memory-leak?forum=transactsql of Nov 2019.

    I replied with a note to this thread, let me know if you want to be copied on the email



    jchang

    Sunday, February 16, 2020 2:34 PM
  • Hi Erland, Joe Sack sent me an email on cu2 in relation to this post https://social.msdn.microsoft.com/Forums/en-US/b1db7482-57da-44fc-84ee-cebe131dd882/sql-server-2019-memory-leak?forum=transactsql of Nov 2019.

    Yes, the issue in that thread has been resolved. The issue in this thread has not.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Sunday, February 16, 2020 2:41 PM