Whoops. Hold on a second. These are all views. We're dealing with nested views right? Ah, that adds a pretty severe level of complexity. It's resolving all the objects on...

Well, the optimizer is going through a binding process on the query. It has to resolve everything involved before it begins the process of optimization. I suspect that's the step...

Using sqlcmd would be the 2005ie way to do it. Same for 2008.

I'm sorry, "first paper"? Do you mean what do you read to get started? Personally I'd suggest you read Craig Mullin's "Database Administration" for a thorough overview of the job....

I'm not aware of a calculation for determining this. Not only is it dependent on the IO of the system, but it's also going to depend on how much activity...

If you're creating a table, there should be a toolbar visible at the top of the screen that includes a button called "Manage Indexes and Keys." It shows a little...

In addition to the suggestions above, it's worth noting that SQL Server 2008 offers Change Data Capture, another way to monitor what was changed in the data.

That's a huge topic. There have been books written about it (note the bottom of this post 😀 ). Which indexes you place on the tables really depends largely on...

It's a binary format that SQL Server uses. Why on earth are you worried about that?

I would give that resume the hairy eyeball, but I think I'd still consider them, but only if they looked so great as to be able to drop that sort...

That is a fantastic document isn't it?

To get around most of Seattle you can walk or ride the bus. It's a very metropolitan area (think New York, London) and not all spread out like LA or...

Yep, you've got the answer right there.

SQL Server parse and compile time:

CPU time = 156 ms, elapsed time = 381 ms.

That parse & compile time is pretty long. It's...

Right. That IO is exactly what we should expect to see. Now we need to see the execution times... Actually, especially the compile time for the query.

Are you running...

OK. I'm stupid.

Of course it gets different execution plans. What I said before about the view, that it runs as is, that's flat out wrong. Instead SQL Server unpacks...