April 23, 2014 at 8:28 am
how can i restrict the query on query window that contain *(astric)
EXP:-
select * from emp
want to stop this king of query,only for the selected column should be allow.
April 23, 2014 at 8:39 am
kumar4ashwani (4/23/2014)
how can i restrict the query on query window that contain *(astric)EXP:-
select * from emp
want to stop this king of query,only for the selected column should be allow.
Short answer...you can't.
You could jump through a lot of hoops and setup database triggers and all sorts of crazy stuff to try to prevent it but it is only going to slow down the whole system.
Honestly there is nothing wrong select * when used appropriately (like inside an exists). It is however terrible when used to shortcut building the list of columns which is what you are trying to prevent.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
April 23, 2014 at 9:31 am
There was an article on this quite some time back: http://www.sqlservercentral.com/articles/SELECT+*/68324/.
April 23, 2014 at 9:37 am
BrainDonor (4/23/2014)
There was an article on this quite some time back: http://www.sqlservercentral.com/articles/SELECT+*/68324/.
Just shoot me if I ever work in a place that uses that implementation!!! Even the author agrees it is pretty horrible to work with. 😉
It is a novel approach however.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
April 23, 2014 at 10:24 am
I can understand the need to prevent the use in production code, but not in ad-hoc queries when developing and testing (I often use it to evaluate a table structure).
You could have a code review policy and prevent changes to stored procedures, functions and views that won't comply with company standards. You could use tools such as Microsoft SQL Server Data Tools, SQLCop, SQL Code Guard or SQL Enlight to review the code (I couldn't find the right product from Red Gate[/url], would it be Code Guard?).
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply