Worst possible SQL Server object name?

Select [Select]

From [From]

Where [Where] = 'Where'

And [nvarchar(50)] = 'nvarchar(50)'

And [int] = 1

I find that people in general are pretty good at avoiding bad characters in object names, either because they are smart about it, or because they get bitten pretty quickly if they also don't follow other good habits (like using QUOTENAME() when composing dynamic SQL.  I could com up with plenty of fictional examples, but for me, the most troublesome offenses I come across in real life are:

1. Embedded spaces or periods

2. Not descriptive enough

3. Too descriptive

Every time I have to type a tbl, vw or usp prefix, I shudder.  But these are just annoying and redundant, not necessarily problematic per se.

in DB2 the following code may work:

SELECT WHERE FROM WHERE SELECT

might be a valid query in the appropriate context:

create table where(where char(10));

dbo.AccessImport

I've always found the GROUP table particularly annoying.

We have a vendor who thinks their clever by naming & grouping their underlying schema like an OO application, "Object.Header" and "Object.Detail"  

If they actually used schemas i'd be happier, but they're all within dbo, so it's hundreds of tables following: dbo.[Object.Detail] etc.  Quite a pain.

How about this one...Celko would probably appreciate:

CREATE TABLE #

(iPK int IDENTITY (1,1)

 ,nValue nvarchar (256)

)

Embedded square brackets

CREATE TABLE [[!]]] ([]]] int IDENTITY (1,1) NOT NULL, [[[]]]]] int)

SELECT [[[]]]]], []]] FROM [[!]]]

We can take this one step further if you'd like... Don't do this at home, kids:

declare @ table ([[] int)

select [@].[[]

from @ [@]

Damn you, Adam.  That query gave me a headache. ;)

This stuff pales in comparison to column names I've had to deal with like "X" and "Y".  Yes, single character column names.

A database called "tlog".