Alternatives to Exporting Large CMDB Dataset from Query Builder (Excel 500,000 Row Limitation)

[Meagan]

Issue Overview

We’ve built a Query Builder model to extract CI Relationship along with the Business Application. The application owner is defined on the Business Application table, we require a full extract of all related CIs for analysis along with the Owners in order to know who to speak to with regards to discrepancies on the CIs.

The query runs successfully and returns all expected records; however, the export process not working as we are only able to extract parts of the data and load it into our external reporting tool.

Symptoms

• The file contains only a partial dataset.

We are aware that Excel has a practical limitation around ~500,000 rows for manageable exports (even though the absolute limit is higher), which seems to be creating problems when the dataset approaches or exceeds this size.

What We Need Help With

1. Is there a known row-limit or performance limitation when exporting Query Builder results?
2. Does Query Builder have its own export cap separate from Excel and CSV limits?
3. Are there recommended alternative methods to extract CMDB datasets that exceed 500k rows, such as:
• Table API / Scripted REST APIs
• Exporting through Scheduled Jobs
• Data Extraction or IntegrationHub ETL
• Transform Map or data source dumps

Context

The export is required to identify the application owner of the associated Business Application record, and provide them the complete dataset for review.

Request

If anyone has:

• Worked around large Query Builder export limits,
• Used alternative extraction patterns for very large CMDB datasets,
• Or has best practices for mass CI data export,

your insights would be greatly appreciated.

Thanks in advance!