Why is it a poor idea?Did we, or did we not, just go through how many hundreds of posts on this very subject, at the end of which you said, "You Win!"?
I have worked in medium-large companies that divide projects into smaller project rather than one-big-EXE. Perhaps you guys are not partitioning properly.What does this have to do with the price of tea in China? I said, "Managing databases is more labor intensive than managing code, so you are, in fact, doing something extra." This is why people hire full-time DBAs (we have two full-timers, and one part-timer), because it takes more effort to manage a database. What in Hades does this have to do with partitioning? An extra database is an extra database.
Adding a new column in Microsoft SQL-Server was a snap.And how did you put that change under revision control? How did you promote that change to production? Or even QA? Of course adding a column is a snap if you aren't managing it properly.
Tell that to the sales/marketing department.Oddly enough, our sales people know what the applications do without searching source code. They also know what the client's are requesting and using. It's called, "specifications" and "documentation". You ought to try it sometime.
Concession noted for posterity (judging by your failure to respond): you admit that you are in fact creating a jump table as described.