Note that in SQL Server 2005, the curly braces ( {, }) are allowed as part of a GUID (uniqueidentifier) parameter value. However, the GUID value must be enclosed...

I generally do. Triggers are only an exception to the rule. There are certain times when a...

Sorry, my apology - I didn't read your posting thoroughly.

The term "no" is also considered a "noise word". It is in the noiseENU.txt file. Therefore, it is also...

The code shows a clear cut example of why columns in a query should always be qualified. I.e., ALWAYS use aliases!

I got burnt badly with a DELETE statement in...

A few things:

1. Punctuation characters, e.g. the period (.) are removed from indexing and/or search.

1.1 So this results in a search of "no 3"

2. Single digits, e.g., the...

In this thread, and others, there has been, often heated, discussion around "why would anyone have to pass an array (table) of values to a stored procedure?" Along with...

Jeff,

Sorry. Our SaaS application (inciteKnowledge)...

Jeff,

I did answered your specific question which was why would the length of the...

John,

You and I are presenting similar, albeit different, solutions to the initial poster's problem. Note that I stated that in my earlier reply.

As for the performance test: yes, I...

Jeff,

Because SQL Server doesn't allow passing in arrays of values into a stored procedure. This [long overdue] defect is being corrected in SQL Server 2008.

In our web-based (i.e., stateless)...

True, but what have I gained other than an exercise. We're nit picking. The logic in the function is nice, maybe for someone else, but I can't use...

Mark,

I'll wrap up this thread by stating the following:

1. Although (sometimes) faster, changing from VARCHAR(MAX) to VARCHAR(8000) breaks my business logic (use case) requirement.

2. In the performance testing, just look...

The function I presented was initially written for SQL Server 2000. Unfortunately, at that time I had to "chunk" the incoming TEXT datatype into VARCHAR(8000) "chunks" as CHARINDEX and...

Re: "numbers" table usage

I'm not stating that a "numbers" table is not a good thing. Just be cautious with the related logic (code) that utilizes a numbers table.

To wit:...

A very common problem and use case. Even within stored procedures or between stored procedures.

The easy way is a User-Defined Function (UDF) that parses and splits the string into...