duh I missed that one, that's the name of the column..................

Oh forgot to leave out that small factor, almost no clustered indexes (yes I know bad) but that is the one change if I make lose my warranty, trust me...

actually rebuilt less than 1000 indexes out of 30K. Going to look at fill factor on the 1000k that were rebuil

thanks I was missing a paren in my soltution, probably could have looked at it for hours, my duh

sorry it was confusing

I can take a row by row like below

declare @inqid varchar(1000)

set @inqid = '<ExtendedInfo>

<PageCount>1631</PageCount>

<Fragmentation>10.2391</Fragmentation>

</ExtendedInfo>'

declare @EntryID varchar(100)

Declare @Start int, @End int, @Length int

select @Start = (CharIndex('<fragmentation>', @inqid)...

thanks that is what I had figured

if I have a filegroup called Index_1 with 8 files

index_1

Index_2

index_3

etc........

which are all part of this filegroup, when the index is created are the indexes spread across all the individual files,...

what are they using to produce this sql? Can you the run same sql from query analyzer and see same slowness?

As I beat this horse to death, I also found in the snapshot that sos_scheduler went from 4000 to 150,000 at the same time the other metrics all took off

I leaning towards more a bad plan, the sp now runs faster than it ever did before. I have always wondered whether you add/modify or delete and index that...

I have baselines, just stunned to see this happen, I have been a dba for 20 years and 99% of the time this happens either blocking or someone decided to...

time to get my eyes checked the lock reuests went to 50 Million not 500 K Not even sure how you can get to that number.

no blocking that was the first thing I looked for. I had dropped an unused index the night before on a table that the stored proc that ran wild...

Found one more clue, the locks/sec almost tripled right at 8:30, thank goodness for Idera's snapshot with alerts

May have found the needle, started going through the snapshots Idera DM saves, as I scrolled through I noticed there is one stored procedure with about 12 occurances that was...