Dataverse virtual tables on SQL: three latency patterns

SapotaCorp
Virtual tables let Dataverse surface data that lives in another system - SQL Server, Cosmos DB, a REST API - without copying it into Dataverse. The user-facing experience is the same as any table: views, forms, lookups, relationships. The underlying retrieval goes out over the wire to the external source on every read. On paper, the appeal is obvious: no sync, no duplication, always current. In practice, the latency characteristics are what decide whether virtual tables fit the use case. Here ar