Navicat Blog

May 4, 2026 by Robert Gravelle

A well-maintained shared query library is one of the most underrated assets a DBA team can have. When everyone on the team is pulling from the same vetted, documented pool of SQL, you eliminate duplicated effort, reduce the risk of logic errors creeping into production, and make onboarding new team members dramatically faster. But building and sustaining a shared library takes more than just dropping .sql files into a shared folder. Here's how to do it properly.

[Read More]

Apr 24, 2026 by Robert Gravelle

Every time a database client sends a query or receives a result set, that data travels across a network. On a private, isolated network with no external access, this may be an acceptable risk. In most real-world environments, however, where traffic crosses shared infrastructure, cloud networks, or the open internet, an unencrypted database connection is a significant exposure. SSL/TLS encryption closes that gap, and configuring it correctly is one of the more important and frequently overlooked steps in securing a database environment.

[Read More]

Apr 17, 2026 by Robert Gravelle

Database work has traditionally been a highly centralized discipline. DBAs and developers sat near each other, shared the same internal network, and could hand off work with minimal effort. That model has changed considerably. Teams are now routinely spread across cities, time zones, and continents, and the practices that worked in a shared office environment don't automatically translate to distributed ones. Getting collaboration right in this context requires deliberate process design, clear conventions, and tooling that bridges the physical distance without sacrificing security or consistency.

[Read More]

Apr 10, 2026 by Robert Gravelle

No single security control is ever enough to protect a database system on its own. Firewalls can be misconfigured. Credentials can be phished. Software vulnerabilities get discovered in products that were previously considered secure. A defense-in-depth strategy acknowledges this reality by building multiple overlapping layers of protection, so that if one layer fails, others remain in place to contain the damage. For database infrastructure specifically, this approach is not just best practice, it's increasingly a compliance requirement across regulated industries.

[Read More]