I think you've missed the purpose of views in SQL. You're trying to mimic what would've been a scratch tape back in the 1950s on the file system! Your COBOL or FORTRAN program would've instructed the operator to mount a tape on available drive, read and write to it, and then to dismount the tape and return it to general storage.
In the relational world, a view is a virtual table, just as real as a base table. They're not allocated/ deallocated like scratch tapes. In fact, you saw the DBO authority problem when you have the wrong view of how the language works. Have you ever worked in SQL shop everybody had system admin privileges? You never step into the same database twice because it's always changing!
SQL is a declarative language, not a procedural language. That means you tell us what you want in logical terms and you do not procedurally build it row by row. It's a very different mindset. If you post some of your code, we might be able to help you rewrite it.
Please post DDL and follow ANSI/ISO standards when asking for help.