Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Limiting view to only work when called from a stored procedure Expand / Collapse
Author
Message
Posted Friday, April 23, 2010 10:41 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, September 22, 2016 6:31 AM
Points: 137, Visits: 1,355
I 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
WHERE @@PROCID <> 0

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.)

Andrew

Edit: 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.


--Andrew
Post #909671
Posted Friday, April 23, 2010 10:44 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Thursday, September 22, 2016 4:54 AM
Points: 14,468, Visits: 38,065
i 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 SELECT * FROM MillionRowTable against all the time just to see the table structure; that'd prevent any significant delays!


Lowell

--
help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!
Post #909672
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse