SQL Server Archives

Tech Optimizer

August 5, 2026

Google Cloud explains SQL Server to PostgreSQL migration

Google Cloud has introduced its Database Migration Service, which focuses on converting SQL Server stored procedures with multiple result sets into PostgreSQL code. The service uses an automated decision-making process to determine if a SQL Server procedure should be translated into a PostgreSQL stored procedure or function, based on the number of result sets and the presence of a scalar return value. Procedures with a single result set or scalar return value are converted into PostgreSQL stored procedures, while those with multiple result sets are transformed into functions returning a SETOF refcursor. In a healthcare reporting example, a master procedure retrieves patient details and may return multiple result sets along with a status integer. The PostgreSQL translation involves simpler child procedures as standard procedures and more complex routines as functions that open cursors sequentially. Scalar return values are handled by placing them in a dedicated cursor at the end of execution, changing how applications interact with the outputs. Testing of these translated objects must occur within an explicit transaction block due to PostgreSQL cursor lifecycle constraints. The user executes the function to generate cursor references and fetches data sequentially. Google Cloud's internal analysis classifies stored procedures by scanning for direct result sets and considers conditional logic and loops that may complicate result set counts. A directed graph of procedure calls is constructed to determine the result set classification. Database migrations often face challenges due to legacy application logic, especially with stored procedures designed to minimize database round trips. Successful code conversion is only part of the task, as teams must also adjust test harnesses and application data access layers for PostgreSQL's cursor management. Google Cloud's service categorizes SQL Server procedures into three types: no result sets, a single result set, or multiple/dynamic result sets.

Tech Optimizer

July 30, 2026

Generating Referentially Consistent Synthetic Test Data for PostgreSQL in .NET Application Modernization

Satyajit Gokhale, Aiswaryaa Venugopalan, Ruchi Agarwal, Nits Jeganathan, Khurram Khawaja, Vijay Mandadi, and Luke Huan contributed to this article. AWS Transform offers a .NET application modernization service that allows enterprise customers to migrate from Microsoft SQL Server to Amazon Aurora PostgreSQL Compatible Edition. This migration reduces licensing costs and enhances scalability while utilizing an open-source ecosystem. Schema conversion tools can assist in translating DDL to PostgreSQL-compatible definitions, but correctness must be verified by teams to ensure performance under real-world workloads. Traditional testing methods, such as using production data or manual checks, are not scalable and raise privacy concerns. Therefore, there is a need for realistic synthetic data generated at scale that adheres to the migrated schema's constraints. AWS Transform for SQL Server modernization employs an AI agent to generate constraint-respecting synthetic data at scale during the migration workflow. This process involves loading the PostgreSQL schema into a live database, constructing a dependency graph for data generation, and distributing tasks across multiple sub-agents. The agent validates each generated INSERT against the live database, ensuring compliance with constraints and providing error diagnostics for any violations. The synthetic data generation workflow consists of four stages: schema analysis, establishing generation order, distributing tasks across sub-agents, and validation with error recovery. The agent extracts metadata from the PostgreSQL schema, determines a valid table generation sequence, parallelizes data generation while maintaining referential integrity, and generates and validates data row-by-row against the live database. Each successful insertion enriches the context for subsequent generations, while errors are handled through structured diagnostics and iterative regeneration. The process ensures referential integrity and preserves the generation state, allowing for recovery from interruptions without data loss.

Winsage

July 22, 2026

Redmond’s reaper cometh: October 2026 set to bury a graveyard of Microsoft products

October 2026 will see the end of support for several Microsoft products, including Office LTSC 2021, which requires organizations to transition to LTSC 2024 or Microsoft 365 for continued support. Windows Server 2022 will exit mainstream support on October 13, 2026, while Windows 11 24H2 Home and Pro editions will also reach their end of life on the same date. The enterprise and education versions of Windows 11 23H2 will be supported until November 10, 2026. Publisher 2021 will be discontinued without a successor. Additionally, Entra ID Sign-In risk policies will be phased out on October 1, 2026, necessitating a transition to Conditional Access to maintain user and sign-in risk protection. SQL Server 2017 is scheduled for retirement in October 2027.

