When data is updated in a Fabric Data Warehouse or Lakehouse, it's not always up to date immediately when querying the SQL Endpoint.
The same thing happens in a Fabric SQL Database but this is even more noticeable - on the SQL Database object, the data is always up to date, but on the SQL Endpoint object of the same database, the data can lag.
It is possible to refresh this as part of a pipeline by including the refresh SQL endpoint activity, but in my view the data should always be up to date through the endpoint as this can lead to discrepancies.
No CommentsBe the first to comment
Recent ideas
SQL Analytics Endpoint host name - CNAME or defined alias
The host name for a SQL Analytics endpoint is ugly. They look like this: random_ugly_alphanumeric-random_ugly_alphanumeric.datawarehouse.fabric.microsoft.com The first segment looks like it...Mike_Diehl2 hours agoNew MemberNew27Views2likes1CommentFix links generated in multi tenant setups
When I log into Fabric, and I have access to multiple tenants, the links generated for things like monitoring URLs in pipeline runs do not include "ctid=<tenantguid>" query string value, which appear...jwisemanfs4 hours agoNew MemberNew3Views0likes0Comments