|
Group: StrataFrame Users
Posts: 193,
Visits: 9K
|
Hi, All is OK when I create an index within SSMS with this script CREATE NONCLUSTERED INDEX [IX_ligne_1_rpt_et_dev1] ON [dbo].[ligne_1]
(
[cde_cmd] ASC,
[no_ligne_1] ASC,
[cde_mat] ASC
)
INCLUDE ( [epaisseur],
[cal_surf],
[surf_lq],
[lq_m2],
[px2_m2],
[laq_l1],
[laq_l2],
[laq_f2],
[modew],
[mat_four],
[libelle3],
[longueur],
[largeur],
[raly],
[com_lg1],
[typ_laq],
[fl_bcl]) WITH (SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY]but the same description in DDT raises an error when deployment (in log file
X 12/02/2010 16:19:50 -> Le index 'IX_ligne_1_rpt_et_dev1' sur la table 'dbo.ligne_1' a 20 noms de colonnes dans la liste de clés index. La limite maximale pour la liste des colonnes de clés d'index ou de statistiques est 16. Is that limit of 16 column names in an index definition a SF DDT limit, or a Microsoft SMO limit? We really need many indexes like this (with sometimes more than 40 columns as INCLUDE), and hoped that DDT could manage it. Thanks in advance
|
|
Group: StrataFrame Developers
Posts: 6.6K,
Visits: 7K
|
I'm not trying to debate philosophy, and the 16 column limit is referring to the covering indexes, not the INCLUDE columns which are not currently supported anyway. But this is something that we will add to the DDT as we see the need. Thanks.
|