Uncategorized

SQLServerCentral Editorial

The Impact of Small Changes

  • Editorial

A year ago, I started a monthly blogging event for the PostgreSQL community, inspired by T-SQL Tuesdays. I decided to call it PGSQL Phriday. (Time will tell if my insistence on trying to use a literation was a good idea or not.) Like the event for the SQL Server community, we ask someone to be […]

(1)

You rated this post out of 5. Change rating

2023-09-09

100 reads

SQLServerCentral Editorial

A Season of Reflection

  • Editorial

As I think about heading into the fall conference season (and seeing so many familiar faces!!), I realize that I'm going to be asking myself a set of familiar questions. Who am I? What skills do I need to improve on in the coming year? Who do I look up to in the community and […]

You rated this post out of 5. Change rating

2023-09-02

78 reads

SQLServerCentral Editorial

Be Prepared

  • Editorial

I've been reading about the fires in Maui and the horrible loss of life there. My heart goes out to all involved. I hope, if you can, you donate to a good charity to help those poor people. It also inspired me to do another check on our emergency supplies and equipment. No, we don't […]

(2)

You rated this post out of 5. Change rating

2023-08-26

106 reads

External Article

Managing Test Data for Database Development

  • Article

In coming up with a strategy for managing test data, first you need to understand what the many test requirements are likely to be for the particular database you are developing. Next, you need to create all the different categories of test data required to suite test requirements and, finally, work out how to manage it in a way that allows a test-driven approach to development.

Read more in this latest article from Phil Factor

2023-08-18

SQLServerCentral Editorial

Looking Back and Forward

  • Editorial

I took part in a podcast this week, Arrested DevOps. I did one with them once before, almost ten years ago. The host and I were both a little surprised that it had been so long. This caused us to look back a bit. Interestingly enough, ten years ago meant I was only about two […]

You rated this post out of 5. Change rating

2023-07-29

60 reads

Blogs

The Book of Redgate: Profits

By

Redgate is a for-profit company. We look to make money by building and selling...

Session Materials for Techorama & DataGrillen 2026

By

I’ve uploaded the slides for my Techorama session Microsoft Fabric for Dummies and my...

Stop Using Pandas for Aggregations — Try DuckDB Instead

By

If you've ever loaded a 2 GB CSV into pandas just to run a...

Read the latest Blogs

Forums

Even When You Know What You're Doing, You Can Screw Up

By Grant Fritchey

Comments posted to this topic are about the item Even When You Know What...

The New Software Team

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The New Software Team

Database Mail in SQL Server 2022

By Abdellateef Ibrahim

Comments posted to this topic are about the item Database Mail in SQL Server...

Visit the forum

Question of the Day

The string_agg function

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