Hmmmm...thought that would work but when I executed this:

declare @t varchar(max)

set @t = 'test1

test2

'

select @t = replace(@t, char(10) + char(13) + char(10) + char(13), char(10) + char(13))

select @t

I got this:

test1

test2

Now that's what I call simple

Thanks...

yeah thats what i'm doing now (meant to write select instead of set). My question was is it possible to use the function directly in the parameter for the...

Kinda funny. As your reply came in I had just finished running a selectivity analysis against that field and lo and behold it dropped way down under my 2...

After taking a better look at the execution plan, in one instance it was trying to use the wrong index and in another it was using the correct one.

Which honestly...

Ahhhh wait. Now I'm getting somewhere. Based on what you just said I ran 3 different scenerios:

1) LIKE %nn%

2) LIKE %nn

3) LIKE nn%

1 and 2 took the usual...

That's the really odd part. The execution plan and the client stats between both trials are almost identical. It is actually telling me that the client execution time...

I will test UPDLOCK. I've had some deadlocking issues when using that in a select/update transaction in the past but that was with a different version of sql server....

Dynamic tsql is difficult because in my situation, I have a rather long procedure with other local table variables that I need to access. When you use dynamic tsql,...

Does anyone know what will happen if I do a TRUNCATE on a table at the same time I am bulk inserting rows into it? I have to truncate...

Yeah....that is part of my battery. I'm looking at my production system and seeing what the ratio of preserved records vs deleted records are and if I can get...

Thanks for the suggestions. I've put together several scenarios and will be testing them over the next couple weeks. In an isolated environment the tablock works great but...

I'm not keeping the rows. There is a steady stream of large amounts of data from different sources coming into the staging area. The end user applies some...

Yeah already do that....but when you're dealing in hundreds of millions of records with finite resources you have to delete it sometime.....and when the garbage man comes around to remove...

Good point.....this is all being done in a staging area so the indexes/foreign keys that would apply to my OLTP environment don't necessarily apply here....