Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
Good afternoon,
A week ago we noticed a issue when creating a new dataflow or adding items to an existing dataflow. Our Production and Test databases have very large schemas so we have two separate connection strings, one using just the DBO schema and another with access to ALL schemas based on the configured generic user account used in the connection. We have two On-premise data gateways (one for PROD and one for TEST) that have two servers dedicated to each instance.
Prior to this issue it would take 2-3 minutes to load our DBO schema that has approximately 40,000 objects and 5-10 minutes to load all items which is nearly 80,000 objects. After this issue started, the connections will often stop trying to load after 10 minutes and can run for 45 minutes plus without completing successfully.
We've tested this across multiple MS SQL databases on two separate hosting servers and seen the same issue. Some of our smaller database schemas will load , but now take 2-3 minutes (for 1000 objects) or 3-6 minutes (4000 objects) to complete.
This is the screen we see for reference:
Has anyone seen anything like this before, or have any suggestions on items we could check?
Can you point out a particular date when that started?
The first time we saw this behavior was the morning of 9/11/2024.
it was still fine on 9/10? That would rule out the 9/7 service version change.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 43 | |
| 41 | |
| 26 | |
| 25 | |
| 22 |