manish.singh (7/17/2009)

---

Hi deepak,

I am just curius to know whether the above solution worked for 4th, 5th level of the child records. I tried here with some sample data but didnt...

Gaby A. (7/16/2009)

---

I guess someone I (remotely) relate to is Ponder Stibbons, one of the few hardworking wizards in Unseen University, unappreciated by his colleagues, but toiling with Hex, his...

At a guess, it could be something to do with session settings, ie SET ANSI_NULLS , SET CONCAT_NULL_YIELDS NULL etc...

Confirm that they are the same in sys.dm_exec_sessions

I think David is referring to this

http://blogs.conchango.com/jamesrowlandjones/archive/2009/05/28/the-curious-case-of-the-dubious-deadlock-and-the-not-so-logical-lock.aspx

If rebuilding the index doesnt help the post the plan , interesting to see if it stopped with GoodEnoughPlanFound ?

So whats the plan like for

SELECT *

FROM dbo.EmailRecipients er

INNER JOIN Emails e ON er.EmailID = e.EmailID

WHERE er.SentDate IS NULL

AND er.SendingComputerName IS NULL

AND (e.EmailTypeName LIKE 'System:%' or

...

Is this functionally the same ???

SELECT *

FROM dbo.EmailRecipients er

INNER JOIN Emails e ON er.EmailID = e.EmailID

WHERE er.SentDate IS NULL

AND er.SendingComputerName IS NULL

AND (e.EmailTypeName LIKE 'System:%' or

...

Personally i think i would be better to have a seperate code path for where @AdditionalUser is and is not null.

Jeff Moden (7/15/2009)

---

Also, here's what the new zipless sqlplan does in IE...

The XML page cannot be displayed

Cannot view XML input using style sheet. Please correct the error and then...

Hmm,

i dont like the scan on the Users table. Really not sure why its done that.

Maybe you sort out the top X users , then join to the Users table

Maybe...

That will run forever as indexing cant be used,

SQLServer will have to scan each row...

Not that i doubt you but, are you 100% sure that that can be the only explanation ? There were no other bugs that could of caused it to...

To satisfy your curiosity, here's your test run through our 'production level' backup server.

SQL Server Execution Times:

CPU time = 109 ms, elapsed time = 129...

I think in Lowells example , most of the delay is returning the data to the client

if you look at the query plans for

SELECT TOP 10 object_id from sys.columns order...

Tried and tested solution

create table #t1(

RecordID integer,

ParentRecordID integer,

Credit integer)

go

insert into #t1 values(1, NULL, 10)

insert into #t1 values(2, NULL, 5)

insert into #t1 values(3, 1, 7)

insert into #t1 values(4, 1, 8)

insert into...