Do it client side, asp has more powerfull string manipulation features. Sql server is meant to store and send data, not manipulte it.

Remi = rgR'us .

May I suggest you start a new thread for this question as it'll give you greater exposure?

Too many ways to skin the cat here .

Can't you simply import in a temp table, then insert/select in 2 batches.

Well you shouldn't have given such a fitting name... now it's permanent.

or Toys R'us

We'll cross that bridge when we don't meet at PASS this year .

I know it's in septembre. That's all I need to know since I ain't going .

I knew you were early .

rgR'us - A fitting nickname

Sorry, was talking to Noeld . Maybe this is what PM are for .

Are you back from PASS already??

I remember posting a great solution for this problem but I didn't save it. It was one of our discussion about procedural/set solutions but I just can't find it....

The only advantage is logic encapsulation. Other than that, any tsql code will have to replace the same string many times.

The short answer to that question is don't do that. You waste all the power of sql server when you do something like that.