You can make the foreign key non-null, which will force you to have a value, and you can put a unique constraint on the foreign key, making it so only...

There's do and there's juitsu. The "way" or do study in martial arts is a spiritual excercise. The juitsu or "art" is martial in it's intent. Meaning, we're not so...

Well, to quote Adam from Myth Busters, "That's your problem, right there."

Relational data storage more or less requires relationships and those are defined through constraints on the tables. Probably, even...

You also may have columns inside tables with different collation settings. Check that.

There's not enough information to answer this question fully. Yes, you need to use JOIN's to put the tables together, but what columns constitute the primary and foreign keys that...

Rather than changing the locking mechanisms everywhere, I'd strongly suggest looking at the execution plans of the query and the indexes on your tables. Resolve the problems at the root,...

If my understanding of what you're trying to do is correct, then yeah, I think that's the right code. But please, test it and verify it. Don't simply take my...

I know Steve emphasized hitting pads as a way to take off the stress, but I don't mind suggesting, if you don't object to a few bruises (and jambed fingers...

If I'm reading this correctly, something like this:

SELECT wcadmin.WTDocumentMaster.WTDocumentNumber AS NUMBER, wcadmin.WTdocument.nameB2folderingInfo AS FOLDER,

...

Something along these lines should work:

SELECT *

FROM TableA a

WHERE a.Id = (SELECT TOP(1) a2.Id

...

Are these multi-statement table valued functions? If so, understand that this type of function has not statistics. This means the optimizer treats them like a table that returns one row....

If the first guy through creates a plan that uses a scan, unless something fires a recompile of the procedure or the plan ages out of cache, it's going to...

You'll want to rebuild all your indexes and update the space usages after you move it.

But before you move it, use the Upgrade Advisor as mentioned above. There may...

I can't help you on the rogue DBA topic. Hunt 'em down & hurt 'em may be your only option.

As to the rest, why not manage the database code in...

Don't worry about it. There's always more to learn, for everyone. Speaking of which, I need to download 2008 and get started learning new stuff.