Please allow creation of temporary views by lovalvob

Why on earth has this been closed? The suggested workaround is a poor one for many reasons (not least that you have to go and DROP it) and lovalvob has provided a very good reason why this is not-satisfactory.
I agree with lovalvob that temporary views would be very useful for porducing concise, readable code and moreover would support the principle of DRY (i.e. Do not repeat yourself).

I have re-raised this here: https://connect.microsoft.com/SQLServer/feedback/details/714617/t-sql-please-provide-temporary-views

I'm afraid that I didn't notice the reply. The workaround won't work for the following reasons:
1) Create View does not allow the specification of a DB, so you must 'use' tempdb first.
2) I don't think that the 'use' clause is allowed in SPs, which is where most of this would happen.
3) If more than a single instance of the code was running, the drop/create cycles would step on each other.

The purpose of temp views is to isolate complex selection logic near the start of a process and to reference it throughout the rest of the script/sp.

I'm afraid that I didn't notice the reply. The workaround won't work for the following reasons:
1)

Hello, as earlier suggested, there is a workaround using the tempDB, therefore we are not going to pursue this any further.

Best regards
Microsoft SQL Server Engine Team

Thanks for contacing SQL Server team. You can create a view in the tempDB as follows
++++++++++++++
use tempdb
go

create view tempview as select * from locktest..basic_locking where c1 > 200
++++++++++++++++
You can then drop this view. Wondering if this will meet your needs?

thanks
Sunil