I think it makes sense.

Bottom line for me is this: those records that have a null value in the nvarchar column will not eat any storage. That's what I wanted,...

Antares, thanks for sharing your research.

>> In other words you have 6 bytes extra plus the data.

If I'm reading you right, 2 of the 6 bytes is in the column...

>> not unusual for either the app or a component of the app to open a 2nd background connection to do some work

I suspected that, but wanted someone to say...

A reinstall of both Windows and SQL Server is certainly one way to make sure the hardware is working right. But it masks the problem. What really was set wrong?...

Hello Deejay or Dirk 🙂 ,

(I use Undebtedly because "Steve Miller" is a very common name here in the U. S. I can never just call myself simply...

Someone goes to a class to learn about hammers. At the end of the class, the person knows all about the hammers. You use a straight claw for this, a...

We had a similar problem. I spent over 100 hours at it, before the network guys figured it out. I don't quite understand it all, but here it is, in...

>> RETURN 'any string' --this causes error because the function is supposed to return a datetime value

🙂 Reminds me of the old days. Force an error when you want...

Yup. I was just trying to get an example out the door so people would know what I'm talking about. So I was being a little lazy.

Steve

OK, you're using an invalid date in the case where a function returns an invalid datetime.

So maybe in your function you'd do something like this:

----------------------------

IF @@ERROR != 0 GOTO Fail

...

Fail:

...

Are you saying to purposely give an invalid value in the return statement? Maybe my mind is a bit foggy today, but it seems to me if we don't have...

Clear, concise, and to the point. 🙂

(Thanks)

Steve (<sigh>. Now I have to figure out how to code this thing.)

OK, RAISERROR and ROLLBACK are out. Does anyone know whaat to do instead?

Steve

I believe the wording from MS was that it "runs as it was coded". That's been the source of a great deal of entertainment among the developers here. They never...

Simon,

You may have replied to this, but not to me. 🙂

We finally called MS with this problem. The problem comes in that the XML handler was bolted on to the...