Small tables, especially those that occupy less than one extent (that's 8 pages) generally won't defragment.

If I understand the question correctly, you're looking for the UNION operator. To combine the three statements:

SELECT...

FROM....

WHERE...

UNION

SELECT...

FROM..

WHERE...

UNION

SELECT...

FROM...

WHERE...

[/code]

And is that a language term or a mathematic/engineering term?

Actually, you can change the PK from nonclustered to clustered without dropping it. Here's an example:

CREATE TABLE t1

(c1 INT NOT NULL);

ALTER TABLE t1 ADD CONSTRAINT pk_t1 PRIMARY KEY NONCLUSTERED (c1);

CREATE...

Funny, I was wondering the same thing. I even did a google search to try to track it down.

Backups, absolutely.

And, this one does make people crazy, but I've been insisting on it for over a decade now... a tested script to deploy changes to production. No winging it,...

The issue I'm seeing is that Nested Loop operator, NodeId = 17, right before the Hash Match, NodeId = 16, that's performing the aggregation. Two issues there, first, it's using...

Buck Woody addressed this question in a recent blog post:

http://blogs.msdn.com/buckwoody/archive/2008/10/20/erd-designer.aspx

I got that link from our local Microsoft rep. I'm assuming it's on the RSN schedule (Real Soon Now).

If you don't have a clustered index on the table, I'd at least put one on that ID column. After that, take a look at the execution plans to determine...

There are exceptions, but by and large, every table should have a clustered index. The nonclustered indexes have to use RID to track down the data, which is generally not...

I'm not aware of a resource for making these types of decisions except for common sense and experience. You could go to a consulting firm or bounce the ideas off...

What about the Dudettes?

Anyway, short of installing it & checking the version, I'm not sure what you could do.

And while I'm on it, I've run Powershell scripts against SQL Server 2008 before. I created a silly little test script for placing a load on a copy of AdventureWorks...

It looks like it did precisely what you told it to. It limited the names to where they did not equal 'Name1' and it showed those for values not...