How do I fire a sql statement from being seen by a trace session

Hi
I am trying to do an OPENROWSET call to an ODBC driver which needs a key
to work but i need to keep the KEY hidden from being seen/ traced.
Is there a way to execute an sql statement and disable a tracing session or
another way stop a OPENROWSET argument from being traced and duplicated.
Thank you in advance for your time..
EdwinEdwin,
You can't hide anything away from the Profiler. It's not guaranteed that
the Profiler will get every statement but you can't hide statements
kind regards
Greg O
Need to document your databases. Use the firs and still the best AGS SQL
Scribe
http://www.ag-software.com
"Exonet Developer" <Exonet Developer@.discussions.microsoft.com> wrote in
message news:C5F9A585-7362-41AC-8C2D-6D7574FFF60E@.microsoft.com...
> Hi
> I am trying to do an OPENROWSET call to an ODBC driver which needs a key
> to work but i need to keep the KEY hidden from being seen/ traced.
> Is there a way to execute an sql statement and disable a tracing session
> or
> another way stop a OPENROWSET argument from being traced and duplicated.
> Thank you in advance for your time..
> Edwin|||you can add sensitive text like "sp_addlogin" as comment in your sql
statements and sql profiler will hide this statement
Aleksandar Grbic
MCDBA, Senior Database Administrator
"Exonet Developer" wrote:

> Hi
> I am trying to do an OPENROWSET call to an ODBC driver which needs a key
> to work but i need to keep the KEY hidden from being seen/ traced.
> Is there a way to execute an sql statement and disable a tracing session o
r
> another way stop a OPENROWSET argument from being traced and duplicated.
> Thank you in advance for your time..
> Edwin|||Hi Aleksandar,
Can you give me an example of this. I don't really understand what you mean
kind regards
Greg O
"Aleksandar Grbic" <AleksandarGrbic@.discussions.microsoft.com> wrote in
message news:FD863E94-89C2-45D3-B682-F7AA03E0C07C@.microsoft.com...
> you can add sensitive text like "sp_addlogin" as comment in your sql
> statements and sql profiler will hide this statement
> --
> Aleksandar Grbic
> MCDBA, Senior Database Administrator
>
> "Exonet Developer" wrote:
>

How do I fire a sql statement from being seen by a trace sessi

:o) Your tip works great for me.. Thank you very much Aleksandar.
"Aleksandar Grbic" wrote:
> you can add sensitive text like "sp_addlogin" as comment in your sql
> statements and sql profiler will hide this statement
> --
> Aleksandar Grbic
> MCDBA, Senior Database Administrator
>
> "Exonet Developer" wrote:
>But that was bad advice indeed.
Infact another security enhancement in SP4 suppress every statement that
contains the text 'password'
But these things may change in the future.
Roji. P. Thomas
Net Asset Management
http://toponewithties.blogspot.com
"Exonet Developer" <ExonetDeveloper@.discussions.microsoft.com> wrote in
message news:9AD6E379-C45C-4480-9125-963C17BD952F@.microsoft.com...
> :o) Your tip works great for me.. Thank you very much Aleksandar.
> "Aleksandar Grbic" wrote:
>

How do I fire a sql statement from being seen by a trace sessi

try
select * from <table> -- sp_addlogin
and this statement will not be show in profiler
Aleksandar Grbic
MCDBA, Senior Database Administrator
"GregO" wrote:

> Hi Aleksandar,
> Can you give me an example of this. I don't really understand what you me
an
> kind regards
> Greg O
> "Aleksandar Grbic" <AleksandarGrbic@.discussions.microsoft.com> wrote in
> message news:FD863E94-89C2-45D3-B682-F7AA03E0C07C@.microsoft.com...
>
>Hi ,
Well I didn't know that worked. Anyway you can still find the SQL in
syscacheobjects
select * from dbo.syscacheobjects
kind regards
Greg O
Need to document your databases. Use the firs and still the best AGS SQL
Scribe
http://www.ag-software.com
"Aleksandar Grbic" <AleksandarGrbic@.discussions.microsoft.com> wrote in
message news:055AE9C0-055A-4543-AFE4-BAD470D25771@.microsoft.com...
> try
> select * from <table> -- sp_addlogin
> and this statement will not be show in profiler
> --
> Aleksandar Grbic
> MCDBA, Senior Database Administrator
>
> "GregO" wrote:
>|||answer is:
Aleksandar Grbic
MCDBA, Senior Database Administrator
"GregO" wrote:
> Hi ,
> Well I didn't know that worked. Anyway you can still find the SQL in
> syscacheobjects
> select * from dbo.syscacheobjects
>
> --
> kind regards
> Greg O
> Need to document your databases. Use the firs and still the best AGS SQL
> Scribe
> http://www.ag-software.com
>
> "Aleksandar Grbic" <AleksandarGrbic@.discussions.microsoft.com> wrote in
> message news:055AE9C0-055A-4543-AFE4-BAD470D25771@.microsoft.com...
>
>|||Hi Aleksandar ,
Not disputing your post but being seen/traced can mean being seen (which it
can via syscacheobjects) or being traced
kind regards
Greg O
Need to document your databases. Use the firs and still the best AGS SQL
Scribe
http://www.ag-software.com
"Aleksandar Grbic" <AleksandarGrbic@.discussions.microsoft.com> wrote in
message news:E33A74C8-4BA6-4909-8D41-B828416B6C53@.microsoft.com...
> answer is:
>
> --
> Aleksandar Grbic
> MCDBA, Senior Database Administrator
>
> "GregO" wrote:
>|||;)
--
Aleksandar Grbic
MCDBA, Senior Database Administrator
"GregO" wrote:

> Hi Aleksandar ,
> Not disputing your post but being seen/traced can mean being seen (which i
t
> can via syscacheobjects) or being traced
>
> --
> kind regards
> Greg O
> Need to document your databases. Use the firs and still the best AGS SQL
> Scribe
> http://www.ag-software.com
> "Aleksandar Grbic" <AleksandarGrbic@.discussions.microsoft.com> wrote in
> message news:E33A74C8-4BA6-4909-8D41-B828416B6C53@.microsoft.com...
>
>