2004-11-10
1,553 reads
2004-11-10
1,553 reads
2004-11-09
2,229 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,071 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,407 reads
2004-11-05
2,388 reads
2004-11-04
2,074 reads
2004-10-28
1,650 reads
2004-10-27
2,276 reads
2004-10-26
2,144 reads
2004-10-22
2,698 reads
I’ve been thinking a lot lately about what it actually takes to make an...
By Steve Jones
Redgate is a for-profit company. We look to make money by building and selling...
I’ve uploaded the slides for my Techorama session Microsoft Fabric for Dummies and my...
Comments posted to this topic are about the item Even When You Know What...
Comments posted to this topic are about the item The New Software Team
Comments posted to this topic are about the item Database Mail in SQL Server...
We create the following table and then insert some records in it:
create table t1 ( id int primary key, category char(1) not null, product varchar(50) ); insert into t1 values (1, 'A', 'Product 1'), (2, 'A', 'Product 2'), (3, 'A', 'Product 3'), (4, 'B', 'Product 4'), (5, 'B', 'Product 5');What happens if we execute the following query in both Sql Server and PostgreSQL?
select id,
category,
string_agg(product, ';')
over (partition by category order by id
rows between unbounded preceding and unbounded following) as stragg
from t1; See possible answers