Red9

SQL Server Consulting, managed services, and emergency support from expert DBAs.

At Red9, we specialize in SQL Server consulting and management, helping businesses from startups to Fortune 100 companies optimize their data environments. Founded in 2014 in Atlanta, Georgia, our team brings decades of combined experience to ensure your SQL Server runs securely and efficiently. We offer a full range of services: SQL Consulting, Managed SQL Services, Emergency SQL Support, Perform

ance Tuning, Database Migrations, and Upgrades. Our focus is on delivering practical solutions that solve real problems, backed by our reputation as a trusted Microsoft Partner across 44+ industries. At Red9, we don’t just maintain your systems—we enhance them, ensuring your data is secure and your business runs smoothly. Connect with us at Red9 to see how we can help take your SQL Server management to the next level.

11/07/2025

"The server is fine now. But it was slow earlier. Can you check what happened?"

This might be the most frustrating sentence in database troubleshooting.

By the time you investigate, the problem vanished. Evidence gone. Metrics normalized.

Common causes of intermittent slowness:

Noisy neighbor problems. Other applications spike resources during processing windows. Then release them.

Locking issues. Queries waiting on locks from batch processes. Process finishes. Everything fast again.

Batch jobs. Large data imports spiking resource usage temporarily.

Statistics updates. Asynchronous statistics changes breaking ex*****on plans. New plans eventually stabilize.

The challenge? You can't troubleshoot what you can't observe.

We had one case that took 2.5 months to diagnose. Server stable for two weeks. Then randomly slow for days. Cycle repeated every 2-3 weeks.

Turned out to be statistics updates on hundreds of millions of rows changing ex*****on plans unpredictably.

Intermittent issues require pattern recognition. But patterns take time when cycles happen every few weeks.

You're troubleshooting a ghost that only appears when you're not watching.

11/04/2025

Monitoring tools get deployed in minutes. Next, next, next. Done.

Then the alerts start. 47 a day. Half are noise. The rest get ignored. And the one that matters? Missed.

This happens because monitoring tools ship with generic defaults.

They don't know your backup schedules, your maintenance windows, or your index jobs. They just fire alerts.

We tune these tools so they stop screaming and start helping.

Takes a few days to dial in the thresholds, disable the noise, and sync with your environment.

After that? Only alerts that matter.

Monitoring tools aren't magic.

They're amplifiers.

Configure them wrong and they amplify chaos.

Configure them right and they amplify signal.

10/17/2025

Your SQL Server is sharing resources with IIS, application servers, and other workloads right now.

This causes unpredictable performance, resource fights, and reliability headaches that cost you real money. We see this constantly.

Companies running multiple applications on the same SQL Server box.

One client was told they needed a $311,000 hardware upgrade. Their 64 CPU server was struggling with performance.We moved IIS to a separate server. Performance doubled immediately.

No hardware needed.SQL Server needs dedicated resources.

Two ways to fix this:

Migrate SQL to a new dedicated server
Remove everything non-SQL from your current box

The highest-performing SQL environments run dedicated servers.

No roommates. No resource fights.

Is your SQL Server sharing space it shouldn't be?

10/15/2025

You're probably paying for 3x the SQL Server capacity you actually use.

Client came to us running 32 cores on bare metal. Massive over-provisioning because adding hardware later meant weeks of procurement and licensing headaches.

We found they were using 25% of their compute capacity.

Moved them to Azure SQL with 8 vCores. Same performance. 15 minutes downtime. Zero issues post-migration.

Why could we cut 75% of their cores? Cloud changes the equation. Need more power? Click a button. No procurement cycles. No fear-based decisions.

They saved thousands monthly on licensing. Got better reliability than their old setup. Fixed their file server latency by moving to Blob Storage.

Infrastructure decisions driven by fear cost you real money every month.

10/02/2025

Database: crawling at 0.001 mph

DBA: "Have you tried adding an index?"

Database: suddenly ⬇️

09/23/2025

SQL Server 2025 just dropped in public preview.

Microsoft calls it their most developer-friendly release in a decade.

After digging through the features, they might be right.

Here's what caught our attention:

- AI built into the database engine (vector search, hybrid queries)
- Native JSON type (finally, no more NVARCHAR hacks)
- RegEx support (POSIX-compliant)
- 70% performance gains on CPU-bound queries
- Security by default (TLS 1.3, PBKDF2 hashing)
- Real fixes for parameter sniffing and locking issues

The performance improvements alone make this worth testing.

Derek Wilson's team solved the 40-year-old Halloween Protection bug.

Runtime dropped from 6 seconds to under 3, with 80MB less tempdb usage.

For enterprises sitting on 2019 or 2022: this might be the upgrade that's hard to ignore.

We broke down all the details, including what it means for your infrastructure decisions and compliance requirements.

https://lnkd.in/e6k4MR7x

What's your take? Planning to test 2025 or sticking with your current version?

09/19/2025

"Deploy and forget" databases are expensive mistakes.

Just finished a 3-week SQL Server performance project that shows what happens when databases get abandoned after deployment.

