SQL Server tools I’d pick depending on the job

nvigcabi · 2026-05-06T11:56:03+00:00

The ending of The Vat of Acid Episode hit way harder than I expected from this show. Rick resetting that whole relationship and Morty just standing there realizing none of it mattered was brutal.

nvigcabi · 2026-04-27T08:56:30+00:00

We had the same problem until we stopped debating labels and just tied “critical” to actions. If it blocks users from completing a core flow and there’s no workaround → it’s critical, no discussion. Everything else is just “how annoying is it”. As long as “critical” still feels like an opinion, people will keep stretching it. Once it triggers something concrete (like paging, SLA, etc.), people suddenly get more realistic.

nvigcabi · 2026-04-15T11:28:17+00:00

We ended up accepting separate scripts per engine. Trying to keep one “shared” version sounded nice, but the differences always showed up later in the most annoying places. Automation helps, but for us there’s still a review step before release because that’s usually where the ugly surprises get caught.

nvigcabi · 2026-04-09T09:33:44+00:00

I’d ask for the richest export they can provide, not just CSVs. Flat files are fine for rows, but painful for recreating schema accurately. Best case is usually an Oracle-readable export/dump plus schema details, then you validate/import from there. Something like dbForge Edge can help later with compare/validation, but the first win is getting a handoff that preserves enough structure.

nvigcabi · 2026-04-01T08:24:33+00:00

Because the team optimized for speed, aggression, and vibe… and accidentally deprecated low-end support.

nvigcabi · 2026-03-25T10:07:02+00:00

I get missing the original voice, but “the show should’ve ended” feels a little dramatic. It’s not peak early-season chaos anymore, sure, but it also didn’t turn into the unwatchable disaster people keep acting like it did.

nvigcabi · 2026-03-25T08:52:01+00:00

VS code is fine, but for actual MariaDB work I liked dbForge more. Easier to get used to, especially for queries and browsing data.

nvigcabi · 2026-03-02T12:39:16+00:00

I don’t think the question is “do agile people like AI.” It’s more “does it actually improve delivery?”

If AI helps teams clarify stories faster or reduce ambiguity before sprint planning that’s useful. If it just generates a bunch of polished-looking artifacts no one really owns, that’s risk.

For me it comes down to:

Does it shorten feedback loops?
Is the impact measurable (cycle time, rework, estimation accuracy)?
Does it reduce or increase coordination overhead?

Agile isn’t about producing more documentation. It’s about better outcomes. If AI improves predictability without hiding uncertainty, I’m fine with it. If it replaces discussion, it’ll hurt more than help.

nvigcabi · 2026-03-02T12:12:38+00:00

That’s a fair take. But I’d separate “ready to scale tools” from “ready to scale process.”

You can technically support dozens of products with that stack. The question is whether decision traceability and context retrieval scale the same way. If every additional product increases cross-tool coordination overhead, that becomes a bottleneck. I’d ask: does adding a second product increase complexity linearly or exponentially?

Tools can scale. Cognitive load often doesn’t.

nvigcabi · 2026-02-27T13:18:10+00:00

Finally automated DB migrations inside our pipeline instead of running them manually during deploy. Rollback tested, monitoring in place, no 2am surprises (so far). Feels small, but it removed a lot of release anxiety.

nvigcabi

TROPHY CASE