2004-11-19
2,020 reads
2004-11-19
2,020 reads
2004-11-18
1,896 reads
2004-11-17
2,068 reads
2004-11-15
2,179 reads
2004-11-12
3,075 reads
2004-11-11
2,423 reads
2004-11-10
1,546 reads
2004-11-09
2,224 reads
Another in our series of things you should avoid at all costs. Seems silly at first, not having a detailed recovery plan for your SQL Server. Perhaps it is, but having dealt with any number of problems over the last few years, Steve Jones has some ideas why a detailed plan may not be the best thing to spend your time on.
2004-11-09
8,056 reads
This is the first article by Steve Jones that examines a programming technique for handling operations that may be too large to run in a single query.
2004-11-05 (first published: 2001-05-09)
19,164 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;