Changing from Table to View

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all

I had a Table which is not well normalised say A. But It was used so much
that all reports - about 250 depend on that.

I have normalised the table and named it differently say B.

I changed the forms where ever updations are done

But as for reports, If use view named 'A' with same feilds(aliases) taken
from different tables will it have any impliations.

To Make myself clear, I will delete Table A and make a view 'A' with from B
and other tables .

I old table A is also rreferenced in stored procedures and Triggers,
functions and other object only in SELECT commands

is it ok or have some implications


Thanks in advance
 
Hi all

I had a Table which is not well normalised say A. But It was used so much
that all reports - about 250 depend on that.

I have normalised the table and named it differently say B.

I changed the forms where ever updations are done

But as for reports, If use view named 'A' with same feilds(aliases) taken
from different tables will it have any impliations.
Click to expand...

Possibly, but you should still try to do it. Mainly, performance may suffer
for some reports. In those cases, fix them by updating them to be aware of
table B. It should usually be a smallish subset of the reports.
To Make myself clear, I will delete Table A and make a view 'A' with from B
and other tables .

I old table A is also rreferenced in stored procedures and Triggers,
functions and other object only in SELECT commands

is it ok or have some implications
Click to expand...

If those stored procedures and triggers don't do updates to A or they only
perform allowable updates to A (A is not an aggregate query, and no update
affects more than 1 table, etc.) then your fine. Again, you might have a
performance hit here or there, and you should optimise the cases that have
problems if there are any.
 
Back
Top