Queries dragging, a backup you have never test-restored, a license renewal that keeps climbing? Our senior-only DBAs stand behind San Antonio teams, isolate the root cause, and prove each fix with numbers measured before and after. SQL Server is all we do.
Talk to a senior DBA
A senior DBA reads this (not a sales rep) and replies within one business day. No obligation.
You see the findings and the price before you commit.
By clicking, you agree to our Terms of Use and Privacy Notice.
Questions? Get a senior DBA on the line at 1-877-891-1870
SQL Server consulting in San Antonio: the short answer
Red9 runs senior-only SQL Server consulting, performance tuning, managed DBA services, and emergency response for businesses across the San Antonio metro, from downtown and Alamo Heights out to Stone Oak, New Braunfels, and Schertz. SQL Server is all we do, and each engagement starts with a free 145-point health check. Our roster holds 120+ clients, from first-round startups to the Fortune 100; for Managed Services and Emergency Services clients, a production incident gets an answer inside 15 minutes, and every fix lands with numbers taken before and after.
Hunting for a SQL Server consultant close to home in San Antonio? Book your free assessment.
San Antonio runs on data that is regulated, defense-grade, and high in volume. Military and cyber commands, insurers, hospital networks, and energy operators all sit on SQL Server, and each one feels it the moment the database starts to stall. Those are the systems our DBAs live inside day after day.
San Antonio calls itself Military City USA for good reason. Joint Base San Antonio is the largest joint base in the Department of Defense, and the 16th Air Force, the service's information-warfare and cyber command, operates out of Lackland. The contractors feeding that mission carry ITAR, CMMC, and NIST 800-171 duty on their data. We harden and speed up the SQL Server behind that work while access stays locked down and logged.
The city is an insurance and banking anchor for Texas. USAA is headquartered here and ranks among the metro's largest employers, and Frost Bank runs its home office downtown, all of it settling and reporting under SEC, FINRA, and PCI-DSS scrutiny. We tune the high-throughput databases behind policy, claims, lending, and payments, where a procedure that stalls at close of business carries a real dollar cost.
The South Texas Medical Center packs dozens of hospitals, clinics, and research institutes into one district on the northwest side, and Baptist Health System runs facilities across the region. Their clinical and claims data moves under HIPAA, where a slow query turns into a patient-care delay. We speed up the databases behind that care while every touch stays tight and logged.
San Antonio is a serious energy town. Valero Energy runs its Fortune 500 headquarters here, NuStar Energy operates its pipeline network from the metro, and CPS Energy is the largest municipally owned utility in the country. The trading, metering, and grid databases behind that work cannot afford to seize during a demand spike, so we size and tune SQL Server to hold steady when load surges.
We serve businesses across the metro: San Antonio, New Braunfels, Schertz, Converse, Boerne, Seguin, and Universal City, and statewide across Texas, including Austin, Houston, and Dallas, over secure remote access. We schedule around your working week on Central time.
Principal-grade counsel for a San Antonio team staring down a decision on architecture, performance, spend, or how the system scales. We come in while the call is still cheap to get right, ahead of the expensive rebuild it turns into later.
From $4,995 / 20-hr block (hours do not expire)A remote DBA bench for San Antonio teams that would sooner not staff the role in-house. Senior administrators watch, patch, and run your SQL Server day to day, so no one on your side takes a 2am page.
From $395 / moWhen production seizes or slows to a crawl, you reach an engineer who has already beaten this failure mode, with a 15-minute response for Managed Services and Emergency Services clients.
From $2,500 / incidentWe hunt down the queries and indexes draining CPU, IO, and clock time, then rewrite them. The readings get taken going in and taken again coming out.
Moves onto a current version, onto Azure SQL, or onto AWS RDS, run without downtime your customers would clock. SQL Server 2016 loses extended support on July 14, 2026, with 2017 next in October 2027, so we chart the move ahead of the cutoff.
A free, read-only 145-point health check spanning configuration, backups, security, and performance, returned as a fix list ranked by impact. Run the very same check on your own server any time you like.
HA/DR that recovers for real, not one that only reads well on paper. We design and tune clustering and Always On Availability Groups, then layer in log shipping, replication, and Change Data Capture (CDC) for when only the changed rows have to move.
Readiness work on the database feeding the assistants your team wants to wire up, ChatGPT (OpenAI) and Claude (Anthropic), plus the RAG pipelines, vector search, and analytics load those tools drop on SQL Server. Once reporting starts to strain, we shift the production offload, SSRS reports and Power BI datasets and all, into Snowflake, Redshift, or whatever warehouse you already run.
"Since adding Red9 to the reporting and DataWarehousing team, Red9 has done a good job coming up to speed on our environments and helping ensure we continue to meet our customer's needs. Red9 has taken ownership of our servers ensuring they remain healthy by monitoring and tuning inefficient queries."
"[after Red9 sql performance updates] SK46 is about to parade me around the shop on their shoulders!"
"Thanks for the quick turnaround. 16 milliseconds sounds spectacular."
No months-long discovery, no quiet handoff to a junior. The roadmap and the payback it should return are the first things you see.
We open by nailing down the actual problem: which servers are in it, how the trouble shows up, and what the database is on the hook to deliver for your business. We do the asking first, long before we float a proposal.
The 145-point health check reads how the instance is configured, whether a restore would truly bring your backups back, where security leaves a door open, and what is throttling your queries, then ranks each finding by impact. Rather see it for yourself first? Run that same read-only audit against your own server at no cost with our self-serve Health Check.
We take you through what surfaced and what the fix costs, one line at a time. You walk away with a ranked roadmap and a firm figure, and nothing buried in fine print.
Once teaming up makes sense, we run the roadmap and put the before-and-after numbers on the table so the gain is something you can measure. After that, ongoing managed services hold the server steady and keep the same faults from crawling back.
Each of these is a genuine Red9 project, followed all the way through. The numbers are what the client clocked before we started and after the fix went live. We keep the names off the page because they asked us to.
The problem. A nationwide manufacturer running a high-volume ERP had a core query grinding for 31.24 seconds on each run and reading its way through 777.6 million pages a day. It fired often enough that the wait stacked up into hours of lost SQL time, and staff sat watching a spinner all shift.
What we did. We captured the plan and Query Store statistics, then built an index tuned to the query's filter and output so the engine seeks a handful of pages instead of dragging the whole table through memory. We left rollback scripts in place beside it.
777.6 million down to 26.5 million a day, IO off the box.
The result. The query now finishes in about a fifth of a second and pulls 26.5 million pages a day instead of 777.6 million. The IO it used to burn is off the instance, so everything else sharing that server got lighter, and roughly 9 hours of daily SQL processing came back.
What the review found. The ERP query filtered a large table with nothing to support it, so every call scanned the table end to end, on the order of hundreds of millions of reads a day at 31 seconds a run.
What we changed (identifiers generalized for privacy):
-- ERP query scanned the full table: ~31.24 s per run, 777.6M reads/day. CREATE NONCLUSTERED INDEX IX_erp_orders_covering ON dbo.[erp_orders] (/* filter cols */) INCLUDE (/* output cols */); -- rollback: DROP INDEX script provided
The covering index flipped the scan into a seek: the run dropped from 31.24 seconds to 193 ms, and daily reads from 777.6 million to 26.5 million.
The problem. A nationwide multi-site services operator leaned on a cluster of stored procedures that all chewed the same expensive aggregation. The heaviest of them, a status-reporting procedure, ran near 3,200 ms a call and pushed roughly 1,100,000 rows through every execution, so the reports users needed most were the ones that crawled.
What we did. Rather than patch each procedure on its own, we built a single indexed view that pre-computed the shared aggregation, then pointed the procedures at it. One structure carried the load for the whole family. We recorded the readings on both sides of the change in one sitting.
A single structure lifted a whole family of stored procedures at once.
The result. The heaviest procedure returns in about 400 ms instead of 3,200, and it reads roughly 150,000 rows in place of 1,100,000. Because the indexed view backs several procedures, the rest of the family got quicker off the same piece of work.
What the review turned up. A group of stored procedures each recomputed the same heavy aggregation from base tables, so the busiest one read about 1,100,000 rows and ran near 3,200 ms per call.
What we changed (identifiers generalized for privacy):
-- Pre-computed the shared aggregation once in an indexed view; -- the family of procedures reads the view instead of the base tables. CREATE VIEW dbo.vw_status_rollup WITH SCHEMABINDING AS SELECT /* grouped keys */, COUNT_BIG(*) AS rc FROM dbo.[job_records] GROUP BY /* keys */; CREATE UNIQUE CLUSTERED INDEX IX_vw_status_rollup ON dbo.vw_status_rollup (/* keys */);
With the aggregation materialized in the view, the worst procedure fell from about 3,200 ms to 400 ms and from roughly 1,100,000 rows to 150,000, and its siblings rode the same gain.
The problem. A technology services company was carrying a transaction log fragmented into 4,171 virtual log files. That much VLF sprawl drags recovery, slows startup and log backups, and leaves the database fragile exactly when you need it to come back clean. On top of it, the workload had no indexing to speak of, so the hottest access paths were scanning.
What we did. We shrank and regrew the log on sane fixed increments to collapse the VLF count, then worked through the workload and added 25 targeted indexes. We tracked usage after the change to confirm the new indexes were earning their keep.
One index alone served that many reads in a single day.
The result. The log now holds 20 VLFs instead of 4,171, so recovery, startup, and log backups behave, and the 25 new indexes took the scanning off the hot paths. One of them was hit 629,331 times in the first 24 hours, which told us the work landed where it mattered.
What we uncovered. The primary transaction log had grown in tiny increments over years, leaving 4,171 VLFs, and the busiest queries had no supporting indexes, so they scanned base tables under load.
What we changed (identifiers generalized for privacy):
-- Collapse VLF sprawl: shrink the log, regrow it on fixed increments. DBCC SHRINKFILE (N'app_log', 0); ALTER DATABASE [app] MODIFY FILE (NAME = N'app_log', SIZE = 8192MB, FILEGROWTH = 512MB); -- then 25 targeted indexes across the hottest access paths.
Regrowing the log on fixed increments took it from 4,171 VLFs to 20, and the 25 new indexes turned the hot-path scans into seeks, the busiest of them serving 629,331 reads inside a day.
Those wins came off three other teams' SQL Servers. Let us turn up what yours is sitting on.
Get a Free SQL Server Assessment ➜Questions? Get a senior DBA on the line at 1-877-891-1870
Principal-grade SQL Server and performance specialists staff every engagement. No junior staff finding their feet on your production server.
One engine, and only that engine, since 2014, with 10,000+ database audits and thousands of servers behind the count.
Every job ends with before-and-after numbers, the sort your own team can pull up and reproduce.
When production drops at 3am, Managed Services and Emergency Services clients reach a senior DBA in 15 minutes.
Yes. Remote is how most of our clients operate, and it holds up. A senior DBA is within reach across your full San Antonio workday on Central time, with 24/7/365 emergency cover past that for Managed Services and Emergency Services clients. The door stays yours: secure remote connections run over your own VPN or bastion host on least-privilege logins you create and can pull at a moment's notice, with more security stacked on top, and every change ships as a script your team reads before it runs.
Where each choice actually lands the day a SQL Server problem drops on your desk in San Antonio.
| Red9 | In-house DBA hire | Generalist IT / MSP | |
|---|---|---|---|
| Seniority | Only principal-level SQL Server specialists, 15+ years on average, with no juniors in the mix. | One head's worth of knowledge, and every sick day or holiday opens a gap. | Generalists in the main, meeting SQL Server only in the gaps between a stack of other systems. |
| SQL Server focus | SQL Server is all we do. | Pulled across everything else the role has to cover. | A single entry on a long menu of technologies. |
| Emergency response | A senior DBA answering inside 15 minutes, around the clock, for Managed Services and Emergency Services clients. | Only what one person can hold up, minus their nights and time away. | A ticket queue that stretches into hours or days. |
| Proof | Measured numbers from before and after, laid open for you to verify. | Seldom measured, and kept behind the curtain. | Usually nothing to show. |
| Cost model | Billing runs per scoped project, per retainer, or per incident, so there is no salary or benefits load on your books. | A fully loaded San Antonio salary near $135,000 to $160,000, before benefits and idle hours. | Bundled inside a bigger invoice and shallow where the SQL Server depth needs to be. |
| Ramp-up | Senior coverage live within days. | A hire-and-onboard stretch that runs for months. | Slow off the mark, and you re-brief them on every fresh ticket. |
Put senior SQL Server coverage in place within days. Get a Free SQL Server Assessment ➜
Founder & Partner
25+ years making SQL Servers faster.
Chief Operating Officer
Chief Revenue Officer
Every Red9 engagement is run by a senior-only DBA team averaging 15+ years in the trade, with a lead who stays personally answerable for the result.
We back San Antonio teams over secure remote access, across San Antonio, New Braunfels, Schertz, Converse, Boerne, and out through Bexar and Comal counties. The same senior DBA is on the call whether your stack sits downtown, up in Stone Oak, or out toward the Hill Country.
We support teams across the metro and throughout Texas. Explore the areas we serve.
Whoever ends up on the shortlist, hold them to these five checks.
A shop that does nothing but SQL Server will out-know an MSP whose attention is split across dozens of products.
Ask straight out who will be on your box. A cut-rate price usually hides a junior bench getting its practice on your live system.
Demand numbers you can rerun yourself: duration, reads, and CPU, captured before the work and again after it.
Have them commit the response-time SLA, and exactly who it covers, to paper.
Look for real projects with real figures attached, even when the client name is held back.
| Headquarters | Alpharetta, GA (Atlanta metro) |
|---|---|
| Founded | 2014 |
| Focus | Microsoft SQL Server only |
| Team | Senior-only DBAs, 15+ years average experience |
| Clients | 120+, from startups to the Fortune 100 |
| Databases audited | 10,000+ |
| Rating | 4.9 out of 5, 120+ reviews |
| Emergency response | 15 minutes, 24/7/365, for Managed Services and Emergency Services clients |
| Engagement models | Scoped project, monthly retainer, or per-incident |
| Service area | San Antonio and the surrounding metro, plus nationwide via secure remote access |
Remote is how this market runs now, and nearly every account we hold works that way. Red9 covers San Antonio and the surrounding metro, from downtown and Alamo Heights out to Stone Oak, New Braunfels, and Schertz, with senior SQL Server consultants only. Through secure remote access, plus a 15-minute emergency response for Managed Services and Emergency Services clients, a senior DBA reaches your server in minutes, so "near me" really means senior help wherever the box sits, without the drive across the Alamo City.
15 minutes, any hour, any day of the year, and a senior DBA answers instead of a ticket queue. This response-time SLA is available to current Managed Services clients and Emergency Services clients. See Emergency Services ➜
The starting point is a free 145-point health check, no charge. Managed services and remote DBA coverage open at $395/mo, a 20-hour senior DBA block is $4,995 and those hours do not expire, and round-the-clock emergency response runs $2,500 per incident. Put that next to the loaded $135,000 to $160,000 a full-time San Antonio DBA costs in the comparison above and the gap does the selling. Anything bigger is scoped once the health check is in, so you see the whole number before you sign.
The door stays yours. Connections run over your own VPN or bastion host, on least-privilege logins your team creates and can pull at a moment's notice, and every change ships as a script your people read before it runs. NDAs are signed before anything opens. Nothing about the setup requires standing access or an agent installed on your servers, which is exactly what security teams around San Antonio want to hear first.
Almost always. Afternoon slowdowns in a distribution ERP usually trace to a handful of queries that scan where they should seek, and the fix is a matched index and a reshaped query instead of a bigger server. We pull the plans, find the reads, and tune the worst offender first, the same method that took an ERP query from 31 seconds to a fifth of a second in case #1 above for a high-volume operation.
Stop guessing and stop rebooting: repeated restarts can turn a recoverable problem into data loss. Run integrity checks, confirm the last clean backup, and get a senior DBA reading the errors before anyone runs a repair command. Recovery readiness is the quieter half of the job, and neglected internals surface as risk long before corruption does: the client in case #3 above had a transaction log bloated to 4,171 VLFs before we rebuilt it down to 20.
Version support, cloud platforms, and the mechanics of an engagement are covered on our SQL Server consulting page.
Give us 30 minutes. We will point to where your SQL Server is leaking speed, uptime, and money, and spell out what it takes to close the gaps. With the free SQL Server assessment, the findings and the price are yours up front, ahead of any commitment. If the math holds up, we take it from there.
Schedule My Call Now ➜Questions? Get a senior DBA on the line at 1-877-891-1870
