Share via

Status of Sql Server replication bug

Modrall, Mark 15 Reputation points
2026-03-25T19:01:38.7433333+00:00

Hi,

A bit over a year ago, I reported a bug in Sql Server replication where columns using different collations than the db default were not replicated properly (in the specific case, the db default was SQL_Latin1_General_CP1_CI_AI and the columns being mangled by replication were Latin1_General_100_CI_AI_SC_UTF8).

The last message from the Infosys subcontractors for Microsoft said
"Bug Number: 4239338

Expected ETA: Around September.

We will communicate updates through this email once the bug has been resolved and incorporated into the product updates.

You agreed for the temporary case archival for now as there is no active troubleshooting.

We appreciate your time spent on this case and we are very happy working with you.

Thank you for choosing Microsoft products and working with SQL Engine Core Team. If you need anything else regarding this case, please reach out to me directly."

I haven't been able to find the bug number in any of the release notes for any CUs since.

Is there any way to get an update on the bug?

Thanks

SQL Server Database Engine
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Akhil Gajavelly 1,725 Reputation points Microsoft External Staff Moderator
    2026-03-30T03:46:48.5633333+00:00

    Hi @Modrall, Mark

    Thanks for sharing the detailed background on this issue.

    As mentioned in the earlier response, there’s no public visibility for internal bug IDs like 4239338 in CU release notes for Microsoft SQL Server. The most reliable way to get an update is to:

    Re-open the original support case (if possible), or

    • Raise a new support ticket and reference:
      • The internal bug ID 4239338 Your previous case details 
        Affected versions and collation scenario

    The support team can check the internal status, confirm if it has been fixed or scheduled, and share any available workaround or ETA.

    If you do get an update, it would be great if you could share it back here for the benefit of the community.

    Thanks,
    Akhil.

    0 comments
  2. Q&A Assist
    2026-03-25T19:01:51.34+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The available context does not contain any information about bug 4239338 or its fix status, and it does not list that bug in the known-issues/fix tables for the referenced SQL Server cumulative updates. The context also does not provide a public way to look up that specific internal bug number.

    To get an update on this replication bug, the supported path is to re-engage Microsoft Support using the original support case (if still available) or open a new support case and reference:

    • The original support incident number (if known).
    • The internal bug number 4239338.
    • The affected SQL Server versions and collations (for example, database default SQL_Latin1_General_CP1_CI_AI and column collation Latin1_General_100_CI_AI_SC_UTF8).

    Support can check the current internal status of bug 4239338, confirm whether it has shipped in any CU or major version, and advise on any hotfixes, workarounds, or target release.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.