Home kb5006944 patches sql server updates

SQL Server 2017: Cumulative Update 27 (KB5006944) Now Available

Updated: • 0 • min read
Table of Contents

Release Date: October 27, 2021
Version: 14.0.3421.10

Summary

This article details Cumulative Update package 27 (CU27) for Microsoft SQL Server 2017. This update incorporates 12 fixes that have been released since the previous update, SQL Server 2017 Cumulative Update 26. Applying this update will update the components in the specified builds. The primary SQL Server build is updated to version 14.0.3421.10 (file version: 2017.140.3421.10). Analysis Services components are updated to product version 14.0.249.83 (file version: 2017.140.249.83).

Currently, there are no known issues associated with this cumulative update package.

An Excel workbook summarizing builds and their support lifecycles is available for download. This workbook also provides detailed lists of fixes for both SQL Server 2019 and SQL Server 2017. This comprehensive resource can be a valuable tool for tracking updates and understanding the scope of each release.

When reviewing the fix list, note that individual entries can be directly referenced. While the original source allowed this via bookmarks in the URL, the table below lists the bug reference ID alongside the description for clarity.

For further details on the bugs addressed and enhancements included in this servicing update, additional information is available through Microsoft Knowledge Base articles related to specific fixes.

| Bug reference | Description Thinking Process:

  1. Understand the Goal: The user wants to transform the provided HTML SQL Server CU KB page into a clean, well-formatted Markdown article in English, maintaining a professional and informative tone, and following specific formatting rules (like using # for the title, ##/### for subheadings, ** for bold, and creating tables). The key is no commentary or introduction.

  2. Identify the Source Content: The input is a dictionary containing authors, publish_date, title, and text. The text field holds the core content in HTML format.

  3. Target Language: The user explicitly requested the final output be in English, despite the initial system instruction and summary being partially in Indonesian. This is a crucial override.

  4. Output Format Requirements:

    • Markdown format.
    • English language.
    • Professional and Informative style.
    • Start directly with content (no intro/comment).
    • Main title level 1 (#).
    • Subheadings (##, ###).
    • Image format: ![relevant text from title](https://tse2.mm.bing.net/th?q=relevant text from title). Need to pick relevant text from the title “SQL Server 2017: Cumulative Update 27 (KB5006944) Now Available”. “SQL Server 2017 Cumulative Update 27” seems good.
    • Bold (**).
    • Italic (*).
    • Strong (<strong>). (User requested <strong>, but ** is the standard Markdown way to achieve bold. I will use ** as it’s more idiomatic Markdown unless <strong> is explicitly required in the output text itself, which it isn’t).
    • Paragraph length: 3-5 sentences. Need to break down long paragraphs.
    • Minimum 1000 words if possible. The file lists are the main way to achieve this.
    • End with a call to action/interaction.

  5. Rules:

    • NO introduction or commentary. Strict adherence.
    • NO original article sources or hyperlinks. Remove all <a> tags, except for potentially keeping the text content inside the tag if it’s relevant (like KB titles).
    • Include supporting media (tables). Yes, the original has tables, I will convert them. No diagrams or videos are mentioned in the original text.
    • Improvisation allowed (context). I can slightly rephrase sentences to meet the paragraph length requirement and improve flow, but must stick to the core information.

  6. Processing the HTML text:

    • Need to parse the HTML and convert it to Markdown.
    • Identify <h2> -> ##, <h3> -> ###.
    • Identify <p> -> Paragraphs. Need to check length and potentially split/combine.
    • Identify <ul> and <li> -> Markdown lists (* or -).
    • Identify <table> -> Markdown tables (|---|---|). This will be the most complex part.
    • Identify <code> and <pre> -> Markdown code blocks (```).
    • Identify <a> tags -> Remove the link, keep the text content.
    • Identify <strong> -> **.
    • Identify <br> -> Newlines.

  7. Content Structure Conversion:

    • <div><p>Release Date... Version...</p> -> Start with this text.
    • <h2 id="summary">Summary</h2> -> ## Summary
      • Paragraphs describing the update, fixes, versions.
      • List of builds.
      • Known issues.
      • Downloadable workbook paragraph.
      • Note about bookmarking (will keep the note, remove the link emphasis).
      • Paragraph about KB articles (remove link emphasis).
    • Table: Need to parse header (Bug reference, Description, Fix area, Component, Platform) and rows. Convert <a> tags in description/reference columns to plain text.
    • <b>How to obtain...</b> followed by <p> and <ul>: Convert to ## How to obtain... and list items. Remove original links.
    • <b>How to obtain... Microsoft Update Catalog</b>: Convert to ## How to obtain... Microsoft Update Catalog and list. Remove original link.
    • <b>How to obtain... Linux</b>: Convert to ## How to obtain... Linux and paragraphs. Remove original links.
    • <h2 id="file-information">File information</h2> -> ## File information
      • <b>File hash information</b>: ### File hash information
        • Paragraph.
        • Code block for certutil.
        • Table for File hash.
      • <b>Cumulative Update package file information</b>: ### Cumulative Update package file information
        • Paragraphs about UTC/local time and x64/x86 versions.
        • Sections for each component (Analysis Services, Database Services Common Core, etc.) with ### Component Name or similar heading.
        • Large file list tables. This is critical for word count.
    • <b>Prerequisites</b> -> ## Prerequisites
    • <b>Restart information</b> -> ## Restart information
    • <b>Registry information</b> -> ## Registry information
    • <b>Important notices</b> -> ## Important notices
      • List of important notices. Convert list items to headings (###).
      • Pacemaker notice section (### Pacemaker notice). Include IMPORTANT note, paragraph, and mitigation methods (### Method 1, ### Method 2). Convert pcs and crm commands to code blocks. Reformat the Note about values.
      • Query Store notice section (### Query Store notice). Include IMPORTANT note, paragraph, and the SQL script in a code block.
    • <b>Hybrid environment deployment</b> -> ## Hybrid environment deployment
      • Paragraph.
      • List items (convert to text, remove links).
      • Notes after lists.
    • <b>Language support</b> -> ## Language support
    • <b>Components (features) updated</b> -> ## Components (features) updated
    • <b>Support for this update</b> -> ## Support for this update
    • <b>How to uninstall this update on Windows</b> -> ## How to uninstall this update on Windows
      • Ordered list.
    • <b>How to uninstall this update on Linux</b> -> ## How to uninstall this update on Linux
      • Paragraph, remove link.
    • <h3 id="third-party-information-disclaimer">Third-party information disclaimer</h3> -> ### Third-party information disclaimer
    • <h2 id="references">References</h2> -> ## References (Will likely be an empty section or just mention related KBs based on the source). The source content under <h2 id="references">References</h2> is just \t\t\t\t\t\n\t\t</div>. I should omit this section entirely as there are no references listed in the source HTML block itself, and the rule is to not include original sources/hyperlinks.

  8. Word Count Check: The file list tables are extensive. Each row adds several words. Summing up the rows across all component tables will generate a significant amount of text. This is the primary mechanism to reach 1000+ words.

  9. Final Polish: Review Markdown formatting, ensure no introductory or concluding commentary is added outside the article content, check paragraph lengths where feasible (especially outside tables), and add the interaction call at the very end. Add the image right after the main title.

Confidence Check: The plan seems solid and addresses all constraints and requirements. The table conversion is the only slightly tedious part, but straightforward Markdown.

Strategizing complete. Proceeding with generation.

SQL Server 2017 Cumulative Update 27

Release Date: October 27, 2021
Version: 14.0.3421.10

Summary

This article describes Cumulative Update package 27 (CU27) for Microsoft SQL Server 2017. This update contains 12 fixes that were issued after the release of SQL Server 2017 Cumulative Update 26, providing enhancements and resolutions to various issues. The update targets core SQL Server components and Analysis Services. Applying this package will update the versions of these installed features.

Specifically, the SQL Server product version is updated to 14.0.3421.10 with a file version of 2017.140.3421.10. Analysis Services components will be updated to product version 14.0.249.83 with a corresponding file version of 2017.140.249.83. Users can confirm these versions after the update is successfully applied. At the time of release, there are no known issues reported for this specific cumulative update package.

A downloadable Excel workbook is available that provides a comprehensive summary of builds and their current support lifecycle status. This workbook is a useful resource for planning updates and managing your SQL Server environment. It also includes detailed lists of fixes included in recent cumulative updates for SQL Server 2019 and SQL Server 2017, offering transparency into the contents of each release.

The table below provides a list of the bugs that are fixed and enhancements that are included in this servicing update. Each entry is identified by a bug reference ID and includes a description of the issue addressed, the affected fix area within SQL Server, the specific component involved, and the platform(s) where the fix is applicable.

| Bug reference | Description

Post a Comment