A large part of how the optimizer gets the data out of the tables faster is statistics. When you're creating artificial tables, such as table valued functions, there are no...

Ah, I wasn't aware that changed in 2005. Thanks for letting me know. That'll change decisions in the future.

Personally, I kind of don't care, bit or tinyint, but if something...

I'd say it's because it can, and probably did, put statistics on the columns in the temp table that you did with calculations in the other queries. That would make...

It makes sense, but there's not automated way to do a data cleanup like you're asking for. You either have to clean the data manually, or you need to toss...

The main reason I've received for not using bit fields is because they don't allow null values. You have to put a 0 or 1. That's why you may be...

Steve's much more accurate than I am. You have to remember, I spend most of my time working in development, not production. That makes me a lazy b*****d.

What about collation?

If there is a difference between the databases that might cause some odd behavior, reordering columns, affecting how it deals with null values...mabye... It's just a SWAG.

Partitioning is a whole different discussion, that I'm frankly not qualified to take part in.

As to the size of the log... I treat it the same as the data. I...

It's not exactly an introductory book, but my absolute favorite TSQL book is Itzik Ben Gan's Inside T-SQL Querying. It comes from Itzik's course, which is fantastic.

But, for something a...

There's got to be something funky going on with some sort of settings or something. The reason I say this is because I've created a view and a table based...

Yeah, something odd is going on.

Hmmm.... If you short circuit the event, skip the view and use the query from the view directly... same issue?

Thanks for the code. I made a copy of your table and ran an insert, using NULL values for both the GUID's that were defined. It worked fine. The only...

True, the fact that it's getting the error when dealing with NULL certainly suggests a default or a trigger.

It's never a very popular thing to say, but don't share the SQL Server server with any other process. It's a pretty safe rule of thumb (yeah, there are exceptions).

The output will be to the error log. Get ready, it's messy.

I've never seen a performance hit from those flags or heard about one. We set ours on in...