SP_helpindex saveset procedure is not found

[Jesus_Hdez]

Hello,

our Enterprise Vault 8.0 SP2 is starting to record 7162 event IDs and have pointed us to this article: http://www.symantec.com/business/support/index?page=content&id=TECH51231

We are using Centera and have enabled Collections.

We tried to create new indexes manually, but we are not able to find the procedure SP_helpindex saveset to excute it as the first step for that article.

It does not exist as a Stored Procedure in those Vault Store databases... Could anyone please copy its content here?

Thank you in advance.

Regards,

Jesus

[JesusWept3 · Accepted solution]

OK so!

Firstly you would run the sp_helpindex against the vault stores themselves.
telling it 'EXEC sp_helpindex saveset' is actually telling SQL Server to list all indexes that are assigned to the "saveset" table, just as if you ran 'EXEC sp_helpindex JournalArchive' it would give you all the indexes against the Journal Archive table

If you try to run sp_helpindex saveset against a database that doesn't have the saveset table (say the EnterpriseVaultDirectory) you would get the error


Msg 15009, Level 16, State 1, Procedure sp_helpindex, Line 37
The object 'saveset' does not exist in database 'EnterpriseVaultDirectory' or is invalid for this operation.


If you try to run sp_helpindex saveset against a vault store database you would see something like


index_name, index_description, index_keys
IX_IdDateTime, nonclustered located on PRIMARY, IdDateTime
IX_IdTransaction, nonclustered, unique, located on PRIMARY, IdTransaction
IX_Saveset_CollectionIdentity, nonclustered located on primary, CollectionIdentity
IX_Saveset_VaultIdentity, nonclustered located on primary, VaultIdentity
PK_Saveset, clustered, unique, primary key located on primary, ArchivePointIdentity - IndexSeqNo
UN_SavesetIdentity, nonclustered, unique key located on Primary, SavesetIdentity


The index it's telling you to look for is IX_Collection_Saveset_Partition that indexes the CollectionIdentity, SavesetIdentity and IdPartition in a nonclustered index.

From the output above you can see it doesn't exist (at least on my 9 SP1 install it does not), so you would then create it via the SQL Procedure at the bottom (Step 3)

Also note that the SQL Query clearly has a clause that it will not attempt it if the Index does not exist currently, remember this has to be run against the Vault Store databases and not the EnterpriseVaultDirectory database.

You may wish to seek assistance from your DBA