# Schedule Azure SSIS Integration Runtimes: Stop Idle ETL Infrastructure > ZopNight schedules SSIS Integration Runtimes on Azure to run on your team's hours and stop the rest of the time. Read-only setup, dependency-aware, production excluded by default. Source: https://zop.dev/zopnight/azure/ssis-integration-runtimes Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, azure, analytics, scheduling --- Most of what teams spend on SSIS Integration Runtimes in non-production is spent while nobody is watching. In a development, staging, or QA account these resources are billed for every hour they exist, but the people who use them work a fraction of those hours. Nights, weekends, holidays, and the long tail of "we'll get back to that environment next sprint" all meter at full price. ZopNight closes that gap by scheduling your SSIS Integration Runtimes to run on your team's hours and stop the rest of the time, without touching your data and without a migration. It is the most direct lever in [FinOps](https://zop.dev/learn/finops), and for teams comparing tools it is where ZopNight pulls ahead of dashboard-first platforms like [CloudHealth](https://zop.dev/compare/cloudhealth-vs-zopnight). ## Why SSIS Integration Runtimes cost more than they should Cloud providers bill SSIS Integration Runtimes by the hour whether or not anyone is using them, and most non-production fleets default to running 24/7 out of habit rather than need. At typical on-demand rates ($0.30–$5.00/hr) an always-on instance quietly bills the same on a Tuesday afternoon as it does at 3 AM on a Sunday. Here is the shape of it. Say a box runs at a typical on-demand rate of $0.17 an hour. Left on around the clock that is about $124 a month, because a month is roughly 730 hours. Confine it to a single-shift work week, about 50 hours, and you pay for 50 hours instead of 730. Your own rate and hours will differ, but the ratio is the point: in non-production, most of the meter runs while nobody is working. The instinct is usually to reach for a smaller instance type. But rightsizing only helps a resource that is genuinely too big; it does nothing for a correctly-sized resource that simply runs when no one is around. The larger, easier win is refusing to pay for the hours nobody is working, and it carries none of the performance risk of down-sizing a box that might spike tomorrow. ## Stopping and starting SSIS Integration Runtimes safely ZopNight handles the Stop/Start via Azure Data Factory API on every SSIS Integration Runtimes in scope, in dependency order so nothing comes up before what it depends on. A scheduled stop preserves your data exactly as a normal power-off would; ZopNight never terminates or deletes the resource, and idle detection watches CPU, network, and disk signals to surface the SSIS Integration Runtimes that are running but doing nothing. In practice the setup is: Connect your Azure subscription. ZopNight discovers all Data Factory SSIS Integration Runtimes; Define schedules to stop IRs outside business hours or ETL windows; ZopNight stops the IR via Data Factory API. SSIS catalog and packages preserved; Before business hours or ETL windows, ZopNight starts the IR and verifies readiness. If you run SSIS Integration Runtimes you probably also run [SQL Database](https://zop.dev/zopnight/azure/sql-database), [SQL VMS](https://zop.dev/zopnight/azure/sql-vms), [Synapse SQL Pools](https://zop.dev/zopnight/azure/synapse-sql-pools), and scheduling them together is where the dependency ordering earns its keep. Related reading: [scheduling](https://zop.dev/solutions/scheduling) and [cost optimization](https://zop.dev/solutions/cost-optimization). ## How ZopNight schedules SSIS Integration Runtimes The loop that does this is deliberately mechanical, and it starts read-only. You connect Azure with a read-only role, and ZopNight discovers every SSIS Integration Runtimes across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled. Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like "dev-cluster" or "staging-db" so a whole environment follows one cadence. Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a SSIS Integration Runtimes ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it. ## Getting started Getting started is intentionally low-stakes: - Connect Azure with a read-only role. Nothing is scheduled or changed at this stage. - Let ZopNight discover your SSIS Integration Runtimes and review exactly what it found, filtered by account, region, and status. - Create a schedule in your timezone and attach the non-production resources or groups you want it to cover. - Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing. Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action. ## Frequently asked questions ### Does stopping an SSIS IR affect my SSIS packages? No. SSIS packages are stored in the SSISDB catalog database, not on the IR nodes. Stopping the IR deallocates compute resources. Packages are available immediately when the IR restarts. ### How long does it take to start an SSIS Integration Runtime? SSIS IR startup typically takes 20-30 minutes due to node provisioning and SSIS component installation. ZopNight accounts for this longer startup time when scheduling. ### Can I reduce the SSIS IR node count instead of stopping? Yes. ZopNight can scale the node count down during off-peak periods and back up before ETL windows. This is useful when some packages need to run overnight but at reduced parallelism. ### What about Azure-hosted IR vs SSIS IR? ZopNight focuses on SSIS Integration Runtimes which have dedicated compute. Azure-hosted IRs for Data Flow and Copy activities auto-scale and are billed per execution, so scheduling is less impactful. ### How does ZopNight coordinate with Data Factory pipeline schedules? ZopNight can read your Data Factory pipeline trigger schedules and ensure the SSIS IR is running before any triggered pipeline needs it. Override windows can be set for ad-hoc pipeline runs.