23,000 Tables?

Hi,

I wanted to ask if there are any potential hazards with designing a database application with 23,000 tables vs. 300 tables, but some of these tables will have up to 50 fields, within which a large number of NULLs are stored.

We are migrating a system from an old mainframe to Oracle 10g and want to understand what we are getting into. What admin activities are we letting ourselves in for by having so many tables? it feels wrong, but i am not sure if the alternative with so many empty columns is a better alternative.

thanks in advance for any thoughts people might have!

rgds, chris. Received on Wed Nov 08 2006 - 17:43:04 CST