I was wondering what might be the pros & cons of separating one app's data in multiple schemas (based on years for example)? The other solution might be to keep it all in one schema and have a naming convention. This is necessary because the data types and length in one (or various) table(s) might vary from year to year.
The data is coming in batch processes that are used by other systems as well. Actually I might say they are built for other systems and we're just hooked up there and using them for our app so we don't have much of the control over them.
One solution might be to decouple the code from the DB and use views, stored proc's etc. But for that I need to know what it the impact of using various schemas, if any... Hence the question. ;)
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads