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
With each new release of SQL Server, we gain exciting new features—but also face the reality of deprecated features that should be phased out. Although these deprecated features aren’t immediately disabled, they won’t be supported in future SQL Server versions. Ideally, you should start removing them from your code now to avoid potential issues during…
Read more
A database on a specific SQL Server version doesn’t automatically have all features enabled. For example, a database on SQL Server 2019 can still use SQL Server 2014 compatibility, missing some 2019 features. Each database has a Compatibility Level setting that activates certain features of its version. When SQL Server 2014 introduced the Cardinality Estimator,…
Read more
Many developers mistakenly use WITH (NOLOCK) in their SELECT statements without fully understanding its effects. While they might aim to speed up queries or prevent deadlocking, NOLOCK can actually lead to invalid results. What does NOLOCK do? A SELECT statement in SQL Server locks data to prevent modifications during querying. The lock is released after…
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
SQL Server is designed to efficiently manage memory on its own. It requests memory when it’s needed and releases memory back to the system when it’s not. However, the default settings may not be ideal for your situation. An experienced database administrator will usually fine-tune these settings to optimize performance and server stability. Minimum server…
Read more
I’m my last post on SQL Server Setting, I discussed MAXDOP and how it can affect SQL Server performance. In this post, I’ll review another SQL Server configuration setting that can impact performance – Optimize for Ad-hoc Workloads. What is the plan cache? Every time you run a query in SQL Server, an execution plan…
Read more
Did you know that not configuring the MAXDOP setting in SQL Server properly could cause performance problems for your queries?
Deadlocks in SQL Server are more than just a nuisance, they can be problematic, and even lead to data loss and inconsistencies.
Recent Comments