SQL Server
Databases, schemas, tables, views, stored procedures, functions, object definitions when included, linked-server candidates, and unresolved dependency warnings.
What we assess
Modernization scope usually spans jobs, packages, datasets, stored procedures, semantic models, schedules, execution history, and access gaps. TangleMap assesses those surfaces together so teams can see the estate before choosing a path.
Databases, schemas, tables, views, stored procedures, functions, object definitions when included, linked-server candidates, and unresolved dependency warnings.
Jobs, steps, schedules, owners, enabled state, commands, run context, and references to SSIS, SQL, PowerShell, and related operational patterns.
Catalog items, reports, shared datasets, embedded and shared data sources, parameters, RDL definitions, linked reports, subscriptions, item security, and execution-log summaries where access allows.
SSISDB projects, packages, environments, environment variables, parameters, environment references, execution history, and SQL target candidates.
Tabular 1200+ models, tables, columns, measures, relationships, partitions, data sources, refresh metadata, and partition query definitions where available.
Power BI can be considered as a modernization direction, but it is not treated as the assumed answer or a core v1 source system.
Execution and usage history improve prioritization, but the assessment does not depend on every source retaining complete history.
Permission limitations, unsupported versions, dynamic SQL, expressions, and inaccessible metadata reduce confidence. Those limits should be visible in the assessment rather than hidden.
Next step
If the estate is hard to document, hard to scope, or hard to modernize with confidence, start by turning it into structured evidence.