Anonymous

My feedback

  1. 70 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 19 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment An error occurred while saving the comment
    Anonymous commented  · 

    Repro script attached

    An error occurred while saving the comment
    Anonymous commented  · 

    Repro script for below.

    An error occurred while saving the comment
    Anonymous commented  · 

    Repro script attached. We have tested this between a few different versions of SQL Server, all running on Windows Server 2016 (with current updates installed) and MSOLEDBSQL driver 18.2.2.0 installed:

    *** ISSUE PRESENT - MS DTC ERROR ON SELECT ***
    Local Server: Microsoft SQL Server 2014 (SP3-CU3) (KB4491539) - 12.0.6259.0
    Remote Server: Microsoft SQL Server 2014 (SP3-CU2) (KB4482960) - 12.0.6214.1

    *** ISSUE PRESENT - MS DTC ERROR ON SELECT ***
    Local Server: Microsoft SQL Server 2014 (SP3-CU3) (KB4491539) - 12.0.6259.0
    Remote Server: Microsoft SQL Server 2017 (RTM-CU15-GDR) (KB4505225) - 14.0.3192.2

    *** NO ISSUE - SELECT WORKS NORMALLY ***
    Local Server: Microsoft SQL Server 2017 (RTM-CU15-GDR) (KB4505225) - 14.0.3192.2
    Remote Server: Microsoft SQL Server 2014 (SP3-CU3) (KB4491539) - 12.0.6259.0

    *** NO ISSUE - SELECT WORKS NORMALLY ***
    Local Server: Microsoft SQL Server 2017 (RTM-CU15-GDR) (KB4505225) - 14.0.3192.2
    Remote Server: Microsoft SQL Server 2017 (RTM-CU15-GDR) (KB4505225) - 14.0.3192.2

    It seems that the bug is present when the driver is used from a linked server on SQL Server 2014 instance. The other way around seems fine - if the local server is SQL Server 2017 the bug isn't present.

    An error occurred while saving the comment
    Anonymous commented  · 

    We've done some fairly trivial testing on this issue - it only seems to affect a SELECT from the remote side, INSERT/UPDATE/DELETE all work fine without needing an explicit BEGIN DISTRIBUTED TRANSACTION around them.

    Eg this doesn't work:

    select top 10
    TestValue
    from [MyLinkedServer].[MyDB].[dbo].[TestTable]

    But all three of these work fine:

    insert into [MyLinkedServer].[MyDB].[dbo].[TestTable]
    (TestKey,
    TestValue)
    values
    (N'Hello World!',
    N'Hello World Value!')

    update [MyLinkedServer].[MyDB].[dbo].[TestTable]
    set TestKey = N'Changed!'
    where TestKey = N'Hello World!'

    delete [MyLinkedServer].[MyDB].[dbo].[TestTable]
    where TestKey = N'Changed!'

    The state of XACT_ABORT on the statement or connection doesn't seem to make a difference, and it seems to occur even when IMPLICIT_TRANSACTIONS is OFF.

    EXECing remote procs across the linked server also succeeds, even if the proc modifies data on the remote side. This really seems like an outright bug to me.

    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    @Chris Wood: this issue occurs for me using version 18.2.1 of the driver unless you first BEGIN DISTRIBUTED TRANSACTION. Starting a normal BEGIN TRANSACTION instead still triggers the error.

  3. 112 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  15 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  5. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  System Center Data Protection Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  6. 106 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous supported this idea  · 

Feedback and Knowledge Base