john.arnott (6/8/2009)

---

dave.farmer (6/8/2009)

---

Dave (and others),

I believe you got a point simply by posting your response. And hey! I think I get...

Irish Flyer (6/5/2009)

---

NCHAR(1) should not be used, because it is, again, an unnecessary overhead. ASCII character columns, when used with UNICODE column data in T-SQL, are automatically converted for...

Hi Jason,

It...

So, a few problems here:

- "C:\mssql" is not a default install folder, and most people would probably not have their SQL server instance or files installed there;

- If...

Do you have a ready blog article for...

Sorry, I'm in an all-2000 environment right now. Testing is just a question of copying Gail's code from...

Alright, alright, point taken - no more converting to float... now I need to go explain the dateadd/datediff thing to my developers...

I was hoping to be able to provide...

GilaMonster (4/28/2009)

---

Tao Klerks (4/28/2009)

---

As I understand it now, for stored procedures "parameter sniffing" will only happen (or be relevant) if there is not already a full compiled execution/query plan for...

Alright, I lied - one follow-up:

As I understand it now, for stored procedures "parameter sniffing" will only happen (or be relevant) if there is not already a full compiled execution/query...

Thanks Gail, your articles clarified all the questions I had!

The last one also brought to light a potential issue we have with a number of procedures in one of my...

Thanks Paul!

You've just added another dimension of complexity to SQL Performance tuning for me, now I have to go away and think about this. 🙂

The things that are most unclear...

This is not something I had ever heard of:

Paul White (4/28/2009)

---

Though the example given may not result in a good plan either, because SQL Server cannot sniff the local variable...

Interesting approach - we use Convert, relying on the fact that DateTime values are internally stored as floating-point values, with every whole number representing a day:

SET @DateWithoutTime = Convert(DateTime, Floor(Convert(Float,...

Hi,

The following statement is untrue: "it is always a good practice to use DATEDIFF method for date comparison instead of making comparison using logical operators (,=)".

As the previous two posters...

Just in case anyone "in the know" is still on this thread, can anyone explain this phenomenon in SQL Server 2000?

I looked for an explanation among the many (fascinating) comments...