SQL RAISERROR to Better Handle Errors
Learn how and why to use RAISERROR in your SQL Server code to be able to better handle errors that may occur during code execution.
2022-12-02
Learn how and why to use RAISERROR in your SQL Server code to be able to better handle errors that may occur during code execution.
2022-12-02
2022-12-02
82 reads
2022-11-30
446 reads
The previous installment of this series examined aggregate subquery removal and subquery coalescing, describing the latter as similar in some ways to an inverse for “Or Expansion” and “Join Factorization”. In this instalment, it’s time to take a closer look at Or Expansion and we’ll move on to Join Factorization in the next instalment.
2022-11-30
2022-11-28
442 reads
Learn how one company adopted, adapted, and learned from the Agile methodology.
2022-11-28
4,477 reads
In my previous tip, I explained how we are inclined to use archive tables and how they become increasingly problematic over time. This tip will focus on ways to mitigate the issues.
2022-11-28
In this article, we cover things you should know about Azure SQL Database and why this may be a good choice for your database applications.
2022-11-25
2022-11-25
521 reads
In the previous two articles in this series, you learned about SELECT and INSERT, two important data manipulation language (DML) statements in MySQL. In this article, I focus on the UPDATE statement, another valuable DML statement in MySQL.
2022-11-23
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...
If you've ever loaded a 2 GB CSV into pandas just to run a...
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