Service Databases
Consulting and ongoing support for your SQL Server
For companies that rely on SQL Server without a dedicated database administrator: we find out why the database is slow or exposed, prove that your backups restore and, where it makes sense, continue with ongoing support alongside your IT team. Based in Recife, with remote service across Brazil.
Summary
What tends to go wrong
The database was set up years ago, has grown without maintenance, and nobody is quite sure how it is configured anymore. The symptoms creep in: screens that crawl at month-end, lock-ups at peak hours, a disk that suddenly fills up, a nightly backup that has never been restored. When the problem finally surfaces, it surfaces in production.
Who it is for
Companies running an ERP, line-of-business software or in-house applications on Microsoft SQL Server without a dedicated database administrator, or IT teams that want a specialist review before a major change.
Deliverables
What gets delivered
- Assessment report: findings ranked by risk and a prioritized action plan
- Restore evidence: the backup restored in a test, with the revised policy alongside it
- A file for each approved change (performance tuning, migration or upgrade): rehearsal in staging, the way back and, for performance, the before-and-after measurement
- With ongoing support, a regular health report on the instance
- A recommendation on extraction, a replica or off-peak processing to bring data to analytics, with the expected effect on system load
Steps
How the engagement runs
Agreed access
Your IT team sets up a read-only login that it can revoke at any time.
Picture and risks
Configuration and metrics are collected without changing anything, followed by a report with risks in order of priority.
Decision
With the report, you choose what to tackle first, who approves it and what the acceptance criteria are.
Rehearsed change
Each change is rehearsed outside production, applied in an approved window and measured afterward.
Ongoing routine
Monitoring, periodic reviews and fresh recommendations, when a support agreement is in place.
Roles
Who takes care of what
Trustwise
Investigate, recommend, carry out what was approved, document every intervention and measure the effect.
Your company
Grant access, name who approves changes, set aside maintenance windows and run the infrastructure the database lives on.
Engagement
Where to start
The first step is an assessment with an agreed scope. With the report in hand, you choose: fix specific issues as a project, sign up for ongoing support, or carry on with your own team. Commercial terms are set out in a proposal.
Scope
What is included
-
Instance assessment
An inventory of servers, versions and databases, a review of configuration and workload, and a report that separates what is urgent from what can wait.
-
Proven backup and restore
A backup policy sized to how much data the business can afford to lose, restore tests, and a plan for bringing the database back online.
-
Access and database protection
A review of logins and permissions, over-privileged accounts, encryption, auditing and pending updates.
-
Query performance
We trace the most expensive queries, wait types, indexes and statistics, measuring before and after every change.
-
Migrations and upgrades
Moving off unsupported versions, to a new server or to Azure, always rehearsed first and with a defined way back.
-
Ongoing support
Instance monitoring, periodic reviews and health reports on the environment, together with your IT team.
-
Data for analytics without loading the system
Assessing how to move ERP data into dashboards and AI pilots through extraction, a replica or off-peak processing, without competing with day-to-day operations.
Risk signs
When SQL Server deserves a closer look
None of these is unusual, and almost all of them have a cause you can find inside the database itself.
- Scheduled backups that have never gone through a restore test
- A SQL Server version that is out of Microsoft support
- Many users holding administrator rights for convenience
- Reports and month-end jobs that take a little longer every month
- Slowdowns at peak hours with no visible change to the application
- Transaction log or data files growing unchecked
What you get
What the assessment delivers
A report listing each finding, the risk it carries and what to do about it, from the urgent to what can wait. To get there, we work with read access agreed with your IT team and collect configuration and metrics without touching anything in production. The report covers:
- Backup jobs and index maintenance
- Logins, roles and elevated permissions
- Support risks: version, missing updates, disk space
- The most resource-hungry queries and the dominant wait types
- Server and instance settings: memory, parallelism, tempdb
- Inventory of instances, versions, editions and databases
Nothing is changed during the assessment. Changes only happen later, in a window your team approves.
Backup
A backup only counts once it has been restored
The backup policy starts from two targets the business sets: RPO and RTO. We review frequency, retention and the chain of log backups, then restore to a separate environment to check that the file is intact and how long the database takes to come back. The test result is put on record.
Performance
How we deal with slowness
A slow SQL Server nearly always has a concrete cause: a missing or redundant index, stale statistics, a poor execution plan stuck in cache, transactions blocking each other. Before changing anything we record a baseline, rehearse the change outside production and decide how to roll it back. Once it is applied, we measure again and you get the comparison.
Ongoing support
What ongoing support includes
With ongoing support, Trustwise looks after the day-to-day running of the database together with your IT team. The exact scope is agreed in the proposal; these are the items it usually covers.
- Instance monitoring and alert triage
- Periodic reviews with prioritized recommendations
- Regular report on the health of the instance
- Index and statistics maintenance tuned to actual usage
- Backup checks and scheduled restore tests
- Help applying updates in an agreed window
Data for analytics
BI and AI without overloading the ERP
When dashboards or AI pilots start querying the production database, they compete for memory, disk and CPU with the system that invoices and records orders. We work with your IT team to find the route that gets data to analysis without hurting operations.
- Scheduled extraction to an analytics repository, outside the production database
- A read replica reserved for analytical queries
- Processing in a low-load window, aligned with the system's calendar
Each option is validated case by case, based on your SQL Server version, edition and workload.
Technologies
Platforms and tools
- Microsoft SQL Server in your own data center (physical server or virtual machine) or on Azure (Azure SQL and virtual machines)
- Execution plan analysis and instance monitoring
- Built-in diagnostics: DMVs, Query Store, Extended Events
FAQ
Questions we often hear
Does the assessment affect the running system?
No. We use read access and queries against SQL Server's system views, which put very little load on the server. No settings are changed at this stage; changes come later, in a window your team approves.
What is the difference between having a backup and being able to restore it?
A scheduled backup only proves that a file was written. A restore shows whether that file is intact, whether the chain of log backups is complete and how long the database takes to come back. Only a restore test shows whether the RPO and RTO targets agreed with the business are met; our article on testing restores explains both.
Do we need Always On or replicas?
It depends on how much downtime the business can tolerate. In many environments, a well-configured backup with tested restores is enough. When tolerance is low, Always On availability groups or replicas start to make sense, with licensing and infrastructure costs that have to be factored in. The assessment points the way, and our data infrastructure service goes deeper into the design.
Can you migrate us to a newer version or to Azure?
Yes. A migration starts with a compatibility review, goes through a full rehearsal in staging and only then reaches production, with a rollback plan in place. The same care applies to upgrading SQL Server, moving to a new server or taking the database to Azure.
Does ongoing support replace our IT team?
No. It complements your IT team on the database side: your people remain in charge of the environment and the decisions, while Trustwise handles the specialist analysis and routines that were agreed.
Do you work remotely and outside Brazil?
Trustwise is based in Recife and serves companies across Brazil remotely, through controlled access that your IT team defines and can revoke at any time. Work for companies in other countries, in English or Spanish, is considered case by case.
Can we use ERP data for BI or AI without slowing the system down?
In most cases, yes, as long as analytical queries do not run straight against the production database during business hours. The assessment shows whether the best route is scheduled extraction, a read replica or processing in a low-load window, and what each option requires of your environment.