In part 3, I show how to automate creating new tables, dropping old tables, and adjusting the view.
Category: SQL Server
In part 2, I look at general strategies for partitioning an archive table (even without Enterprise!) to reduce long-term data movement.
Over a decade of posts and videos involving bad habits and best practices in SQL Server.
In this series, I look at strategies for archiving data and how it can impact your entire infrastructure.
For October's T-SQL Tuesday, Steve Jones asks us to talk about ways we've used dynamic SQL to solve problems.
SQL Server 2019 Cumulative Update #18 is available, with 26 enhancements. The build number is 15.0.4261.1.
In this tip, I show how to simplify calculations involving nth weekday or non-weekday, with and without a calendar table.
For this month's T-SQL Tuesday, I talk about a not-quite-yet-announced feature in SQL Server 2022 that has the potential to function as a low-effort bad habit logger.
SQL Server 2019 Cumulative Update #17 is available, with 43 enhancements. The build number is 15.0.4249.2.
I talk about ways to use wrapper functions to work around tedious syntax required by the new function, GENERATE_SERIES.
On the 10th anniversary of SQLPerformance.com, I look back on my favorite posts – one from each year.
For this month's T-SQL Tuesday, Deb Melkin asks us get up on our favorite soapbox. I have so many, but this time I picked a new one…
Logging tables can grow unchecked for years, and date range queries against them get more and more expensive if they don't use the clustered index. Read about one way I've mitigated this problem.
Using a fictitious future timeline, I explain how CUs and GDRs differ and why build number alone might not tell the whole story.
In this tip, I show some real-life reasons why you may not want to create all the partitions you'll ever need up front.
I talk about why I prefer CONVERT over CAST to be consistent. Basically, if you sometimes HAVE to use only one, why not just ALWAYS use that one?
A new build is available for SQL Server 2016 SP2 and SP3. From the CVE: "An authenticated attacker could exploit the vulnerability by executing a specially crafted query using $ partition against a table with a Column Store index."
A new build is available for SQL Server 2014 SP3. From the CVE: "An authenticated attacker could exploit the vulnerability by executing a specially crafted query using $ partition against a table with a Column Store index."
There are often multiple ways to express a query and get the same results, often without any change in performance. Learn about one example.
In this tip, I talk about the compatibility between major versions and SQL Server's internal database version.
I continue looking at some of the changes in SQL Server 2022 that aren't on the marketing slides.