In Sql Server, what would the drawbacks and disadvantages be of using a primary key that is:
Two Character Table Identifier + YEAR + MONTH + DAY + HOUR + MINUTE + MILLISECOND + random integer between 0 and 100?
Why would this be preferred to using an Integer Auto_Incremented field? (Unless it wouldn't, then I want to know that too.)
I would love reasons why this is a really bad design practice. Casting everything in order to get back that integer value is also a total pain in the ass.
I basically stand once chance at getting my small team of developers access to help improve our applications' database, which it needs badly-To avoid situations like primary key Varchar(50) fields with left-padded zero's, or to just start improving the non-normalized database, or comma-separated lists in one field. Help me dba stackExchange, you're my only hope.