“This SQL Server is critical. It’s used 24/7. So, we’re behind on patching, and we disabled our scheduled preventative maintenance jobs because they interfered with production. Our database is just too important to do that. We know that maintenance is important, but we just can’t.” Does that sound familiar? I hope not. It’s not a…
Read more
Storing sensitive information in a database, like passwords or social security numbers, is common practice. However, storing them securely is less common. Unfortunately, one of the most typical approaches is to store sensitive information in a table as clear text. That means that anyone with access to that table can see all of that sensitive…
Read more
Since security and permissions are a big part of a DBA’s job, it’s important to be able to find out things like who has elevated login permissions or when a login was last used. Here are a few queries to help you check your server and database access. Most of these scripts are based off…
Read more
A common mistake database developers make in SQL Server is naming their stored procedures with the “sp_” prefix. Organizations sometimes even adopt this as a standard convention (along with the “tbl_” prefix for tables!). So, why is this considered a bad practice? It’s inefficient. The “sp_” prefix is used by SQL Server to designate internal…
Read more
No one wants a slow, unreliable SQL Server that leaks data like a sieve. No, they want a fast, reliable, and secure database environment. However, they may not want it right now. Creating a better SQL environment can wait until later, right? It might seem that way, but the risks will only grow while you…
Read more
Does the perfect SQL Server exist? And what would that even look like? Let’s think about it for a moment. If the perfect SQL Server exists, it would be flawlessly tuned for its workload. It would have the ideal amount of hardware resources, and its settings would be perfectly optimized. The perfect SQL Server would…
Read more
In my last post, I broke down the parts of the anatomy of the SQL Server transaction log. In this post, I will share a few tips for keeping your transaction logs well-maintained and your SQL Server databases happy and healthy. Here are 7 important tips for managing your transaction logs: Now, let’s break these…
Read more
SQL Server is a critical component for many businesses, and its health and performance can have a significant impact on operations. If SQL Server is having a bad day, a lot of people are having a bad day. Users, patients, loan officers, etc, and of course, IT. That’s why we recommend performing a SQL Server…
Read more
Many businesses depend on data systems. Data systems help doctors schedule appointments with patients. They allow construction companies to manage projects and calculate costs. The list goes on and on. And if a key data system isn’t available, it hurts. It’s disruptive. And users, customers, patients, and leadership get unhappy. That’s why it’s important to…
Read more
No one likes to think about how to detect database corruption. But, Imagine this: you’re arriving at your job expecting an ordinary day. You begin receiving calls that the main application is returning a weird error when submitting or updating data; A severe error occurred on the current command. The results, if any, should be…
Read more
Recent Comments