VIEWS 3

  • Comments posted to this topic are about the item VIEWS 3

    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]

  • Thank you bitbucket. Nice and straight forward question.

    --- Babu

  • Nice one, thanks. No room for error there.

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

  • According to CREATE VIEW (Transact-SQL):

    When a view is created, information about the view is stored in the following catalog views: sys.views, sys.columns, and sys.sql_expression_dependencies.

    Information that is stored in system tables also consumes space...

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

  • baabhu (3/19/2012)


    Thank you bitbucket. Nice and straight forward question.

    --- Babu

    +1

    Thank you very much.

  • Koen Verbeeck (3/20/2012)


    According to CREATE VIEW (Transact-SQL):

    When a view is created, information about the view is storedin the following catalog views: sys.views, sys.columns, and sys.sql_expression_dependencies.

    Information that is stored in system tables also consumes space...

    Of course it does. You explained :w00t:

    minimal space required for the CREATE VIEW statement…

  • dawryn (3/20/2012)


    Koen Verbeeck (3/20/2012)


    According to CREATE VIEW (Transact-SQL):

    When a view is created, information about the view is storedin the following catalog views: sys.views, sys.columns, and sys.sql_expression_dependencies.

    Information that is stored in system tables also consumes space...

    Of course it does. You explained :w00t:

    minimal space required for the CREATE VIEW statement…

    That is the space for the CREATE VIEW statement. That is stored in the sys.sql_modules catalog view. What I'm going after is that extra information is also stored in other catalog views. Not just the CREATE statement.

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

  • Nice question, got it right without having to look anything up. I must be slowly learning something.

  • This was removed by the editor as SPAM

  • Koen Verbeeck (3/20/2012)That is the space for the CREATE VIEW statement. That is stored in the sys.sql_modules catalog view. What I'm going after is that extra information is also stored in other catalog views. Not just the CREATE statement.

    +1

    I chose the same "wrong" answer for the same reason. The question was explicit in excluding the CREATE, so it's a fair assumption that the other system tables are not excluded (or it should have said 'minimal space required for the system tables').

  • Thanks for the nice easy question. Had to think about the objects held in the system views, but figured that wasn't what you were testing and where trying to cover with the "space used for the Create Statement" - since you can't create it without populating all the system views!

  • Koen Verbeeck (3/20/2012)


    That is the space for the CREATE VIEW statement. That is stored in the sys.sql_modules catalog view. What I'm going after is that extra information is also stored in other catalog views. Not just the CREATE statement.

    All mentioned is stored in system catalogs to make views operational and takes minimal space required after create view statement is executed. Catalog views are one form of means to query data from system catalogs.

  • dawryn (3/20/2012)


    Koen Verbeeck (3/20/2012)


    That is the space for the CREATE VIEW statement. That is stored in the sys.sql_modules catalog view. What I'm going after is that extra information is also stored in other catalog views. Not just the CREATE statement.

    All mentioned is stored in system catalogs to make views operational and takes minimal space required after create view statement is executed. Catalog views are one form of means to query data from system catalogs.

    It takes minimal space, but space is space. And it ain't only the CREATE VIEW statement...

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

  • Koen Verbeeck (3/20/2012)


    It takes minimal space, but space is space. And it ain't only the CREATE VIEW statement...

    I agree any metadata takes space, there is no question about it. Everything about database structure is stored in such form and it takes a lot less space than data and indexes.

  • Great easy question. I think I sat there with the answers already checked for a few minutes thinking to myself, "What's the catch?" and trying to figure out what it was, but there wasn't one. 🙂



    Everything is awesome!

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

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