July 9, 2009 at 7:28 am
I create SQL queries that a number of people use, and sure enough it seems that every so often a comma gets added, or code goes missing. Is there a way to 'lock' a query from this sort of manipulation? Unfortunately some of the queries require the user to input information - so I am not sure this is possible.
As an alternative, I may just create password protected word documents of the queries as back up.
July 9, 2009 at 8:22 am
Can these SQL statements be defined as views ? If so, then the users can just select from the views and add a where clause as needed.
SQL = Scarcely Qualifies as a Language
July 9, 2009 at 8:50 am
make it a stored procedure, grant them execute permission on it
July 15, 2009 at 7:06 am
Here is an idea: You could always just put all the .sql files (assuming the workers know which ones they need) and put it out somewhere (team site, read-only folder, etc) which they could have access. They open it, input what they need and if they need a customized version they can save it and use it for themselves but can't change the original query you have set up. Sounds more like a file management problem.
July 16, 2009 at 12:08 pm
russell (7/9/2009)
make it a stored procedure, grant them execute permission on it
Remember to have the stored proc check the input value is formatted properly, or else the same error problem will occur.
Gaby
________________________________________________________________
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply