Paul Ibison

Currently work in Aldgate, London for Pygmalion - a Microsoft CTEC - as a Trainer/Developer/Consultant. Specialise in SQL 2000 OLAP and am now beginning to learn Sharepoint Server and .NET
  • Interests: Collecting slide-rules and watching my complete collection of 'Are you being served'.

SQLServerCentral Article

Log Shipping vs. Replication

SQL Server high availability. Log shipping or replication, clustering or some other solution. It's a challenge and as companies grow more dependent on their databases, it's one that more and more DBAs face everyday. Paul Ibison has taken a look at how log shipping and replication can be compared in the quest for high availability.

(37)

You rated this post out of 5. Change rating

2008-06-27 (first published: )

66,421 reads

SQLServerCentral Article

High Availability (DR) Using SQL Server 2005 Transactional Replication

One of the four high availability technologies in SQL Server is replication, though this can be very cumbersome to setup and get working. Longtime author Paul Ibison looks at how this has changed from SQL Server 2000 to 2005 and what you should consider before setting this up.

(9)

You rated this post out of 5. Change rating

2008-04-17

7,790 reads

SQLServerCentral Article

Retain NULL values vs Keep NULLs in SSIS Dataflows - Which To Use?

Integration Services allows you to import all kinds of data easily into SQL Server as well as transform is along the way. Longtime author Paul Ibison brings us a look at how you should set your transformations to deal with NULL values.

(38)

You rated this post out of 5. Change rating

2008-02-13

14,204 reads

SQLServerCentral Article

Altering a column on a Replicated Table

SQL Server 2000 replication is usually simple and easy to setup and work with. However there are many restrictions to ensure this, one of which is the alteration of a column which is engaged in replication. Author Paul Ibison brings us two options for altering columns.

(15)

You rated this post out of 5. Change rating

2008-01-14 (first published: )

45,610 reads

SQLServerCentral Article

Merge Replication - Manual Range Handling

SQL Server 2000 replication is a great feature, but it can cause some headaches at times. Since the use of identities is something many people take advantage of, learning to handle these in a replication scenario is critical. Author Paul Ibison has done extensive work with replication and brings us two techniques to help manage the ranges of values.

(2)

You rated this post out of 5. Change rating

2005-01-13

12,802 reads

Technical Article

How to Short-circuit Where Clauses

There are many times when you might be concatenating text in a stored procedure to make a where clause, because the input parameters are optional. An alternative is to create many versions of the stored procedure - one for each possible combination of parameters - which can soon become too big. There is a more […]

(4)

You rated this post out of 5. Change rating

2001-11-25

4,295 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