Re: hiding sql from sql profiler
From: Kalen Delaney (replies_at_public_newsgroups.com)
Date: 07/31/04
- Next message: Mischa Sandberg: "Re: Any tips - string or binary data will be truncated"
- Previous message: Daniel: "There seems to be a memory leak in srv_paraminfo"
- In reply to: tonman: "hiding sql from sql profiler"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 30 Jul 2004 19:26:00 -0700
The only SQL code that can't be seen through a trace, by someone with
sysadmin rights on SQL Server, is the contents of an encrypted stored
procedure. So write all your code in procedures with encryption. There is no
way to prevent sysadmins from seeing ad-hoc SQL statements sent to the SQL
Server.
-- HTH ---------------- Kalen Delaney SQL Server MVP www.SolidQualityLearning.com "tonman" <tonman@discussions.microsoft.com> wrote in message news:1E1ABB7C-09BC-4F0E-A509-7C1BA817342A@microsoft.com... > i would like to prevent my customers from viewing sql statements/stored procs that i create for their use (for example using sql profiler). i basically want to protect my source from reuse. > > is there a way to prevent the output of the sql being issued to the server? > > thanks, > t
- Next message: Mischa Sandberg: "Re: Any tips - string or binary data will be truncated"
- Previous message: Daniel: "There seems to be a memory leak in srv_paraminfo"
- In reply to: tonman: "hiding sql from sql profiler"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading
