Can RaptorDB Pro (Live Connect) become the primary read-only data access layer for ServiceNow?

[PRanjan]

Hi Community,

I have a few architecture questions regarding RaptorDB Pro (Live Connect) and would appreciate guidance from anyone who has implemented it in production.

Our current architecture looks like this:

• ServiceNow data is extracted daily into a SQL database using OLEDB.
• SQL transformations and aggregations are performed in the database.
• Curated datasets are built from the transformed data.
• Power BI reports connect to those datasets.

Separately, our ServiceNow Platform team receives a growing number of requests from internal teams for read-only access to ServiceNow data (Incidents, Tasks, KB Articles, Work Notes, Attachments, etc.) for analytics, automation, AI, and other integration scenarios.

This raises a few questions:

1. Can Live Connect realistically replace the daily reporting extract and intermediate SQL database, or is it intended to complement an existing reporting architecture?
2. If SQL transformations and aggregations are currently performed in the reporting database, what is the recommended approach after moving to Live Connect?
   • Push transformations into Live Connect SQL?
   • Perform them in Power Query?
   • Use the Power BI semantic model?
   • Another recommended pattern?
3. Would ServiceNow recommend Live Connect as the preferred access mechanism for enterprise read-only consumers, instead of provisioning multiple REST API integrations, where no create/update/delete operations are required?
4. How does Live Connect scale in environments with many Power BI datasets and scheduled refreshes? Has anyone encountered the documented SQL API limits in production?
5. Are tables such as Incident, Task, Change, Knowledge Articles, Work Notes, and Attachment metadata fully accessible through Live Connect, or are there scenarios where the REST Table API remains the recommended approach?
6. For customers who have implemented RaptorDB Pro, what were the biggest architectural lessons learned? If you were implementing it again, would you make the same design decisions?

Our objective is to understand where Live Connect best fits within an enterprise ServiceNow architecture and whether it should be viewed primarily as a reporting capability or as a broader governed read-only data access layer.

Any real-world experiences or recommendations would be greatly appreciated.

Thank you! 
@RobJenkins