Use COLLATE to tell SQL Server which collation to use.

E.g.:

select * from [2000_table] a

join [linkedServer]. .dbo.[2005_table] b

on a.NID = b.NID...

Why "for xml path('')"?

This tells the database engine to concatenate the values into a string, and the extra space is a side effect. When using the path option to build...

🙂

I'm not saying disliking SQL CLR is bad. 😉

This is the expected behaviour - you run into a deadlock.

But most importantly, you're neglecting the fact that triggers fire per statement, not per row, so the ootcome of this...

Well, as long as you're happy, I'm happy. 🙂

I figured, since you dislike SQL CLR, I wouldn't mention 3rd party tools at all. 😉

Have you read the article on sys.databases in Books Online? You really should. 🙂

Anyway, here's the query:

select[name]

,state_desc

fromsys.databases

...or if you want a 1 for every database in recovery, and a 0...

Well, what do you need?

Well, there is no built in functionality in SQL Server 2005 to achieve what you need, that's for sure. 🙂

SQL CLR is an option, but why not let the client...

Read up on noise words and noise files in Books Online. You can remove individual noise words from the noise file for the appropriate language (or remove all words, and...

SQL Server is not a text editor. 🙂

Seriously, your best option is to use a client application. You could also resort to SQL CLR, and design a procedure/function, but that...

Without seeing the actual data (you haven't posted any) all I can suggest is to CAST the integer values to character values, so that you can compare them. It seems...

Please, explain what you actually need - in business terms - and what you expect to achieve.

Generally, in every day use you don't really need any in-depth knowledge of how...

Luckily for humanity, such programmers often find good answers in forums such as this one. 😉

"Scary" is an understatement. 😀

It seems the function's definition is a glitch...