Stop guessing why your SQL Server is slow or crashing. We connect Oklahoma City companies with expert DBAs to tune performance, eliminate bottlenecks, and lower costs. No junior staff, just senior expertise. 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.
Prefer to talk? A senior DBA is reachable at 1-877-891-1870
SQL Server consulting in Oklahoma City: the short answer
Red9 delivers senior-only SQL Server consulting, performance tuning, managed DBA services, and emergency response to companies across the Oklahoma City metro, taking in Edmond, Norman, Moore, Midwest City, and Yukon. A single database engine, and no others, since the firm opened in 2014. The free 145-point health check runs before anything is proposed. We carry 120+ clients, from seed-stage startups up to the Fortune 100; Managed Services and Emergency Services clients have production incidents answered inside 15 minutes, and every change goes out with the numbers taken around it.
Need a SQL Server consultant covering Oklahoma City this week? Book your free assessment.
Oklahoma City runs on data that accumulates: well histories, maintenance records, inventory movements, patient charts. None of it gets smaller, and most queries against it were written when the tables were far smaller.
Exploration and production companies are headquartered here, with midstream operators, service companies, and analysts around them. Production, measurement, and land records land in SQL Server continuously and stay for the life of the asset, so partitioning and retention design lead.
The metro carries one of the country's larger aircraft maintenance and overhaul clusters, along with a supplier base around it. Work orders, parts traceability, and inspection records have to stay retrievable for years, and a slow parts lookup stops a hangar rather than a screen.
OU Health, Integris, and the Oklahoma Health Center district anchor a substantial care and research sector, with clinical and revenue-cycle databases falling under HIPAA. We comply with HIPAA and SOX, sign NDAs on every engagement, and carry cyber insurance, and every action taken over our access is logged.
Sitting where I-35 meets I-40 makes this a distribution metro, with warehouses, wholesalers, retail chains, and food and agriculture operators keeping inventory and order data on SQL Server. Those inventory procedures run thousands of times a day, which is where the arithmetic gets interesting: see the inventory case below.
We work with organizations across the metro: Oklahoma City, Edmond, Norman, Moore, Midwest City, Yukon, and Mustang, out to Shawnee, Stillwater, and Tulsa, and throughout Oklahoma, all over secure remote access. Scheduling follows your operating windows, on Central time.
Senior judgment on the architecture, licensing, and retention decisions an Oklahoma City team has to live with for a decade. The design conversation is always cheaper than the rebuild.
From $4,995 / 20-hr block (hours do not expire)Senior administrators running your instances daily: monitoring, patching, verified restores, and growth planning. Nobody on your side has to become the accidental DBA.
From $395 / moA storm, a power event, or a corrupt page at 4am reaches an engineer who has met the failure before, with a 15-minute response for Managed Services and Emergency Services clients.
From $2,500 / incidentWe rank the workload by its real daily cost, including the CPU that parallel plans hide, then rebuild what sits at the top and log the readings on both sides.
Version upgrades, Azure SQL, or AWS RDS, sequenced so your users never see the seam. Extended support for SQL Server 2016 stops on July 14, 2026, and 2017 in October 2027, which puts the decision on this year's agenda.
145 read-only checks over configuration, backups, security, and performance, returned free as a fix list in value order. You can also point it at your own instance whenever you like.
Recovery designed for a region that loses power in the spring. We build and tune failover clusters and Always On Availability Groups, keeping the secondary off the primary's power feed, and add log shipping, replication, or Change Data Capture (CDC) where only the deltas need to move.
Groundwork on the databases your team wants to point an assistant at, ChatGPT (OpenAI) or Claude (Anthropic), plus the RAG pipelines, vector search, and analytical traffic those tools add to SQL Server. Where reporting has begun to fight the operational load, we move the offload, SSRS and Power BI datasets included, onto Snowflake, Redshift, or whichever warehouse you already run.
"Red9 shown immense responsibility & admirable skill in handling production issues, resizing production DB & delivering projects with pin point accuracy without any issues."
"Red9 works hard at making sure we have plans that are repeatable and able to carry us into the future from a hardware and performance perspective."
"MSSQL System/Performance Review and SSRS Authentication. Enjoyed working with you!"
Four steps, discovery measured in days, and the same senior DBA through the audit and the work. The roadmap and its expected payback arrive before any spend.
Which instances hold the business up, what the failure looks like from the outside, and how long the data has to be kept. Retention shapes half the design decisions here.
The audit works through 145 checks on configuration, whether the backup chain would truly restore, where security is exposed, and what the workload is costing, ranking each finding by the value of the fix. You can also run the same read-only audit on your own instance beforehand, free, through our self-serve Health Check.
One working session through the findings, ordered by value, with the hours and the cost against each. You come away with a plan and a firm figure.
After approval we work the plan and record readings around each change, which makes every improvement checkable. Managed services then hold the estate steady as the tables keep growing.
Three real Red9 projects, tracked from the first review through to the last measurement. The clients recorded every figure here, before and after. Names are kept private at their request.
The problem. An automotive services chain had a search stored procedure the report describes as running several times a minute, taking a disproportionate share of the server's resources. A representative run showed 37,061 ms of duration, 64,446 ms of CPU, and 932,204 logical reads, and the CPU figure exceeding the duration told us the plan was going parallel; the plan itself showed the scan.
What we did. We indexed the access paths the procedure actually uses, so the engine seeks instead of scanning, then re-measured the same procedure under comparable load.
37,061 ms down to 391 ms, on a procedure that fires every few seconds.
The result. The procedure returns in 391 ms using 281 ms of CPU and 3,687 reads. On something the report has running several times a minute, that took a standing load off the instance.
What the review found. The procedure searched wide tables on predicates with no supporting index, so each execution scanned and the optimizer recruited extra cores to get through it, which is what pushed CPU past the wall-clock figure.
What we changed (identifiers generalized for privacy):
-- Search procedure: several runs per minute, 37,061 ms, 64,446 ms CPU, 932,204 reads. CREATE NONCLUSTERED INDEX IX_red9_message_search_status ON dbo.[message_log] (statusCode, createdOn) INCLUDE (accountRef, bodyRef); -- second index added on the recipient lookup path -- rollback: DROP INDEX scripts supplied for both
Once the seeks existed the plan stopped going parallel, and the CPU accounting came back in line with the clock.
The problem. A hospitality software company ran a revenue refresh procedure about 7,007 times a day, averaging 260.74 ms per call with 1,234.76 ms of CPU. The CPU figure being nearly five times the duration meant several cores were working inside every call. Across the day the procedure drove 751,802,051 logical reads.
What we did. We captured the Query Store baseline, then created one nonclustered index keyed on the three columns the procedure filters, with the status description carried as an included column so the engine never returns to the base table, and captured the same statistics again.
A 114-fold cut, worth about 30 minutes of SQL processing a day.
The result. The refresh completes in 2.29 ms using about a millisecond of CPU, and the daily read volume fell by roughly 748 million. About 30 minutes of daily SQL processing went back to the platform, and the cores that had been recruited for the scan went with it.
What the review found. The procedure filtered a queue table on a plan, month, and segment combination with no index behind it, so each of its 7,007 daily calls scanned and parallelized. The status column it returned forced a lookup on every row it kept.
What we changed (identifiers generalized for privacy):
-- Revenue refresh: ~7,007 calls/day, 260.74 ms each, 1,234.76 ms CPU, 752M reads/day. CREATE NONCLUSTERED INDEX IX_red9_revenue_queue_plan_month_segment ON dbo.[revenue_refresh_queue] (planId, monthId, segmentId) INCLUDE (statusDesc); -- before/after captured with Query Store; DROP INDEX rollback provided
Three key columns and one include, and the parallel scan turned into a seek.
The problem. A floral importer and distributor had an inventory movement procedure running about 9,307 times a day at 167.02 ms per call, with 119.31 ms of CPU. The daily read total came to 93,470,201 pages, all to answer questions about individual barcoded items.
What we did. We created one covering index keyed on the barcode column with the two harvest and timing columns the procedure returns carried as included columns, then re-captured the Query Store figures on the same workload.
A 113-fold reduction, at roughly 9,307 calls a day.
The result. The inventory procedure answers in a little over a millisecond, the instance performs 93 million fewer reads a day, and about 26 minutes of daily SQL processing was returned. One index, with its rollback script attached.
What the review found. The procedure looked items up by barcode on a table with no index on that column, so every call scanned to find a single row and then went back to the table for the two fields it needed.
What we changed (identifiers generalized for privacy):
-- Inventory procedure: ~9,307 calls/day, 167.02 ms each, 93.5M reads/day. CREATE NONCLUSTERED INDEX IX_red9_lot_open_barcode_includes ON dbo.[lot_open] (barcode) INCLUDE (postHarvestStage, wakeDate); -- before/after captured with Query Store; DROP INDEX rollback provided
A single-column key with the returned fields included is the whole change, and at 9,000 calls a day it removed 93 million reads.
Every number above was measured on somebody else's instance. 30 minutes and we will put the same arithmetic on yours.
Get a Free SQL Server Assessment ➜Rather talk it through? A senior DBA answers at 1-877-891-1870.
A principal-grade specialist does the reading and the writing on your estate, with 15 years or more behind the judgment.
This engine has been the entire business since 2014, spanning 10,000+ audited databases and thousands of servers.
Duration, CPU, and reads on both sides, with the parallel accounting explained rather than quietly averaged away.
Through storm season and every other week, Managed Services and Emergency Services clients reach a senior DBA within 15 minutes.
Yes, and in a metro that loses power to weather most springs, coverage from outside the affected grid is worth something in itself. A senior DBA stays reachable through your whole Oklahoma City workday on Central time, with 24/7/365 emergency cover on top for Managed Services and Emergency Services clients. You keep the access: connections come in over your VPN or bastion host on least-privilege logins you create and can revoke instantly, with further controls layered above, and every change arrives as a script your team reads before running it.
How the three options actually differ once an Oklahoma City database starts costing you hours you cannot see.
| Red9 | In-house DBA hire | Generalist IT / MSP | |
|---|---|---|---|
| Seniority | Principal-grade SQL Server specialists averaging 15+ years, with no junior tier behind them. | The capability is one person deep, and this market is short of them. | Generalist teams where the database waits behind the network. |
| SQL Server focus | SQL Server is all we do. | Divided across every other platform in the building. | One item on a very long service menu. |
| Emergency response | Available every hour of the year, with a 15-minute response for Managed Services and Emergency Services clients. | Limited to one person's hours and their own power supply. | A queue that grows whenever the weather does. |
| Proof | Duration, CPU, and reads from both sides, with parallel plans counted honestly. | Seldom captured in a form you could audit. | Usually a claim without a measurement. |
| Cost model | Scoped project, retainer, or single incident, and no headcount lands on your budget. | A loaded Oklahoma City salary near $105,000 to $130,000, plus benefits and idle stretches. | Rolled into a larger invoice you cannot break down. |
| Ramp-up | Reading your workload within days. | Months to recruit here, then months to ramp. | Slow to engage, and the context resets on every ticket. |
Senior SQL Server cover can be running within days. Get a Free SQL Server Assessment ➜
Founder & Partner
25+ years making SQL Servers faster.
Chief Operating Officer
Chief Revenue Officer
Working under that leadership is a senior-only DBA bench averaging 15+ years, and one named lead stays personally accountable for your result.
We support Oklahoma City teams over secure remote access, from downtown and Bricktown out through Edmond, Norman, Moore, Midwest City, and Yukon. The same senior DBA answers whether the instance sits in an energy office tower or a distribution center off I-40.
Coverage runs across the metro and throughout Oklahoma. Explore the areas we serve.
Five things to pin down before anybody connects to your estate.
Ask how much of their work is this engine, and for how long. Depth on one platform is what spots the unusual case.
Get the name and years of the person who will hold your logins, and check who takes over when they are away.
Ask how they treat a query whose CPU exceeds its duration. If that does not register as parallelism, keep looking.
In this region, ask when the failover was last tested and what the measured recovery time came out at.
Real projects, real figures, the method, and a rollback for each change. Anonymized clients are normal.
| 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 | Oklahoma City and the surrounding metro, plus nationwide via secure remote access |
Yes. Red9 covers Oklahoma City and the surrounding metro, from downtown and Bricktown out to Edmond and Yukon, south through Moore and Norman, and east to Midwest City, with a senior SQL Server consultant on every account. Remote is the standard model in this market and what practically all of our clients use. Secure remote access and a 15-minute emergency response for Managed Services and Emergency Services clients put a senior DBA on the estate long before anybody could reach your building on I-35.
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 first step is a free 145-point health check, read-only and with nothing to sign. Managed services and remote DBA run from $395/mo. A 20-hour senior block is $4,995 and the hours do not expire. Per-incident emergency cover opens at $2,500. Against a loaded Oklahoma City DBA salary of $105,000 to $130,000, the figure carried in the comparison table above, a senior block is roughly two weeks of that hire and it produces in the first. Larger scopes are priced once the audit is in hand.
Energy estates grow in one direction only, because production and measurement history gets written every day and deleted almost never. We partition the largest history tables so a recent-activity query stops walking a decade of readings, keep the analytical reporting on its own path, and set file growth and memory for the size the tables will be next year. Archiving gets a written policy, since retention decisions here are usually contractual rather than technical.
It means the recovery target should be tested rather than assumed, and the secondary copy should not share a power feed with the primary. We set the recovery point and recovery time objectives first, then choose the mechanism that meets them, whether that is a synchronous replica in a second facility, an asynchronous one further out, or restores into a cloud subscription. Then we rehearse a failover on a calm week and record how long it actually took.
It means the plan is going parallel, so several cores are accumulating time inside one call, and the query is costing you more than the clock suggests. That is a signal worth chasing rather than a reporting error. In case #2 above, a refresh procedure showing 1,234.76 ms of CPU against 260.74 ms of duration came back at 2.29 ms with CPU near 1 ms, and its daily reads fell from 752 million to about 4 million.
Yes. Nonprofits and government agencies get the same free 145-point health check on the same terms as anyone else, and the report ranks every finding with a price attached, written so a board or a municipal committee can approve line by line. Managed services and remote DBA run from $395/mo. A 20-hour senior block is $4,995 and the hours do not expire.
Version coverage, platform options, and how an engagement is structured are all set out on our SQL Server consulting page.
30 minutes is enough to start. We will find where the estate gives away speed, uptime, and money, and tell you what each fix is worth. The free SQL Server assessment shows you the findings and the price before you decide anything.
Schedule My Call Now ➜Rather talk it through? A senior DBA answers at 1-877-891-1870.
