MariaDB logo

Kyubit Business Intelligence · MariaDB

MariaDB reporting & self-service BI

Turn operational MariaDB records into a repeatable reporting workspace for your team.

Connect natively to MariaDB, prepare a visual semantic model, and share browser-based reports and dashboards. Give users reusable measures and dimensions for questions that go beyond a single saved report.

Download Kyubit & start your trialExplore the workflow
Kyubit analytic grid showing a semantic model with multiple measures and dimensions
Kyubit interface example using sample data.

Replace a recurring export with a reusable analysis

Start with a report someone prepares repeatedly from MariaDB: weekly sales by location, service activity by category, or purchasing by supplier. Instead of rebuilding the same breakdown in a spreadsheet, make its source data and business definitions available in a Kyubit model.

  1. Select a questionChoose one report with a known owner and verified totals.
  2. Structure the dataIdentify the transaction grain, measures and grouping fields.
  3. Publish the modelProcess the data and give the intended users access.
  4. Reuse the resultSave reports, build dashboards and schedule regular delivery.

The model becomes the reusable foundation. Colleagues can change a date range or explore another grouping without requiring a separate export for each request.

Design the model around the way MariaDB records change

Kyubit model designer with fact and dimension tables arranged on a canvas
Kyubit interface example using sample data.

Use the diagram designer to choose a fact table, connect related tables and map columns to business fields. A service-activity model, for example, might link event counts or recorded amounts to service categories, locations and dates.

  • Define the meaning of each fact row before joining related tables.
  • Give dimensions names that report readers recognize.
  • Create hierarchies for useful drill paths, such as region and location.
  • Use details for identifiers that do not need their own aggregate breakdown.

For changing statuses, decide whether the report should show the latest state or a history of states. The source data must contain the history if you want to analyze how it changed over time.

Follow the visual model designer guide to create and validate the first model.

Use native MariaDB connectivity and validate your actual schema

Configure a MariaDB data source with the host, database and account appropriate to the reporting workload. Inspect the selected records and verify relationships before importing a larger history.

Check source objects and column mappings

Validate the tables, reporting views or prepared query results used by your chosen workflow. Check date, amount and category values with realistic records, especially when data originated in an application migration.

Treat MariaDB as its own source

Kyubit provides native MariaDB connectivity alongside MySQL connectivity. Test your MariaDB server and schema directly; do not assume a MySQL-oriented script or report definition validates every MariaDB-specific behavior.

Working with both engines? The MySQL BI page covers application and order-reporting examples, while the SQL-to-BI overview explains the shared analytical workflow.

Keep recurring reports aligned with new and corrected records

MariaDB operational data can include both new activity and changes to earlier records. Choose the processing schedule according to those two patterns.

  • Incremental: use the configured workflow to bring in new appended records.
  • Partial: refresh an appropriate recent period when existing records can change.
  • Full: rebuild when the model or reporting history requires a complete refresh.

Agree how corrections outside the usual refresh window will be handled. If an old transaction changes, a schedule that only appends new rows will not necessarily include that correction.

Kyubit full, partial and incremental processing options
Kyubit interface example using sample data.

Test with both a new record and a corrected earlier record so the refresh behavior matches the report owner's expectations.

Make daily results visible, with detail close at hand

Build an operational dashboard from the prepared model using trends, charts and KPI cards. Add slicers for locations or service categories, then use the analysis grid to investigate a result in more detail.

Kyubit performance dashboard with slicers, KPIs, a trend and a flow chart
Kyubit interface example using sample data.

Save a focused report for readers who only need the results. For regular updates, use scheduled reporting after the relevant model processing has completed.

Host the reporting application in your own environment

Application requirements

Kyubit runs on Windows/IIS and uses Microsoft SQL Server for internal databases. MariaDB remains the reporting source and can stay on a separate host reachable by the Kyubit server.

Access for creators and readers

Configure Kyubit users and permissions for models and saved content. The database connection account controls source access; model and report permissions control what users can open within the application.

Processing places selected source data in Kyubit's analytical environment. Include that environment in your backup and access plan. Review permanent licensing or subscription licensing for the edition that fits your deployment.

Frequently asked questions about MariaDB BI

Does Kyubit have native MariaDB support?

Yes. MariaDB is a natively supported relational source. Configure the MariaDB connection and test the source objects and columns required by your model.

Can a recurring MariaDB export become a shared report?

Yes. Model the relevant records, define measures and dimensions, and save analyses or dashboards for authorized users. The model can also support additional breakdowns beyond the original report.

Will incremental processing pick up every status correction?

Not necessarily. Incremental appending and updates to existing records are different requirements. Configure an appropriate partial or full refresh for changed data and validate that behavior.

Can users explore MariaDB data without SQL?

Yes. Users can analyze a prepared model through measures, dimensions, hierarchy drill-down and slicers. The initial model should be designed and checked by someone familiar with the source.

Can I host everything on a Linux MariaDB server?

Kyubit requires a Windows/IIS application environment and Microsoft SQL Server for internal databases. Your MariaDB source can remain on Linux, but MariaDB alone does not replace those application requirements.

Try Kyubit with your MariaDB data

Choose a recurring MariaDB report, reproduce its known totals in Kyubit, and test how colleagues can explore the same model.

Download Kyubit & start your trial