2023-05-01
130 reads
2023-05-01
130 reads
Once you've done a number of SQL code-reviews, you'll be able to identify signs in the code that indicate all might not be well. These 'code smells' are coding styles that, while not bugs, suggest design problems with the code. In this PDF, Phil Factor's put together 119 of those code smells so you can see what to avoid and why.
2014-09-25
12,476 reads
By Patrick
SQL Server Audit is an efficient way to track and log events that occur...
I presented at SQL Saturday Pittshburgh this past weekend about populating your data warehouse...
By Steve Jones
A customer was asking recently about the RPO for their estate, and I showed...
Hi all, I'm on a sql server 2019 standard edition (15.0.4375.4) where I've a...
Dear All, I am facing issue when update my license SRSS 2022 from...
Hey all, Just wondering how do you guys / girls set up git repo(s)...
CREATE TABLE t0 ( id INT PRIMARY KEY , field1 VARCHAR(1000) , field2 VARCHAR(MAX)); INSERT INTO t0 SELECT gs.value , REPLICATE ('X', 1000) , REPLICATE ('Y', 1000) FROM generate_series(1, 10, 1) gs; GO
select STRING_AGG(field1, ';') within group (order by id) from t0;
select STRING_AGG(field2, ';') within group (order by id) from t0;