Stop guessing why your SQL Server is slow or crashing. Red9 pairs your El Paso team with senior DBAs to keep your SQL Server fast and online 24/7. You never deal with junior staff or account managers. 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 El Paso: the short answer
Red9 provides senior-only SQL Server consulting, performance tuning, managed DBA services, and emergency response to organizations across El Paso and the surrounding communities, including Socorro, Horizon City, Canutillo, San Elizario, Fabens, and Anthony. This engine has been our only line of work since 2014. The free 145-point health check opens each engagement. Our list holds 120+ clients, from seed-stage startups up to the Fortune 100; Managed Services and Emergency Services clients get a production incident answered inside 15 minutes, and readings are taken around every change we make.
Need a SQL Server consultant who covers El Paso through your Mountain-time business day? Book your free assessment.
El Paso is one half of a two-country manufacturing region. Parts cross the bridges all day, customs brokers keep the paperwork ahead of the trucks, and Fort Bliss sits alongside a large health and university sector.
The bridges, the intermodal yards, and the warehouse belt keep a dense customs-brokerage and logistics sector busy. The expensive statements are usually reporting queries nobody rewrote after the tables grew. One was reading 9.1 million pages a day: case #3 below.
A large share of North American assembly happens across the river in Ciudad Juárez, with engineering and supply-chain functions on the El Paso side. Replication lag across that link turns into wrong stock figures. We size the links against real throughput and monitor the lag.
Fort Bliss is one of the Army's largest installations, with a regional medical center, a teaching health sciences campus, and the University of Texas at El Paso around it. Clinical and student systems run continuously, so integrity checks go into quiet hours.
El Paso holds consumer-products and retail distribution plus multi-site service businesses across the region. These break where the application meets the database: a timeout dressed up as a network fault. We rewrote one procedure and cut it from 38 seconds to 1: see case #1 below.
We work with organizations across the region: El Paso, Socorro, Horizon City, Canutillo, San Elizario, Fabens, and Anthony, out to Las Cruces and Santa Teresa in New Mexico, and statewide across Texas, all over secure remote access. Work is booked around your shift pattern on Mountain Time.
Principal-grade input on an architecture, edition, or replication decision an El Paso team is about to lock down. 20 hours now saves a rebuild later.
From $4,995 / 20-hr block (hours do not expire)Senior administrators holding the estate day to day: alerting, patching, restore verification, replication-lag watching, and index and statistics work.
From $395 / moThe engineer who picks up has already met this failure, with a 15-minute response for Managed Services and Emergency Services clients.
From $2,500 / incidentThe workload ranked by daily cost, then indexed, re-keyed, or rewritten. Some statements need the SQL changed rather than an index added, and we treat that as ordinary work.
Version moves, Azure SQL, or AWS RDS, cut over on a schedule your customers never notice. Extended support for SQL Server 2016 stops on July 14, 2026, and 2017 in October 2027.
145 read-only checks across configuration, backups, security, and query cost, handed back in the order that repays fastest. The same audit runs on your own instance free.
Recovery measured rather than assumed. We design and tune clusters and Always On Availability Groups, and apply log shipping, replication, or Change Data Capture (CDC) when only changed rows should cross a slow link.
Groundwork on the databases your team wants an assistant reading, whether ChatGPT (OpenAI) or Claude (Anthropic), plus the RAG pipelines, vector search, and analytical traffic those tools aim at SQL Server. When reporting starts squeezing transactions, we move the offload, SSRS and Power BI datasets included, onto Snowflake, Redshift, or the warehouse you run today.
"We view Red9 as an extension of our IT department. We utilize Red9's SQL Server expertise and service in multiple ways. They monitor/manage our SQL Server performance, making suggestions when necessary. We use Red9 for support when we encounter issues. And we utilize Red9 as a resource in our application development changes to make certain our SQL statements are efficient. Their team is responsive, knowledgable and care about their level of service."
"Red9 has exceptional depth in systems and has demonstrated that they can provide solid architectural direction for the environments and for the projects. Great work."
"Red9 is fair and honest on how they treat both fellow team members and our internal customers."
Four stages, counted in days, and the senior DBA who audits the estate is the one who changes it. Nothing is committed until you hold the ranked plan and its price.
Which instances the business depends on, what the symptom looks like from a user's chair, and what was deployed shortly before it started. The timing question closes most cases.
145 checks over instance configuration, whether backups restore inside your target, where security is exposed, and what every statement costs a day, ranked by return. Curious first? Run the same read-only audit against your own instance at no cost from our self-serve Health Check.
One walk through the report in priority order, with hours and cost against each line, and you finish holding a ranked plan and a number that will not move.
Approved, we work the plan and capture readings on both sides of each change, which makes every gain checkable in your own tooling. Managed services afterwards keep the estate steady.
Three real Red9 projects, each carried from the opening look to the closing measurement. The clients recorded every figure themselves, before and after. Names are kept out because that was the agreement.
The problem. An automotive services chain had a stored procedure taking 38 seconds to run, long enough that the application timed out before it returned. Inside, the procedure scanned the same tables repeatedly and pulled far more data than the result needed: 687,475 logical reads and 60,663 ms of processor time on every execution.
What we did. We rewrote it. The single WHERE clause was trying to satisfy several different access patterns at once, which left the optimizer no selective predicate to work with. Splitting the logic into a second SELECT joined by UNION ALL gave each branch a filter an index could serve, and we added the index that branch needed.
60,663 ms of CPU down to 922 ms for the same result set.
The result. The procedure returns inside a second and reads 314 pages instead of 687,475, so the application no longer times out on it. The processor time it used to burn, more than a minute per call, went back to everything else on the server.
What the plan showed. One predicate covered several access patterns, so the optimizer chose a scan for all of them and did it more than once per execution. That is why the read count came in 2,189 times larger than the answer required.
What we changed (identifiers generalized for privacy):
-- Procedure: 38 s per run, 687,475 reads, application timing out. -- before: one SELECT, one WHERE clause covering several access patterns -- after : split into two selective branches SELECT ... FROM dbo.[work_orders] WHERE branchId = @branchId AND statusCode = @status UNION ALL SELECT ... FROM dbo.[work_orders] WHERE customerId = @customerId AND statusCode = @status; -- supporting index added for the second branch; prior proc text retained as rollback
Each branch got a predicate an index could seek on. Duration fell from 38 seconds to 1 and reads from 687,475 to 314.
The problem. A property software company had three heavy statements on its production database, and the worst was not the slowest. A small function was being called about 2,500,000 times a day at 7 ms of CPU each, which added up to roughly five hours of processor time a day on its own. Two further statements were running long on top of that, one a few hundred times a day and one a few thousand.
What we did. We tuned all three with covering and nonclustered indexes matched to their predicates. The headline change was the frequent one: cutting 7 ms of CPU per call to 1 ms across two and a half million executions gives back about 4.3 hours of SQL work daily, and nothing about the application had to change.
About six more minutes a day back, at roughly 6,000 executions.
The result. More than four hours of daily processor time came back on a server that was previously spending it on a call nobody had flagged. The other two statements improved alongside it, worth another eight minutes a day between them.
What the review found. The frequent call was CPU-heavy: its logical read count barely moved, so the cost sat in the work it repeated on every call. What it lacked was an index letting it find the right row directly, so it paid for extra work two and a half million times a day.
What we changed (identifiers generalized for privacy):
-- Query #2 (headline): ~2,500,000 exec/day, 7 ms CPU each, ~5 hrs/day. CREATE NONCLUSTERED INDEX IDX_RED9_Answer_ID ON main.[Answer] (id); -- Query #1: a few hundred exec/day, covering index on the subscription key CREATE NONCLUSTERED INDEX IDX_RED9_MemberSubscriptionData_SubscriptionID ON main.[MemberSubscriptionData] (subscriptionId); -- Query #3: ~6,000 exec/day, 93 ms -> 34 ms (covering index) -- rollback: DROP INDEX scripts provided for all three
Three indexes, no application change, and about four and a half hours of daily SQL work removed between them.
The problem. A beverage distributor ran a promotions query joining promotion sections, codes, and customers against an orders table, filtered on a sales-history date with no adequate index behind it. At roughly 34 runs a day it averaged 1,874.96 ms and 268,545 reads per execution, which came to about 9.1 million pages a day.
What we did. We created a nonclustered index on the sales-history date column with seven columns included, chosen so the query never leaves the index for the fields it returns. Query Store supplied the before-and-after readings.
1,853.75 ms of CPU down to 137.37 ms, almost all of it read work.
The result. The promotions query answers in under 140 milliseconds, and it stopped issuing 8.6 million logical reads a day. Because the included columns cover the output, the plan stays a seek as the orders table grows, and we retest it as the data shifts.
What the review found. The filter sat on a sales-history date on the orders table, and the existing indexes did not lead with that column, so the plan scanned and then looked up seven more fields per qualifying row. That combination produced 268,545 reads per execution.
What we changed (identifiers generalized for privacy):
-- Promotions query: ~34x/day, 1,874.96 ms avg, ~9.1M reads/day. CREATE NONCLUSTERED INDEX IX_Red9_Orders_SalesHistoryDate ON dbo.[Orders] (salesHistoryDate) INCLUDE (isToDistributor, ticketNumber, isVoided, shippedDate, toCustomerId, waitingForWhat, enteredById); -- rollback: DROP INDEX IX_Red9_Orders_SalesHistoryDate provided
Leading with the filtered date and carrying the output columns turned the scan into a range seek: 137.41 ms and 14,969 reads a run.
Those readings all belong to other companies. Half an hour is enough for us to read yours.
Get a Free SQL Server Assessment ➜Rather talk it through? A senior DBA answers at 1-877-891-1870.
15 years or more behind whoever reads your plans, and the same person all the way through.
We have worked SQL Server and nothing else since 2014, across 10,000+ audited databases.
Duration, reads, and CPU taken either side of every change, in tools your engineers can run.
Any hour, any day, Managed Services and Emergency Services clients reach a senior DBA within 15 minutes.
Yes, and that is the honest case for remote in this city. A senior DBA stays reachable through your entire El Paso workday on Mountain Time, with 24/7/365 emergency cover on top for Managed Services and Emergency Services clients. Access remains under your control: connections arrive over your VPN or bastion host on least-privilege logins you create and can pull at once, with further controls above that, and every change comes as a script your engineers read before it runs.
How the three options hold up on the morning an El Paso production database starts holding trucks at the gate.
| Red9 | In-house DBA hire | Generalist IT / MSP | |
|---|---|---|---|
| Seniority | Principal-grade SQL Server specialists averaging 15+ years, with no junior tier beneath them. | One hire owns the discipline, and the local pool of senior SQL Server people is small. | Generalists who touch SQL Server between many other systems. |
| SQL Server focus | SQL Server is all we do. | Divided across every other platform the role covers. | One line on a broad services list. |
| Emergency response | Staffed round the clock all year, with a 15-minute response for Managed Services and Emergency Services clients. | Limited to one person's waking hours in one time zone. | A shared queue where your outage waits behind everyone else's. |
| Proof | Readings captured around each change and reproducible by your own team. | Rarely written down in a form anyone can audit. | Described in a report rather than measured. |
| Cost model | By project, by month, or by incident, with nothing carried on payroll in between. | A loaded El Paso salary of roughly $100,000 to $125,000, plus benefits and the search first. | Bundled into a larger invoice with no database line to inspect. |
| Ramp-up | Working your estate inside the week. | A recruiting cycle of months, then months of ramp. | Slow to engage, and the background gets repeated on each ticket. |
Senior SQL Server cover can be running before your next month-end. Get a Free SQL Server Assessment ➜
Founder & Partner
25+ years making SQL Servers faster.
Chief Operating Officer
Chief Revenue Officer
Beneath them sits a senior-only DBA bench averaging 15+ years, with one named lead accountable for your outcome from start to finish.
We support El Paso teams over secure remote access, across the city, Socorro, Horizon City, Canutillo, San Elizario, and out toward Las Cruces. The same senior DBA answers whether the instance sits downtown, in a warehouse near the bridges, or on a campus network.
Coverage runs across the El Paso region and the rest of Texas. Explore the areas we serve.
Five checks worth running when the shortlist is short.
Ask what share of their year is SQL Server. In a small market, a generalist is often the only option offered, so make them prove otherwise.
Get the name and the years for whoever holds the credentials, and confirm the person does not change after signature.
Mountain Time puts El Paso an hour off most of Texas. Ask which hours a senior DBA is genuinely on duty rather than which hours the brochure claims.
Response time and who qualifies for it, stated as numbers inside the agreement.
Estates here often span sites and a border. Ask how they measure replication lag and what they do when it grows.
| 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 | El Paso, the Borderplex, and statewide Texas, plus nationwide via secure remote access |
Yes, and remote is the honest answer for this market. Red9 covers El Paso and the surrounding communities, from the central business district out through Socorro, Horizon City, Canutillo, San Elizario, and Fabens, with a senior SQL Server consultant on the account. El Paso sits a long way from every other Texas metro, so the list of specialists within driving distance is short, and secure remote access puts one on your instance without the travel. Emergency response for Managed Services and Emergency Services clients runs to 15 minutes.
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 ➜
Start with the free 145-point health check, which is what puts a real number on the work instead of an estimate. Managed services and remote DBA then run from $395/mo, a 20-hour senior DBA block is $4,995 and the hours do not expire, and 24/7 emergency response begins at $2,500 per incident. Against a loaded El Paso DBA salary of $100,000 to $125,000, set out in the comparison above, a month of retainer runs about four percent of a month of that role, and it covers nights as well. Larger scopes get priced after the check.
Latency and time zones, usually in that order. Replication and Change Data Capture feeds that behave on a local network start queueing across a slower circuit, and the backlog shows up as stale inventory instead of an error. Time zones cause the quieter damage: El Paso runs on Mountain Time while much of the operation around it does not, so batch windows and date-only columns stop lining up. We size the link against real throughput and pin the boundaries explicitly.
Often, and a rewrite is worth testing before a bigger server. A procedure that scans the same tables several times over usually has one WHERE clause doing too many jobs at once; splitting it so each branch gets a selective predicate lets the engine use an index for each. One procedure shaped that way, in case #1 above, went from 38 seconds to 1 second, with reads falling from 687,475 to 314, and the application stopped timing out.
Six milliseconds times two and a half million is over four hours of processor time every day. At that frequency the per-call figure stops being the interesting number and the daily total takes over, which is why we rank workloads that way. A function running 2,500,000 times a day, shown in case #2 above, came down from 7 ms of CPU per call to 1 ms, and gave back about 4.3 hours of SQL work daily.
Yes. El Paso nonprofits and government agencies get the free 145-point health check on the same terms as any commercial client, and it returns 145 findings ordered by risk with a price beside each, written to be read in a board meeting or a county budget session. Managed services and remote DBA run from $395/mo. A 20-hour senior block is $4,995 and the hours do not expire.
The general questions, which versions and platforms we support and how an engagement is structured, are answered on our SQL Server consulting page.
Half an hour is enough to show where your SQL Server gives up speed, uptime, and money, and what recovering each of those takes. The free SQL Server assessment lays the findings and the figure out before anything is agreed.
Schedule My Call Now ➜Rather talk it through? A senior DBA answers at 1-877-891-1870.
