{"id":2809,"date":"2026-11-05T01:27:03","date_gmt":"2026-11-05T01:27:03","guid":{"rendered":"https:\/\/www.kingbaseglobal.com\/blog\/tech-blog\/converged-database-benefits-htap-architecture-audit\/"},"modified":"2026-11-05T01:27:03","modified_gmt":"2026-11-05T01:27:03","slug":"converged-database-benefits-htap-architecture-audit","status":"publish","type":"post","link":"https:\/\/www.kingbaseglobal.com\/blog\/tech-blog\/converged-database-benefits-htap-architecture-audit\/","title":{"rendered":"Converged Database Benefits_ HTAP Architecture Audit"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/kingbase-bbs.oss-cn-beijing.aliyuncs.com\/qywx\/blogImage\/e489b9ba-47b6-43cc-bc23-9897229974a8.webp\" alt=\"Step-by-step technical guide cards arranged in a wooden rack, representing structured database migration procedures.\" \/><\/p>\n<h2>Prerequisites and Environment Setup<\/h2>\n<p>Before implementing a converged database architecture, ensure the following prerequisites are met. This guide assumes a commercial database environment (such as KingbaseES) where specific configuration parameters may vary by version.<\/p>\n<ol>\n<li><strong>Software Version<\/strong>: Verify the installed database version supports hybrid storage (row\/column) and resource queue management. Consult the vendor documentation for supported versions.<\/li>\n<li><strong>Hardware Resources<\/strong>: Ensure sufficient CPU, memory, and I\/O bandwidth to handle concurrent OLTP and OLAP workloads.<\/li>\n<li><strong>Access Rights<\/strong>: Administrative access is required to modify resource queues, storage formats, and security policies.<\/li>\n<li><strong>Backup Strategy<\/strong>: A full backup of the existing fragmented systems (OLTP and OLAP) must be taken before any schema changes or configuration modifications.<\/li>\n<\/ol>\n<h2>Step 1: Configure Resource Queues for Workload Isolation<\/h2>\n<p>To prevent analytical queries from starving transactional processes, configure resource queues to limit concurrent sessions and resource usage.<\/p>\n<ol>\n<li><strong>Identify Workload Types<\/strong>: Define distinct queues for OLTP (transactional) and OLAP (analytical) workloads.<\/li>\n<li><strong>Set Resource Limits<\/strong>: Assign specific resource limits to each queue. For example, limit the number of concurrent sessions for OLAP to prevent excessive CPU consumption.<\/li>\n<li><strong>Assign Users to Queues<\/strong>: Map database users or application roles to the appropriate resource queues.<\/li>\n<\/ol>\n<p><strong>Example Configuration Logic<\/strong>:<\/p>\n<ul>\n<li>Create a queue for OLTP with high priority and limited session caps if necessary to ensure low latency.<\/li>\n<li>Create a queue for OLAP with lower priority and explicit memory\/CPU limits.<\/li>\n<\/ul>\n<p><em>Note: Specific SQL commands for creating resource queues depend on the database engine. Refer to the vendor&#8217;s administration guide for the exact syntax.<\/em><\/p>\n<h2>Step 2: Optimize Storage Formats for Mixed Workloads<\/h2>\n<p>Converged databases often use hybrid storage to support both row-oriented (for transactions) and column-oriented (for analytics) access.<\/p>\n<ol>\n<li><strong>Analyze Table Access Patterns<\/strong>: Identify tables that are frequently updated (OLTP) versus those that are primarily read for aggregation (OLAP).<\/li>\n<li><strong>Configure Storage Formats<\/strong>:\n<ul>\n<li>Set transactional tables to row-store format for fast point lookups and updates.<\/li>\n<li>Set analytical tables or partitions to column-store format for efficient scanning.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Verify Storage Settings<\/strong>: Ensure the database engine is correctly interpreting the storage format for each table.<\/li>\n<\/ol>\n<p><strong>Verification Query<\/strong>:<br \/>\nCheck the storage format of tables to ensure they align with their workload type.<\/p>\n<pre><code class=\"language-sql\">-- Example syntax to check table storage properties (syntax varies by engine)\nSELECT table_name, storage_type\nFROM information_schema.tables\nWHERE table_schema = 'public';\n<\/code><\/pre>\n<p><em>Note: Replace <code>information_schema.tables<\/code> and <code>storage_type<\/code> with the specific system catalog views and column names defined in your database&#8217;s documentation.<\/em><\/p>\n<h2>Step 3: Implement Query Optimization and Plan Stability<\/h2>\n<p>The query optimizer must handle mixed workloads efficiently. Ensure statistics are up-to-date to prevent suboptimal execution plans.<\/p>\n<ol>\n<li><strong>Update Statistics<\/strong>: Run statistics collection on all relevant tables, especially those with significant data changes.<\/li>\n<li><strong>Monitor Execution Plans<\/strong>: Use the database&#8217;s query execution plan viewer to identify plans that use full table scans for transactional queries or index lookups for large aggregations.<\/li>\n<li><strong>Use Query Hints (If Supported)<\/strong>: If the engine supports query hints, use them to guide the optimizer for critical queries.<\/li>\n<\/ol>\n<p><strong>Verification Query<\/strong>:<br \/>\nCheck for long-running queries or those with high resource usage.<\/p>\n<pre><code class=\"language-sql\">-- Example syntax to view active queries and resource usage (syntax varies by engine)\nSELECT query_id, user, duration, resource_usage\nFROM sys_active_queries\nORDER BY duration DESC;\n<\/code><\/pre>\n<p><em>Note: Replace <code>sys_active_queries<\/code> with the appropriate system view for monitoring active sessions in your database.<\/em><\/p>\n<h2>Step 4: Configure Security and Access Control<\/h2>\n<p>Implement unified security policies to manage access for both transactional and analytical users.<\/p>\n<ol>\n<li><strong>Define Roles<\/strong>: Create distinct roles for OLTP users (read\/write) and OLAP users (read-only).<\/li>\n<li><strong>Apply Row-Level Security (RLS)<\/strong>: If supported, configure RLS policies to restrict data access based on user attributes.<\/li>\n<li><strong>Enable Encryption<\/strong>: Ensure data at rest and in transit is encrypted according to organizational security standards.<\/li>\n<\/ol>\n<p><strong>Verification Query<\/strong>:<br \/>\nCheck current security policies and user permissions.<\/p>\n<pre><code class=\"language-sql\">-- Example syntax to list user roles and permissions (syntax varies by engine)\nSELECT grantee, privilege_type, table_name\nFROM information_schema.role_table_grants;\n<\/code><\/pre>\n<p><em>Note: Replace <code>information_schema.role_table_grants<\/code> with the specific system catalog for user permissions in your database.<\/em><\/p>\n<h2>Verification: Ensuring Performance Stability<\/h2>\n<p>After configuration, verify that the converged database meets performance requirements.<\/p>\n<ol>\n<li><strong>Baseline Comparison<\/strong>: Compare current OLTP latency and OLAP throughput against pre-migration baselines.<\/li>\n<li><strong>Resource Contention Check<\/strong>: Run concurrent OLTP and OLAP workloads. Monitor CPU, memory, and I\/O usage. Ensure OLTP latency does not degrade significantly.<\/li>\n<li><strong>Query Isolation Check<\/strong>: Verify that long-running analytical queries do not block transactional commits. Check for lock waits.<\/li>\n<li><strong>Data Consistency<\/strong>: Run reconciliation scripts to ensure data in the converged database matches the source systems.<\/li>\n<\/ol>\n<p><strong>Example Verification Steps<\/strong>:<\/p>\n<ul>\n<li>Execute a standard OLTP transaction and measure response time.<\/li>\n<li>Execute a complex analytical query and measure duration.<\/li>\n<li>Run both simultaneously and observe any increase in OLTP latency. If the increase exceeds acceptable thresholds, adjust resource queue limits.<\/li>\n<\/ul>\n<h2>Rollback: Reverting to Fragmented Architecture<\/h2>\n<p>If the converged database fails to meet performance or functional requirements, follow these steps to rollback.<\/p>\n<ol>\n<li><strong>Stop Traffic<\/strong>: Redirect application traffic away from the converged database to the legacy systems.<\/li>\n<li><strong>Restore Backup<\/strong>: Restore the legacy OLTP and OLAP systems from the pre-migration backup.<\/li>\n<li><strong>Validate Legacy Systems<\/strong>: Ensure the legacy systems are operational and data is consistent.<\/li>\n<li><strong>Analyze Failure<\/strong>: Investigate the root cause of the performance or functional issues in the converged database before attempting another migration.<\/li>\n<\/ol>\n<p><strong>Rollback Verification<\/strong>:<\/p>\n<ul>\n<li>Confirm that OLTP transactions are processing normally on the legacy system.<\/li>\n<li>Confirm that OLAP reports are generating correctly from the legacy warehouse.<\/li>\n<li>Ensure no data loss occurred during the switch-over.<\/li>\n<\/ul>\n<h2>FAQ<\/h2>\n<h3>How do I verify that resource queues are effectively isolating OLTP and OLAP workloads?<\/h3>\n<p>Monitor system metrics for CPU wait times, memory usage, and I\/O latency during concurrent workloads. Use system views to check for lock waits or long-running transactions that block commits. Adjust queue limits if OLTP latency increases significantly.<\/p>\n<h3>What are the key configuration steps for hybrid storage in a converged database?<\/h3>\n<p>Identify tables based on access patterns (update-heavy vs. read-heavy). Configure transactional tables to use row-store format and analytical tables to use column-store format. Verify settings using system catalog queries.<\/p>\n<h3>How can I troubleshoot query performance issues in a mixed workload environment?<\/h3>\n<p>Analyze execution plans for transactional and analytical queries. Check for full table scans on transactional tables or index lookups on large aggregations. Update statistics and consider query hints if supported. Monitor resource usage to identify contention.<\/p>\n<h3>What is the recommended rollback procedure if the converged database migration fails?<\/h3>\n<p>Redirect traffic to legacy systems, restore them from pre-migration backups, and validate their operation. Investigate the root cause of the failure in the converged database before retrying.<\/p>\n<hr \/>\n<p><strong>\ud83d\udca1 More Resources<\/strong><\/p>\n<p>If you would like to dive deeper into KingbaseES and its application practices across various industries, we have compiled the following official resources to help you get started quickly and develop and operate with efficiency:<\/p>\n<ul>\n<li><a href=\"https:\/\/bbs.kingbase.com.cn\/\">Kingbase Community<\/a>: A one-stop interactive platform for technical exchanges, Q&amp;A, and experience sharing\u2014join forces with fellow DBAs and developers.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/Solution-Oracle.html\">Kingbase Solutions<\/a>: One-stop full-stack database migration and cloud-native solutions, supporting smooth migration of multi-source heterogeneous data, ensuring high availability, real-time integration, and sustained high performance.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/Customers.html\">Kingbase Case Studies<\/a>: Real-world user scenarios and implementation outcomes, showcasing KingbaseES&#8217;s outstanding capabilities in high availability, high performance, and IT adaptation.<\/li>\n<li><a href=\"https:\/\/docs.kingbase.com.cn\/en\">Kingbase Documentation<\/a>: Authoritative and comprehensive product manuals and technical guides, covering the entire lifecycle from installation and deployment to development, programming, and operations management.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/Download.html\">Free Download<\/a>: Get the latest installation packages, drivers, tools, and patches, supporting multiple platforms and domestic chip architectures.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/blog\/\">Digital Construction Encyclopedia<\/a>: Covers digital strategy planning, data integration, metrics management, database visualization applications, and more to empower enterprise digital transformation.<\/li>\n<\/ul>\n<p><strong>Open Source Resources:<\/strong><\/p>\n<ul>\n<li><a href=\"https:\/\/github.com\/hgsandy\/Kingbase-docs\">GitHub &#8211; Kingbase-docs<\/a>: Kingbase documentation open-source repository\u2014Stars and contributions are welcome.<\/li>\n<li><a href=\"https:\/\/gitee.com\/hgsandy\/kingbase-docs\">Gitee &#8211; Kingbase-docs<\/a>: Domestic mirror repository for Kingbase documentation for faster access.<\/li>\n<\/ul>\n<p>Welcome to explore the resources above and begin your Kingbase journey!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Prerequisites and Environment Setup Before implementing a converged database architecture, ensure the following prerequisites are met. This guide assumes a commercial database environment (such as KingbaseES) where specific configuration parameters&#8230;<\/p>\n","protected":false},"author":2170,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"meta_description":"","_kingbase_seo_description":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-2809","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts\/2809","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/users\/2170"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/comments?post=2809"}],"version-history":[{"count":0,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts\/2809\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/media?parent=2809"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/categories?post=2809"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/tags?post=2809"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}