Re: Security violation by my host



Mike (no@xxxxxxxxx) writes:
Cannot answer your question directly as you need legal advice however in
the mean time I would sugest adding encryption to you stored procedure
as follows:

CREATE PROCEDURE MyProcedure @Pramr1 int, @AnotherParam nvarchar(10), ....

WITH ENCRYPTION

AS

.SQL code

GO

This will encrypt the SP in the database so if anyone opens it will be
unreadable. A word of warning make sure you have the SP code some where
safe.

Note that this is not real encryption, only obfustication. Anyone who
wants to get the code in clear text, and who knows how to do a Google
search will do so.


--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.



Relevant Pages

  • Re: MS Access linked tables SQL Server
    ... Protocol Encryption selection so that all connections to the SQL Server are ...
    (microsoft.public.sqlserver.security)
  • Re: SSIS as part of scheduled job fails
    ... Can't even open the package. ... Deloyed to SQL store. ... Microsoft SQL Server Management Studio ... Encryption not supported on SQL Server. ...
    (microsoft.public.sqlserver.dts)
  • Re: SSIS as part of scheduled job fails
    ... Can't even open the package. ... Microsoft SQL Server Management Studio ... Encryption not supported on SQL Server. ...
    (microsoft.public.sqlserver.dts)
  • Re: Encryption
    ... I realize that almost any encryption scheme can be cracked if you throw ... using "in the box" SQL Server technologies. ... Has the behavior of native SQL Server encryption changed such this ... So it's difficult what security hole you ...
    (microsoft.public.sqlserver.security)
  • Re: Encryption
    ... migrate to Sql 2005/8 eventually. ... SA can bypass the encryption. ... The 3rd party shim we use now has caused many ongoing compatibility ... Has the behavior of native SQL Server encryption changed such this ...
    (microsoft.public.sqlserver.security)