November 11, 2009 at 1:54 am
Hi guys, I posted a topic in the security section yesterday but looking at it I think it's more a general question than SQL Server security related, here is the url but I will re-post the text below. Any help on this matter will be greatly appriciated.
http://www.sqlservercentral.com/Forums/Topic816416-1526-1.aspx
I work for a start-up internet retailer/auction house. In the last two weeks we have had a run of people have opened fraudulant accounts to try manipulate auction prices on the site and I have just been asked to try and sort out the problem :ermm:
So far I have been flagging these users up by their email address extentions as they are using Hungarian and Russian email addresses, I then run an update statement on the users table to disable their account. I wanted to create a trigger that would do this for me when a new record has been created in the users table but there is some sort of ADO.Net component in the web site that does the insert into the table so I can't set up the trigger on proc as I thought.
What I wanted to know is if I can set up a trigger on the table to check when a new row has been added which would then check if the conditions I set are true and disable the account accordingly. I would also appriciate any other fraud prevention advise you guys can offer.
November 12, 2009 at 7:56 am
Using a trigger to capture the insert statement would be the best idea.
Good luck.
November 12, 2009 at 8:30 am
The insert trigger will run after the insert from ADO.NET and then examine the table. The new rows will be in the "inserted" virtual table and you can use an update statement to operate on them.
November 13, 2009 at 5:57 am
Thanks guys, working now!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply