Troubleshoot Excel Macro Delays When Connecting to an OLAP Cube
Question details
The user needs to identify why an Excel macro report runs significantly slower against KYVOS than against SSAS and to locate the delay stage in the request flow.

- Product
- Microsoft Excel with VBA macro and OLAP cube connections to KYVOS and SSAS
- Device & OS
- not provided
- Scenario
- A macro report connects to an OLAP cube and completes faster against SSAS but slower against KYVOS, with similar response size and request count.
- Observed behavior
- The Excel-to-KYVOS request flow contains unexplained gaps that are not explained by response size or request count.
Before profiling, confirm that the same Excel workbook, macro settings, and connection string can run against both KYVOS and SSAS. Enable macro execution and external data refresh permissions in Excel.
Profile each Excel-to-KYVOS request stage and compare it with SSAS
Use this first to locate the exact stage where the macro delay occurs, including request creation, server execution, and response processing.
Response size and request count often look similar even when one tier adds latency. Timestamping each stage makes the unexplained gaps visible and gives KYVOS support actionable data.
Open the Excel workbook, click File > Options > Trust Center > Trust Center Settings > Macro Settings, enable VBA macros, and add timestamp logging to the VBA routine before and after each connection and refresh call.
Add Debug.Print or worksheet log entries with Now() at request creation, after connection open, after OLAP query or refresh, and after workbook processing, then run the same macro against KYVOS and SSAS.
Subtract each stage's timestamps for KYVOS and SSAS to identify whether the delay is in network transfer, server execution, authentication, or client-side processing.

Investigate network, authentication, connection pooling, and KYVOS configuration
Use this when the delay is outside the macro code and relates to infrastructure or service configuration.
Run controlled benchmarks and send profiling results to KYVOS support
Use this when you need evidence to escalate the issue or confirm which component causes the delay.
Use WPS Office as a Free, Lightweight Excel Alternative for Daily Spreadsheet Work
WPS Office does not resolve KYVOS OLAP server or Excel VBA macro environment issues, but it offers a free, lightweight Office alternative with strong Excel file compatibility, familiar ribbon-style UI, and easy migration for everyday spreadsheet and report work.
- 1. Download and install WPS Office: Go to the official WPS Office download page, download the free installer, and complete installation on your Windows or macOS computer.
- 2. Open the Excel workbook in WPS Spreadsheets: Launch WPS Spreadsheets, click File > Open, select the workbook, and use the familiar ribbon tools to review or edit report layouts.
- 3. Keep Excel for OLAP and VBA tasks while using WPS for daily spreadsheet work: Continue using Microsoft Excel for KYVOS/SSAS OLAP cube queries and VBA macros, and use WPS Office for lightweight editing and sharing of the resulting Excel files.

Frequently Asked Questions
Why is my Excel macro slower against KYVOS than SSAS when response size is similar?
Similar response size does not rule out network latency, authentication delays, connection pooling, or longer query execution plans. Add timestamps around request creation, server execution, response delivery, and workbook processing to compare stage-by-stage.
What should I log in the Excel macro to troubleshoot OLAP cube delays?
Log the time before and after connection open, OLAP refresh or query execution, response retrieval, and workbook processing. Use VBA Now() or a worksheet log and run the same routine against KYVOS and SSAS.
Does WPS Office support Excel OLAP cube connections and VBA macros?
WPS Office can open many Excel files and provides familiar spreadsheet features, but KYVOS/SSAS OLAP cube diagnostics and full VBA macro automation are best handled in Microsoft Excel. Use WPS Office for lightweight editing and daily spreadsheet work.
When should I contact KYVOS support?
Contact KYVOS support after you have timestamped stage logs, network latency tests, query profiling results, and a controlled SSAS baseline. These help isolate whether the delay is in Excel, the network, or KYVOS server execution.




