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,405 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,165 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,567 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,798 reads

Blogs

From Planning to Practice: Setting Up Your FinOps Framework

By

As someone who works in DevOps, I’m always focused on creating systems that are...

“We love to debate minutiae”

By

I am guilty as charged. The quote was in reference to how people argue...

Advice I Like: Knots

By

Learn how to tie a bowline knot. Practice in the dark. With one hand....

Read the latest Blogs

Forums

Restoring On Top II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring On Top II

SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)

By Terry Jago

Comments posted to this topic are about the item SQL Art 2: St Patrick’s...

Breaking Down Your Work

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Breaking Down Your Work

Visit the forum

Question of the Day

Restoring On Top II

I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:

-- run yesterday
CREATE DATABASE DNRTest2
GO
USE DNRTest2
GO
CREATE TABLE NewTable (id INT)
GO
Today, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today
USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens?

See possible answers