> I have different schema data that I'd like to store across tables, and > it is sorted in chronological order.
Please explain what you mean by "schema", and especially "schema data". In a relational database there is only one schema per database. This single schema describes the tables and indices, views, and triggers stored in that particular database (and, for other database engines, there may be other types of objects described in the schema). Some database engines provide "views" of the single schema and pretend that these views comprise "multiple schemata", however, they are not. They are simply a filtered view of the single schema for the database. With these systems (such as Oracle, SQL Server, etc etc etc) the "schema" you choose simply imposes a "filtered view" and "defaults" on certain attributes of the real single schema. For example, there is an attribute (column) in the schema called "schema name". When you choose a schema then all you get to see are the things where the column [schema name] is equal to what you set, plus the dbo. When you create a new object, the [schema name] is automagically set to be the name of the schema you are choosing to use. The magic of the schema table queries make it "appear" as if the items in your chosen [schema name] obscure the remainder of the schema, but this is only an illusion created by the WHERE clause. > But then I also want to be able to make queries across tables when I > do a query that says after time X, I want it to show me all rows -- > obviously different schema doesn't make this possible. > > So, In my application code I'm going to through loop through all the > tables. The table count is usually high hundreds (~600-800) > > I'm wondering if other people do this kind of stuff. Or another option > is to duplicate the data in some non schematized format (like a > summary table of sorts that essentially duplicates every row in every > table) I really don't understand what you are trying to accomplish. Are you truing (for some unexplained reason) to "partition" data that otherwise would belong in one table into a large number of tables for some reason -- for example, instead of having a column [Colour] which describes the colour of the thing the tuple is describing, instead have a bunch of tables called Red, Yellow, Green, Blue (etc), so that you have to search all of them instead of just one?
