Thanks Steve 🙂

There is an urgent message in the bathroom at Redgate…

process #2 is being blocked by a lack of fiber.

Hey GilaMonster - thanks so much for that article link. It's exactly what I was looking for 🙂

- Z

Thanks for the feedback. I'm of the same mind. Smaller single purpose procs are much easier to maintain and re-use.

I know this topic is stale, but as long as your nText field is not too large, you can cast it as nvarchar and then use replace().

example

update testTable

set testNtext...

This is extra useful since SET ROWCOUNT affecting updates is going away in the next release of SQL. http://msdn2.microsoft.com/en-us/library/ms188774.aspx

First off, cool article

I'm also using SQL 2000, so instead of using sys.views I use:

IF object_id('Digits') is not null drop view Digits

Here is...

I inherited a datawarehouse which used two generic tables:

CREATE TABLE [typeGrp] (

[typeGrpId] [int] IDENTITY (1, 1) NOT NULL ,

[typeGrpDesc] [varchar] (40) NOT NULL ,

PRIMARY KEY CLUSTERED ([typeGrpId]),

UNIQUE...