Winsage

July 14, 2026

Microsoft Patch Tuesday for July 2026 — Snort rules and prominent vulnerabilities

Microsoft's July 2026 security update addresses 622 vulnerabilities, with 57 classified as "critical." Two critical vulnerabilities, CVE-2026-56155 (Active Directory Federation Services) and CVE-2026-56164 (Microsoft SharePoint Server), have been exploited in the wild. The critical vulnerabilities include 48 remote code execution (RCE) vulnerabilities, seven elevation of privilege (EoP) vulnerabilities, one spoofing vulnerability, and one security feature bypass vulnerability. RCE vulnerabilities affect various Microsoft services, including Windows Media, Microsoft Office, and SQL Server, with eleven rated as "more likely" to be exploited. Additional important vulnerabilities include CVE-2026-49170, CVE-2026-49795, and CVE-2026-50325. Talos is releasing a new Snort ruleset to detect these vulnerabilities, and Cisco Security Firewall customers are advised to update their ruleset.

Winsage

July 14, 2026

Microsoft rolls out massive Windows 11 security update with 416 fixes

Microsoft released its July 2026 Patch Tuesday cumulative updates for Windows 11, addressing numerous security vulnerabilities and enhancing Secure Boot functionalities. The updates include: - KB5101650 for Windows 11 25H2 and 24H2, updating systems to builds 26200.8875 and 26100.8875. - KB5101649 for Windows 11 26H1, updating devices to build 28000.2525. The release addresses a total of 622 Microsoft Common Vulnerabilities and Exposures (CVEs), including: - 416 vulnerabilities in Windows. - Fixes for Microsoft Office, Edge, Exchange Server, SharePoint Server, SQL Server, Defender, and Azure services. Key vulnerabilities fixed include: - CVE-2026-50661: A BitLocker Security Feature Bypass vulnerability. - CVE-2026-56155: An AD FS Elevation of Privilege vulnerability that has been exploited. - CVE-2026-56164: A SharePoint Server Elevation of Privilege vulnerability. The updates also introduce new Secure Boot certificates, rectify issues from previous patches affecting third-party applications, and incorporate curl 8.21.0 for security improvements. Users are advised to back up data before installation, which requires a system reboot.

Winsage

July 12, 2026

Microsoft is killing 15 products in 2026, including Windows 11 24H2 and Office 2021

Microsoft will discontinue support for several products in 2026, including: 1. Windows 11 24H2 (Home and Pro) - End of servicing on October 13, 2026. 2. Office 2021 and Office LTSC 2021 - End of support on October 13, 2026. 3. Windows Server 2012 and 2012 R2 - Final ESU year ending on October 13, 2026. 4. SQL Server 2016 - Extended end of support on July 14, 2026. 5. SharePoint Server 2016 and 2019, Project Server 2016 and 2019 - Support ends on July 14, 2026. 6. Microsoft Publisher - Retired after October 2026. 7. Exchange Server 2016 and 2019, Skype for Business Server - Final ESU cutoff on October 31, 2026. 8. Windows 11 Enterprise and Education 23H2, .NET 8, .NET 9, PowerShell 7.4 - End of servicing on November 10, 2026. 9. Windows 10 2016 LTSB and IoT Enterprise LTSB 2016 - Extended support ends on October 13, 2026. 10. Windows 11 SE - Support ends on October 1, 2026. 11. Dynamics CRM 2016 and older versions - Lost support earlier in January 2026. 12. Microsoft Configuration Manager, version 2409 - End of support on June 6, 2026. 13. Visual Studio 2022 LTSC channels, versions 17.10 and 17.12 - End of support in January and July 2026, respectively. 14. InfoPath 2013, SharePoint Designer 2013 - End of support on July 14, 2026. 15. Azure service retirements - Occurring in late 2026. Organizations are advised to review their software landscape and plan for transitions to avoid disruptions.

Tech Optimizer

July 8, 2026

PostgreSQL Extensions Are an Architecture Decision, Not an Afterthought

