statistics showing as non clustered indexes in compare
russ_kw
Posts: 2
I'm using SQL Compare v. 5.3.0.44. I've got a situation where I believe that user created statistics are showing up in the compare as non clustered indexes.
The scenario is this. I have a table in a SQL Server 2005 database, and if when I view it in SQL Server Management studio and expand the tree view, it shows that there is one clustered index, and 2 non clustered indexes under the Indexes, and under statistics it shows a bunch of statistics named either _dta_index_tablename_ or _dta_stat_nnnnn. I believe that these were created by a co-worker using the SQL 2005 Database Tuning Advisor.
Now if I use SQL Compare on this table, these _dta_index_tablename objects that show as statistics in the original table are showing as NONCLUSTERED indexes in the compare. So if I use the tool to sync it to another server, these end up as non clustered indexes.
I saw another post (http://www.red-gate.com/messageboard/vi ... php?t=4172) that addresses a similar issue with the SQL data compare. Is this a bug in SQL Compare as well? If so, is there an estimated time a new version will be available.
UPDATE
It turns out that the _dta_index_ objects in the statistics were "hypothetical indexes", and according to the MS documentation are used and maintained by the Database Tuning Advisor, but nonetheless I wouldn't think they should be viewed as real indexes by SQL Compare.
The scenario is this. I have a table in a SQL Server 2005 database, and if when I view it in SQL Server Management studio and expand the tree view, it shows that there is one clustered index, and 2 non clustered indexes under the Indexes, and under statistics it shows a bunch of statistics named either _dta_index_tablename_ or _dta_stat_nnnnn. I believe that these were created by a co-worker using the SQL 2005 Database Tuning Advisor.
Now if I use SQL Compare on this table, these _dta_index_tablename objects that show as statistics in the original table are showing as NONCLUSTERED indexes in the compare. So if I use the tool to sync it to another server, these end up as non clustered indexes.
I saw another post (http://www.red-gate.com/messageboard/vi ... php?t=4172) that addresses a similar issue with the SQL data compare. Is this a bug in SQL Compare as well? If so, is there an estimated time a new version will be available.
UPDATE
It turns out that the _dta_index_ objects in the statistics were "hypothetical indexes", and according to the MS documentation are used and maintained by the Database Tuning Advisor, but nonetheless I wouldn't think they should be viewed as real indexes by SQL Compare.
Comments
Sorry for the delay in replying to this post.
I believe that this issue is related in some way to the SQL Data Compare post http://www.red-gate.com/messageboard/vi ... php?t=4172.
A bug report has already been raised to report this issue which should be fixed in SQL Compare V6 currently in development, scheduled for release in July 2007.
Many Thanks
Eddie
Eddie davis
Red Gate Software Ltd
Technical Support
Senior Product Support Engineer
Redgate Software Ltd
Email: support@red-gate.com