﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / Security (SS2K8)  / Disabling an account on unexpected SQL Statement / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Tue, 21 May 2013 11:53:30 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Disabling an account on unexpected SQL Statement</title><link>http://www.sqlservercentral.com/Forums/Topic1366347-1526-1.aspx</link><description>Can you give an example of code not looking genuine? SELECT queries and execution of stored procedures would be hard to manipulate in this way as they don't fire DML triggers. You might be able to do something with extended events or via the results of traces, but if you use a trace, there's always going to be a lag.</description><pubDate>Wed, 03 Oct 2012 06:27:04 GMT</pubDate><dc:creator>K. Brian Kelley</dc:creator></item><item><title>Disabling an account on unexpected SQL Statement</title><link>http://www.sqlservercentral.com/Forums/Topic1366347-1526-1.aspx</link><description>Hi Folks,Wondering if anyone had any ideas on this dilema?I want to be able to trace code through my database, looking for certain patterns of sql code.If the code being run, does not look genuine, i want to be able to lock the account that is sending it.I am considering looking at the dmv's and pulling out the running queries and then locking the account, and send an alert.Are there better ways of doing this?Thanks. </description><pubDate>Mon, 01 Oct 2012 01:40:19 GMT</pubDate><dc:creator>goodhereinit</dc:creator></item></channel></rss>