2

Will moving views from one schema to another have any adverse effect on performance?

I have about 40 views in one schema. I want to create a new schema which will have all the correct permissions. Suppose TableA resides in schema A. So my view will be in schema A. So I would do simply select * from TableA. Now I move this view to schema B. Since the table is in schema A, I would need to do select * from A.TableA. Will this cross-schema query cause any performance issues?

derobert
  • 49,731
  • 15
  • 94
  • 124
Saro Khatchatourian
  • 1,047
  • 3
  • 14
  • 24

2 Answers2

4

this is not where you might start in a performance review.

the sql of the actual view is probably far more important than which schema you place it in.

edit:

where the view resides should not affect performance. (aside from how the schema is laid out across blocks and datafiles)

Randy
  • 16,480
  • 1
  • 37
  • 55
  • I am not sure if my point is coming across. I have about 40 views in one scheme. I want to create a new scheme which will have all the correct permissions. The code will exeucte because we will test it. Suppose TableA resides in schemeA. So my view will be in schemeA. So I would do simply select * from TableA. Now I move this view to SchemeB. since the table is in SchemeA, I would need to do Select * FROM SchemeA.TableA. Would this cause any performance issues? As far as I know, the answer is no. Just wanted to confirm. Thanks. – Saro Khatchatourian Oct 07 '11 at 15:49
2

If it's not a materialized view, it should have very little effect on performance.

Cade Roux
  • 88,164
  • 40
  • 182
  • 265