Table Usage Analytics

I think table and custom table usage should be added to the scope of usage analytics.
I have large data sources that have been around for many years. Often dashboards are unused (which I can currently track with usage analytics) and can be deleted or archived. But the data that drives them is much harder to keep track of. I have no way of knowing which tables are used in dashboards and which ones could be removed. This is especially true for custom tables that eat up build time and might not be used at all.

sspringstead

Posted 1 year ago·Last reply 1 year ago

2 comments

Ido Darnell

·1 year ago · Edited

Hey sspringstead

You’ve brought up a really important challenge, understanding which tables (especially custom ones) are actually in use across your Sisense instance is critical for keeping things lean, performant, and maintainable. This becomes even more urgent as data models grow and evolve over time.

We ran into this exact issue with several customers, which is why we built an internal tool that’s now available as a plugin: Asset Auditor.

Before I get into the details of what we have available, I will say that you can achieve this with some custom code and scripts, but this will need to be developed and then maintained. If you're interested in achieving this please see below

While your request focuses on table usage, Asset Auditor actually covers that and much more:

Table and Column Utilization – Easily see which tables and columns are actively used in widgets and dashboards, and which ones are not.
Unused Data Models – Identify full ElastiCubes or data models that haven’t been queried in weeks/months.
Custom Table Tracking – Get visibility into which custom SQL tables are in use and which are just slowing down your builds.
Widget and Dashboard Errors – Surface broken or deprecated content before it impacts users.
Plugin and Feature Usage – Understand which plugins or features are widely adopted and which are going unused.

We’ve heard from admins that one of the biggest pain points is not having centralized visibility into what’s used and what’s just sitting idle, especially when preparing for server upgrades, debugging slow builds, or doing content cleanup.

We're actually hosting a webinar on September 16th where we'll be showing Asset Auditor live and discussing how it helps BI teams reclaim control over their Sisense environments.

Learn more about our webinar here

Happy to share more details or answer questions here in the thread!

We're always here to help

Ido from QBeeQ

QBeeQ - Gold Sisense Partner

info@qbeeq.io

Feel free to subscribe to our newsletter to stay up to date with the latest QBeeQ news

DRay

·1 year ago

Hello sspringstead,

Thank you for submitting your idea!

I have brought this Idea to the product team and will post updates here as they are available.

One of the ways we prioritize development efforts is by community interest. I encourage other users to vote and comment on this suggestion. The more engagement an idea receives the higher the likelihood of it being considered for implementation.

Thank you for being a valuable part of our community!