Re: Determine if column is never used?

My suggestion would be to redo the entire schema the way it should be done.
Then migrate the data into the new schema where it belongs. then for legacy code create views that emulate the old schema. then upgrade the old code one by one until the views are not required.

Old source that contains updates and inserts need the original tables... put triggers on these to reload any new rows into the new schema.

alternatively: you could strip off your best guess columns one by one, and replace the orig table with views for the old style queries.

Then you have a good new system.

Lots of work :)
Randy

chrisoc_at_ans.net wrote:
>
> Is there a way to see the stats on column access within a table?
> The goal would be to either drop columns entirely or to build
> new tables that could be joined if the need exists but the
> frequency is rare.
>
> I am dealing with a legacy database that is highly unnormalized and
> a few tables in it have literally hundreds of columns.
>
> Going through megs of app source (ughhh) would still miss the adhoc
> queries so I want evidence that some data is indeed "dead weight",
> if I can get at the numbers.
>
> Chris O'Connor
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Wed Oct 27 1999 - 16:17:36 CDT