A common issue in database migrations is the unplanned accumulation of extensions in PostgreSQL, leading to extension sprawl. Teams often install extensions without documenting the rationale, resulting in a complex web of dependencies that complicates future upgrades and removals. The installation process involves PostgreSQL accessing a control file that details the extension's version and dependencies, which can lead to multiple extensions being installed unintentionally. Upgrading and removing extensions are often neglected, causing risks such as the loss of dependent objects. Extensions typically default to the public schema, which can become cluttered; relocating them to dedicated schemas can improve organization. Trusted Language Extensions (TLE) allow non-privileged users to utilize procedural languages in managed databases without needing superuser access. Key extensions recommended for use include pg_stat_statements, pg_trgm, hstore, citext, and PostGIS, each serving specific use cases. Proper governance is essential for managing extensions, including documenting their purpose, ownership, and dependencies, to prevent operational surprises.

Tech Optimizer

July 3, 2026

Percona & HexaCluster team up on database migrations

Percona has formed a strategic alliance with HexaCluster to assist organizations in migrating from proprietary databases to open-source alternatives, specifically PostgreSQL, MySQL, and MariaDB. The partnership combines Percona's migration assessment and production support with HexaCluster's migration software for diverse database environments. The migration process will begin with a comprehensive assessment by Percona to outline the scope and plan the transition. Percona will lead the migration efforts, while HexaCluster will provide software solutions for complex migrations. This collaboration aims to help enterprises reduce costs associated with proprietary databases and minimize risks during migration. HexaCluster specializes in PostgreSQL migration and offers tools for migration assessment, schema conversion, data migration, and live replication. Percona supports various database systems and emphasizes open-source solutions to give organizations more control over their data infrastructure.

Winsage

July 1, 2026

Steve Ballmer once trashed Linux as “a cancer” — now it’s saving Windows 10 holdouts

In 2001, Steve Ballmer, then CEO of Microsoft, referred to Linux as a "cancer" threatening Microsoft's intellectual property and likened its users to "communist thieves." By 2016, after Microsoft ported SQL Server to Linux, Ballmer expressed enthusiasm for the change and acknowledged that the conflict with open-source had benefited Microsoft's financial success. In 2020, Microsoft President Brad Smith admitted the company had been on the wrong side of history regarding open source and noted the need for change. Microsoft has since embraced open-source technologies, introducing products like Azure Linux 4.0, built on Fedora. As Windows 11's transition becomes difficult for users, advocacy groups have criticized Microsoft for ending support for Windows 10, which could lead to millions of discarded computers. Microsoft extended Windows 10's life through an Extended Security Updates program until October 14, 2026, with a recent announcement pushing it to 2027. Rising hardware costs and design flaws in Windows 11 have led some users to consider alternatives like Linux. A survey revealed that 30% of PCs are still running Windows 10, and a poll showed that 68% of respondents plan to stick with Windows 10 through 2027.

Winsage

June 30, 2026

Steve Ballmer once called Linux a “cancer” — it’s funny Windows 10 holdouts may now see it as the cure for Windows 11’s hardware rules and the RAM crisis

Former Microsoft CEO Steve Ballmer initially described Linux as a "cancer" in 2001 but changed his perspective by 2016, supporting Microsoft's decision to port SQL Server to Linux. Microsoft President Brad Smith acknowledged the company's past underestimation of the open-source movement in 2020. Microsoft has integrated open-source solutions into its products, including PowerShell and Visual Studio Code, and launched Azure Linux 4.0. As Microsoft phases out support for Windows 10, critics argue this leads to programmed obsolescence, affecting up to 400 million PCs. Microsoft extended support for Windows 10 through its Extended Security Updates (ESU) program until October 14, 2026, with an additional extension through 2027. Rising hardware costs and stringent requirements for Windows 11 hinder many users' transitions. Advocacy groups are encouraging users to consider Linux, highlighting its advantages. Recent surveys show that 30% of HP PCs still run Windows 10, and a poll indicated that 68% of participants plan to stay with Windows 10 through 2027. There is a growing awareness among consumers regarding the potential shift to open-source alternatives like Linux.