Platform Evolution
Assessment run-2026-07-27-1 · 213 of 213 repos assessed
Repos / phenix-provider-databases

phenix-provider-databases

Monorepo of 25 SQL Server database projects (Create/Change script packages) for the per-provider staging databases behind Phenix accommodation, car hire, attractions and transfers integrations.

78 · greenmediumlooseOn-premZDD: not applicabledatabase

Health score

78

0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.

Runtime currency / 25
18
Runtime outside the standard generations (for example SQL Server or tooling)
Legacy transport / 15
15
No legacy WCF or SOAP surface
Test posture / 15
0
No tests
Security hygiene / 15
15
No credentials found in source
Dangerous coupling / 15
15
No dangerous coupling detected
Activity / 10
10
Actively maintained
Deployment hygiene / 5
5
CI in place
Health over time
2026-07-24 (run-2026-07-24-1): 782026-07-27 (run-2026-07-27-1): 78
No change since 2026-07-24 (78 to 78).

Facts

Languagessql
FrameworksTC azure-pipelines-templates db packaging
RuntimesSQL Server
Tests / CInone / CI in place
Last commit2026-06-09
OwnerOwner unknown (mapping to be curated)
DomainSelling and quoting (system generated; curate in repo-owners.json to override)
Product areaPhenix
HostedOn-prem Deployed to our own machines
  • Release "\provider-databases\provider-attractionsrepository-db": QA: deployment-group phase (agents on our own machines)
  • Release "\provider-databases\provider-attractionsrepository-db": Staging: deployment-group phase (agents on our own machines)
  • Release "\provider-databases\provider-attractionsrepository-db": Production: deployment-group phase (agents on our own machines)
  • Release "\provider-databases\provider-attractionsrepository-db": Training: deployment-group phase (agents on our own machines)
  • Release "\provider-databases\provider-avis-db": QA: deployment-group phase (agents on our own machines)
Releases25 release pipeline(s): \provider-databases\provider-attractionsrepository-db; \provider-databases\provider-avis-db; \provider-databases\provider-bonotel-db; \provider-databases\provider-carhiredepots-db; \provider-databases\provider-carhirerepository-db; \provider-databases\provider-desertadventures-db; \provider-databases\provider-dosomethingdifferent-db; \provider-databases\provider-ehi-db; \provider-databases\provider-flexibleautos-db; \provider-databases\provider-galileo-db; \provider-databases\provider-holidaytaxis-db; \provider-databases\provider-hotelbeds-db; \provider-databases\provider-jumeirah-db; \provider-databases\provider-mms-db; \provider-databases\provider-musement-db; \provider-databases\provider-nightsbridge-db; \provider-databases\provider-resorthoppa-db; \provider-databases\provider-resortmarketing-db; \provider-databases\provider-sunnycars-db; \provider-databases\provider-swapsystems-db; \provider-databases\provider-transfers-db; \provider-databases\provider-travco-db; \provider-databases\provider-trustyou-db; \provider-databases\provider-ttigiata-db; \provider-databases\provider-webbeds-db
Integrationsqlserver
SourceOpen in Azure DevOps

Risk flags

Each flag links to its glossary definition.

Dependencies in context

Laying out the graph…
greenamberreddata store (square, dashed link)Node size follows fan-in. Click any node to open it.

Entanglement

loose No binding mechanisms apply: this system needs no untangling work.

    Depends on / used by

    Depends on (0)
    Nothing internal.
    Used by (0)
    No internal dependents.
    Data stores
    sqlserver:AttractionsDoSomethingDifferentsqlserver:AttractionsMusementsqlserver:AttractionsRepositorysqlserver:CarHireAVISsqlserver:CarHireDepotssqlserver:CarHireEHIsqlserver:CarHireFlexibleCarHiresqlserver:CarHireRepositorysqlserver:CarHireSunnyCarssqlserver:HotelsBonotelsqlserver:HotelsDesertAdventuressqlserver:HotelsGalileosqlserver:HotelsHotelBedssqlserver:HotelsJumeirahsqlserver:HotelsNightsBridgesqlserver:HotelsSwapSystemssqlserver:HotelsTravcosqlserver:HotelsWebBedssqlserver:ProviderMrAndMrsSmithsqlserver:ProviderResortMarketingsqlserver:Transferssqlserver:TransfersHolidayTaxissqlserver:TransfersResortHoppasqlserver:TrustYousqlserver:TTIGIATAData

    Migration playbooks

    Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.

    ZDD adoption

    Not applicable

    Not a deployed service (libraries, database definitions, desktop apps) or a retirement candidate not worth the investment. Schema repo: changes ride with the owning services under the expand and contract pattern.

    SQL Server exit

    Owned at estate level

    This repo is a database definition, not a service. Its future is decided by the stage 4 database-as-product work for the systems that share it, not by a service-level migration.

    Containerisation

    Not applicable

    Database definition repos deploy schema, not a service.

    Recommended actions

    No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.

    Assessment notes

    phenix-provider-databases

    Purpose

    Source control for 25 provider-specific SQL Server databases under db/ProviderDatabases/ — one folder per third-party supplier feed (hotels: HotelBeds, WebBeds, Travco, Bonotel, Jumeirah, NightsBridge, SwapSystems, Galileo, Desert Adventures, Mr & Mrs Smith; car hire: AVIS, EHI, SunnyCars, FlexibleCarHire, Depots, Repository; attractions: Musement, DoSomethingDifferent, Repository; transfers: Transfers, HolidayTaxis, ResortHoppa; content: TrustYou reviews, TTI GIATA codes, ResortMarketing). Each holds Create scripts (tables, stored procedures — e.g. board-basis mappings, hotel/facility merges) and numbered Change migration scripts (~540 SQL files total).

    Tech stack

    Pure T-SQL packaged via stub netstandard2.0 csproj files whose only job is to copy the Create/Change folders into a deployable package; built with .NET SDK 3.1 through the shared InternalOSS azure-pipelines-templates CI template. Nerdbank.GitVersioning at the repo root.

    Deployment

    The most release-linked repo in this batch: 25 release pipelines under \provider-databases\ (one per database), each fed by its own path-filtered YAML build pipeline in the database folder; release_count 25. Two extra build pipelines (AttractionsDoSomethingDifferent DB, provider-webbedsv2-db) exist without a matching release folder entry.

    Dependencies

    No internal estate code dependencies — it is consumed the other way round: the provider gateway services (phenix-accommodation, phenix-carhire, phenix-attractions, phenix-transfers) and downloader jobs read/write these databases. External dependencies are the third-party supplier feeds whose data the schemas stage.

    Data stores

    Defines the 25 databases listed in the front matter. Several names also appear in other repos' assessments (e.g. HotelsDesertAdventures in phenix-accommodation, AttractionsRepository in phenix-attractions), confirming cross-repo coupling through these stores.

    Integration points

    SQL Server only; schema/stored-procedure contract consumed by the provider services and downloaders.

    Code health

    No tests (schema-only repo, and no tSQLt or similar). YAML CI per database is a strength. Actively maintained (last commit 2026-06-09) with change scripts referencing recent work items. Root README is boilerplate scaffold text; no per-database documentation.

    Modernisation risks

    Medium: the Create+numbered-Change script pattern relies on discipline rather than a declarative/state-based tool (no DACPAC or migrations framework), and there is no automated schema drift detection or testing. The databases are shared integration points between downloaders and gateway APIs, so schema changes here can break multiple services; 25 separate release pipelines add operational overhead.