I was always under the impression that this is BAD practice for user written stored procedures, as SQL automatically assumes any proc name starting with "sp_" is a system proc and searches the master database for it first, only going to the user database if it can't find it. This can lead to a loss of performance, or even to the wrong proc being run if your name happens to match an existing system proc.

I've got to be honest, a part of me agrees with Phil here, and I find my teeth on edge when I open a new database at a client's site and see every table prefixed with "tbl" or "tbl_" (or in really bad cases a mixture of both). Over the years as a DBA whenever I've designed a database I've always tried to give tables meaningful names, but assumed that a fellow DBA could tell it was a table without me having to "tibble" it.

And when I find all the column names "tibbled" as well, then it makes me want to flail about with a blunt instrument in a way that would have my neighbours on the evening news saying things like "He seemed such a nice man, always kept himself to himself..." and "He was always so polite and quiet..."