InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 09:25:13 GMT20http://www.sqlservercentral.com/Forums/Topic909671-49-1.aspxi actually can see how that is a good idea; some views pulling together a lot of stuff shouldn't be ad hoc queried;I like the idea.i might actually rename some tables and create views with the original name and add that feature;I have some MillionRowTables that developers query [b]SELECT * FROM MillionRowTable [/b]against all the time just to see the table structure; that'd prevent any significant delays!Fri, 23 Apr 2010 10:44:57 GMTLowellhttp://www.sqlservercentral.com/Forums/Topic909671-49-1.aspxI have a rather long, complex view that should only be called from inside a stored procedure (one right now, possibly more later). Because it takes so long to execute without a WHERE clause, and since it should really only be used inside procedures that specify the necessary conditions, I want to make sure this view is never called directly. Setting the correct access rights will guarantee this for the most part, but I would like to even restrict ad hoc queries by someone with administrative access to the database.To do this, I added the clause [code="sql"]WHERE @@PROCID <> 0[/code] to the end of the view definition. That way, if it is queried directly, it returns zero rows but it still returns the expected rows when called inside the procedure.Other than documentation, are there other potential problems this might cause? Is this overkill?(I know it needs to be documented, and that is an issue because it is too easy for someone to edit the view definition in the GUI and cause the comments to disappear.)AndrewEdit: Ok, I tried. When I preview this it looks the way I want it, but when I view the actual post it converts the SQL inequality to HTML entities.Fri, 23 Apr 2010 10:41:10 GMTAndrew in WV