<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[bugzbaggy]]></title><description><![CDATA[RenzBagasbas]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/my-blog</link><generator>RSS for Node</generator><lastBuildDate>Thu, 18 Jun 2026 21:53:58 GMT</lastBuildDate><atom:link href="https://renzbagasbas1130.wixsite.com/renzbagasbas/zh/blog-feed.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[SQL Server 2022 Engine Crashes on Windows Server 2025 — Tracing the Cause to an EDR Heap Hook Incompatibility]]></title><description><![CDATA[[UPDATED] In March 2026, our production messaging-database cluster started crashing again. Same exception code as the incident we resolved last year (0xc0000005, Access Violation), but a different stack signature, different servers, different cloud, and ultimately a completely different root cause. This time the bug wasn't in SQL Server. It wasn't in the storage drivers. It wasn't in our queries. It was in something we'd never have suspected without comparing the crashing servers against a...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/sql-server-2022-engine-crashes-on-windows-server-2025-tracing-the-cause-to-an-edr-heap-hook-incomp</link><guid isPermaLink="false">6a14253af3bc0136e51a9de6</guid><pubDate>Mon, 25 May 2026 10:35:58 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_bec6851d7d7947b18114fb31eb9a2aa9~mv2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[The Mechanic Goes Beyond Limits]]></title><description><![CDATA[On public speaking, the age of AI, and why I finally stopped making excuses. There's a photo of me on a conference room screen. Batik shirt, arms crossed, smiling — probably more confident than I actually felt in that moment. "AI-Enhanced CI/CD Workflow for SQL Server, Renz Bagasbas, Senior Database Administrator." I stared at that slide for a few seconds before I walked up. Took a breath. And then I spoke. That probably sounds like nothing. For a lot of people, it is nothing. But for me —...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/the-mechanic-goes-beyond-limits</link><guid isPermaLink="false">6a0598bf68a3e7adcb176ace</guid><pubDate>Thu, 14 May 2026 10:05:06 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_8ee2a674053840f5ba96a325a8233d27~mv2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[AI-Powered SQL Migration Script Generator]]></title><description><![CDATA[[UPDATED] There's a principle that stuck with me recently. The core idea was simple: stop describing what you want to build — start building it. If you can explain what you want clearly enough, AI can build it. But the catch is that "clearly enough" is doing a lot of heavy lifting in that sentence. Without structure, AI coding tools produce confident-looking output that quietly falls apart. They ignore your conventions, invent patterns you didn't ask for, and generate code that contradicts...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/ai-powered-sql-migration-script-generator</link><guid isPermaLink="false">69a1c6ec2e226d5eb67c231c</guid><pubDate>Fri, 06 Mar 2026 05:35:24 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_fd16748448d840bea77dd49fd1c3ef59~mv2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[SQL Server 2022 Enterprise Repeated Engine Crashes (Access Violation Exceptions)]]></title><description><![CDATA[In late October 2025, our production SQL Server 2022 Enterprise cluster running on AWS EC2 started crashing repeatedly with Access Violation (0xc0000005) exceptions. This wasn't just any database going down — this cluster is the heart of the business. It powers the core platform that our customers depend on every day: real-time communications services, call routing, messaging, and the APIs that integrate with everything downstream. When this database cluster goes offline, the entire...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/sql-server-2022-enterprise-repeated-engine-crashes-access-violation-exceptions</link><guid isPermaLink="false">69a17c214882ec6a3ac25958</guid><pubDate>Fri, 27 Feb 2026 11:17:47 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_be6e0e50c64c49b5acd8ab6ac07d495e~mv2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[When Forced Quorum Mode Haunts You]]></title><description><![CDATA[It was a regular Thursday afternoon. The kind where you're wrapping up tasks, maybe thinking about what to have for dinner. And then, at 4:36 PM, the alerts started rolling in. Transaction processing delays. Partial database inaccessibility. The production database cluster — the one that powers core services for an entire region — was going down. Not because of a hardware failure. Not because someone fat-fingered a config change. But because of something far more subtle: a ghost from a...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/when-forced-quorum-mode-haunts-you</link><guid isPermaLink="false">699d2d19f1d815afdb21c261</guid><pubDate>Tue, 24 Feb 2026 05:49:04 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_602beab5f4a043f79a217fe2f1cf661f~mv2.png/v1/fit/w_666,h_384,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[The Two Settings That Fixed Our Production CPU Crisis]]></title><description><![CDATA[How default SQL Server configuration brought a production server to its knees — and how two settings fixed it in under a minute. The Escalation It started with a message from my manager: Attached was a screenshot of CPU pinned near 100%. Not a good look on a production server handling live traffic. The Investigation My first instinct was to hunt for a rogue query. That's usually the culprit — some poorly optimized SELECT statement doing a full table scan, or a report running during peak...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/the-two-settings-that-fixed-our-production-cpu-crisis</link><guid isPermaLink="false">69901277a816bdca356e2d07</guid><pubDate>Sat, 14 Feb 2026 06:27:26 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_976a48a2b8764781bbed542d1da80b94~mv2.png/v1/fit/w_594,h_280,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[How I Built an End-to-End Database CI/CD Pipeline with AI-Generated Migration Scripts]]></title><description><![CDATA[[UPDATED] Database deployments have always been the weak link in most CI/CD pipelines. Application code gets automated pipelines, blue-green deployments, and rollback strategies from day one. Databases? They still get a DBA manually executing scripts, a process that doesn't scale, burns productive hours, and leaves too much room for human error. That workflow needs to be automated, but done carefully, because a bad database deployment can do far more damage than a bad application deployment....]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/how-i-built-an-end-to-end-database-ci-cd-pipeline-with-ai-generated-migration-scripts</link><guid isPermaLink="false">698f339e460b9174760e0c51</guid><pubDate>Fri, 13 Feb 2026 15:51:30 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_a6b424629eb443f5b4b4c2fcc70a4394~mv2.png/v1/fit/w_1000,h_685,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Solving Replication’s Limits with SQL Distributed Availability Group]]></title><description><![CDATA[[UPDATED] One of the major projects I was tasked with in my current role involved solving two persistent issues: Build a redundant Numbering Lookup microservice  used by multiple applications. The requirement? It must read from secondary, asynchronous, read-only replicas of NumberingDB, distributed across several regions (DC2, DC3, DC4). The primary source of truth remains NumberingDB in DC1, and our service must only query its regional replicas. Replace SQL Replication  for the...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/solving-replication-s-limits-with-sql-distributed-availability-group</link><guid isPermaLink="false">687a13167d98edd85d341392</guid><pubDate>Fri, 18 Jul 2025 10:37:46 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_9ac4c13e9426410996d9f5ef57eb8ed3~mv2.png/v1/fit/w_1000,h_601,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Migrating SQL Server Databases with dbatools]]></title><description><![CDATA[I worked on a migration project where two production databases were moved from a legacy standalone SQL Server 2014 instance to a high...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/migrating-sql-server-databases-with-dbatools</link><guid isPermaLink="false">686e47ed02d16d34d6475c76</guid><pubDate>Thu, 10 Jul 2025 08:24:07 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_346f29bcbe39463ea76e1eb553b34557~mv2.png/v1/fit/w_595,h_219,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[dbatools: SQL Server Administration Made Practical]]></title><description><![CDATA[Managing SQL Server day-to-day isn't just about setting it up, it’s about keeping it running smoothly: managing logins, scheduling jobs,...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/dbatools-sql-server-administration-made-practical</link><guid isPermaLink="false">6853b9da21ea1ac780c8a4aa</guid><pubDate>Fri, 04 Jul 2025 06:54:53 GMT</pubDate><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Week Seven Onwards]]></title><description><![CDATA[The first six weeks in a new DBA role are often a blur, equal parts learning, adjusting, and firefighting. There’s a lot to take in:...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/week-seven-onward</link><guid isPermaLink="false">685a92c57d12e91fd9b41a3c</guid><pubDate>Tue, 24 Jun 2025 12:06:22 GMT</pubDate><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[dbatools: Simplifying SQL Server Configuration with PowerShell]]></title><description><![CDATA[SQL Server configuration used to mean a lot of clicking around in SSMS, memorizing registry tweaks, or juggling half a dozen scripts....]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/dbatools-simplifying-sql-server-configuration-with-powershell</link><guid isPermaLink="false">68537c900daa1dfa62014957</guid><pubDate>Thu, 19 Jun 2025 11:04:30 GMT</pubDate><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Week Six: Index Health with Brent Ozar's First Responder Kit]]></title><description><![CDATA[Earlier, in Week 3, I had explored Glenn Berry’s Diagnostic Queries  and Microsoft’s Best Practices Checker . Both of those do give some...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/week-six-index-health-with-brent-ozar-s-first-responder-kit</link><guid isPermaLink="false">6846cb50e0f98f52e29e83fc</guid><pubDate>Wed, 11 Jun 2025 02:56:45 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_5a3b6d7f80df47eaad583d671d397836~mv2.png/v1/fit/w_464,h_402,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Week Five: Part 2 - Working Smart with Very Large Tables in SQL Server 2022]]></title><description><![CDATA[Not too long after we reconfigured SQL Server's memory, we expected to see the pressure drop. We did see some improvement, fewer flushes,...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/week-five-part-2-working-smart-with-very-large-tables-in-sql-server-2022</link><guid isPermaLink="false">683981fcd569a830f8adc3ce</guid><pubDate>Fri, 30 May 2025 12:57:46 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_6ded2f54f1f9415c81254b062ad28317~mv2.png/v1/fit/w_786,h_335,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Week Five: Part 1 - Working Smart with Very Large Tables in SQL Server 2022]]></title><description><![CDATA[By automating sp_WhoIsActive and deploying it across all our production SQL Servers, I’ve built a pretty reliable, near-real-time view of...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/week-five-part-1-working-smart-with-very-large-tables-in-sql-server-2022</link><guid isPermaLink="false">6835954f81150f32c9f2dcd0</guid><pubDate>Wed, 28 May 2025 10:38:09 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/46731a_93a072259e8e4e3183d486095aba1486~mv2.jpg/v1/fit/w_965,h_587,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Week Four:  sp_WhoIsActive Automation – Smarter Query Monitoring]]></title><description><![CDATA[For Week Four, I've put up the work in a more systematic way. If Week Three was about collecting baselines, Week Four is about using that...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/week-four-sp_whoisactive-automation-smarter-query-monitoring</link><guid isPermaLink="false">682e831cce61513cbe92158a</guid><pubDate>Thu, 22 May 2025 02:44:33 GMT</pubDate><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Week Three: Baselining Part 2 – Microsoft's Best Practices Checker for SQL Server]]></title><description><![CDATA[In Part 1 of this Week 3 dive into SQL Server baselining, I used Invoke-DbaDiagnosticQuery from dbatools  to run Glenn Berry’s diagnostic...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/week-three-baselining-part-2-microsoft-s-best-practices-checker-for-sql-server</link><guid isPermaLink="false">68244bc92588d90209144a84</guid><pubDate>Wed, 14 May 2025 08:45:07 GMT</pubDate><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Week Three: Baselining Part 1 - Glenn Berry’s Diagnostic]]></title><description><![CDATA[Week three goal was pretty starightforward: Baselining a critical task to ensure our SQL Server instances are running smoothly. To gather...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/week-three-baselining-part-1-glenn-berry-s-diagnostic</link><guid isPermaLink="false">681b42332c91cb5abdcafcef</guid><pubDate>Wed, 07 May 2025 11:43:52 GMT</pubDate><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Week Two: Laying the Groundwork]]></title><description><![CDATA[The first week marked the beginning of my journey in this new role. I spent that first stretch getting my bearings meeting the team,...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/week-two-laying-the-groundwork</link><guid isPermaLink="false">680b91849e2e9d6190c55db5</guid><pubDate>Tue, 29 Apr 2025 10:07:41 GMT</pubDate><dc:creator>renzbagasbas1130</dc:creator></item><item><title><![CDATA[Starting Fresh: My First Week in a New Role]]></title><description><![CDATA[Updated:  Just added some new resources under "My Essential SQL Tools" that should be more useful. I recently stepped into a new chapter...]]></description><link>https://renzbagasbas1130.wixsite.com/renzbagasbas/post/starting-fresh-my-first-week-in-a-new-role</link><guid isPermaLink="false">6808c0de765eb353ed5c745a</guid><pubDate>Wed, 23 Apr 2025 10:32:43 GMT</pubDate><dc:creator>renzbagasbas1130</dc:creator></item></channel></rss>