Using the new catalog.stop_operation stored procedure, you can programmatically stop a runaway SSIS6 package based on row count metrics, preventing memory overload.
Searching for SSIS6 is understandable – we all want the next major leap in ETL tooling. However, the smartest strategy is to recognize that Microsoft has shifted from versioned, on-premise software to continuous, cloud-native services.
The functional equivalent of SSIS6 is already here, distributed across: Using the new catalog
Rather than waiting for a box labeled "SSIS6", modern data professionals should build a future-proof ETL strategy that embraces hybrid execution, real-time streams, and open-source scripting. SSIS as we know it will continue to work – but the spirit of SSIS6 lives today in the cloud.
Are you ready for the next generation of data integration? Start your migration to Azure Data Factory and never look back. Rather than waiting for a box labeled "SSIS6",
Have thoughts on what SSIS6 should include? Share your feature wishlist in the comments below.
Microsoft Power Query (M) and Dataflows in ADF are popular for data wrangling. SSIS6 would embed Power Query Online as a native source transformation – no more custom OData or REST calls. Users could prep data visually, then export the M-code into a SSIS package. Have thoughts on what SSIS6 should include
Start by lifting and shifting at least one project to the cloud. This makes your ETL cloud-ready without rewriting. Use the SSIS Integration Runtime in ADF to gain elasticity and hybrid connectivity.