2017-07-13
1,035 reads
2017-07-13
1,035 reads
2017-07-11
1,187 reads
2017-07-06
1,316 reads
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.
2017-07-05
7,732 reads
2017-06-28
1,104 reads
2017-06-21
1,126 reads
Your SQL Server drives are running out of disk space and you want a way to quickly tell which sub-directories are taking the most space - here's how to do it with T-SQL.
2017-06-16
4,950 reads
In this article, I will provide a set of examples to showcase the use of OUTPUT clause within the MERGE statement and how to capture the OUTPUT clause results into an archive table.
2019-03-08 (first published: 2017-06-08)
171,148 reads
In this article, I will provide a set of examples to showcase the use of OUTPUT clause in capturing the results of the updated rows into a table variable for the UPDATE statements.
2017-06-06
195,541 reads
2017-05-25
1,050 reads
By Brian Kelley
Do you have a case where you have a named instance you'd like to...
By Steve Jones
I was trolling the docs and noticed the SIGN() function. I have never written...
By ReviewMyDB
The T-SQL Tuesday #201 round-up: nine bloggers on whether temp tables are a friend...
Comments posted to this topic are about the item Admin Rights for Everyone
Comments posted to this topic are about the item Kerberos Authentication for Aurora PostgreSQL:...
Comments posted to this topic are about the item RegEx Functions I
Which of these RegEx functions need compatibility level 170 in SQL Server 2025?
See possible answers