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
We’re a week late, once again my fault. I was still coming out of...
By Steve Jones
I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...
By Steve Jones
I’m in the UK today, having arrived this morning in London. Hopefully, by this...
Hi there, Has anyone else had any trouble with Database Mail in Cumulative Update...
I have a script task that tries to execute a HTTP request, which seems...
Comments posted to this topic are about the item SQL Server 2025 Standard Developer...
If I use BASE4_ENCODE() in SQL Server 2025, is the output URL Safe by default?
See possible answers