August 1, 2013 at 9:12 am
Thanks for a really easy one, Naseer!
August 1, 2013 at 10:43 am
Dave62 (8/1/2013)
Thanks for the question.Here's an interesting read on the use of VIEW DEFINITION permissions instead of encryption.
Options For Hiding SQL Server Code[/url]
Enjoy!
+1
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 1, 2013 at 12:57 pm
Revenant (8/1/2013)
Thanks for a really easy one, Naseer!
And a great reminder as well!
Not all gray hairs are Dinosaurs!
August 2, 2013 at 2:26 am
Data_God (8/1/2013)
It should be pointed out though that just because you create a view WITH ENCRYPTION, it is still possible for users with the appropriate permissions to see the definition of the view.
Are you sure about that? Which permissions, and how can they see the definition?
August 2, 2013 at 8:35 am
Thanks Guys...! 🙂
Best,
Naseer Ahmad
SQL Server DBA
August 3, 2013 at 4:27 am
By encrypting a view, you help prevent all users (regardless of database privileges), including yourself, from ever seeing the view definition. Thus, you will not be able to alter the view definition. Choose OK to save the view in encrypted form. Choose Cancel to cancel the Save operation.
August 3, 2013 at 12:05 pm
Nice and easy one..
Thanks..
August 5, 2013 at 3:49 am
Good Question. Answer is really easy one.Thanks:smooooth:
August 8, 2013 at 7:14 am
Pretty easy one. Thanks a lot. 🙂
Viewing 9 posts - 16 through 24 (of 24 total)
You must be logged in to reply to this topic. Login to reply