Heh... I thought you said "without looping".

Nicely done... If I may suggest, however, a method that avoids both loops and dynamic SQL...

--===== If the test table exists, drop it

     IF OBJECT_ID('TempDB..#HexToAlpha','U') IS NOT...

He doesn't get it as a hex/binary number... he get's it as a string.

Nicely done, Brian.  And, Jan, I agree... we've asked you to post the cursor code a couple of times now...

There is a "good" reason ... they're probably not allowed to put their own stored procedures in and it must pass a DBA review......

Here's an example... you can't do unlimited hierarchies, but it's normally good enough.  And, it's not your specific example... it for something I did for someone else... thought it might...

Unlike DTS, Query Analyzer, and BCP, OSQL was NOT designed to scan the data and size the output accordingly.  Since you don't want headers, BCP is the best bet.  DO...

Tell me... is AppointmentDate a VARCHAR column? 

Unless you need absolutely awesome performance on a huge table, this'll do nicely with pretty good performance...

 SELECT i.IntName,r.RegName,r.RegInterests

   FROM Registrations r,

        Interests i

  WHERE ','+r.RegInterests+',' LIKE '%,'+CAST(i.fk_Interests AS...

That's just not the way we do things here... lot's of folks busted a hump trying to help and now you're not going to take the time to explain what...

No need for even a single CAST or CASE...

 SELECT (

         SELECT COUNT(*) * 100.0

           FROM @ProviderLink

          WHERE PLtat + PLunworkable > 75

        ) 

     / (COUNT(*)) AS Percentage

 ...

Thanks folks... great feedback and I appreciate it very much.

Ben, I've not found much on Triangular joins but I did write an explanation for someone else on this forum.  Please...

You can go a bit further... the following will return the number of spaces found for each row for that column...

 SELECT pkcolumnname, LEN(yourcolumn) - LEN(REPLACE(yourcolumn,' ','')) AS Spaces

  ...

How is it that a casual user has been allowed access to backups?  That, in itself, would be a violation on PCI audits...

The problem may be with any SQL DMO or sp_OA* code you may have... if you forget to close and drop connections, you may end up with a "connection leak".