My role
Application, database and systems modernization
The result
The modernization moved the SQL infrastructure to SQL Server 2022 alongside server changes. My work connected the technical migration with application recovery, validation and the operational readiness of the clinic.
01
The problem
A clinical application cannot be modernized by treating its database as an isolated component. Older SQL Server and Windows infrastructure, application compatibility and workstation access all affect whether the practice can return to its normal workflow after a change.
02
Operational context
This work involved an ABELDent production environment at dentalcorp, a large application database and a move from older SQL Server infrastructure to SQL Server 2022, with associated Windows Server modernization. The public account describes the technical scope without identifying the practice or exposing its data.
03
My contribution
I worked through the application, database and server dependencies, troubleshooting compatibility and recovery issues, coordinating with the application vendor and supporting cutover validation and clinic readiness. The work required connecting what the database and server were doing with what staff experienced at the workstation.
04
Constraints
- Production clinical workflows and an existing application had to remain the basis for readiness decisions.
- SQL Server, Windows Server, application versions and workstation launch behaviour had interdependent compatibility requirements.
- The public case excludes patient data, private tickets, internal addresses and detailed production configuration.
05
Implementation decisions
- Treat database and server modernization as one application-readiness problem, rather than separate infrastructure tasks.
- Investigate dependencies across the workstation, application, SQL service and underlying server before choosing the next intervention.
- Bring vendor coordination, recovery and post-change workflow validation into the delivery work.
06
Alternatives considered
- A successful database migration alone would not establish that the application and workstations were ready for use.
- Treating every slow or failed application launch as a database fault would overlook client, service and server dependencies.
07
Validation approach
- Application compatibility and workstation access following the infrastructure changes.
- SQL and server behaviour during troubleshooting and recovery.
- Post-change application operation and clinic readiness, with unresolved issues carried into stabilization.
08
What this shows
The modernization moved the SQL infrastructure to SQL Server 2022 alongside server changes. My work connected the technical migration with application recovery, validation and the operational readiness of the clinic.
09
Limits of the evidence
- This is a sanitized historical account; production records and system access are not part of the public case.
- No downtime, performance-improvement or financial result is quantified here.
Inspect the work
A similar problem in your organization?
This example can be a starting point for defining your own project, its dependencies and acceptance criteria.
Legacy systems & database modernization