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,394 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,160 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,559 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

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,293 reads

Blogs

How to Parameterize Fabric Linked Services in Azure Data Factory for Azure Devops Deployment

By

Quite the title, so let me set the stage first. You have an Azure...

Deployment Pipelines in Fabric – What Are They?

By

In the realm of software development and content creation, the deployment pipeline serves as...

Ad Hoc SQL Server Help

By

I just need a few hours of your time… We get a variation of...

Read the latest Blogs

Forums

A Quick Restore

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Restore

Guarding Against SQL Injection at the Database Layer (SQL Server)

By Terry Jago

Comments posted to this topic are about the item Guarding Against SQL Injection at...

Ola Hallengren Index Optimize Maintenance can we have data compression = page

By JSB_89

I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...

Visit the forum

Question of the Day

A Quick Restore

While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:

USE DNRTest

BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
/*
Bunch of stuff tested here
*/RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance.

See possible answers