schemabinding

Cannot create index on view because the view is not schema bound error 1939

泄露秘密 提交于 2019-12-04 16:49:01
问题 The third part of this assignment I'm working on says, "Create and index the existing Northwind view called “dbo.Orders Qry” based on the columns OrderID and EmployeeID." It is expected that I will get an error; however, my instructor only told us to Google it. I did, but scheme binding isn't even in this week's lesson or any others, and the things I've found are too in-depth for me to understand. Is this an issue of me not checking a box or changing a setting somewhere? 回答1: Sounds like this

Cannot create index on view because the view is not schema bound error 1939

时光总嘲笑我的痴心妄想 提交于 2019-12-03 10:38:42
The third part of this assignment I'm working on says, "Create and index the existing Northwind view called “dbo.Orders Qry” based on the columns OrderID and EmployeeID." It is expected that I will get an error; however, my instructor only told us to Google it. I did, but scheme binding isn't even in this week's lesson or any others, and the things I've found are too in-depth for me to understand. Is this an issue of me not checking a box or changing a setting somewhere? Sounds like this is describing an indexed view , you can read up on them at Microsoft's site here . Microsoft enabled this

Downsides to “WITH SCHEMABINDING” in SQL Server?

烂漫一生 提交于 2019-12-03 02:55:29
问题 I have a database with hundreds of awkwardly named tables in it (CG001T, GH066L, etc), and I have views on every one with its "friendly" name (the view "CUSTOMERS" is "SELECT * FROM GG120T", for example). I want to add "WITH SCHEMABINDING" to my views so that I can have some of the advantages associated with it, like being able to index the view, since a handful of views have computed columns that are expensive to compute on the fly. Are there downsides to SCHEMABINDING these views? I've

Downsides to “WITH SCHEMABINDING” in SQL Server?

我们两清 提交于 2019-12-02 16:29:42
I have a database with hundreds of awkwardly named tables in it (CG001T, GH066L, etc), and I have views on every one with its "friendly" name (the view "CUSTOMERS" is "SELECT * FROM GG120T", for example). I want to add "WITH SCHEMABINDING" to my views so that I can have some of the advantages associated with it, like being able to index the view, since a handful of views have computed columns that are expensive to compute on the fly. Are there downsides to SCHEMABINDING these views? I've found some articles that vaguely allude to the downsides, but never go into them in detail. I know that