_WA_Sys_ ...
Aug 22, 2001
Hello Listers !
I ran the sp_helpindex for a particular table on a CRM db and it returned with a list of 63 indexes, most of which had an index name beginning with _WA_Sys .. followed by what looked like a system generated name.
But when I open the design table in the EM and bring up a list of indexes, I don't find any of the indexes which begin with _WA_Sys .. listed.
I am running SQL 7, sp 2 on NT4, sp 6.
Any light on the anamoly ? Are they some temp indexes created by SQL 7 ?
TIA for any help
Vijay
View 1 Replies
Nov 5, 1999
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... indexes are changed from indexes that do not appear on the DB Artisan list of indexes (in the source database) to ones that do appear in the DB Artisan list of indexes (in the target database).
1) I'm trying to find out if this subtle change in status for the statistics indexes harms their functioning for statistics use.
2) Also, does this subtle change in status for the indexes lead to performance problems such as increased response time.
3) Should we delete the _WA_Sys_ indexes in the target database and let the system create its own there?
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
View 1 Replies
View Related
Feb 3, 2000
After converting from SQL Server 6.5 to 7.0, there exist a number of indices in sysindexes with names starting with _WA_Sys_, e.g. _WA_Sys_PGJ_GROUP_JOB_ID_3EA749C6. When a Complete Compare is executed in ERwin, these indices are reported as variances to the data model. When a DROP INDEX statement is executed, SQL Server complains that the index isn't in the system catalog. The following is an example:
DROP INDEX ASSIGNED_INSERTER_SETUP._WA_Sys_PGJ_GROUP_JOB_ID_3 EA749C6
Cannot drop the index 'ASSIGNED_INSERTER_SETUP._WA_Sys_PGJ_GROUP_JOB_ID_ 3EA749C6', because it does not exist in the system catalog.
General SQL Server error: Check messages from the SQL Server.
Execution Failed!
How do we drop these indices? Thank you in advance for your assistance.
Regards, Peter
View 1 Replies
View Related