Foundation?

Read that on the plane coming back from London. Laughed to myself quite a...

Doctor Who 2 (7/18/2012)

---

I'm really pressed for time this morning so can't fully answer your question, Steve (sorry).

One geeky book I've read this summer, and thoroughly enjoyed it, was "Zero...

Will add to my list.

But, yeah, reading keeps me sane with all...

Nice avatar 🙂

Up to Dan. If there's space, he has to add you to the list. PM him.

fuller.artful (7/18/2012)

---

Cryptonomicon - World War II seen as a war between four mathematicians, who all attended school together. In part, it addresses a core question of information theory: given that...

Yes

Lynn Pettis (7/17/2012)

---

Mostly requests for assistance, but I have tried to engage him where I think...

GilaMonster (7/17/2012)

---

Steve Jones - SSC Editor (7/17/2012)

---

Gail? When she's got the three...

You use NULL, as Scott mentioned.

create PROCEDURE [dbo].[spUpdateTableA]

@TableAPK int, --only required parameter

@ColumnA nvarchar(50) = NULL,

@ColumnB int = -1

as

begin

SET NOCOUNT ON

SET XACT_ABORT ON

declare @ErrorMessage nvarchar(4000);

begin try

--Start the transaction

begin transaction

update TableA

set ColumnA...

Gail? When she's got the three of us in the dojo?

Scott has a good idea. Can you show some pseudocode or some real code that explains how this should work for you, takilroy? It seems as though you're honing in...

My guess, and it's that, is that you are transferring over the index definition to SQL Server for the PK, trying to parse it, and it's failing because there are...

Not sure what's broken, but in SQL Server, only 16 fields allowed for primary keys.

If you have really wide ranging items, perhaps a lookup tables makes sense.

Personally, I never would use NULL in the field as an update. If someone wanted to remove data...