I guess I'll be alone in this. :-D I don't believe it's necessarily a bad design at all.
First, having the 80 files won't degrade performance. It won't enhance it, but it won't degrade it.
As for maintenance and administration, it won't cause any heartache if you've automated things like backups. It fact, it could reduce backup times if your automation checks to see if there have been inserts, updates, or deletes and backing up only those files that have actually experienced a change.
It will also make dropping a customer easier in the future if the system was setup to tolerate just dropping a file.
Last but not least, if will also allow for "piecemeal" restores if that was a consideration in the grand design of things.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs