This article should help you: http://www.sommarskog.se/dyn-search.html

You can begin by posting the errors and the code that produces them.

Agreed completely. There are still plenty of sites on 7.0 and even some on 6.5. Getting 2000 certification now will be valuable for years to come (or at...

Sunil,

If you search groups.google.com you can probably find some "brain dumps" of the exam... That may be helpful. You should also review all of the past questions of the...

Julian,

Personally I tend to avoid ISNULL altogether; COALESCE behaves identically with only two values, and is a standard function as opposed to the proprietary ISNULL. One less thing to...

David,

Hmm, let's see... For a table that has a list of countries... How about "Countries"?

Internationalization and schema naming schemes gets into some strange territory. The philosophical question must be...

Thomas:

Navigation of an adjacency list requires looping or recursion. Itzik Ben-Gan has some articles showing some techniques for doing this; check the SQL Server Magazine archives here:

Can you put either an IF block or a CASE expression in to eliminate the error completely? Wouldn't you rather safely handle it?

David,

Enlighten us as to the contents of the mysterious A35020 table.

As for naming schemes, I personally think the common-sense scheme is best: Name the table based on whatever it contains!...

I haven't ever had to maintain 300 lookup tables, but in an app that required around 150, each with between maybe 5 and 20 rows, it was pretty easy. ...

Ahh, yeah, I definitely agree with that

I agree with Calvin Lawson on this, it's not a performance question but a maintenence question.  For instance, CHECK constraints (CHECK x IN ('A', 'B', 'C')) will perform marginally better...

Here are two articles that argue the opposite:

http://www.sqlservercentral.com/columnists/dsumlin/lookupstrategy.asp

http://www.sqlservercentral.com/columnists/nraghavendra/storekeystoringmiscdata.asp

You'll notice in one that I got into a battle with the author about it...

David,

When developers attempt to use these tables to get rid of JOINs, they'll convert this:

SELECT AuxTbl1.Value AS Aux1, AuxTbl2.Value AS Aux2

FROM SomeTable

JOIN AuxTbl1 ON SomeTable.AuxID1 = AuxTbl1.AuxID1

JOIN AuxTbl2 ON SomeTable.AuxID2...