<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DBMS_SQLTUNE on Greatfinish Blog</title><link>https://greatfinish.top/tags/dbms_sqltune/</link><description>Recent content in DBMS_SQLTUNE on Greatfinish Blog</description><generator>Hugo -- gohugo.io</generator><language>zh-cn</language><copyright>© 2026 Greatfinish Blog · [沪ICP备2026022892号](https://beian.miit.gov.cn/)</copyright><lastBuildDate>Tue, 17 Mar 2026 21:00:00 +0800</lastBuildDate><atom:link href="https://greatfinish.top/tags/dbms_sqltune/index.xml" rel="self" type="application/rss+xml"/><item><title>达梦 SQL 优化实战：一次 BLKUP2 回表代价过高问题的定位与解决</title><link>https://greatfinish.top/posts/dm-blkup2-sql-optimization/</link><pubDate>Tue, 17 Mar 2026 21:00:00 +0800</pubDate><guid>https://greatfinish.top/posts/dm-blkup2-sql-optimization/</guid><description>一次达梦 SQL 优化实战：SQL 最终只返回 15 行，但因缺少 SO_ID、SO_DET_NO 联合索引，在 SHOP_SALE_ORDER_DETAIL 宽表上产生大量 BLKUP2 回表。通过新增联合索引和收集统计信息，逻辑读从 40046153 页降到 46 页。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://greatfinish.top/posts/dm-blkup2-sql-optimization/featured.jpg"/></item><item><title>Oracle SQL Tuning Advisor 实战：从 AWR 定位慢 SQL 到索引优化落地</title><link>https://greatfinish.top/posts/oracle-sql-tuning-advisor-sta-case/</link><pubDate>Sat, 20 Dec 2025 21:30:00 +0800</pubDate><guid>https://greatfinish.top/posts/oracle-sql-tuning-advisor-sta-case/</guid><description>一次 Oracle SQL 优化实战：AWR 定位 SQL_ID f6asas4cp2n53，SQL Monitor 显示执行约 27 秒且 User I/O 等待明显，SQL Tuning Advisor 建议 SQL Profile 和复合索引，最终创建 UI_SALES_INVOICES(IOTYPE,CSTID) 索引后性能降至约 5 秒。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://greatfinish.top/posts/oracle-sql-tuning-advisor-sta-case/featured.jpg"/></item></channel></rss>