Server and Database Administration
Server and database administration covers the routine work a system needs. It tracks who has access, how quickly storage is filling, whether indexes still match the queries and which version is installed.
What deferred administration looks like
- The database has not been upgraded since it was installed
- Indexes were added early and never reviewed as the data grew
- Nobody can produce a current list of who holds administrative access
- A replica exists, and nobody is sure whether it is current
The routine itself
Taking over an inherited system
Work starts with the current access lists, configuration and version status, read against what the vendor still supports. Findings are written down. Anything overdue receives a plan and a date before the routine settles.
Frequently asked questions
Is server and database administration different from monitoring?
Yes. Monitoring watches and reports. Administration is the work itself, such as the accounts, the upgrades, the index rebuilds and the archiving.
Can you take over a system another vendor built?
Yes. Taking over an inherited setup is routine work. The first pass documents what exists, because inherited environments often differ from their diagrams.
Will a version upgrade break our application?
It can, so upgrades are tested on a copy first and applied in an agreed window with a way back. Staying several versions behind carries its own risk.
Who owns the servers and databases under this arrangement?
You do, in accounts held in your business name. Our access is named, scoped and can be revoked at any time.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
- No obligation
- A reply within one business day
- Your details stay private
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirements