In a way I think of this as a constraint, like any other in a db.

You have a basevalue, but for it to be correct in regard to the viewer,...

This seems to be a client error..?

(of which I'm not too familiar with.. ADO, ASP et all)

It seems like the recordset method is attempting something on a closed connection?

Anyway,...

Could you elaborate on how this fails?

Like what error do you get?

/Kenneth

However, this is no exact science, and there are more factors than just semantics.

For inner joins, there is no difference for the endresult if stuff goes into the ON clause...

There's a way that requires a brief shutdown of the prod server, and another that does not, but may be more involved in syntax. If shutdown is not an option,...

You're right.

It's not converted to a constant per se, but I'd say the the behaviour is identical as if it had.

By assuming the value from the outer table, the subquery...

This is a very old trap that's been around seen 6.x days.

Basically, what's happening with a statement like:

DELETE #Test_Delete

WHERE MyId IN

(SELECT MyId FROM dbo.Account) --MyId field does not exist...

No, there is no difference between the two.

This is also easily checked - you can just run the two queries in QA and inspect the plans generated..

The difference is that they are two different languages.

Both SQL, but still different dialects.

SQL Server uses Transact SQL only.

You cannot use PL-SQL specifics in SQL Server at all, because SQL...

Try changing sp_dropdevice @DeviceName,'DELFILE'

to

execute sp_dropdevice @DeviceName,'DELFILE'

/Kenneth

Ah, I see...

Though I can't for the life of me figure out why any tab would be valid in a datacolumn.

I never ever...

As already been said, there is no definite 'way to go' - it always depends. It may not be 50-50, but sometimes not exists is better, other times a not...

A nice and short UDF.

It does have some limitations, though.

While it cases o'malley as O'Malley successfully, it also cases words like don't and...

You don't need either LTRIM nor RTRIM nor SUBSTRING.

All it takes is:

SELECT @stringWithTab = REPLACE(@stringWithTab, CHAR(9), '')

.. now @stringWithTab contains 'stringWithOutTab'

PS.

Invalid msg about substring is when the parameters gets...

Well, it doesn't treat o'malley as O'Malley, but it's close..

(you have to modify yourself for that)

Anyway, here's a combined properCase and whitespace trimmer...