About
A consultancy for the ETL engine that quietly runs the nightly close.
Packvane is a consultancy for SQL Server Integration Services. That is the whole of what we do.
Why a firm for one ETL engine
Most mid-market companies have an SSIS estate, and very few have an SSIS engineer. The packages were written by people who have moved on, they run the nightly finance, operations and compliance loads, and the current team — one to three BI developers or DBAs — keeps them alive without ever having chosen them.
The market that serves those teams is mostly talent marketplaces selling an individual by the hour, and platform consultancies selling a rewrite before anyone has read the packages. Neither answers the question the team actually has, which is: what is in here, what has to move, and what can be left alone.
Answering that well requires knowing this particular engine in detail — package configurations, protection levels, the SSISDB catalog, SQL Agent step chains, the components that assessment tooling flags and does not fix. It is not glamorous knowledge and it is not transferable. It is worth having a firm for.
What we are honest about
SSIS is mature, not growing. It still ships inside SQL Server, Microsoft has not announced an end date for it, and it will run the nightly batch at a great many companies for years yet. New platform investment is going elsewhere, and the path for existing packages onto the newer platforms is less settled than the Azure route.
We maintain and modernise what runs. We do not claim SSIS is the future, and we do not recommend a rewrite in order to sell hours.
The urgency in this market comes from the server, not the ETL: SQL Server 2016 left extended support on 14 July 2026, and Extended Security Updates are the paid alternative to moving. Every one of those instances carries an SSIS estate and a set of SQL Agent jobs with it. That is a real deadline, and it is a different question from whether your packages should be rebuilt.
Who does the work
Senior US-based data engineers, working in your repository, your SSISDB and your SQL Agent. Engagements run as projects or as staff augmentation alongside your existing team, billed hourly.
We publish what we know at Tutorials — component mappings, catalog migrations, reconciliation harnesses — including the parts that would let you do the work without us.
Getting in touch
Tell us what you are running: roughly how many packages, which SQL Server version, and what is prompting the conversation. A senior engineer replies within one business day.