I am working with a vendor-supplied database, and my team found a very curious structure in their schema. In place of a table, there is a view containing only hard-coded values, with this definition: (names and values changed to protect the ... well, whomever) create view dbo.thestatus as select 0 status,'foo' status union select 1,'bar' union select 2,'grak' union select 3,'gnict' union select 4,'schmoo' union ... etc. I do not have a tremendous long experience with database design, but at face value this seems like a very slow structure, because I have a hunch it cannot be indexed, and that the query optimizer would probably react with only fear and puzzlement when asked to use this to compose a query result. We are in the process of evaluating/tuning for performance on this system. Am I crazy? Is there a reason anyone can think of that would make this structure a legit design, that I am not aware of? I want to just change this to a table with the same name. Eschew obfuscation, whilst doggedly pursuing the reduction of complexification.