I'm curious. When you say you found it rather hard in SQL Server 2000, what exactly were you doing?
The Replace() function exists in SQL Server 2000 as well as 2k5, and AFAIK it's not that difficult unless you don't know what string you're searching for.
The Replace() function doesn't work on Text and NText fields in SQL 2000. You have to use SubString() and/or Stuff() and cycle through the column or variable changing the first found instance of the pattern until they are all accounted for.
Okay, I see your point. I just tested it in 2k5 and got the same result when using a real Create Table / Update Table statement. Which doesn't make sense when BOL says:
"The string expression to be searched. The string_expression1 argument can be of data types that are implicitly convertible to nvarchar or ntext."
Hrm. You're right. There has to be a better way to do this. I wonder if Full Text Indexing makes these harder, different or no different.