The client's system had missing indexes, poor configuration, and one massive problem: their replication setup was copying data but skipping all non-clustered indexes.

Every performance improvement kept disappearing overnight.

The results after we fixed it:

CPU time dropped from 20+ million to 2.5 million (87.5% reduction)
Massive reduction in logical reads across all queries
Same workload, dramatically better response times
Found an additional optimization layer for 100-200% more improvement

Week 1-2: Standard performance tuning, but changes kept reverting

Week 3: Found the root cause - replication wasn't copying indexes

After fix: Persistent improvements that actually stick

The business impact? Client can either handle way more concurrent users or move to a cheaper server and cut cloud costs.

Your database needs the same attention you give your application code. SQL Server performance tuning works when you fix the fundamentals first.

Stop treating your database like infrastructure you can ignore.

Red9 helps enterprise clients identify and fix the performance bottlenecks that are costing you money every day.

09/17/2025

Are you wasting thousands on SQL Server Software Assurance?

Most companies automatically renew SA without questioning if they actually need it. We see this all the time.

One client was paying $7,200 yearly for Software Assurance on a SQL Server system they hadn't upgraded in six years.

They dropped SA and saved that money for performance tuning that actually improved their business operations.

Software Assurance makes sense if you:

Upgrade SQL Server every 4-5 years
Need passive DR replicas
Plan to migrate to Azure
Run dense virtualization

Skip it if you:

Keep SQL versions for 7+ years
Have no cloud migration plans
Run stable workloads with no changes planned

The math is simple: SA adds 20-25% to your annual licensing costs. Over three years, you pay 60-75% more than the base license cost.

Stop funding Microsoft's R&D if you're not using the benefits.

Ready to audit your SQL Server licensing strategy?

Red9 helps enterprise clients make data-driven decisions about SA investments and find better ways to optimize database performance.

09/09/2025

We see the same performance killers across so many databases.

Legacy applications are killing people.

Look, these older systems have handwritten queries that nobody optimized properly.

Poor code quality from frameworks that were outdated 10 years ago. The biggest problem is you can't fix the application code. Vendor completely locks you out.

Modern apps? Just as bad, different reasons.

Auto-generated queries by frameworks that don't know what they're doing. Terrible data modeling decisions.

Implicit conversions everywhere because someone picked the wrong data types and now you're burning memory like crazy.

The pattern is always the same: "Give us tables, we need to start pushing data." Zero time for proper schema design. Then six months later - surprise! - performance is garbage.

There’s a couple of good examples from our clients..

One actually gets it. They develop their own stuff, release twice monthly, and here's the crazy part - they listen to our recommendations. Result? Their "high season" nightmare completely disappeared.

But then there's another. One company running their entire B2B operation on legacy CRM.

Application vendor won't touch anything. We had to fix everything through indexing alone. Their SQL Server upgrade? Took a year and a half because the vendor couldn't handle migration complexity.

Every single onboarding, we see either old school mess or new school poorly implemented code.

Even the clients with good code can have data structure problems.

Application vendors resist improvements because they painted themselves into a corner. They promise customizations, then get stuck maintaining multiple versions. One custom feature means developing for two codebases forever.

Some performance problems aren't SQL Server issues.

They're application decisions made years ago that you're now stuck with.

09/04/2025

Banking vs Data Warehousing: Why your SQL Server settings should be completely different.

A lot of CTOs we talk to use the same configuration for everything. Which can be a costly mistake.

Why?

In banking environments, you need lightning-fast transactional processing.

ATM withdrawals. Credit card purchases. Account transfers.

Simple queries that need immediate response times.

You DON'T want one heavy report consuming all your CPUs while customers wait.
So for example, we set:

Cost Threshold: Higher (25-50)
Max-DOP: Conservative (25-50% of CPU cores)

Higher cost thresholds prevent small transactional queries from unnecessarily going parallel, reducing overhead while allowing larger queries to still benefit from parallelism when appropriate.

Conservative Max DOP settings ensure critical transactions get consistent response times.

But data warehousing?
Completely different ballgame.

You're running complex analytical queries across massive datasets.

These queries are SUPPOSED to be heavy.

You WANT them using multiple CPUs efficiently when appropriate.

So the settings adjust:

Cost Threshold: Much higher (100-500)
Max-DOP: Unlimited Utilizations

Remember, SQL Server's default cost threshold is just 5 - far too low for most production environments.

For data warehousing, much higher thresholds prevent smaller support queries from going parallel while allowing truly large analytical queries to utilize multiple cores effectively.

One size doesn't fit all.

Your environment determines your optimization strategy.

We've seen companies waste significant resources using OLTP settings for analytics servers.

Or worse, using default settings for everything.

The result? Slow performance everywhere and inflated cloud bills.

Know your workload.

Configure accordingly.

Proper tuning can deliver substantial cost savings.

Address

11720 Amber Park Drive, STE 160
Alpharetta, GA
30009

Website

https://red9.com/

Alerts

Be the first to know and let us send you an email when Red9 posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Want your business to be the top-listed Business in Alpharetta?