I have to admit that I've been guilty of the occasional "tibble" in my time, but I've usually managed to avoid prefixing tables or databases. Of course, you should always avoid using "sp_" as a prefix for stored procedures.

By far the worst example of tibbling I've seen is a database developed by a contractor. I think he designed it by reading an "MS Access 1.0 for Dummies" book. Every table is named "TBL_CMPYNM_SOMETHING", every view is named "VW_CMPYNM_SOMETHING", and every stored procedure is named "sp_cmpynm_something" (where "CMPYNM" is the company name with the vowels removed).

Most tables have a primary key called "ID", although in some cases it's "UniqueID", some have a "UniqueID" and a separate primary key, and some have no primary key at all.

He had some concept of data normalization, but no idea when to stop - hey, you never know when they'll change the number of days in a week, right??!

Of course, once we paid him for the initial work, he ran off in the direction of the bank, laughing maniacally, leaving me to maintain this monstrosity!