Post reply

Preventing Database access

  • November 5, 2004 at 10:16 am

    #163616

    Hi,

    One of our products uses SQL Server as the database engine. Now, we don't want anyone buying it to be able to access objects like stored procs and triggers.

    Has anyone got any ideas of how to achieve this. Is it possible at all ?

    Thanking in anticipation

    Hamid

  • November 5, 2004 at 12:32 pm

    #529149

    Hi,  We had to deal with the same thing,

    We used the "with encryption" clause on all of the stored procedures ect.

    a few warnings:

    Once you encrypt the stored procedure you cannot read it yourself.  Keep .SQL files of everything you write or do not encrypt the procedures until the database is Complete and stable.

    Encrypted stored procedures cannot be scripted with Generate script (see above)

    Encrypted stored procedures can be reverse engineered if a person is motivated enough (I got one back after an oops).

    We  determined that the benifits of using stored procedures out weighed the relatively minor chance that someone would reverse engineer them. 

     

    HTH

    Tal McMahon

     

     

     

    Kindest Regards,

    Tal Mcmahon

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply