A look into clustering to detect outliers in R. An extension on univariate statistical tests to include multivariate data.
TSQL Code must work properly and efficiently. That's not enough though. Unless you are working alone, have perfect memory and plan to never change job, then you need to comment and document your code, it must be inherently readable, well laid out, use informative and obvious names, and it must be robust and resilient; written defensively. It must not rely on deprecated features of SQL Server, or assume particular database settings. Robert Sheldon starts a series of articles that explains the basics.
A holiday in the US has Steve Jones thinking about compromise and communication.
In this post, Tim Smith looks at the different options you can use to audit your SQL Server extracts and loads during the ETL process.
You will see here a way to handle history tables. This way only takes into account Date-based data cleanup but is easily generalizable.
This week Steve asks you to make sure you practice your restore skills periodically.
Steve Jones saw a database design test for developers, but he's never been given one.
By Steve Jones
A customer was trying to compare two tables and capture a state as a...
By Zikato
When I'm looking at a query, I bet it's bad if I see... a...
By Steve Jones
This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...
Comments posted to this topic are about the item A Quick Second Opinion
Comments posted to this topic are about the item Five Intelligent Query Processing Features...
Comments posted to this topic are about the item Checking the Error Log I
On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?
See possible answers