VIEWS 3

Question

Post reply

VIEWS 3

Ron McCullough

SSC Guru

Points: 63877
More actions
March 19, 2012 at 8:25 pm

#270390

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]
March 20, 2012 at 3:24 am

This was removed by the editor as SPAM

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

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

baabhu SSCertifiable Points: 6205 More actions · Answer 1

Thank you bitbucket. Nice and straight forward question.

--- Babu

Henrico Bekker One Orange Chip Points: 27652 More actions · Answer 2

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

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 3

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

Carlo Romagnano SSC-Insane Points: 22669 More actions · Answer 4

baabhu (3/19/2012)
Thank you bitbucket. Nice and straight forward question.
--- Babu

+1

Thank you very much.

dawryn SSCertifiable Points: 5481 More actions · Answer 5

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…

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 6

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

Skanker Hall of Fame Points: 3059 More actions · Answer 7

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

Toreador SSChampion Points: 11365 More actions · Answer 8

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').

Michael Riemer SSCertifiable Points: 5190 More actions · Answer 9

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!

dawryn SSCertifiable Points: 5481 More actions · Answer 10

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.

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 11

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

dawryn SSCertifiable Points: 5481 More actions · Answer 12

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.

Dana Medley SSCertifiable Points: 6764 More actions · Answer 13

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!