Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #1906
| Newsgroups | comp.databases.ms-sqlserver |
|---|---|
| Date | 2015-04-14 09:42 -0700 |
| Message-ID | <5b308c23-aca5-4c1f-89c6-3e578aaf2fd1@googlegroups.com> (permalink) |
| Subject | Engine Tuning Advisor recommending non-clustered index on clustered PK columns |
| From | Mark D Powell <markp28665@gmail.com> |
A recent Database Engine Tuning Advisor run on a SQL Server 2008 R2 RTM system has several recommendations that puzzle me because the recommendation is for a two column non-clustered index on the same two columns that are the clustered PK. In one case there are only two other columns consuming a total of 5 bytes on the row so I just cannot see any valid reason for this recommendation. - - There is a index reorganization job I added to the system that runs every Sunday but statistics update is left to SQL Server. - - Does anyone have a good idea of what would cause these recommendations? - - -- Mark D Powell --
Back to comp.databases.ms-sqlserver | Previous | Next — Next in thread | Find similar
Engine Tuning Advisor recommending non-clustered index on clustered PK columns Mark D Powell <markp28665@gmail.com> - 2015-04-14 09:42 -0700
Re: Engine Tuning Advisor recommending non-clustered index on clustered PK columns Erland Sommarskog <esquel@sommarskog.se> - 2015-04-14 20:29 +0200
Re: Engine Tuning Advisor recommending non-clustered index on clustered PK columns Mark D Powell <markp28665@gmail.com> - 2015-04-15 09:59 -0700
Re: Engine Tuning Advisor recommending non-clustered index on clustered PK columns rja.carnegie@gmail.com - 2015-04-15 20:40 -0700
csiph-web