Stop dealing with database outages and slow queries. Red9 provides Buffalo organizations with senior database administrators who make performance problems disappear. You get 15+ years of expertise and zero junior handoffs. 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 Buffalo: the short answer
Red9 runs senior-only SQL Server consulting, performance tuning, managed DBA services, and emergency response for organizations across Buffalo and Western New York, including Amherst, Cheektowaga, Tonawanda, West Seneca, Hamburg, Orchard Park, and Niagara Falls. Since 2014 we have worked this engine and no other. The free 145-point health check starts every engagement. There are 120+ clients on our list, from seed-stage startups up to the Fortune 100; Managed Services and Emergency Services clients get a production incident answered inside 15 minutes, and every change carries a measurement on each side.
Need a SQL Server consultant covering Buffalo and Niagara? Book your free assessment.
Western New York carries an unusual mix: a bank holding company downtown, a cancer center and three hospital systems on one medical campus, engine plants along the river, and the second-busiest truck crossing on the northern border.
Kaleida Health and Roswell Park anchor the Buffalo Niagara Medical Campus, with University at Buffalo researchers alongside them and Catholic Health across the region. These estates run continuously and get judged on failed jobs and blocking, which is the ground case #1 below covers.
M&T Bank runs from downtown Buffalo with regional insurers around it, and the metro holds a lot of processing work nobody sees. These fail quietly: a nightly reconciliation that took 20 minutes now takes three hours. We find those and rebuild them.
Ford stamping at Woodlawn, GM's Tonawanda engine plant, and the aerospace and motion-control suppliers toward East Aurora run production and quality data on SQL Server. Add the customs brokers at the Peace Bridge and a slow lookup stops a truck. We tune those paths around the shift pattern.
Rich Products and Delaware North both grew up here, and around them sit venues, clubs, and food operations with modest servers, heavy transaction rates, and no downtime on an event weekend. One high-frequency query we tuned ran 2,000 times a day. Case #3 below has the figures.
We work with organizations across Western New York: Buffalo, Amherst, Cheektowaga, Tonawanda, West Seneca, Hamburg, and Orchard Park, out to Niagara Falls, Lockport, and Jamestown, and statewide across New York, all over secure remote access. Maintenance windows get set around your shift calendar on Eastern time.
A principal-grade read on the architecture, edition, and capacity decision sitting on a Buffalo team's desk. Cheap to argue about now, expensive to undo in 18 months.
From $4,995 / 20-hr block (hours do not expire)Senior administrators owning the daily grind: alert triage, failed-job chasing, patching, restore verification, index upkeep. It runs whether the roads do or not.
From $395 / moThe person answering has already fixed this failure somewhere else, with a 15-minute response for Managed Services and Emergency Services clients.
From $2,500 / incidentStatements ordered by what they cost per day, then covered, rewritten, or re-keyed. Blocking and deadlocks get the same treatment, because they are a locking design problem rather than a hardware one.
Version jumps, Azure SQL, or AWS RDS, scheduled so customers notice nothing. Extended support for SQL Server 2016 ended July 14, 2026, and 2017 goes in October 2027, so a 2016 instance is already past its window.
145 read-only checks spanning configuration, backup restorability, security exposure, and query cost, returned ranked by payback. The same audit is yours to run against your own instance for free.
Failover that has been rehearsed and timed. We design and tune clusters and Always On Availability Groups, and use log shipping, replication, or Change Data Capture (CDC) where only the changed rows have to move.
Preparation on the databases your team wants an assistant reading, ChatGPT (OpenAI) or Claude (Anthropic), plus the RAG pipelines, vector search, and analytical load those tools aim at SQL Server. When reporting starts crowding out transactions, we shift the offload, SSRS and Power BI datasets and all, onto Snowflake, Redshift, or the warehouse you already have.
"What a rare, great feeling it is to know when you hand off a project to someone, you can sit back and simply expect the best possible outcome. Red9’s cool confidence and eagerness to deliver results are surpassed only by their deep penetrating knowledge of SQL. Whether it's SQL design, development, optimization, or recovery, Red9 is a SQL Gem."
"Update on daily reboots. We stopped reboot last weekend and we didn’t face any issues."
"The team made major performance improvements to several database servers based on Red9's work/research. They were also instrumental in refining our interviewing process for SQL candidates."
Four stages, days apart rather than weeks, and the senior DBA who runs the audit stays on to do the work. The ranked plan and its price arrive before any commitment does.
Which instances the business depends on, how the symptom looks to the people living with it, and what changed just beforehand. That last one answers most cases.
The audit reads 145 points: instance configuration, whether the backups restore inside your target, where security is open, and what each statement costs a day, all ranked by return. Curious ahead of a call? Point the same read-only audit at your own server for nothing via our self-serve Health Check.
We go through the report line by line with the hours and the cost attached. You come away with a ranked plan and a fixed figure.
Once approved we work the plan, recording readings either side of every change so your team can confirm each gain. Managed services then hold the estate steady instead of letting it drift back.
Three actual Red9 projects, each tracked from the first review through to the closing figure. Each reading came out of the client's own monitoring, on both sides of the work. We keep the names back because they asked us to.
The problem. A medical device manufacturer's production instance had a rough February. Alert volume climbed 83.5% to 167 for the month, one of them a P1 blocking-query incident, deadlocks stayed elevated at 1,133, SQL errors rose 52% to 16,575 with 7,276 of those a new data-truncation fault in one table, and storage latency began drifting from 15-20 ms toward 25-30 ms. On top of that, VPN and directory permission changes were locking our own DBAs out of the server they were supposed to be watching.
What we did. Access came first: we worked through several VPN and zero-trust configurations with the client's MSP until administrative access was stable again. Then we handled the 167 alerts, contained the P1 blocking incident and 25 P2s, cleared the failed-job backlog, opened a storage-latency investigation on the rising numbers, and took the truncation errors to the application team as a code fix rather than a database patch.
Throughput held flat through the whole stability push.
The result. The instance ended the month with one failed job instead of 10, the blocking incident closed, and the truncation errors owned by the team that could actually fix them. Throughput held flat while all of this was cleaned up: 736.3 million transactions went through the instance.
What the month looked like. Of the 16,575 SQL errors that month, 7,276 were data-truncation failures in one table, and that is an application contract problem for the app team to own. The P1 was a single long-running statement holding locks across a busy window; killing it restored service, and the query itself went onto the tuning list.
How the month was worked (findings summarized, identifiers withheld):
-- Managed services month, production instance -- P1 blocking : one long-running statement holding locks; contained, then tuned -- P2 x25 : IO and read-latency alerts, deadlock events, failed jobs -- errors : 16,575 total; 7,276 = truncation in one table -> app team -- jobs : 10 failing -> 1 -- storage : latency 15-20ms -> 25-30ms, investigation opened
Each item carried an owner and a next step, so the client could see which faults were ours to fix and which belonged to the application or the storage vendor.
The problem. A banking and fintech provider had a customer account-activity summary running about 90 times a day at 1,774 seconds each. That is nearly half an hour per execution and roughly 44 hours of SQL processing time a day, with 8,338,727 logical reads behind every run.
What we did. We built a covering nonclustered index on the transaction-date column of the account-activity table, with the four columns the query returns included so the engine never has to leave the index. Testing ran on a restored copy with production-matched parameters, before-and-after came from Query Store, and a DROP INDEX rollback went over with it.
8,338,727 pages down to 184,309 for the same result set.
The result. A statement that used to run for half an hour finishes in under a minute, and the 43 hours of daily run time behind it comes back to the rest of the workload once the index ships to production. Read volume per run dropped by more than eight million pages.
What the review found. The query summarized file and transaction activity by customer, filtering on a transaction date with no index on that column. Every one of its ~90 daily runs scanned the whole account-activity table and then looked up four more columns per qualifying row.
What we changed (identifiers generalized for privacy):
-- Account-activity summary: ~90x/day, 1,774 s avg, 8,338,727 reads/run. CREATE NONCLUSTERED INDEX IX_Red9_AccountActivity_DateTxn ON dbo.[account_activity] (dateTxn) INCLUDE (customerName, customerNumber, dateInserted, fileName); -- rollback: DROP INDEX IX_Red9_AccountActivity_DateTxn provided
With the date indexed and the output columns carried along, the scan became a range seek: 44 seconds and 184,309 reads.
The problem. A membership sports club had a cluster of high-frequency statements on its club-management server. The worst ran about 2,000 times a day at 617 ms and 31,615 reads apiece, another sat at 149 ms, and the instance was logging errors in the low thousands each month.
What we did. Two indexes went in for the top statements, TempDB got reconfigured, and we assessed replication as a way to push the read-only reporting workload off the transactional instance, and costed an availability group with a readable secondary as the alternative. 23 hours of senior time covered the lot.
On roughly 2,000 runs a day, with a second statement cut from 149 ms to 86.
The result. The busiest statement now costs 27 ms and 44 reads, and the second one improved alongside it. Error volume also fell 41% in the same period, with no demonstrated link to the indexes. The club also left with a costed option for moving reporting off the transactional server rather than continuing to tune around the conflict.
What the review found. Two hot statements on the club-management database were scanning for want of a matching index, and TempDB was configured with a single data file against a workload that leaned on it heavily. Reporting queries were also running against the same instance as member transactions.
What we changed (identifiers generalized for privacy):
-- Query #1: ~2,000x/day, 617 ms, 31,615 reads. Query #2: 149 ms. CREATE NONCLUSTERED INDEX IX_Red9_member_activity_lookup ON dbo.[member_activity] (memberId, activityDate) INCLUDE (activityType, amount); -- second index added for Query #2; TempDB split across multiple equal data files -- replication assessed for read-only reporting; AG sizing costed separately -- rollback: DROP INDEX scripts provided for both
Query #1 fell to 27 ms and 44 reads, Query #2 to 86 ms, and the TempDB change took contention off the shared workload.
All three sets of readings came off other companies' instances. Spend 30 minutes with us 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 reads the plan and writes the fix. Nobody serves an apprenticeship on your production instance.
This engine only, since 2014, across 10,000+ audited databases.
Duration, reads, and CPU logged before the change and again after, in tooling you already run.
Snow day or holiday, Managed Services and Emergency Services clients get a senior DBA inside 15 minutes.
No, and in a city that loses roads for days at a time it helps: remote is how virtually every client of ours works. A senior DBA stays reachable through your full Buffalo workday on Eastern time, with 24/7/365 emergency cover on top for Managed Services and Emergency Services clients. You keep control of access the whole way: connections come over your VPN or bastion host on least-privilege logins you issue and can pull in seconds, with more controls above that, and every change arrives as a script your engineers review first.
How the three choices behave on the day a Buffalo production database becomes the whole company's problem.
| Red9 | In-house DBA hire | Generalist IT / MSP | |
|---|---|---|---|
| Seniority | Principal-grade SQL Server specialists averaging 15+ years, and no junior layer under them. | One hire carries every database in the building. | Generalists who reach SQL Server between other platforms. |
| SQL Server focus | SQL Server is all we do. | Diluted by whatever else the role absorbs. | One product among a long supported list. |
| Emergency response | Every hour of every day, and a 15-minute response for Managed Services and Emergency Services clients. | Only what one person covers when awake and in town. | A queue measured in hours. |
| Proof | Before-and-after readings your own engineers can reproduce. | Seldom captured anywhere shareable. | Summarized rather than measured. |
| Cost model | Scoped project, monthly retainer, or single incident, and no headcount to defend. | A loaded Buffalo salary near $105,000 to $130,000, plus benefits and the vacancy first. | Absorbed into a wider invoice where the database share stays hidden. |
| Ramp-up | Inside the estate within days. | Months of recruiting, then months of ramp. | Slow to engage, and the history gets retold each ticket. |
Senior SQL Server cover on a Western New York estate can be running inside a week. Get a Free SQL Server Assessment ➜
Founder & Partner
25+ years making SQL Servers faster.
Chief Operating Officer
Chief Revenue Officer
Working under them is a senior-only DBA bench averaging 15+ years, and one named lead owns your result end to end.
We support Buffalo-area teams over secure remote access, across the city, Amherst, Cheektowaga, Tonawanda, West Seneca, and Orchard Park. The same senior DBA picks up whether the instance sits downtown, on the medical campus, or at a plant along the river.
Coverage runs across the Buffalo metro and the rest of New York. Explore the areas we serve.
Five things worth establishing before anyone gets a login.
Ask what proportion of their billed work is SQL Server. Every hour of ours has gone into SQL Server since 2014.
Names and years, confirmed in writing, and a commitment that the same person stays after the contract is signed.
Ask who watches the estate when your building is shut. A single hire is one vacation or resignation away from unavailable.
The response time and who it applies to belong in the agreement, in numbers.
Ask to see a report where something got worse. A vendor who only shows wins is editing.
| 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 | Buffalo, Niagara, and Western New York, plus nationwide via secure remote access |
Yes. Red9 covers Buffalo and the wider Western New York area, out through Amherst, Cheektowaga, Tonawanda, West Seneca, Orchard Park, and up to Niagara Falls, and a senior SQL Server consultant stays on the account. Remote is how nearly all of our clients operate, which matters more here than in most markets: a February storm does not sit between your instance and the DBA working on it. Managed Services and Emergency Services clients also carry a 15-minute emergency response.
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 free 145-point health check comes before any number, because scoping without evidence is guessing. Then managed services and remote DBA run from $395/mo, a 20-hour senior DBA block is $4,995 and the hours do not expire, and 24/7 emergency response starts at $2,500 per incident. Weigh that against a loaded Buffalo DBA salary of $105,000 to $130,000, which the comparison above lays out, and a month on retainer costs about four percent of a month of that hire. Bigger programs are priced once the check is in.
We are, from outside the snow belt, which is the practical argument for remote coverage in this city. Managed Services clients get alerting, failed-job triage, blocking and deadlock response, and patch scheduling that carries on whether the Thruway is open or shut. On one estate we run, described in case #1 above, monthly failed jobs went from 10 to 1 while 167 alerts were handled in the same period, including a P1 blocking incident.
Rarely. A statement sitting at 29 minutes is usually scanning a large table, and the plan, the row counts, and the waits tell us why before we touch anything. We read the plan, confirm what the query genuinely needs, and cover it. One 1,774-second query in case #2 above came back in 44 seconds after a single covering index, with reads down from 8,338,727 to 184,309.
Three, in ascending order of effort. Tune the reports first, because a lot of reporting pain is one bad plan, and fixing it can remove the need for anything else. Next, distribute the read-only workload with replication or a readable secondary so analysts stop competing with order entry. Last, move the offload properly, SSRS and Power BI datasets included, onto a warehouse. We size which of the three you actually need before quoting any of them, which is how case #3 above was scoped.
Yes. Buffalo nonprofits and government bodies get the free 145-point health check on the same terms as everyone else, and 145 findings come back ranked by risk with a cost against each, written to be read straight into a board or county meeting. 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, cloud platforms, and how a standard engagement is structured are all on our SQL Server consulting page.
30 minutes is enough to show you where your SQL Server is losing speed, uptime, and cash, and what each of those costs to recover. The free SQL Server assessment gives you the findings and the figure first, with no obligation attached.
Schedule My Call Now ➜Rather talk it through? A senior DBA answers at 1-877-891-1870.
