to be clear - do you have an index on sourceid in t1?

it might be wise to take a snapshot of the query plan and post it up here

david.alcock (4/25/2012)

---

Just wanted to ask, if a log file has got too big and then subsequently a log backup has been taken, the recovery mode switched to simple but the...

csarsonas (4/25/2012)

---

@michael-2, sir you're right... i didn't able to put indexes in DRSummTemp table (this is just an extension table handling current records). The original table contains nulls and...

also is DRID a foreign key? - it looks like it to me - why is it nullable? is there a foreign key constraint on it? - i'd definatly look...

no indexes on drsumtemp then ? - you said 600k rows.... i'm guessing the correct indexes will make a difference

sean's solution proboably performs better than mine

even better, i formatted it as you wanted

select l.name,test.testdate from tests

inner join

(

select locid,max(testdate) as md from tests

group by locid

) as lf

on lf.locid=tests.locid and lf.md=tests.testdate

inner join location l on l.locid=tests.locid

where...

select tests.* from tests

inner join

(

select locid,max(testdate) as md from tests

group by locid

) as lf

on lf.locid=tests.locid and lf.md=tests.testdate

where pfreal<0.7

somebody forgot to close and deallocate their cursor!! 😛

Single user on a particular module will have an estimation of 4-5 sec data retrieval (stored procedure was used to retrieve data). row count of the table is 600,000+ records...

this looks like an ideal candidate for redesigning the tables into a single and using range partitioning for each month

the output of your procedure is in a dataset. it is management studio that chooses how to display this.

the only way for management studio to display it how you want...

there there a trigger on the target table ?

in the original suggestion it was stated to use a raid 1 (mirror) for the C and D drives - but this would mean your d: drive that takes the...

are you replicating triggers as well?

the PK violations could be caused by a trigger at the subscriber.

if not then have a look at xp_replcmds and related extended stored procs (i...