|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL Profiler: PASSWORD override available?I can appreciate the SQL Profiler exception of:
-- 'password' was found in the text of this event. -- The text has been replaced with this comment for security reasons. However, when you are testing an application where you want to see the specific statement that has the word 'password' in it, is there any way to override this in SQL Profiler? I don't believe it's possible because any way to change this behaviour would
negate the point of the feature -- Show quoteHTH Jasper Smith (SQL Server MVP) http://www.sqldbatips.com I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Chuck Hawkins" <charles.hawkins@NOSPAMjenzabar.net> wrote in message news:OvMU0GF7FHA.1000@tk2msftngp13.phx.gbl... >I can appreciate the SQL Profiler exception of: > -- 'password' was found in the text of this event. > -- The text has been replaced with this comment for security reasons. > > However, when you are testing an application where you want to see the > specific statement that has the word 'password' in it, is there any way to > override this in SQL Profiler? > The feature appears to be based on information coming from the server side
of the application and not from the client side. With SQL 2005 Profiler, I can see queries with PASSWORD in the TextData coming from a SQL 2005 server but not from a SQL 2000 server. So, I'm wondering if there is some undocumented trace flag out there that changes the behavior of the SQL 2000 server to return PASSWORD-stringed TextData? Thanks, Chuck Hawkins Show quote "Jasper Smith" <jasper_smi***@hotmail.com> wrote in message news:eKkqGzG7FHA.3592@TK2MSFTNGP12.phx.gbl... >I don't believe it's possible because any way to change this behaviour >would negate the point of the feature > > -- > HTH > > Jasper Smith (SQL Server MVP) > http://www.sqldbatips.com > I support PASS - the definitive, global > community for SQL Server professionals - > http://www.sqlpass.org > > "Chuck Hawkins" <charles.hawkins@NOSPAMjenzabar.net> wrote in message > news:OvMU0GF7FHA.1000@tk2msftngp13.phx.gbl... >>I can appreciate the SQL Profiler exception of: >> -- 'password' was found in the text of this event. >> -- The text has been replaced with this comment for security reasons. >> >> However, when you are testing an application where you want to see the >> specific statement that has the word 'password' in it, is there any way >> to override this in SQL Profiler? >> > > This was probably a fix/enhancement in the 2005 trace provider that did not
meet the bar for retrofitting into SQL2000. I'm not aware of anything you can do to alter the behaviour in SQL2000 (but that doesn't mean it doesn't exist <g>) -- Show quoteHTH Jasper Smith (SQL Server MVP) http://www.sqldbatips.com I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Chuck Hawkins" <charles.hawkins@NOSPAMjenzabar.net> wrote in message news:ujHCT4G7FHA.476@TK2MSFTNGP15.phx.gbl... > The feature appears to be based on information coming from the server side > of the application and not from the client side. > > With SQL 2005 Profiler, I can see queries with PASSWORD in the TextData > coming from a SQL 2005 server but not from a SQL 2000 server. > > So, I'm wondering if there is some undocumented trace flag out there that > changes the behavior of the SQL 2000 server to return PASSWORD-stringed > TextData? > > Thanks, > > Chuck Hawkins > > > > "Jasper Smith" <jasper_smi***@hotmail.com> wrote in message > news:eKkqGzG7FHA.3592@TK2MSFTNGP12.phx.gbl... >>I don't believe it's possible because any way to change this behaviour >>would negate the point of the feature >> >> -- >> HTH >> >> Jasper Smith (SQL Server MVP) >> http://www.sqldbatips.com >> I support PASS - the definitive, global >> community for SQL Server professionals - >> http://www.sqlpass.org >> >> "Chuck Hawkins" <charles.hawkins@NOSPAMjenzabar.net> wrote in message >> news:OvMU0GF7FHA.1000@tk2msftngp13.phx.gbl... >>>I can appreciate the SQL Profiler exception of: >>> -- 'password' was found in the text of this event. >>> -- The text has been replaced with this comment for security reasons. >>> >>> However, when you are testing an application where you want to see the >>> specific statement that has the word 'password' in it, is there any way >>> to override this in SQL Profiler? >>> >> >> > > |
|||||||||||||||||||||||