Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Creating objects (invisible)

Author  Topic 

saglamtimur
Yak Posting Veteran

91 Posts

Posted - 2004-05-06 : 07:17:50
I create objects with encryption, like

create proc test
with encryption
as
select 1

ok this works fine and nobody can see object text. But my problem is creating object so that nobody can see how it is created. If I execute above statement I can trace it from profiler and see its text. Is there a way to hide this proccess, and nobody can see how it is created.

Thanks in advance.

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-05-06 : 14:29:53
The only people who have access to profiler are the sysadmins. And, no there's no way to restrict this from them. They, being the DBA, need to know what you are putting on the system.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-05-06 : 14:32:24
I suspect that this is so that a third party company can hide their code when installing the database. Don't you have an NDA with them?

Tara
Go to Top of Page

saglamtimur
Yak Posting Veteran

91 Posts

Posted - 2004-05-06 : 18:49:17
Thanks for your responses.
Tara, can you explain what NDA is?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-05-06 : 18:52:10
Non-disclosure agreement. It's part of the contract that you have with the customer.

Tara
Go to Top of Page

MichaelP
Jedi Yak

2489 Posts

Posted - 2004-05-06 : 19:14:08
Even if you encrypt your stored procs, I've been told there are tools that will decrypt them. Bottom line, if someone really wanted to see your stored proc code, they will be able to eventually. This sorta goes back to another lengthy post recently that boils down to "there's not such thing as 100% security." If someone wants to see the code bad enough, there's a way to get it, or get most of it.

These sort of problems are why I like developing hosted applications. The only thing the client gets is a client application. I store all the database stuff on my end, where the client can't touch it.

Michael

<Yoda>Use the Search page you must. Find the answer you will.</Yoda>
Go to Top of Page
   

- Advertisement -