Database care for SQL Server and Postgres

• Backups nobody has restored. A backup you’ve never tested is a hope, not a plan.
• A version past its support date. SQL Server 2016 lost Microsoft support in July 2026; PostgreSQL 14 follows on November 12, 2026. Unsupported means no more security fixes.
• One person who knows how it works. And they’re busy, or they’ve left.
• Reports done by hand. Someone exports to Excel every Monday to answer the same questions.
• It’s getting slow. Screens that took a second now take ten, and nobody knows why.

• Health check. Backups and a real test restore, security and logins, version and support status, performance and a written report with the three fixes that matter most.
• Upgrades and modernization. Off unsupported versions to current SQL Server or PostgreSQL, on your own server or in the cloud, with a rehearsal first and a way back.
• Monthly care. Monitoring, patching, backups verified every month, and small changes, with one team to call.
• Your data on the web. Customer portals, online booking and live dashboards built on the database you already have, not another copy of it.
• Training. Hands-on sessions so your staff can run the everyday work themselves.

We start with a read-only health check, so nothing changes until you’ve seen the report. Every project is quoted in writing before work starts, and upgrades are rehearsed on a copy of your data first. We work remotely over a secure connection, so where you are doesn’t matter.

Database work is by request and priced on time, agreed with you in writing before we start. Ask us.

The same database skills sit under everything else we build. Alpine, our booking and point-of-sale system, runs on PostgreSQL, and our websites and apps can read and write the data your business already keeps. Running an old version? Read what to do when SQL Server or PostgreSQL loses support.