When we reach for it
Existing Microsoft estates and the applications that were built against them. Licensing and support are already in place, which is a real consideration whatever the technical merits.
SQL Server engineering
Microsoft’s relational database, with strong tooling and a deep presence in enterprise estates, particularly behind .NET applications.
When we would argue against it
Licensing cost is a genuine architectural input, and it is the reason we check the shape of a workload before assuming it should follow an application to the cloud.
What it looks like in delivery
A good deal of this work is untangling business logic from stored procedures far enough to test it, and getting query plans under control on tables that have grown by two orders of magnitude since they were designed.
Where this appears on the site
Nothing on this site names it yet
We work in SQL Server, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.
Working in SQL Server?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.