Changing log growth strategy in SQL Server 2022
I discuss my roller coaster of emotions since learning that SQL Server 2022 would support instant file initialization for log files.
I discuss my roller coaster of emotions since learning that SQL Server 2022 would support instant file initialization for log files.
In this tip, I take a quick look at some changes to Always Encrypted that make it easier to use.
I've long been pro-schema-prefix, but in this post I talk about an exception to the rule at Stack Overflow, and why it works well.
I show how GENERATE_SERIES makes for easier set building, and decent alternatives while you're still stuck on older versions.
While it might promote less than ideal practices, I show how to use a DDL trigger to keep views in sync with a volatile schema.
In the final part of this series, I convert my T-SQL code to MySQL, so you can build a fancy archives page in WordPress.
Certainly not to encourage people to stay on ancient versions if they don't have to, I took a crack at replicating TRY_PARSE on older versions.
I show that a new experimental feature in Docker 4.16+ lets you run "real" SQL Server on Apple M1+ chips.
For my first post on Simple Talk, I rip apart a made-up stored procedure as if I had encountered it during a code review.
Over a decade of posts and videos involving bad habits and best practices in SQL Server.
In the second part of this series, I show how to use a calendar table to simplify rendering an archives page.
I recently added a switch and an adapter to take much better advantage of AT&T's 5-gig service.
A good round of updates for most modern versions of SQL Server, including the first cumulative update for SQL Server 2022.
I started a short series on building visual calendars, like those seen in the monthly archives page here.
I discuss an organization’s responsibility for protecting personal information.
For T-SQL Tuesday #158, I talk about a couple of justifiable worst practices.
The story behind new SQLBlog-branded clothing (with proceeds going to The Trevor Project and Black Lives Matter).
I talk about some of the pivotal criteria guiding how Stack Overflow will migrate to Azure.
I recognize this year's recipient of my Community Influence of the Year award.
I talk about my foray into mentoring, and how you should mentor for a career, not just for a role.
In part 3, I show how to automate creating new tables, dropping old tables, and adjusting the view.
In part 2, I look at general strategies for partitioning an archive table (even without Enterprise!) to reduce long-term data movement.
For T-SQL Tuesday #156, I talk about the qualities I expect in T-SQL code before I consider it "production quality."
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.
SQL Server 2017 Cumulative Update #31 is available, with 24 enhancements. The build number is 14.0.3456.2. This is the last mainstream cumulative update for SQL Server 2017!
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 look at DBA, DBRE, and SRE roles and share how they have differed in my experience.
I talk about ways to use wrapper functions to work around tedious syntax required by the new function, GENERATE_SERIES.
For this month's T-SQL Tuesday, I talk about the community event that had the most profound impact on my career and, more importantly, my life.
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 article, I discuss several advantages to maintaining a technical blog.
I talk about a few of the things I worked on in my first month as a DBRE at Stack Overflow.
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 2019 (GDR = 15.0.2095.3, CU = 15.0.4236.7). 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 2017 (GDR = 14.0.2042.3, CU = 14.0.3445.2). 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 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.
I talk about some of the things I do to be more productive, and hopefully some of these can help you in your role, too.
I warn about a cumbersome change to setup, where something is checked by default when it shouldn't be.