Post reply

Protecting Intellectual Property - execute access only to SP

  • November 1, 2011 at 9:08 pm

    #1401961

    Thanks, will do that in the stored procs and views... how to do that in tables?

  • November 1, 2011 at 9:23 pm

    #1401962

    PhilM99 (11/1/2011)

    Thanks, will do that in the stored procs and views... how to do that in tables?

    Read this for a nice explanation.

    http://sqlserverperformance.wordpress.com/2011/01/10/fun-with-extended-properties-in-sql-server-2008/

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • November 2, 2011 at 2:04 pm

    #1402412

    PhilM99 (11/1/2011)

    Thanks, will do that in the stored procs and views... how to do that in tables?

    Just don't give any permissions to the tables. Force application to work using stored procedures only. If this is not possible and you have to give to the end users select access on the tables then what do you want to hide? There is no code in the tables. What kind of intellectual property are you talking about then? Column names and types? It doesn't make any sense to hide this information from the client.

    Alex Suprun

  • November 2, 2011 at 8:23 pm

    #1402484

    Of course, I forgot myself. Yes all access is via stored procs, so they don't even need to know about the tables.

    Problem solved. Thanks all. Phil

Viewing 4 posts - 16 through 18 (of 18 total)

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