{"id":86,"date":"2026-04-12T18:51:35","date_gmt":"2026-04-12T18:51:35","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/alibaba-cloud-quick-bi-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-analytics-computing\/"},"modified":"2026-04-12T18:51:35","modified_gmt":"2026-04-12T18:51:35","slug":"alibaba-cloud-quick-bi-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-analytics-computing","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/alibaba-cloud-quick-bi-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-analytics-computing\/","title":{"rendered":"Alibaba Cloud Quick BI Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Analytics Computing"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Analytics Computing<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>Quick BI is Alibaba Cloud\u2019s business intelligence (BI) and data visualization service for building dashboards, ad-hoc analyses, and shared data reports on top of your existing data sources.<\/p>\n\n\n\n<p>In simple terms: <strong>connect Quick BI to your data (databases, data warehouses, or files), model that data into datasets, and then build interactive charts and dashboards that business and engineering teams can consume<\/strong>\u2014with governed access control and sharing.<\/p>\n\n\n\n<p>Technically, Quick BI is a <strong>managed, cloud-hosted BI application<\/strong> (SaaS-style) that sits in the Analytics Computing layer of Alibaba Cloud. It provides a browser-based authoring experience, a semantic\/dataset layer for reusable metrics and dimensions, and publishing\/sharing mechanisms for organization-wide reporting. It typically queries data from external sources (for example, Alibaba Cloud databases\/warehouses) and may optionally use caching\/extract\/accelerations depending on edition and configuration\u2014<strong>verify exact behaviors in official documentation for your edition<\/strong>.<\/p>\n\n\n\n<p>The main problem Quick BI solves is the gap between raw data and decision-making: teams need a <strong>reliable, repeatable, secure<\/strong> way to turn data into KPIs, operational dashboards, and analytics without building custom visualization apps or maintaining self-hosted BI infrastructure.<\/p>\n\n\n\n<blockquote>\n<p>Service name status: As of the latest Alibaba Cloud public materials, the service is still called <strong>Quick BI<\/strong>. If your account\/region shows different naming, <strong>verify in official docs<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Quick BI?<\/h2>\n\n\n\n<p><strong>Official purpose (what it is):<\/strong> Quick BI is Alibaba Cloud\u2019s managed BI and analytics visualization service that helps organizations build, publish, and share data analyses and dashboards.<\/p>\n\n\n\n<p><strong>Core capabilities (what it does):<\/strong>\n&#8211; Connect to data sources (Alibaba Cloud data platforms and common databases; availability depends on edition\/region\u2014<strong>verify<\/strong>).\n&#8211; Build datasets\/semantic models for reuse (metrics, dimensions, calculated fields).\n&#8211; Create interactive analyses and dashboards (filters, drill-down, sorting, cross-filtering).\n&#8211; Govern access (workspace, role-based permissions, row\/column-level restrictions where supported\u2014<strong>verify<\/strong>).\n&#8211; Share and distribute content (links, embedding, scheduled delivery\/exports where supported\u2014<strong>verify<\/strong>).<\/p>\n\n\n\n<p><strong>Major components (how it is organized conceptually):<\/strong>\n&#8211; <strong>Quick BI workspace\/tenant<\/strong>: Organizational boundary for content, users, and permissions (terminology can vary by console\u2014<strong>verify<\/strong>).\n&#8211; <strong>Data sources<\/strong>: Connection definitions to your databases\/warehouses\/files.\n&#8211; <strong>Datasets (semantic layer)<\/strong>: Curated, reusable \u201canalysis-ready\u201d entities built from tables\/views\/queries.\n&#8211; <strong>Analyses \/ dashboards<\/strong>: Visual and interactive content built on datasets.\n&#8211; <strong>Sharing &amp; permissions<\/strong>: Controls for who can view\/edit\/publish and what data they can see.<\/p>\n\n\n\n<p><strong>Service type:<\/strong> Managed BI\/analytics SaaS on Alibaba Cloud (web console and governed user access). It is not a data warehouse; it sits on top of your data platforms.<\/p>\n\n\n\n<p><strong>Scope (regional\/global\/zonal and account\/project boundaries):<\/strong>\n&#8211; Quick BI is delivered as a <strong>managed cloud service<\/strong> accessible through the Alibaba Cloud console.\n&#8211; Resource scope (tenant\/workspace, region binding, and data residency) can vary by subscription and region. <strong>Verify your region and residency requirements<\/strong> on the official Quick BI documentation\/product page.<\/p>\n\n\n\n<p><strong>How it fits into the Alibaba Cloud ecosystem:<\/strong>\nQuick BI commonly sits at the top of a typical Alibaba Cloud analytics stack:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Storage\/ingest<\/strong>: OSS, Log Service (SLS), streaming services (varies)<\/li>\n<li><strong>Compute\/warehouse<\/strong>: MaxCompute, AnalyticDB, Hologres, E-MapReduce (Spark\/Hive), RDS\/PolarDB<\/li>\n<li><strong>Integration\/governance<\/strong>: DataWorks, Data Lake Formation (where applicable), RAM, ActionTrail<\/li>\n<li><strong>Visualization &amp; consumption<\/strong>: <strong>Quick BI<\/strong> (business dashboards and analytics), sometimes complemented by DataV (large-screen visualization)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Quick BI?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Faster decisions<\/strong>: KPI dashboards reduce time-to-insight for finance, ops, sales, and product teams.<\/li>\n<li><strong>Single source of truth<\/strong>: Standardize metric definitions in datasets\/semantic models instead of per-team spreadsheets.<\/li>\n<li><strong>Self-service analytics<\/strong>: Reduce dependency on a small data engineering team for every new report.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed BI<\/strong>: No servers to run, patch, or scale like self-hosted tools.<\/li>\n<li><strong>Broad data connectivity<\/strong>: Designed to connect with common Alibaba Cloud data services and external databases (exact list varies\u2014<strong>verify<\/strong>).<\/li>\n<li><strong>Reuse via dataset layer<\/strong>: Build once, reuse across multiple dashboards.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Governed sharing<\/strong>: Workspace-based access, user roles, and controlled publishing.<\/li>\n<li><strong>Operational visibility<\/strong>: Most BI platforms provide refresh\/history\/error views for datasets and schedules (exact controls vary\u2014<strong>verify<\/strong>).<\/li>\n<li><strong>Separation of duties<\/strong>: Admins manage users and data sources; analysts build content; viewers consume.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Central access control<\/strong>: Manage access at the service level and at the dataset\/content level.<\/li>\n<li><strong>Auditability<\/strong>: Alibaba Cloud governance tooling (for example, RAM and ActionTrail) can complement Quick BI governance. <strong>Verify which Quick BI actions are auditable<\/strong> in your environment.<\/li>\n<li><strong>Data minimization<\/strong>: Use datasets\/permissions to avoid exposing raw tables broadly.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Elastic consumption<\/strong>: The BI layer scales as a service; performance depends heavily on your underlying data source design (indexes, partitions, aggregate tables, and concurrency capacity).<\/li>\n<li><strong>Caching\/acceleration options<\/strong>: Often available in BI tools; capability and limits are edition-dependent\u2014<strong>verify<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose Quick BI<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You already store data in Alibaba Cloud databases\/warehouses and need dashboards quickly.<\/li>\n<li>You need governed, shareable analytics across multiple teams.<\/li>\n<li>You prefer managed services and want to avoid operating a BI stack.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose Quick BI<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You need a highly customized front-end analytics application with bespoke UX (you may need a custom app + APIs).<\/li>\n<li>You require an open-source-only stack or strict on-prem-only BI (unless Quick BI supports your specific hybrid requirements via gateways\u2014<strong>verify<\/strong>).<\/li>\n<li>Your data sources cannot be securely connected due to networking\/compliance constraints and you cannot deploy the required connectivity components.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Quick BI used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Retail and e-commerce (sales funnels, inventory, cohort analysis)<\/li>\n<li>Finance and fintech (risk dashboards, reconciliation, regulatory reporting)<\/li>\n<li>Manufacturing (OEE, quality defects, supply chain dashboards)<\/li>\n<li>Logistics (delivery performance, route efficiency)<\/li>\n<li>Gaming and media (engagement KPIs, retention cohorts)<\/li>\n<li>SaaS and internet services (product analytics, revenue metrics)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>BI analysts and data analysts<\/li>\n<li>Data engineering and platform teams (data modeling + governance)<\/li>\n<li>Product managers (feature KPIs)<\/li>\n<li>Operations teams (SLA\/SLO dashboards)<\/li>\n<li>Finance and business ops (bookings, ARR, gross margin)<\/li>\n<li>Security and compliance teams (audit-focused dashboards, if sources available)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>KPI dashboards (daily\/weekly metrics)<\/li>\n<li>Ad-hoc slicing\/dicing<\/li>\n<li>Executive reporting packs<\/li>\n<li>Operational monitoring dashboards (business metrics, not infrastructure metrics)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data warehouse-centric (MaxCompute\/AnalyticDB\/Hologres) + Quick BI for consumption<\/li>\n<li>Lakehouse-style (OSS + compute engine) + curated BI datasets<\/li>\n<li>Operational DB reporting (RDS\/PolarDB) with careful performance safeguards<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Production vs dev\/test usage<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dev\/Test<\/strong>: Validate datasets, metric definitions, and dashboard UX using limited data or non-sensitive copies.<\/li>\n<li><strong>Production<\/strong>: Strong governance (RAM + workspace roles), controlled data sources, performance-tested queries, and scheduled refresh policies.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios where Quick BI is commonly a strong fit.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Executive KPI dashboard<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Leadership needs consistent KPIs (revenue, retention, CAC, NPS) without manual spreadsheet work.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Central dataset definitions + shareable dashboards with permissions.<\/li>\n<li><strong>Example:<\/strong> CFO dashboard reading from a curated \u201cfinance_kpi\u201d dataset in AnalyticDB.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Sales pipeline and forecast reporting<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Sales ops needs near-real-time views into pipeline stages and forecasting accuracy.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Interactive filtering by region\/rep\/segment and scheduled refresh.<\/li>\n<li><strong>Example:<\/strong> Sales dashboard sourced from CRM extracts loaded into MaxCompute daily.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) E-commerce conversion funnel analysis<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Product teams need drop-off analysis across checkout steps.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Funnel-style dashboards (or equivalent charting) and drill-down by device\/channel.<\/li>\n<li><strong>Example:<\/strong> Web events aggregated in Hologres; Quick BI dashboard shows step conversion rates.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Marketing attribution reporting<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Marketing wants unified ROI across multiple ad platforms.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Dataset modeling to standardize campaign dimensions and metrics.<\/li>\n<li><strong>Example:<\/strong> Ad spend ingested via DataWorks into a reporting schema; Quick BI reports ROI by channel.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Supply chain and inventory visibility<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Inventory imbalances cause stockouts and overstocks.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Time-series views, alerts via scheduled distribution (if supported), and role-based access.<\/li>\n<li><strong>Example:<\/strong> Inventory snapshot table in RDS\/AnalyticDB; Quick BI dashboard tracks weeks-of-supply.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Customer support analytics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Support leaders need ticket backlog, SLA breaches, and root causes.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Slice by product, severity, region; drill into trends.<\/li>\n<li><strong>Example:<\/strong> Ticketing data loaded into MaxCompute; Quick BI shows SLA compliance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Financial reconciliation reporting<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Finance needs reconciliation across payment processors and internal ledgers.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Controlled access to sensitive datasets; consistent reconciliation KPIs.<\/li>\n<li><strong>Example:<\/strong> Daily reconciliation tables computed in MaxCompute; Quick BI dashboards for finance team only.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Multi-tenant SaaS usage analytics (internal)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Engineering and product need tenant-level usage and performance KPIs.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Row-level access patterns (where supported) and reusable datasets.<\/li>\n<li><strong>Example:<\/strong> Usage events aggregated by tenant_id; internal dashboards for CSMs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Data quality &amp; pipeline health reporting (business-facing)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Data reliability issues undermine trust.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Data quality KPIs (freshness, completeness) tracked in a dataset.<\/li>\n<li><strong>Example:<\/strong> DataWorks outputs DQ metrics to a table; Quick BI shows pipeline SLA health.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Regional operations reporting<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Regional teams need localized reporting with restrictions.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Workspace segmentation + dataset permissions.<\/li>\n<li><strong>Example:<\/strong> APAC\/EMEA dashboards built on same dataset but restricted by region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Embedded analytics (application portal)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A product needs to show dashboards to internal users or customers.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Many BI tools support embedding with access control (capability varies\u2014<strong>verify<\/strong>).<\/li>\n<li><strong>Example:<\/strong> Operations portal embeds a Quick BI dashboard for store managers.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Audit and compliance reporting<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Compliance teams need periodic reports from governed sources.<\/li>\n<li><strong>Why Quick BI fits:<\/strong> Standardized reporting, controlled access, exports (if supported).<\/li>\n<li><strong>Example:<\/strong> Monthly access review dashboard from IAM logs loaded into a warehouse.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<p>Feature availability varies by <strong>edition, region, and tenant settings<\/strong>. Confirm in official docs for your subscription.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Data source connections<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Lets you define connections to supported databases\/warehouses and other sources.<\/li>\n<li><strong>Why it matters:<\/strong> BI is only as good as its connectivity; centralized connections reduce duplicated credentials.<\/li>\n<li><strong>Practical benefit:<\/strong> Analysts can build datasets without re-entering connection details each time.<\/li>\n<li><strong>Caveats:<\/strong> Network reachability (VPC vs public), whitelists, and encryption settings can be tricky. Some sources require gateways\u2014<strong>verify<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Dataset \/ semantic modeling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Builds reusable datasets with curated fields, joins, calculated measures, and business definitions.<\/li>\n<li><strong>Why it matters:<\/strong> Prevents \u201cmetric drift\u201d (different definitions across dashboards).<\/li>\n<li><strong>Practical benefit:<\/strong> You can publish a \u201cSales KPI\u201d dataset that everyone uses consistently.<\/li>\n<li><strong>Caveats:<\/strong> Complex joins and calculations may push load to your source system; performance engineering is still required.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Interactive dashboards and ad-hoc analysis<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides chart building and dashboard composition with filtering and drill interactions.<\/li>\n<li><strong>Why it matters:<\/strong> Non-engineers can explore data without writing SQL (depending on dataset design).<\/li>\n<li><strong>Practical benefit:<\/strong> Faster iteration for KPI changes and exploration.<\/li>\n<li><strong>Caveats:<\/strong> For large datasets, \u201cself-service\u201d still needs well-designed aggregates\/partitions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Permissions and content governance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Manages who can view\/edit datasets and dashboards.<\/li>\n<li><strong>Why it matters:<\/strong> BI often includes sensitive financial or customer data.<\/li>\n<li><strong>Practical benefit:<\/strong> Share dashboards widely while restricting sensitive datasets.<\/li>\n<li><strong>Caveats:<\/strong> Fine-grained security (row\/column-level) is often edition-dependent\u2014<strong>verify<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Scheduling and distribution (if enabled)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Refreshes datasets and\/or delivers reports on a schedule.<\/li>\n<li><strong>Why it matters:<\/strong> Executives and ops teams rely on timely recurring reports.<\/li>\n<li><strong>Practical benefit:<\/strong> Automated refresh reduces manual export workflows.<\/li>\n<li><strong>Caveats:<\/strong> Schedules increase load on data sources; set concurrency and off-peak windows.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Exporting and sharing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Enables sharing dashboards via links, permissions, and possibly export to files (PDF\/Excel\/image depending on features\u2014<strong>verify<\/strong>).<\/li>\n<li><strong>Why it matters:<\/strong> Many stakeholders still want \u201coffline\u201d report packs.<\/li>\n<li><strong>Practical benefit:<\/strong> Publish a monthly business review report.<\/li>\n<li><strong>Caveats:<\/strong> Exports can become a data leakage vector; apply strict access controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Multi-workspace \/ organizational management<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Separates content and permissions across teams (e.g., Finance workspace vs Marketing workspace).<\/li>\n<li><strong>Why it matters:<\/strong> Reduces accidental changes and supports least privilege.<\/li>\n<li><strong>Practical benefit:<\/strong> Different admins and dataset owners per department.<\/li>\n<li><strong>Caveats:<\/strong> Cross-workspace sharing may be limited or require special configuration\u2014<strong>verify<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Performance features (caching\/acceleration)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Improves query response with caching or extracts in some BI architectures.<\/li>\n<li><strong>Why it matters:<\/strong> Dashboard interactivity depends on fast queries.<\/li>\n<li><strong>Practical benefit:<\/strong> Reduce load on source systems for repeated queries.<\/li>\n<li><strong>Caveats:<\/strong> Cache invalidation and freshness must be designed; capabilities depend on edition\u2014<strong>verify<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Collaboration features<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Enables multiple authors\/teams to build and manage content.<\/li>\n<li><strong>Why it matters:<\/strong> BI is iterative and cross-functional.<\/li>\n<li><strong>Practical benefit:<\/strong> Shared datasets enable standardization.<\/li>\n<li><strong>Caveats:<\/strong> Without naming\/versioning conventions, content sprawl happens quickly.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Administration and operational controls<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> User management, license assignment (if applicable), data source management, and content governance.<\/li>\n<li><strong>Why it matters:<\/strong> Prevents uncontrolled growth and security risk.<\/li>\n<li><strong>Practical benefit:<\/strong> Centralized administration reduces risk of credential misuse.<\/li>\n<li><strong>Caveats:<\/strong> Admin UI and audit outputs differ by region\/edition\u2014<strong>verify<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-level architecture<\/h3>\n\n\n\n<p>Quick BI is a managed BI layer that authenticates users (via Alibaba Cloud account and\/or organization users), connects to approved data sources, generates queries based on user interactions, and renders visualizations in the browser.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow (conceptual)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>User signs in<\/strong> to Quick BI using Alibaba Cloud identity (and any configured organization\/user directory features).<\/li>\n<li>User opens a <strong>dashboard<\/strong> that references one or more <strong>datasets<\/strong>.<\/li>\n<li>Quick BI translates dashboard interactions into <strong>queries<\/strong> against the connected data source(s).<\/li>\n<li>Data source returns results; Quick BI may apply formatting\/aggregation (depending on modeling).<\/li>\n<li>Dashboard renders charts; user can filter\/drill, triggering more queries.<\/li>\n<li>Scheduled refresh and report delivery (if configured) runs under service-controlled tasks.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related services (common patterns)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>MaxCompute \/ AnalyticDB \/ Hologres \/ E-MapReduce<\/strong>: Analytical backends that serve BI queries efficiently.<\/li>\n<li><strong>ApsaraDB RDS \/ PolarDB<\/strong>: Operational databases; use with care (read replicas, aggregates).<\/li>\n<li><strong>DataWorks<\/strong>: ETL\/ELT pipelines to build curated tables for BI.<\/li>\n<li><strong>OSS<\/strong>: Data lake storage feeding compute engines; sometimes file-based data.<\/li>\n<li><strong>RAM (Resource Access Management)<\/strong>: Access control for users\/operators at Alibaba Cloud account level.<\/li>\n<li><strong>VPC\/networking services<\/strong>: Control connectivity to private data sources (gateway patterns may apply\u2014<strong>verify<\/strong>).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<p>Quick BI depends on:\n&#8211; Identity and billing under your Alibaba Cloud account.\n&#8211; Your selected data source services for data availability, performance, and SLA.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model (practical view)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Administrative access<\/strong>: Granted via Alibaba Cloud RAM users\/roles and Quick BI admin roles (exact mapping varies).<\/li>\n<li><strong>Content access<\/strong>: Managed inside Quick BI (workspace roles, dataset permissions).<\/li>\n<li><strong>Data access<\/strong>: Enforced by a combination of:<\/li>\n<li>Data source credentials used by Quick BI (service account pattern).<\/li>\n<li>Dataset-level controls (where supported).<\/li>\n<li>Data source native controls (database users\/roles, views).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model (typical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Quick BI is a managed service. When it connects to your databases\/warehouses:<\/li>\n<li>For public endpoints, you may need to <strong>configure allowlists\/whitelists<\/strong> (for example, database IP allowlist) to include Quick BI outbound IPs\u2014<strong>verify official docs for the correct IP ranges<\/strong>.<\/li>\n<li>For private endpoints (VPC), you may need a <strong>connectivity mechanism<\/strong> (gateway\/agent\/private link) depending on what Quick BI supports in your region\/edition\u2014<strong>verify<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dashboard performance:<\/strong> track slow dashboards by reviewing dataset queries, database slow query logs, and warehouse query history.<\/li>\n<li><strong>Refresh failures:<\/strong> use Quick BI task history (if available) plus underlying data source logs.<\/li>\n<li><strong>Audit:<\/strong> use Alibaba Cloud governance tools such as RAM policies and ActionTrail (if Quick BI emits events\u2014<strong>verify<\/strong>).<\/li>\n<li><strong>Data governance:<\/strong> treat datasets as governed assets; use DataWorks\/metadata tools where appropriate.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  U[Business User&lt;br\/&gt;Browser] --&gt;|Login| QB[Quick BI (Alibaba Cloud)]\n  QB --&gt;|Query| DS[(Data Source&lt;br\/&gt;RDS\/AnalyticDB\/MaxCompute)]\n  DS --&gt;|Result Set| QB\n  QB --&gt;|Dashboards\/Charts| U\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Identity_and_Governance[Identity &amp; Governance]\n    RAM[RAM Users\/Roles\/Policies]\n    AT[ActionTrail (audit)&lt;br\/&gt;(verify Quick BI events)]\n  end\n\n  subgraph Data_Platform[Alibaba Cloud Data Platform]\n    DW[DataWorks (ETL\/ELT)]\n    WH[(MaxCompute \/ AnalyticDB \/ Hologres)]\n    RDS[(RDS\/PolarDB Operational DB)]\n    OSS[(OSS Data Lake)]\n  end\n\n  subgraph BI[Analytics Computing - BI Layer]\n    QB[Quick BI Workspace\/Tenant]\n    DSDEF[Data Source Definitions]\n    DATASET[Datasets \/ Semantic Model]\n    DASH[Dashboards &amp; Reports]\n  end\n\n  subgraph Consumers[Consumers]\n    Exec[Executives]\n    Ops[Ops\/Finance\/Marketing]\n    Embed[Internal Portal&lt;br\/&gt;(Embedding if supported)]\n  end\n\n  RAM --&gt; QB\n  AT --&gt; QB\n\n  OSS --&gt; DW\n  RDS --&gt; DW\n  DW --&gt; WH\n\n  QB --&gt; DSDEF\n  DSDEF --&gt; WH\n  DSDEF --&gt; RDS\n\n  QB --&gt; DATASET --&gt; DASH\n  DASH --&gt; Exec\n  DASH --&gt; Ops\n  DASH --&gt; Embed\n<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<p>Before starting, confirm the following.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Account\/subscription\/tenancy requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An active <strong>Alibaba Cloud account<\/strong> with billing enabled.<\/li>\n<li>An active <strong>Quick BI subscription\/instance<\/strong> for your account (edition-dependent).<\/li>\n<li>Access to at least one supported data source (or a file upload capability, if your edition supports it\u2014<strong>verify<\/strong>).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM (RAM) requirements<\/h3>\n\n\n\n<p>You typically need one of the following:\n&#8211; Alibaba Cloud account administrator privileges, <strong>or<\/strong>\n&#8211; A RAM user\/role with permissions to:\n  &#8211; Purchase\/activate Quick BI (if not already active)\n  &#8211; Manage Quick BI users\/workspaces (admin tasks)\n  &#8211; Create\/modify data sources in Quick BI\n  &#8211; Access\/provision the underlying data source (RDS\/AnalyticDB\/etc.)<\/p>\n\n\n\n<p><strong>Tip:<\/strong> Use least privilege. Create a dedicated RAM role\/user for BI administration and separate users for authors\/viewers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Quick BI is typically billed via <strong>subscription\/edition and user licensing<\/strong> (details vary\u2014<strong>verify on pricing pages<\/strong>).<\/li>\n<li>Your data sources (RDS\/AnalyticDB\/MaxCompute) have separate costs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">CLI\/SDK\/tools needed<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>No CLI is required for basic Quick BI usage.<\/li>\n<li>For this lab, you may use:<\/li>\n<li>Alibaba Cloud console<\/li>\n<li>A SQL client for your database (DMS in Alibaba Cloud console can work for RDS)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Quick BI availability and features can differ by region and international vs mainland China sites.<\/li>\n<li><strong>Verify supported regions<\/strong> on the Quick BI product page and documentation:<\/li>\n<li>https:\/\/www.alibabacloud.com\/product\/quick-bi<\/li>\n<li>https:\/\/www.alibabacloud.com\/help\/en\/quick-bi<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas\/limits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Common limits include number of users, workspaces, datasets, refresh schedules, and data source connections.<\/li>\n<li>These are often <strong>edition-based<\/strong>. <strong>Verify quotas<\/strong> in your Quick BI admin\/billing docs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (for the hands-on lab)<\/h3>\n\n\n\n<p>For the tutorial below, you need:\n&#8211; One MySQL-compatible database reachable by Quick BI:\n  &#8211; ApsaraDB RDS for MySQL (recommended for a clean lab), <strong>or<\/strong>\n  &#8211; Another supported MySQL endpoint you control<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<p>Quick BI pricing is <strong>not a single usage meter like pure compute<\/strong>. It is usually structured around <strong>editions and user licensing<\/strong>, plus optional add-ons and the cost of your underlying data platform.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing dimensions (typical)<\/h3>\n\n\n\n<p>Verify the current model on official sources, but expect one or more of:\n&#8211; <strong>Edition\/plan<\/strong> (Standard\/Professional\/Enterprise or similar tiers\u2014names vary)\n&#8211; <strong>User seats<\/strong> (authors\/designers vs viewers\/consumers; some models separate roles)\n&#8211; <strong>Add-ons<\/strong> (advanced governance, higher capacity, embedding, scheduling, etc.\u2014verify)\n&#8211; <strong>Contract pricing<\/strong> for enterprises (negotiated)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Free trials or limited-time promotions may exist for new accounts.<\/li>\n<li><strong>Do not assume a free tier<\/strong>; check the current offer on the product\/pricing page.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Primary cost drivers<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Number of licensed users (especially content creators).<\/li>\n<li>Edition tier (advanced features and capacity).<\/li>\n<li>Dashboard\/query concurrency requirements (often drives bigger data warehouses, not necessarily Quick BI itself).<\/li>\n<li>Scheduled refresh frequency and dataset complexity (affects warehouse compute costs).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden\/indirect costs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Underlying data source costs<\/strong>: The biggest cost is often your warehouse\/database compute.<\/li>\n<li><strong>Network egress<\/strong>: If data sources are cross-region or cross-border, data transfer can add cost and latency.<\/li>\n<li><strong>Operational overhead<\/strong>: Curating BI-ready models often requires DataWorks jobs, which have their own cost.<\/li>\n<li><strong>Security tooling<\/strong>: Centralized audit\/log retention can add cost (for example, ActionTrail\/SLS usage\u2014verify).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keep Quick BI and data sources in the <strong>same region<\/strong> when possible.<\/li>\n<li>Prefer private connectivity options when supported; otherwise, use strict allowlists and TLS.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start with a small number of author seats; scale viewers separately if licensing allows.<\/li>\n<li>Use <strong>curated aggregate tables<\/strong> for dashboards to reduce expensive queries.<\/li>\n<li>Reduce refresh frequency where near-real-time is not required.<\/li>\n<li>Use partitioning and indexing in the underlying data source.<\/li>\n<li>Implement a \u201ccertified datasets only\u201d policy to reduce duplicated datasets and compute.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (model, not numbers)<\/h3>\n\n\n\n<p>Because exact prices vary by edition\/region and are updated by Alibaba Cloud, a realistic starter cost model is:\n&#8211; Quick BI: entry edition + a small number of author seats\n&#8211; Data source: smallest suitable pay-as-you-go RDS instance (or an existing warehouse)\n&#8211; Data transfer: same-region, minimal<\/p>\n\n\n\n<p><strong>You must price this using official pricing pages for your region and edition.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations<\/h3>\n\n\n\n<p>In production, cost planning should include:\n&#8211; Quick BI enterprise edition (if required for governance\/embedding\/scheduling)\n&#8211; Separate author and viewer licensing (if applicable)\n&#8211; Dedicated analytics warehouse capacity (AnalyticDB\/MaxCompute\/Hologres) sized for concurrency\n&#8211; DataWorks ETL compute\n&#8211; Backup\/retention policies and data lifecycle management\n&#8211; Network architecture (private connectivity, NAT, egress)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Official pricing references<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Product page (often links to pricing): https:\/\/www.alibabacloud.com\/product\/quick-bi  <\/li>\n<li>Documentation landing page (navigate to Billing\/Buy\/Edition): https:\/\/www.alibabacloud.com\/help\/en\/quick-bi  <\/li>\n<\/ul>\n\n\n\n<p>If you have access to the Alibaba Cloud pricing calculator for your account\/region, use it. If not, consult the product pricing section and billing docs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab walks you through connecting Quick BI to a MySQL database, modeling a dataset, and publishing a dashboard.<\/p>\n\n\n\n<blockquote>\n<p>Notes before you start<br\/>\n&#8211; Console UI labels can change by region\/edition. If a menu item differs, use the closest equivalent and <strong>verify against official docs<\/strong>.<br\/>\n&#8211; Do <strong>not<\/strong> open your database broadly to the internet. Use strict allowlists and strong credentials.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Build a Quick BI dashboard (\u201cSales Overview\u201d) powered by a MySQL table, with:\n&#8211; Total revenue KPI\n&#8211; Revenue by product category bar chart\n&#8211; Date filter for order date<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Prepare a small MySQL schema and sample data.\n2. Activate Quick BI and set up a workspace.\n3. Add MySQL as a data source in Quick BI.\n4. Create a dataset from the sales table.\n5. Build and publish a dashboard.\n6. Validate results and clean up.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Prepare a MySQL database and load sample data<\/h3>\n\n\n\n<p>You can use:\n&#8211; <strong>ApsaraDB RDS for MySQL<\/strong> (recommended), or\n&#8211; Any MySQL endpoint you control that Quick BI can reach.<\/p>\n\n\n\n<p><strong>Option A (recommended): Use ApsaraDB RDS for MySQL<\/strong>\n1. In Alibaba Cloud console, create an RDS for MySQL instance (pay-as-you-go for a short lab).\n2. Create a database named <code>quickbi_lab<\/code>.\n3. Create a privileged user (for the lab only) like <code>quickbi_user<\/code> with a strong password.\n4. Ensure network connectivity:\n   &#8211; If using a <strong>public endpoint<\/strong>, configure the RDS allowlist appropriately.\n   &#8211; If using <strong>VPC-only<\/strong>, confirm Quick BI can access it through supported private connectivity (gateway\/private access patterns vary\u2014<strong>verify in Quick BI docs<\/strong>).<\/p>\n\n\n\n<p><strong>Load the sample schema<\/strong>\nRun the following SQL in your MySQL client (DMS is often used for RDS in Alibaba Cloud):<\/p>\n\n\n\n<pre><code class=\"language-sql\">CREATE DATABASE IF NOT EXISTS quickbi_lab;\nUSE quickbi_lab;\n\nDROP TABLE IF EXISTS sales_orders;\n\nCREATE TABLE sales_orders (\n  order_id      BIGINT PRIMARY KEY,\n  order_date    DATE NOT NULL,\n  region        VARCHAR(32) NOT NULL,\n  category      VARCHAR(64) NOT NULL,\n  product_name  VARCHAR(128) NOT NULL,\n  quantity      INT NOT NULL,\n  unit_price    DECIMAL(10,2) NOT NULL\n);\n\nINSERT INTO sales_orders (order_id, order_date, region, category, product_name, quantity, unit_price) VALUES\n(10001, '2026-03-01', 'APAC', 'Accessories', 'USB-C Cable', 10, 9.99),\n(10002, '2026-03-01', 'APAC', 'Accessories', 'Wireless Mouse', 3, 24.50),\n(10003, '2026-03-02', 'EMEA', 'Laptops', 'Ultrabook 13', 1, 999.00),\n(10004, '2026-03-02', 'AMER', 'Monitors', '27-inch Monitor', 2, 219.99),\n(10005, '2026-03-03', 'AMER', 'Accessories', 'Keyboard', 4, 39.90),\n(10006, '2026-03-03', 'EMEA', 'Laptops', 'Developer Laptop 15', 1, 1299.00),\n(10007, '2026-03-04', 'APAC', 'Monitors', '24-inch Monitor', 2, 149.00),\n(10008, '2026-03-04', 'EMEA', 'Accessories', 'Laptop Stand', 5, 29.00),\n(10009, '2026-03-05', 'AMER', 'Laptops', 'Ultrabook 13', 2, 979.00),\n(10010, '2026-03-05', 'APAC', 'Accessories', 'USB-C Hub', 6, 34.99);\n\n-- A simple view that Quick BI can use as a clean source (optional)\nDROP VIEW IF EXISTS v_sales_orders;\nCREATE VIEW v_sales_orders AS\nSELECT\n  order_id,\n  order_date,\n  region,\n  category,\n  product_name,\n  quantity,\n  unit_price,\n  (quantity * unit_price) AS revenue\nFROM sales_orders;\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Database <code>quickbi_lab<\/code> exists.\n&#8211; View <code>v_sales_orders<\/code> returns rows with a computed <code>revenue<\/code> field.<\/p>\n\n\n\n<p><strong>Quick verification<\/strong><\/p>\n\n\n\n<pre><code class=\"language-sql\">SELECT category, SUM(quantity * unit_price) AS total_revenue\nFROM sales_orders\nGROUP BY category\nORDER BY total_revenue DESC;\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Activate Quick BI and create a workspace<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to the Quick BI console from Alibaba Cloud:\n   &#8211; Product page: https:\/\/www.alibabacloud.com\/product\/quick-bi\n   &#8211; Docs: https:\/\/www.alibabacloud.com\/help\/en\/quick-bi<\/li>\n<li>If required, purchase\/activate an edition for your account.<\/li>\n<li>In Quick BI, create or select a <strong>workspace<\/strong> for this lab (for example, <code>Lab-Workspace<\/code>).<\/li>\n<li>Confirm you have an author\/designer role for content creation.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You can access the Quick BI authoring interface and see a workspace ready for assets.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Add MySQL as a data source in Quick BI<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In Quick BI, find <strong>Data Sources<\/strong> (or equivalent).<\/li>\n<li>Choose <strong>Add Data Source<\/strong>.<\/li>\n<li>Select <strong>MySQL<\/strong> (or \u201cApsaraDB RDS for MySQL\u201d if there is a specific connector).<\/li>\n<li>Enter connection details:\n   &#8211; Hostname\/IP (RDS endpoint)\n   &#8211; Port (default 3306)\n   &#8211; Database name (<code>quickbi_lab<\/code>)\n   &#8211; Username (<code>quickbi_user<\/code>)\n   &#8211; Password (use a secure secret manager outside of Quick BI where possible\u2014see Security section)<\/li>\n<li>\n<p>Configure network\/security:\n   &#8211; If asked for encryption\/TLS, enable it if supported by your DB configuration.\n   &#8211; If asked for allowlist IPs, consult Quick BI docs for outbound IP ranges and add them to the DB allowlist. <strong>Do not guess IP ranges. Verify in official docs.<\/strong><\/p>\n<\/li>\n<li>\n<p>Test the connection and save.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Data source status shows <strong>Connected<\/strong> (or an equivalent successful test message).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Create a dataset from the view\/table<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Navigate to <strong>Datasets<\/strong> (or \u201cData Modeling\u201d).<\/li>\n<li>Create a new dataset from the MySQL data source.<\/li>\n<li>Select <code>v_sales_orders<\/code> (recommended) or <code>sales_orders<\/code>.<\/li>\n<li>Set field types:\n   &#8211; <code>order_date<\/code> as Date\n   &#8211; <code>revenue<\/code> as numeric measure (if using view)\n   &#8211; <code>category<\/code>, <code>region<\/code>, <code>product_name<\/code> as dimensions<\/li>\n<li>Add a calculated field if you used the base table:\n   &#8211; <code>revenue = quantity * unit_price<\/code><\/li>\n<li>Save the dataset as <code>ds_sales_orders<\/code>.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Dataset <code>ds_sales_orders<\/code> is available and preview returns the expected columns.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Build an analysis (charts)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create a new <strong>Analysis<\/strong> (or \u201cWorkbook\u201d\/\u201cAd hoc analysis\u201d depending on UI).<\/li>\n<li>Select dataset <code>ds_sales_orders<\/code>.<\/li>\n<\/ol>\n\n\n\n<p>Create the following visuals:<\/p>\n\n\n\n<p><strong>Visual A: KPI \u2014 Total Revenue<\/strong>\n&#8211; Metric: <code>SUM(revenue)<\/code>\n&#8211; Format: currency\/decimal as appropriate<\/p>\n\n\n\n<p><strong>Visual B: Bar chart \u2014 Revenue by Category<\/strong>\n&#8211; Dimension: <code>category<\/code>\n&#8211; Metric: <code>SUM(revenue)<\/code>\n&#8211; Sort by <code>SUM(revenue)<\/code> descending<\/p>\n\n\n\n<p><strong>Visual C: Trend \u2014 Revenue by Date<\/strong>\n&#8211; Dimension: <code>order_date<\/code> (daily)\n&#8211; Metric: <code>SUM(revenue)<\/code><\/p>\n\n\n\n<p>Add a <strong>global filter<\/strong>:\n&#8211; Filter field: <code>order_date<\/code>\n&#8211; Type: date range\n&#8211; Apply to all visuals<\/p>\n\n\n\n<p>Save the analysis as <code>Sales Overview - Analysis<\/code>.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Analysis renders three visuals and a date range filter changes the displayed totals.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Publish a dashboard and share it<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create a new <strong>Dashboard<\/strong>.<\/li>\n<li>Add the visuals from your analysis.<\/li>\n<li>Arrange:\n   &#8211; KPI on top\n   &#8211; Bar chart left\n   &#8211; Trend chart right or below<\/li>\n<li>Set dashboard name: <code>Sales Overview<\/code>.<\/li>\n<li>Configure permissions:\n   &#8211; Create a \u201cViewers\u201d group\/role if available.\n   &#8211; Grant view-only access to intended users.<\/li>\n<li>Publish.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Dashboard is accessible via the Quick BI portal for users with permission.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>Use this checklist:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Data source test succeeds<\/strong> in Quick BI.<\/li>\n<li>Dataset preview returns the rows and computed <code>revenue<\/code>.<\/li>\n<li>Dashboard KPI matches a direct SQL check:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-sql\">SELECT SUM(quantity * unit_price) AS total_revenue\nFROM sales_orders;\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"4\">\n<li>Filtering by date changes totals (for example, only <code>2026-03-01<\/code> should include order_id 10001 and 10002).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<p>Common problems and realistic fixes:<\/p>\n\n\n\n<p><strong>Problem: Connection test fails (timeout)<\/strong>\n&#8211; Likely causes:\n  &#8211; DB not reachable from Quick BI due to allowlist\/VPC routing\n  &#8211; Wrong endpoint\/port\n&#8211; Fix:\n  &#8211; If using public endpoint, confirm RDS allowlist includes the correct Quick BI outbound IP ranges (<strong>verify in official docs<\/strong>).\n  &#8211; Confirm security group rules and that port 3306 is open to the required sources only.<\/p>\n\n\n\n<p><strong>Problem: Authentication fails<\/strong>\n&#8211; Likely causes:\n  &#8211; Wrong username\/password\n  &#8211; User not permitted from that host\n&#8211; Fix:\n  &#8211; Reset DB user password.\n  &#8211; Verify MySQL user privileges for <code>quickbi_lab<\/code> and the view\/table.<\/p>\n\n\n\n<p><strong>Problem: Dashboard is slow<\/strong>\n&#8211; Likely causes:\n  &#8211; Queries scanning too much data\n  &#8211; Missing indexes\/partitions\n&#8211; Fix:\n  &#8211; Use aggregate tables for BI.\n  &#8211; Add indexes (for MySQL: on <code>order_date<\/code>, <code>category<\/code>, <code>region<\/code> depending on queries).\n  &#8211; Limit date ranges and avoid high-cardinality dimensions.<\/p>\n\n\n\n<p><strong>Problem: Numbers don\u2019t match finance totals<\/strong>\n&#8211; Likely causes:\n  &#8211; Different metric definition (gross vs net revenue)\n  &#8211; Currency conversion missing\n&#8211; Fix:\n  &#8211; Create a governed dataset with certified metric definitions.\n  &#8211; Use a dimension table for currency and enforce consistent conversions upstream.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing costs and reduce risk:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In Quick BI:\n   &#8211; Delete or archive the <code>Sales Overview<\/code> dashboard.\n   &#8211; Delete the analysis and dataset (<code>ds_sales_orders<\/code>).\n   &#8211; Remove the MySQL data source (especially if it stores credentials).<\/li>\n<li>In your database:\n   &#8211; Drop the schema if it\u2019s lab-only:\n     <code>sql\n     DROP DATABASE IF EXISTS quickbi_lab;<\/code><\/li>\n<li>If you created an RDS instance purely for this lab:\n   &#8211; Delete\/release it in the Alibaba Cloud console to stop billing.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Use an analytics backend for BI<\/strong> (MaxCompute\/AnalyticDB\/Hologres) when concurrency and large scans are expected. Avoid running heavy BI workloads on operational databases.<\/li>\n<li><strong>Adopt a curated modeling layer<\/strong>: build \u201cBI-ready\u201d tables\/views with stable schemas and documented definitions.<\/li>\n<li><strong>Separate layers<\/strong>:<\/li>\n<li>Raw ingestion layer (immutable)<\/li>\n<li>Cleansed\/standardized layer<\/li>\n<li>BI mart layer (aggregated, denormalized, optimized for dashboards)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>RAM least privilege<\/strong> for admins and authors.<\/li>\n<li>Use <strong>separate workspaces<\/strong> for departments and environments (Dev\/Test\/Prod) if your edition supports it.<\/li>\n<li>Store credentials in a secure process:<\/li>\n<li>Prefer database accounts with minimal privileges (read-only on specific schemas\/views).<\/li>\n<li>Rotate credentials regularly.<\/li>\n<li>Implement <strong>row\/column-level security<\/strong> where supported; otherwise enforce it with database views.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Control dataset refresh and dashboard polling frequency.<\/li>\n<li>Reduce expensive queries using:<\/li>\n<li>Pre-aggregations (daily\/weekly fact tables)<\/li>\n<li>Materialized views (if supported by your warehouse)<\/li>\n<li>Partition pruning (date partitioning is essential)<\/li>\n<li>Monitor warehouse compute utilization and scale based on BI concurrency windows.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Design datasets to avoid multi-billion-row scans for interactive dashboards.<\/li>\n<li>Keep dashboard visuals limited and purposeful; too many visuals can multiply query load.<\/li>\n<li>Use \u201ctop N\u201d patterns and filters by default (e.g., last 30 days).<\/li>\n<li>Validate performance with representative user concurrency.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat dashboards as production assets:<\/li>\n<li>Version critical datasets and dashboard definitions (export or documented change control).<\/li>\n<li>Establish ownership (dataset owner, dashboard owner).<\/li>\n<li>Build upstream SLAs for data freshness and communicate in dashboards (e.g., \u201cLast refreshed at \u2026\u201d).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Define an operational checklist:<\/li>\n<li>Daily refresh success<\/li>\n<li>Slow dashboard reports<\/li>\n<li>Permission review<\/li>\n<li>Credential rotation status<\/li>\n<li>Use tags\/naming conventions:<\/li>\n<li>Prefix datasets with domain: <code>FIN_<\/code>, <code>MKT_<\/code>, <code>OPS_<\/code><\/li>\n<li>Suffix environment: <code>_DEV<\/code>, <code>_PROD<\/code><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Maintain a \u201ccertified datasets\u201d catalog:<\/li>\n<li>Only certified datasets can be used for executive dashboards.<\/li>\n<li>Document metric definitions inside dataset descriptions and a central wiki.<\/li>\n<li>Periodically remove unused assets to reduce clutter and risk.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<p>Security in Quick BI is shared across:\n&#8211; Alibaba Cloud identity (RAM)\n&#8211; Quick BI internal roles\/permissions\n&#8211; Data source permissions and network boundaries<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>RAM users\/roles<\/strong> for administrative control of Alibaba Cloud resources.<\/li>\n<li>Use Quick BI\u2019s internal roles (admins\/authors\/viewers) to control content access.<\/li>\n<li>For enterprise setups, integrate with corporate identity if supported by Quick BI in your region\/edition\u2014<strong>verify<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>In transit:<\/strong> Prefer TLS connections to databases where supported.<\/li>\n<li><strong>At rest:<\/strong> Your data sources (RDS\/AnalyticDB\/MaxCompute) should have encryption-at-rest enabled where applicable.<\/li>\n<li>For any caching\/extract features in Quick BI, <strong>verify encryption behavior<\/strong> in official docs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Avoid exposing databases publicly just for BI.<\/li>\n<li>If public endpoints are required:<\/li>\n<li>Use strict allowlists.<\/li>\n<li>Use dedicated read-only DB users.<\/li>\n<li>Consider read replicas for BI load.<\/li>\n<li>For private endpoints:<\/li>\n<li>Use supported private connectivity (gateway\/private access) where available\u2014<strong>verify<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do not share database passwords in documents or chat tools.<\/li>\n<li>Limit who can create\/modify data sources in Quick BI.<\/li>\n<li>Rotate credentials; prefer separate credentials per environment\/workspace.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Track:<\/li>\n<li>Who created data sources and who has admin privileges.<\/li>\n<li>Changes to certified datasets and executive dashboards.<\/li>\n<li>Use Alibaba Cloud audit tools (e.g., ActionTrail) if Quick BI integrates\u2014<strong>verify<\/strong>.<\/li>\n<li>Retain logs according to compliance requirements.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data residency can be a hard requirement. Confirm:<\/li>\n<li>Which region hosts your Quick BI tenant<\/li>\n<li>Whether dashboards\/cache store data<\/li>\n<li>Cross-border data transfer implications<\/li>\n<li>Apply data classification:<\/li>\n<li>Mask or exclude PII fields unless required<\/li>\n<li>Use aggregation and anonymization where possible<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Using a single shared \u201croot-like\u201d DB account for all dashboards.<\/li>\n<li>Over-broad network allowlists (0.0.0.0\/0) to make connectivity \u201ceasy.\u201d<\/li>\n<li>Letting every analyst create their own data source credentials.<\/li>\n<li>Exporting sensitive dashboards to files and sharing outside controlled channels.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use a dedicated <strong>BI read replica<\/strong> or warehouse for Quick BI.<\/li>\n<li>Implement <strong>least privilege<\/strong> and workspace isolation.<\/li>\n<li>Enforce a certified dataset process for sensitive KPIs.<\/li>\n<li>Add a periodic access review (quarterly) for viewers and authors.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<p>Because Quick BI is an editioned managed service, many limitations are <strong>configuration- and subscription-specific<\/strong>. Validate in your tenant.<\/p>\n\n\n\n<p>Common real-world gotchas:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Feature differences by edition\/region<\/strong>: Scheduling, embedding, advanced permissions, or caching may differ.<\/li>\n<li><strong>Networking complexity<\/strong>: Connecting to VPC-only databases may require a gateway\/private access method (support varies).<\/li>\n<li><strong>Performance is mostly your warehouse<\/strong>: Slow dashboards often reflect:<\/li>\n<li>Poor partitioning<\/li>\n<li>Unoptimized joins<\/li>\n<li>Overly granular visuals<\/li>\n<li><strong>Operational DB impact<\/strong>: Direct BI querying of RDS\/PolarDB can cause production performance degradation unless isolated (replica\/warehouse).<\/li>\n<li><strong>Metric inconsistency<\/strong>: Without a strong dataset governance process, teams create multiple \u201crevenue\u201d definitions.<\/li>\n<li><strong>Content sprawl<\/strong>: Dashboards proliferate without lifecycle management and naming standards.<\/li>\n<li><strong>Permissions mismatch<\/strong>: Users might have dashboard access but not dataset access (or vice versa). Document your sharing model.<\/li>\n<li><strong>Cross-region latency and cost<\/strong>: Avoid cross-region data connections where possible.<\/li>\n<li><strong>Exports as data exfiltration<\/strong>: Restrict export features for sensitive dashboards.<\/li>\n<li><strong>Quotas<\/strong>: Limits on number of datasets, refresh schedules, or concurrent queries may exist and can cause unexpected failures at scale\u2014verify in admin console\/docs.<\/li>\n<li><strong>Schema drift<\/strong>: Upstream column renames break dashboards; enforce schema contracts in your data marts.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>Quick BI is one option in a broader analytics and visualization landscape.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Within Alibaba Cloud<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>DataV<\/strong>: Often used for large-screen, presentation-style visualizations (operations centers). Quick BI is more BI\/reporting oriented.<\/li>\n<li><strong>DataWorks + Warehouse + Custom UI<\/strong>: For teams that need full control; higher engineering cost.<\/li>\n<li><strong>Third-party BI on Alibaba Cloud<\/strong>: Tableau\/Power BI\/Looker deployed with Alibaba Cloud infra.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Other clouds and self-managed options<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AWS: QuickSight<\/li>\n<li>Microsoft Azure: Power BI (service) and Fabric components<\/li>\n<li>Google Cloud: Looker \/ Looker Studio<\/li>\n<li>Open-source\/self-managed: Apache Superset, Metabase, Redash (community), Grafana (for time series), etc.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Comparison table<\/h4>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Alibaba Cloud Quick BI<\/strong><\/td>\n<td>Alibaba Cloud-centric BI dashboards and governed reporting<\/td>\n<td>Managed service, integrates with Alibaba Cloud data platforms, dataset governance and sharing<\/td>\n<td>Edition\/region feature differences; connectivity constraints may apply<\/td>\n<td>You want a managed BI service tightly aligned with Alibaba Cloud<\/td>\n<\/tr>\n<tr>\n<td><strong>Alibaba Cloud DataV<\/strong><\/td>\n<td>Large-screen \u201cdata wall\u201d visualization and real-time presentation<\/td>\n<td>Strong presentation visuals; good for NOC\/command center style<\/td>\n<td>Not primarily a governed BI semantic layer; can be less suited for ad-hoc BI<\/td>\n<td>You need presentation-style big-screen dashboards<\/td>\n<\/tr>\n<tr>\n<td><strong>Tableau (self-managed or cloud)<\/strong><\/td>\n<td>Advanced analytics orgs needing rich visual design<\/td>\n<td>Mature ecosystem, powerful visualization and modeling<\/td>\n<td>Higher cost, admin overhead, licensing complexity<\/td>\n<td>You already standardize on Tableau and can justify ops\/cost<\/td>\n<\/tr>\n<tr>\n<td><strong>Microsoft Power BI<\/strong><\/td>\n<td>Microsoft ecosystem organizations<\/td>\n<td>Tight integration with Microsoft stack, strong enterprise adoption<\/td>\n<td>Data residency and cross-cloud connectivity may be complex<\/td>\n<td>Your enterprise is Microsoft-first and already licensed<\/td>\n<\/tr>\n<tr>\n<td><strong>Amazon QuickSight<\/strong><\/td>\n<td>AWS-centric BI<\/td>\n<td>Serverless BI in AWS, good IAM integration<\/td>\n<td>Best fit when data is in AWS<\/td>\n<td>Your stack is primarily AWS<\/td>\n<\/tr>\n<tr>\n<td><strong>Looker (Google Cloud)<\/strong><\/td>\n<td>Semantic modeling + governed analytics<\/td>\n<td>Strong modeling layer (LookML) and governance<\/td>\n<td>Complexity and cost; best in GCP-centric stacks<\/td>\n<td>You want a code-based semantic layer and are GCP-aligned<\/td>\n<\/tr>\n<tr>\n<td><strong>Apache Superset (self-managed)<\/strong><\/td>\n<td>Cost-sensitive teams with engineering support<\/td>\n<td>Open-source, customizable, flexible<\/td>\n<td>You operate it (upgrades, scaling, security), governance varies<\/td>\n<td>You need open-source control and can run the platform<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: Retail group with centralized analytics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A retail enterprise has multiple regions and brands. Executives need consistent KPIs (net sales, returns, stock turns), while regional managers need filtered dashboards. Data resides in Alibaba Cloud analytics services.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>Data ingestion into OSS + DataWorks orchestration<\/li>\n<li>Curated warehouse in MaxCompute\/AnalyticDB (domain marts: Sales, Inventory, Finance)<\/li>\n<li>Quick BI workspaces per department + certified datasets<\/li>\n<li>Row-level restrictions for regional managers (or enforced via database views if Quick BI feature is not available)<\/li>\n<li><strong>Why Quick BI was chosen:<\/strong><\/li>\n<li>Managed BI aligned with Alibaba Cloud ecosystem<\/li>\n<li>Faster rollout to business users<\/li>\n<li>Strong permissioning model for broad sharing<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Standard KPI definitions across brands<\/li>\n<li>Reduced manual reporting effort<\/li>\n<li>Faster regional decision loops with consistent governance<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: SaaS product analytics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A SaaS startup needs product usage dashboards for founders and customer success, but cannot afford a heavy BI ops burden.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>Application data in RDS\/PolarDB<\/li>\n<li>Nightly ELT (DataWorks or lightweight jobs) into an analytic store (AnalyticDB\/Hologres if needed as scale grows)<\/li>\n<li>Quick BI dashboards for usage KPIs (active users, feature adoption, churn signals)<\/li>\n<li><strong>Why Quick BI was chosen:<\/strong><\/li>\n<li>Managed service reduces operational overhead<\/li>\n<li>Quick dashboards without building custom UI<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>A single portal for metrics<\/li>\n<li>Better customer success prioritization<\/li>\n<li>A clear path to scale by moving heavy analytics from RDS to an analytics warehouse<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Is Quick BI a data warehouse?<\/strong><br\/>\n   No. Quick BI is a BI\/visualization layer. Your data remains in your databases\/warehouses (and possibly cached\/extracted depending on features\u2014verify).<\/p>\n<\/li>\n<li>\n<p><strong>Do I need to write SQL to use Quick BI?<\/strong><br\/>\n   Not always. Many analyses can be built through datasets and drag-and-drop fields, but complex logic often benefits from SQL views or upstream modeling.<\/p>\n<\/li>\n<li>\n<p><strong>Which data sources does Quick BI support?<\/strong><br\/>\n   It supports a set of Alibaba Cloud services and common databases. The exact list varies by region\/edition\u2014verify in the official connector documentation.<\/p>\n<\/li>\n<li>\n<p><strong>Can Quick BI connect to VPC-only databases?<\/strong><br\/>\n   Sometimes, but it depends on supported connectivity methods (gateway\/private access). Verify the recommended network architecture in official docs.<\/p>\n<\/li>\n<li>\n<p><strong>How do I prevent dashboards from overloading production databases?<\/strong><br\/>\n   Use an analytical backend or read replica, build aggregates, and limit refresh frequency. Avoid running heavy joins against OLTP primaries.<\/p>\n<\/li>\n<li>\n<p><strong>Does Quick BI support row-level security (RLS)?<\/strong><br\/>\n   Some BI products do; Quick BI capabilities can vary by edition. If not available, enforce RLS using database views and per-user credentials or parameterized views\u2014verify supported patterns.<\/p>\n<\/li>\n<li>\n<p><strong>How do I manage multiple departments?<\/strong><br\/>\n   Use workspaces and role-based access. Maintain certified datasets per domain and central governance.<\/p>\n<\/li>\n<li>\n<p><strong>Can I embed Quick BI dashboards into an internal portal?<\/strong><br\/>\n   Embedding is often an enterprise feature in BI tools. Verify Quick BI embedding support, authentication model, and licensing implications.<\/p>\n<\/li>\n<li>\n<p><strong>What is the best backend for Quick BI at scale?<\/strong><br\/>\n   A warehouse optimized for analytical queries (MaxCompute\/AnalyticDB\/Hologres) is typically better than OLTP databases.<\/p>\n<\/li>\n<li>\n<p><strong>How do I handle schema changes without breaking dashboards?<\/strong><br\/>\n   Use stable views for BI, apply schema versioning, and coordinate changes through a data contract process.<\/p>\n<\/li>\n<li>\n<p><strong>Can Quick BI schedule report emails or exports?<\/strong><br\/>\n   Many BI services support scheduled distribution; availability and configuration depend on edition\u2014verify.<\/p>\n<\/li>\n<li>\n<p><strong>How do I audit who accessed a sensitive dashboard?<\/strong><br\/>\n   Use Quick BI access controls and audit tools provided by the service; complement with Alibaba Cloud governance (RAM\/ActionTrail) where applicable\u2014verify audit coverage.<\/p>\n<\/li>\n<li>\n<p><strong>Does Quick BI store my data?<\/strong><br\/>\n   Typically it queries connected sources and may store metadata and possibly cached extracts. Verify data storage\/caching behavior for your edition and region.<\/p>\n<\/li>\n<li>\n<p><strong>How do I estimate cost accurately?<\/strong><br\/>\n   Combine Quick BI licensing (edition + users) with underlying data source costs (warehouse compute, storage, ETL). Use official pricing pages\/calculators.<\/p>\n<\/li>\n<li>\n<p><strong>What\u2019s the best way to onboard new analysts?<\/strong><br\/>\n   Provide a training workspace, a set of certified datasets, naming conventions, and a \u201cdashboard checklist\u201d (filters, freshness timestamp, owner, and definitions).<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Quick BI<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official product page<\/td>\n<td>Alibaba Cloud Quick BI<\/td>\n<td>Product scope, entry points to docs and pricing: https:\/\/www.alibabacloud.com\/product\/quick-bi<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>Quick BI Documentation (Alibaba Cloud Help Center)<\/td>\n<td>Primary reference for connectors, modeling, dashboards, admin: https:\/\/www.alibabacloud.com\/help\/en\/quick-bi<\/td>\n<\/tr>\n<tr>\n<td>Official billing\/pricing<\/td>\n<td>Quick BI pricing\/billing references<\/td>\n<td>Confirms edition\/user pricing model (navigate from product page or billing docs): https:\/\/www.alibabacloud.com\/product\/quick-bi<\/td>\n<\/tr>\n<tr>\n<td>Getting started<\/td>\n<td>Quick BI Getting Started (in docs)<\/td>\n<td>Step-by-step onboarding guidance (find under Quick BI docs): https:\/\/www.alibabacloud.com\/help\/en\/quick-bi<\/td>\n<\/tr>\n<tr>\n<td>Architecture guidance<\/td>\n<td>Alibaba Cloud Architecture Center<\/td>\n<td>Patterns for data platforms that commonly feed BI: https:\/\/www.alibabacloud.com\/architecture<\/td>\n<\/tr>\n<tr>\n<td>Data integration (upstream)<\/td>\n<td>DataWorks Documentation<\/td>\n<td>Building curated BI marts and pipelines that power Quick BI: https:\/\/www.alibabacloud.com\/help\/en\/dataworks<\/td>\n<\/tr>\n<tr>\n<td>Analytics backends<\/td>\n<td>MaxCompute Documentation<\/td>\n<td>Common warehouse backend for BI: https:\/\/www.alibabacloud.com\/help\/en\/maxcompute<\/td>\n<\/tr>\n<tr>\n<td>Analytics backends<\/td>\n<td>AnalyticDB Documentation<\/td>\n<td>Low-latency analytical DB for dashboards: https:\/\/www.alibabacloud.com\/help\/en\/analyticdb<\/td>\n<\/tr>\n<tr>\n<td>Operational database<\/td>\n<td>ApsaraDB RDS for MySQL Documentation<\/td>\n<td>Practical for small labs and operational reporting (with care): https:\/\/www.alibabacloud.com\/help\/en\/rds<\/td>\n<\/tr>\n<tr>\n<td>Videos\/webinars<\/td>\n<td>Alibaba Cloud YouTube channel \/ webinars<\/td>\n<td>Product demos and best practices (availability varies): https:\/\/www.youtube.com\/@AlibabaCloud<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<p>The following training providers may offer Quick BI, Alibaba Cloud analytics, or broader DevOps\/data platform training. Verify course outlines on their sites.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>Engineers, DevOps, cloud teams, data platform practitioners<\/td>\n<td>Cloud + DevOps + platform fundamentals; may include analytics tooling overviews<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Students, beginners, working professionals<\/td>\n<td>DevOps\/SCM and related ecosystem skills; may include cloud tooling<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud operations and platform teams<\/td>\n<td>Cloud operations practices; may include monitoring and governance around analytics stacks<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs, reliability engineers, operations leads<\/td>\n<td>Reliability engineering practices applicable to analytics platforms<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>Ops + automation practitioners<\/td>\n<td>AIOps concepts and automation; potentially relevant for operating data\/BI ecosystems<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<p>These sites are presented as training resources\/platforms. Verify the specific Quick BI\/Alibaba Cloud coverage directly on each site.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>Cloud\/DevOps training content (verify exact topics)<\/td>\n<td>Beginners to intermediate practitioners<\/td>\n<td>https:\/\/www.rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps and cloud training (verify exact topics)<\/td>\n<td>Engineers and operations teams<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Consulting\/training-style resources (verify offerings)<\/td>\n<td>Teams seeking hands-on guidance<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>Support and training resources (verify scope)<\/td>\n<td>Ops\/DevOps teams needing assistance<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<p>These organizations may provide consulting services related to cloud, DevOps, and platform delivery. Verify service scope, references, and contracts directly with them.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting (verify specifics)<\/td>\n<td>Cloud architecture, migrations, operations<\/td>\n<td>Designing an Alibaba Cloud analytics stack feeding Quick BI; governance and IAM setup<\/td>\n<td>https:\/\/www.cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>Training + consulting (verify specifics)<\/td>\n<td>Platform enablement, DevOps and cloud adoption<\/td>\n<td>Standing up data platform best practices; operational readiness for BI<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting (verify specifics)<\/td>\n<td>CI\/CD, infrastructure automation, operational maturity<\/td>\n<td>Infrastructure and governance patterns that support analytics workloads and BI<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before Quick BI<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>SQL fundamentals<\/strong>: SELECT\/JOIN\/GROUP BY\/window functions.<\/li>\n<li><strong>Data modeling<\/strong>: star schema basics, facts\/dimensions, slowly changing dimensions.<\/li>\n<li><strong>Alibaba Cloud foundations<\/strong>:<\/li>\n<li>RAM (users, roles, policies)<\/li>\n<li>VPC basics (subnets, security groups, endpoints)<\/li>\n<li>OSS basics (if your data lake uses it)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Quick BI<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Data platform engineering<\/strong>:<\/li>\n<li>DataWorks for ETL\/ELT orchestration<\/li>\n<li>MaxCompute\/AnalyticDB\/Hologres performance tuning<\/li>\n<li><strong>Governance<\/strong>:<\/li>\n<li>Metadata management, lineage, data quality checks<\/li>\n<li><strong>FinOps for analytics<\/strong>:<\/li>\n<li>Cost optimization for warehouses and refresh patterns<\/li>\n<li><strong>Security<\/strong>:<\/li>\n<li>Data classification, masking, least-privilege patterns for BI<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>BI Analyst \/ Data Analyst<\/li>\n<li>Analytics Engineer<\/li>\n<li>Data Engineer (curated marts and performance)<\/li>\n<li>Cloud\/Data Platform Engineer<\/li>\n<li>Solution Architect (analytics)<\/li>\n<li>Business Operations \/ Finance Analytics<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Alibaba Cloud certification availability changes over time and differs by region. Check Alibaba Cloud certification pages and learning paths. If Quick BI-specific certification is not listed, focus on:\n&#8211; Alibaba Cloud data analytics certifications (where applicable)\n&#8211; Data engineering and cloud architecture tracks<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Build a governed \u201cSales Mart\u201d in a warehouse and publish executive dashboards in Quick BI.<\/li>\n<li>Create department workspaces with role-based access and a certified dataset process.<\/li>\n<li>Implement a \u201cdata freshness\u201d KPI and operational dashboard for pipeline SLAs.<\/li>\n<li>Build an operational reporting pattern using RDS read replica + aggregate tables to protect OLTP.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>BI (Business Intelligence):<\/strong> Tools and practices for turning data into reports\/dashboards and insights.<\/li>\n<li><strong>Dataset (Semantic Model):<\/strong> Curated representation of data with defined fields, metrics, joins, and calculations.<\/li>\n<li><strong>Dimension:<\/strong> Categorical field used to group\/slice data (e.g., region, category).<\/li>\n<li><strong>Measure\/Metric:<\/strong> Numeric value aggregated for analysis (e.g., revenue, count).<\/li>\n<li><strong>KPI:<\/strong> Key performance indicator used to track business objectives.<\/li>\n<li><strong>OLTP:<\/strong> Online transaction processing (operational databases optimized for writes and point reads).<\/li>\n<li><strong>OLAP:<\/strong> Online analytical processing (systems optimized for aggregations and scans).<\/li>\n<li><strong>Row-level security (RLS):<\/strong> Restricting which rows a user can see based on identity\/attributes.<\/li>\n<li><strong>Workspace\/Tenant:<\/strong> Organizational boundary for BI assets, users, and permissions.<\/li>\n<li><strong>Data mart:<\/strong> Subject-oriented, curated dataset optimized for reporting (e.g., sales mart).<\/li>\n<li><strong>Partitioning:<\/strong> Splitting tables (often by date) so queries scan less data.<\/li>\n<li><strong>Allowlist\/Whitelist:<\/strong> Network rule allowing only approved IPs\/services to connect.<\/li>\n<li><strong>Data freshness:<\/strong> How up-to-date a dataset is relative to its source.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Quick BI is Alibaba Cloud\u2019s managed BI service in the <strong>Analytics Computing<\/strong> category. It helps teams connect to data sources, curate datasets, and publish interactive dashboards with governed access.<\/p>\n\n\n\n<p>It matters because it reduces the time and operational burden of delivering trustworthy analytics to stakeholders\u2014while providing permissioning and sharing controls that spreadsheets and ad-hoc scripts cannot.<\/p>\n\n\n\n<p>Architecturally, Quick BI fits best on top of a curated analytics backend (MaxCompute\/AnalyticDB\/Hologres) and a governed ETL layer (often DataWorks). Cost is typically driven by <strong>edition\/user licensing<\/strong> plus the often-larger cost of your underlying data warehouse compute. Security requires careful attention to <strong>least privilege<\/strong>, safe connectivity (avoid overly public databases), and controlled exports\/sharing.<\/p>\n\n\n\n<p>Use Quick BI when you want a managed Alibaba Cloud-aligned BI platform for dashboards and reporting. Next, deepen your skills by building a production-ready analytics mart (with partitions, aggregates, and clear metric definitions) and then standardize certified datasets for organization-wide consumption.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Analytics Computing<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,4],"tags":[],"class_list":["post-86","post","type-post","status-publish","format-standard","hentry","category-alibaba-cloud","category-analytics-computing"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/86","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=86"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/86\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=86"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=86"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=86"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}