Hi All,
The component that loads hierarchy items does simply not sort anything. Well, for performance it's a good idea to let the SQL engine classify data so that you do not have to add an order by to your query.
The problem is that the hirearchy table is using a clustered index on the hierarchy ID instead of the hierarchy name.
Please try the following query on your Servidesk database (Ensemble by default).
Take care as it modifies the db index structure it may not be supported by Symantec. We do that on all our Servidesk installations and it works fine.
-- Start of script to change the Hierarchy index
IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[HierarchyItem]') AND name = N'PK_HierarchyItemID')
ALTER TABLE [dbo].[HierarchyItem] DROP CONSTRAINT [PK_HierarchyItemID]
Go
ALTER TABLE [dbo].[HierarchyItem] ADD CONSTRAINT [PK_HierarchyItemID] PRIMARY KEY NONCLUSTERED
(
[HierarchyItemID] ASC
)WITH(PAD_INDEX = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF) ON [PRIMARY]
Go
CREATE CLUSTERED INDEX [IX_HierarchyName] ON [dbo].[HierarchyItem]
(
[Name] ASC
)WITH(PAD_INDEX = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF) ON [PRIMARY]
GO
-- End of script to change the Hirearchy index
Enjoy!
Fabrice
Edit: Added some spaces - copy/paste concern. :)