I am using Sql Server 2000 and want to know why we can not create index on bit fields?
相关问题
- sql execution latency when assign to a variable
- What is the best way to cache a table from a (SQL)
- php PDO::FETCH_ASSOC doesnt detect select after ba
- Bulk update SQL Server C#
- SQL to Parse a Key-Value String
相关文章
- Entity Framework 4.3.1 failing to create (/open) a
- Use savefig in Python with string and iterative in
- Code for inserting data into SQL Server database u
- Accessing an array element when returning from a f
- Delete Every Alternate Row in SQL
- Linux based PHP install connecting to MsSQL Server
- SQL Azure Reset autoincrement
- How do we alias a Sql Server instance name used in
Just a limitation of the product. SQL Server 2005+ does allow this.
Because of the Tipping Point a single column
bit
index is unlikely to be very useful unless the values are heavily skewed (a scenario for which filtered indexes in 2008 can help)Still - could be useful as part of a composite covering index though.
I would guess this is by design.A bit field can only have 1 of 2 values, so it would not be selective enough for an index to be useful.