Your SQL Servers are the backbone of your company’s data operations. They power critical applications and store valuable information. They enable financial decisions, undergird operational activities, and support your sales processes. But what happens if there’s a problem? What happens when data is lost or corrupted? Or if one of your key systems is down…
Read more
Ready to dive into our most popular blog posts? We’ve compiled a list of the top five blog posts that have resonated the most with our readers. Whether you’re new to our blog or a long-time reader, read on for valuable insights into data management, IT strategies, and more. Want to stay up to date…
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
SQL Server Availability Groups can present challenges after a failover, such as missing logins, outdated passwords, or absent SQL Server Agent jobs. Some clients address these issues by requiring the primary replica to remain on the same instance. If a failover occurs due to an outage or patching, they generally request to revert the AG…
Read more
The SERO Group will be at the IT Symposium in Louisville on August 21st! I’m looking forward to connecting with industry leaders, sharing insights, and discussing the latest trends and innovations. The event will be at the Louisville Marriott East from 8:30 a.m. to 3:15 p.m. If you’re in the area, stop by our table…
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
So, you’ve decided your organization’s data needs to remain highly available. Given the options in SQL Server, you’ve decided an Availability Group makes the most sense for your scenario. What’s next? Involve Stakeholders Early in the Process of Building a SQL Server Availability Group Before jumping into building your Availability Group, it’s crucial to identify…
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
I recently had a discussion with a client that turned to the question of SQL Server code compatibility with Azure SQL Database. We were designing a new pipeline for their on-premises SQL environment, and they mentioned their abandoned cloud migration effort from a few years earlier. The business ended up pausing this effort because of…
Read more
Recent Comments