Phil Parkin (9/7/2012)

---

Lynn's solution is the way to go.

In her solution, basedata is a CTE - effectively a subquery in this case - from which the normalised data is...

Andrew-495157 (9/7/2012)

---

This is a really odd issue!!

A parameterised SP runs fine on my test database wth a certain set of input values.

On the customers's production database with the same...

Try this:

CREATE TABLE #tblBlocks

(

BlockID int,

FieldID...

TravisDBA (9/7/2012)

---

Martin Luther King said "The time is always right to do what is right" so I would urge anyone observing that behaviour at a conference not to stand idly...

ChrisM@Work (9/7/2012)

---

CELKO (9/6/2012)

---

.. it doesn't mean that I don't know any basics of data modeling, RDBMS or Date fields [sic] in SQL. I believe this forum is not just...

tribhuwan.tiwari (9/7/2012)

---

Hi

I need to desin a fucntion which takes three parameters

calculateTime(@threadStatusId,@fromDate,@toDate)

I have table Report which contains the folowwing data

There are 10 types of possible frmStatusId and toStatusId.

PrdId RptId...

Andy Hyslop (9/7/2012)

---

Hi Jeff

Good catch I think that you may be correct on that thinking about it (although I haven't tested either)

I suppose this would be a work around for...

Why does he have to be so anal all the time? It gets real tiring reading it day after day. I wish SQLTeam would take him back.

You are basing a generic question off the data from a specific table and index without giving anyone the benefit of know anything about the table, the data contained in...

pooyan_pdm (9/6/2012)

---

when the index key is non-unique even when you're looking for a single value(a user_seek) sql server performs a range_sacan because there might be more than one records with...

And I gave you a valid answer, scans can be single record scans.

pooyan_pdm (9/6/2012)

---

this index also has some column included in it's leaf level.

Both col1,col2 are non-unique so even if the engine is looking for a single combination of them it should...

Shot in the dark based on what you have posted, single record scans.

I guess we are supposed to be miracle workers here and know just what went wrong given minimal information.

Unfortunately you didn't give very much with which to work. We can't see from here what you see there. What is in the SQL error logs, were there...