Do you know your getdate()?
This article takes a closer look at SQL Server getdate() and sysdatetime() functions.
2012-02-03 (first published: 2010-05-12)
27,812 reads
Jacek Osuchowski
Using Server Side Traces for Dynamic Performance Evaluation
This article describes a method of gathering and analyzing performance data using SQL Trace.
2009-12-01
5,418 reads
2009-03-11 (first published: 2009-02-13)
1,765 reads
Blogs
Sample Data with GenAI in Seconds
By Steve Jones
A friend was asking for help with some data analysis. This was in PowerBI,...
TSQL Tuesday #188 Growing community
I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...
Time to Revive our YouTube Channel
It’s been forgotten about and neglected for few years but I’ve decided to dust...
Forums
How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory
Comments posted to this topic are about the item How a Legacy Logic Choked...
People Make Odd Choices
Comments posted to this topic are about the item People Make Odd Choices
SQL Server 2022 Clusterless Distributed Availability Group
Comments posted to this topic are about the item SQL Server 2022 Clusterless Distributed...
Question of the Day
Query Plan Regressions --
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers