I built SQLVault Pro as a free tool for the SQL Server DBA community — because keeping track of dozens (or hundreds) of instances shouldn't require a spreadsheet. SQLVault Pro lets you maintain a clean, searchable inventory of your SQL Server instances. Track which application each instance powers, what environment it belongs to (dev/test/prod), and what Always On / HA configuration it's part of. Search by database name, username, table, or index — and get to the right instance fast without digging through notes or tickets. Export functions are already in — database lists, user lists, and instance lists, ready for auditing. 👇 Check the video below to see it in action. One Docker pull and you're running. What's coming next: 📥 Bulk import — add all your instances at once, no more one-by-one entry 🤖 AI-powered search — locate any instance faster with natural language My goal is to make this the go-to inventory tool for SQL Server DBAs. Free. Always. 🔗 https://lnkd.in/dV7BHiVy Contributions and pull requests are very welcome — let's build this together. #SQLServer #DBA #DatabaseManagement #OpenSource #SQLVaultPro #DatabaseInventory #DevOps
More Relevant Posts
-
💡 Learning from a Real Production Scenario – SQL Server Always On Yesterday I faced an interesting issue related to Always On Availability Groups (3-node setup) that gave me a valuable learning. 🔧 Scenario: • 3-node Always On setup • Backup preference was configured on the 3rd node (secondary replica) • Secondary replica had 100% backup priority ⚠️ What Happened: • On 30th March, the primary server was rebooted due to an issue • After reboot, the preferred backup replica value became 0 on all nodes • As a result, backups started failing 🔍 Root Cause Insight: Even though: • Backup preference was set to secondary • Backup priority was correctly assigned (100) 👉 The reboot caused a mismatch where one database’s commit time was still reflecting 30th March 👉 This led to SQL Server not selecting any valid preferred replica for backup 📘 Key Learning: • Always On backup preference settings can reset or behave unexpectedly after failover/reboot • Don’t rely only on backup priority — always validate replica state and commit synchronization • Monitor sys.fn_hadr_backup_is_preferred_replica and database sync status after any restart/failover ✅ Actionable Takeaway: After any restart/failover: • Verify backup preference behavior • Check replica roles & sync state • Validate last commit time across replicas This was a good reminder that real-world behavior can differ from configuration expectations. #SQLServer #AlwaysOn #DatabaseAdministration #Learning #ProductionIssue #DBA:
To view or add a comment, sign in
-
Most SQL Server environments have no single source of truth for their instances. Spreadsheets get outdated. Wikis get abandoned. Tribal knowledge walks out when someone leaves. I built SQLVault-Pro to fix that a free, open-source SQL Server inventory tool that gives you a clean, structured view of every instance you manage. What you get: → Centralized inventory of all your SQL Server instances → Bulk import via CSV to onboard fast — no manual entry one by one → Sample mock data in the live demo so you can see it in action immediately → Dead-simple deployment: one Docker command and you're live docker run -d -p 3001:3001 -v sqlvault-data:/app/data worlber/sqlvault-pro:latest Try the live demo → https://lnkd.in/dk7hGvTu (Login: admin / admin) ⭐ Star the project and report bugs or feature requests on GitHub → https://lnkd.in/dV7BHiVy If you manage more than 5 SQL Server instances and you're still using a spreadsheet — this is for you. #SQLServer #DBA #DatabaseManagement #OpenSource #DevTools #SQLVaultPro
To view or add a comment, sign in
-
When people in the OpenVMS world hear "database migration," they often imagine a multi-year rewrite project. And sometimes that's true. But with Mimer SQL, the picture is different — because we've built our migration paths specifically around Rdb. Mimer SQL supports Embedded SQL and Module SQL, which are the same interfaces Rdb applications typically use. That means application code often needs far less rework than you'd expect. The database changes; much of the application logic doesn't. For organizations facing the Rdb/x86_64 wall, this means: → You can stay on OpenVMS and your existing IA-64 hardware initially — no forced leap → Migrate from Rdb to Mimer SQL first, while everything else stays the same → Once the database migration is done, move to x86_64 at your own pace — OS, hardware, and application independently → Run a mixed environment if needed: database on x86_64, applications still on IA-64, or vice versa — Mimer SQL doesn't constrain you → Preserve your application portfolio throughout — no full rewrite at any stage It's not a perfect situation — no situation involving forced migration ever is. But it's a realistic one. #OpenVMS #OracleRdb #EnterpriseIT #LegacyModernization #MimerSQL #DatabaseMigration
To view or add a comment, sign in
-
-
I’m excited to share SP_DBA_CurrentlyExec, a SQL Server troubleshooting stored procedure I built to help SQL DBAs quickly understand what a server is doing in real time. It provides a live view of executing sessions and can also surface blocking chains, backup history, disk health, SQL Agent job status, Query Store information and AlwaysOn lag from a single command. If you spend time investigating performance issues, blocking, waits, or operational health, this tool is designed to make that process faster and simpler. You can find it here: https://lnkd.in/duA7B5Mk I’d love your feedback, ideas, and contributions from the SQL Server community. #SQLServer #AzureSQL #DBA #DataPlatform #PerformanceTuning #Troubleshooting #MicrosoftDataPlatform #SQLFamily
To view or add a comment, sign in
-
SQL MCP Server: From Setup to Live Data In a previous post, I covered what SQL MCP Server is, why it matters, and why getting the security model right is non-negotiable. If you haven't read that one, please start there. This post is the follow-up where I'll walk through the full setup and usage. We'll install the tools, configure the server, expose a couple tables, and connect Claude Desktop to query live SQL Server data. It's a simple example of the how-to beginning to end. What you need before you start....more https://lnkd.in/ewFAREB7
To view or add a comment, sign in
-
Ever wished you could just point at a MSSQL db and get a REST API without writing a single line of code? I built a tool that does exactly that. ⚡ Zero-config: no complex setup, no deployment hassle ⚡ No-code: just connect your DB and go ⚡ Fast build: spin up APIs in seconds, not hours 🌐 npm cli: https://lnkd.in/gVqhQmac 🛠️ github: https://lnkd.in/gfQfQHEs 📚 blog: https://lnkd.in/gSHGdmuu ⚠️ This isn’t meant to replace thoughtfully designed REST APIs. Instead, it’s a quick way to prototype, or accelerate development , especially for internal tools, admin panels, or early-stage projects. Compared to tools like Hasura, this is lightweight , no-GraphQL engine, no service setup, no external dependencies. Just a simple CLI. #mssql #sqlserver #restapi #odata #autoapi #restmssql #zerocode #fastify
To view or add a comment, sign in
-
The list of SQL Server Intelligent Query Processing features you get when you combine Query Store with 2022 (or higher) compat level really is game changing: https://lnkd.in/gdKjJ6Ny If you're performance tuning T-SQL, you need to be on this level.
To view or add a comment, sign in
-
Exactly! This is why I try to get teams to use the highest compat level available. I've been championing DOP Feedback and other intelligent query processing features for quite awhile now. Check the compatibility level for your databases and then check out the link below to see what features your databases are missing out on. #sqlserver
The list of SQL Server Intelligent Query Processing features you get when you combine Query Store with 2022 (or higher) compat level really is game changing: https://lnkd.in/gdKjJ6Ny If you're performance tuning T-SQL, you need to be on this level.
To view or add a comment, sign in
-
🧑💻 The DBA's Checklist: SQL Server Health Check Essentials A proactive SQL Server health check is essential for maintaining a fast, stable, and secure database environment. 🔗 Explore this structured checklist to avoid hidden bottlenecks, silent failures, and costly downtimes: https://lnkd.in/d6kTvQQa Instead of manually digging through logs, system settings, and performance counters, you can utilize specialized tools and simplify routine diagnostics and generate actionable insights in minutes. ✨ Here, dbForge Studio for SQL Server is one of the most functional and user-friendly options with its automated health check tools, performance dashboards, and comprehensive diagnostics. ✅ Download the AI-powered dbForge Studio for SQL Server for free: https://lnkd.in/ga7QZSgm With its help, you can automate SQL Server health checks and enjoy better and faster performance. #dbForge #Devart #dbForgeStudio #SQLServer #SQLServerTools #SQLServerIDE #SQLIDE #DatabasePerformance #DBA #SQLServerTutorial
To view or add a comment, sign in
-
-
🚀 Mastering SQL Server ACID Properties: Your Database's Superpower! 💾 Ever wondered why your SQL Server transactions never leave data in limbo? Atomicity, Consistency, Isolation, Durability—ACID properties ensure rock-solid reliability! From all-or-nothing commits to crash-proof durability, I've broken it down with examples in my latest blog. Perfect for DBAs, devs, and SREs leveling up their game! What’s your go-to ACID scenario? Drop it below! 👇 #SQLServer #Database #ACID #DBA #TechBlog #SRE🔥👉 Read now:
To view or add a comment, sign in
MWG•531 followers
1moCongratulations 🎈🎊🍾🎉