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...

You really do need to change the query in some fashion to get all three tables joined together

SELECT table1.column1

,table2.column1

,table3.firstname

...

I agree. But I do think you're climbing out on a limb to dismiss the use of column names. Yes, they're a pain the tucas to type, but you could...

You're going to need to clarify just a bit what you're talking about. Do you mean that some tool displayed things in this way? I'm not aware of a facility...

BEGIN and END are logical groupings and control flow statements within a TSQL statement. They aren't terminators to the SQL utility in the same way that GO is. So if...

You can make uniqueidentifiers null. So the problem lies somewhere else. Do you have a trigger on the table or a default on the column that would be causing this?...

While it gets messing to maintain, when we have a number of parameters that may or may not be referenced, basically a search screen, this is how we configure the...

I have to agree. The beauty of the auto-grow is that you don't have to sweat details like that sometimes. The only suggestion I'd make is to set the auto-grow...

Actually, you've got it right. It's going to update alll the rows from one table where the id's match in the second table.

Maybe you phrased the question wrong or I...