da-zero (8/24/2010)

---

Carlo Romagnano (8/24/2010)

---

One way to avoid worrying about NULLs is never to use them, always declaring columns as not allowing NULLs and designating default values for "empty" or "unknown"....

SQL2008???

What's the difference from the other versions of sqlserver or ANSI...

One way to avoid worrying about NULLs is never to use them, always declaring columns as not allowing NULLs and designating default values for "empty" or "unknown". This will save...

That's false: COUNT(*) returns the number of ROWS regardless of values of columns. :w00t:

Answer is very easy: SELECT DISTINCT does not have parameters.

It's the same, but many people get it wrong again.:-D:-D:-D

Hugo Kornelis (7/14/2010)

---

Carlo, you are missing an impportant point in your repro.

The performance difference in the question is not caused by rebuilding or converting the table contents, but by rebuilding...

Option 1 is the right and only choice, Option 2 runs fast same as Option 1.

The performance problem is done converting NULL to NOT NULL and not viceversa.

Try this script...

The lesson is:

"GO" may be dangerous if no error checking is done!

If you want an increment of 10, so all values are 0, 10, 20 and so on,

be warn of SET IDENTITY_INSERT <table> ON

may lead to unwanted sequence:

create table #a(i int...

EXEC('SELECT*FROM[sysobjects]ORDERBY1desc')

In this case the "order by" clause is missing

ORDERBY1desc is the alias of [sysobjects]

???????????????????????????????????

😎

Try this:

select*from sysobjects order by 1desc

No space in 1desc

vk-kirov (5/18/2010)

---

Maybe the word "job" is a little bit confusing in the context of the QOTD because in SQL Server it means "specified series of operations performed sequentially by SQL...

Starting from sql2000 sp4 and sql2005, sql2008, the optimizer changed strategy to retrieve data when you specify parameters in the where clause. So, in this case "column1 between @from and...

I full agree.