Seeking Best Practice for Live Detail Reporting in Sisense (Replacing SSRS)

Afternoon Sisense community,

Our team is looking to replicate the functionality of a crucial SSRS report within Sisense. This report is used by a department to obtain a detailed list of jobs for a specific month. The workflow involves:

1. Running the report for a selected month (typically the current or previous month).
2. Reviewing the output for discrepancies.
3. Updating the source system based on the review.
4. Re-running the report immediately to verify the changes (requiring live data).

Current Sisense Implementation & Performance Issue

I've attempted to recreate this report's dataset using a Live Model connected to a Redshift SQL View. The view is complex:

• It contains approximately 50 columns of detailed data.
• It involves JOINs across 15 different tables to consolidate all necessary dimensions and metrics.

The Issue: The performance of this Live Model is unacceptable. Users are accustomed to the SSRS report running a stored procedure and returning the filtered data in under 30 seconds. My Sisense Live Model is timing out.

Constraints & Goal

• Requirement: The data must be live (no ElastiCube, as users need immediate reflection of system changes after updates).
• Target Performance: Sub-30-second return for monthly filtered data.

Request for Guidance

Given the high number of columns, multiple joins, and the strict requirement for live data with fast filtering (specifically by month), what would be the recommended best practice for implementing this detailed report in Sisense?

Are there specific Sisense configurations, data modeling techniques for live connections that would address this performance bottleneck while meeting the "live" requirement?

Thank you for your insights!