Forum Discussion
Integration Runtime Busy Error When Deploying DACPAC to Warehouse
Hi Mahimaa29,
Can you post a screenshot of your copy job?
When it is running, can you monitor the system resources (CPU, memory) of your gateway machine and see what is going on there?
YOu might need to get a more powerful gateway server.If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Super UserHi Mahimaa29,
You’re hitting a very “plumbing-layer” issue, not a row-count limit. A DACPAC is meant to deploy schema (and optional seed scripts) to a Warehouse. The “Integration Runtime busy” message points to runtime saturation or gateway/concurrency limits during your pipeline/connection step-not to 100k rows being “too big.”
- Use DACPAC for schema only. Deploy the objects to your Warehouse via SQL Projects/SqlPackage, not the data. See Microsoft’s guidance for Warehouse/SQL projects and SqlPackage usage: SQL database projects + SqlPackage in Fabric.
- Load the data with COPY INTO (recommended) or a Pipeline Copy activity. For larger loads, stage files and use COPY INTO for high-throughput ingestion: COPY INTO best practices.
- Address the “runtime busy” angle:
- If you use Pipelines/gateways, check capacity/throughput and reduce bursts (parallel Lookups/Copies), and add retries. Monitor with the Fabric Capacity Metrics app: Metrics app overview.
- If you’re using a self-hosted IR/VNET Gateway, verify machine resources, version, and concurrency; scale up/out if needed: Self-hosted IR troubleshooting.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.