Migration tool changes statistics objects _WA_Sys... into true indexes.

Questions:

We use the product DB Artisan for many of our dba tasks. When we use DB Artisan to migrate tables from unit test to system test, for example, the _WA_Sys... statistics objects are changed from objects that do not appear on the list of indexes (in the source database) to ones that do appear in the list of indexes (in the target database).

1) Does this change from statistics object to a real index (in the target database) wreck it for statistics use.

2) Also, does this change from statistics object to official index hurt performance?

3) Should we delete the real indexes with names that start with _WA_Sys_ in the target database, so that the SQL-Server 7.0 system can then create its own statistics objects?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Background:

With SQL-Server 7.0, certain indexes are automatically created. They have names that start with _WA_Sys_. They are used by SQL-Server 7.0 for statistics that SQL-Server uses for its decision making.

One place to find out more about these automatically created statistical 'indexes' is in SQL Server Books Online, part of the SQL-Server 7.0 package. Use the 'search' method and search for 'statistical information'. The first entry returned gives some information about the indexes that appear when the database option 'auto create statistics' is set to true.

Dave

-----------------------------------------------------------------------------