|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Today @ 5:08 AM
Points: 221,
Visits: 329
|
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 5:02 AM
Points: 2,365,
Visits: 1,825
|
|
In BOL under Creating Indexes (Database Engine) section its mentioned that there can be 249 non clustered indexes per table. But In BOL under Create table sections its mentiond 999
"Keep Trying"
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 10:47 PM
Points: 2,023,
Visits: 4,948
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Monday, January 14, 2013 10:48 AM
Points: 121,
Visits: 52
|
|
| I am also confused because in BOL (Indexes Section) is mentioned 249 {The maximum number of nonclustered indexes that can be created per table is 249.} . This is a really documentation bug I think. Even if, I'll expend some time to prove this in my srv.
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 6:13 AM
Points: 5,296,
Visits: 7,236
|
|
Chirag (3/20/2009)
In BOL under Creating Indexes (Database Engine) section its mentioned that there can be 249 non clustered indexes per table. But In BOL under Create table sections its mentiond 999 
As others have already said, this is a documentation bug in BOL. The maximum number of nonclustered indexes was 249 on SQL Server 2005 and before, but the maximum has been increased to 999 for SQL Server 2008. Apparently, MS has overlooked one page when applying this modification to BOL.
Hugo Kornelis, SQL Server MVP Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Monday, June 03, 2013 6:20 AM
Points: 954,
Visits: 1,878
|
|
Just as well one of the answers wasn't 250, or I would have gone for that (1C + 249NC). I hit the wrong page in BOL first, and it's only when the answer I was expecting wasn't in the choices that I dug a bit further.
Couldn't the answer also be 1498 when we take the 249 XML indices and 249 spacial indices into account as well?
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Today @ 5:08 AM
Points: 221,
Visits: 329
|
|
Yes, the answer could have been that also, but for in the question we have (clustered + non clustered) explicitly mentioned.
Sriram
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Thursday, June 13, 2013 12:24 PM
Points: 2,892,
Visits: 5,871
|
|
How very un-binary of them... I found 999 an odd number to have as a maximum.
To help us help you read this
For better help with performance problems please read this
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Friday, May 17, 2013 2:11 PM
Points: 3,108,
Visits: 2,114
|
|
Regardless of the discrepancy, 249 or 999, any design that requires anywhere near that theoretical maximum, is most probably a 'pile of dung' !
Regards Rudy Komacsar Senior Database Administrator
"Ave Caesar! - Morituri te salutamus."
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Monday, April 06, 2009 1:29 PM
Points: 2,057,
Visits: 215
|
|
| When the question specifies the version of SQL Server, you should double check that the selected article in BOL is for that version. The Local Help search in BOL lists only the 2005 version of CREATE INDEX while the MSDN Online search section lists articles for both the 2005 and the 2008 versions.
|
|
|
|