SQL views

  • Error Handler

    Ten Centuries

    Points: 1086

    Comments posted to this topic are about the item SQL views

    Naseer Ahmad
    SQL Server DBA

  • kapil_kk


    Points: 21316

    Easy one for the day 🙂

    To get quick answer follow this link:

  • Vinay Kumar


    Points: 6098

    kapil_kk (7/31/2013)

    Easy one for the day 🙂

    +1 🙂

    Vinay Kumar
    Keep Learning - Keep Growing !!!

  • Lokesh Vij


    Points: 10836

    Thanks for the easy one Naseer!

    ~ Lokesh Vij

    Guidelines for quicker answers on T-SQL question[/url]
    Guidelines for answers on Performance questions

    Link to my Blog Post --> www.SQLPathy.com[/url]

    Follow me @Twitter

  • RossRoss


    Points: 1646

    Thought this was a trick question for a minute!

  • Koen Verbeeck

    SSC Guru

    Points: 258965

    Easy one today, thanks.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Carlo Romagnano


    Points: 21987

    Easy qotd, but explanation is really confused.

    Schemabinding doesn't hide the definition and users of the database could still view the definition if TDE is enabled.

    Why do you think that Schemabinding should hide the definition of the VIEW?

    TDE encrypts only data on storage, but "database user" can simply see them by a SELECT.

  • This was removed by the editor as SPAM

  • Bangla

    Hall of Fame

    Points: 3137

    Nice one...

  • Anipaul


    Points: 24681

    Simple and good one....



    Points: 5507

    Easy one for the day

  • Data_God


    Points: 2772

    Nice question and the answer was quite obvious. 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. Also, WITH ENCRYPTION prevents the view from being published as part of SQL Server replication.

    See below for the documentation from MSDN



    Indicates that SQL Server will convert the original text of the CREATE VIEW statement to an obfuscated format. Note that obfuscated views can be reverse engineered because SQL Server must de-obfuscate views for execution. In SQL Server 2000, the obfuscated text is visible in the syscomments system table and may be susceptible to de-obfuscation attempts.

    Using WITH ENCRYPTION prevents the view from being published as part of SQL Server replication.

  • Data_God


    Points: 2772

    Just to be clear, in my previous reply, the view definition in syscomments can be de-obfuscated in SQL Server 2000 for those of us who are still having to maintain very old systems that can only be run on SQL 2000. (Yes, we have two applications that our company depends upon that can only be run on SQL 2000). I would love to retire these systems but the powers that be in the company insist that we must keep these systems around because they find them so useful and are "deathly afraid of change".

  • Tee Time

    Hall of Fame

    Points: 3693

    Good question!

  • Dave62


    Points: 6664

    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]


Viewing 15 posts - 1 through 15 (of 25 total)

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