Growing Need for a SELECT TRIGGER - by Arnie Rowland

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 212165 Comments
Status Closed Workarounds
Type Suggestion Repros 1
Opened 9/25/2006 5:30:54 PM
Access Restriction Public



My post today at: microsoft.public.sqlserver.programming...

Perhaps there hasn't been a groundswell of interest since in the past, it 
was not seen as technically practical.

However, as you indicated, since the underlying architecture has changed, 
and it may not be overly complex to implement, I think that there is a 
growing 'real' market need -that will grow into a strong demand in a 
relatively short time.

You only have to deal with HIPPA, where all data reads containing patient 
medical information MUST be logged, to quickly understand the need for a 
SELECT trigger. I suspect that upcoming regulatory approaches concerning 
data privacy (read: identity theft) will obviate a need for SELECT triggers 
with concomitant logging.

I agree, it is easy to do the logging using stored procedures, and I require 
all data access to be through stored procedures. But the majority of .NET 
applications being created, using Microsoft tools, instructions, and 
examples, are using direct table (or view) access in the DAL with SELECT 

Put me down as one who supports adding a SELECT trigger to the wish list.
Sign in to post a comment.
Posted by Microsoft on 9/27/2006 at 6:56 PM
Hi Annie
Thanks for your feedback. We are certainly considering your suggestion for future release of SQL Server.

- Christian