Before a rebuild
Before grown or orphaned databases and applications are rebuilt, it must be clear which procedures, views, jobs, SSIS packages and C# application accesses are affected.
When nobody knows exactly any more which program depends on which data, every change becomes a risk. In two days on site I make this visible, and your team gets an overview with a source location for every connection.
Databases, stored procedures, SSIS packages, agent jobs and applications that grew over decades can turn into a “black box”. When that happens, or when key people retire, guesswork is not enough. With my locally running software toolset COMPIDDA I make all technical dependencies of your system landscape visible deterministically – down to the exact line of code.
Before grown or orphaned databases and applications are rebuilt, it must be clear which procedures, views, jobs, SSIS packages and C# application accesses are affected.
Nobody dares to touch the grown procedures and systems any more? The assessment reads all dependencies automatically and documents them on site – the basis for disentangling step by step.
Protection against knowledge loss when key staff retire or leave (“island knowledge”); new requirements become plannable again.
R, write W, execute X), joint review of the critical nodes, briefing of your team and handover of the interactive documentation.
COMPIDDA reads database objects and source code and documents the dependencies as a diagram with exact source locations.
The analysis runs entirely on your premises and works deterministically, without AI hallucinations. Anything that cannot be resolved unambiguously stays visibly marked; the business assessment remains with the people responsible on your side.
How COMPIDDA reads T-SQL, SSIS packages, SQL jobs, SSRS reports and C#/.NET data access is described in detail under database optimisation. Technical details on COMPIDDA →
In practice: how I was responsible for a 24/7 platform as technical app owner is shown in the NXP Semiconductors case study.
Briefly describe which systems are affected. In the initial call (20 minutes) we clarify whether the assessment is worthwhile.
Should your team ship releases itself? DevOps coaching · Is the database slowing you down? Database optimisation