-
Title
Project database design is enhanced to significantly drop the CPU utilization in some specific cases. -
Description
High CPU usage when reading from or writing to Migration Manager for Exchange SQL database in certain cases. -
Cause
Non-optimal SQL database usage when a considerable part of messages is not migrated due to a filter configured for the mailbox or calendar synchronization job. -
Resolution
UPDATE: THIS IS NOW RESOLVED in the latest cumulative Hotfix for Migration Manager for Exchange found here
This issue has been fixed in public update 20180329EX.IMPORTANT: This hotfix resolves the issue only for new SQL databases created after the hotfix installation.
In case the project database had been created before this update was installed and you are planning to filter a considerable part of messages, please perform the following procedure:
- Stop all agents that are running.
- Close Migration Manager console (Project Manager application).
- Start Microsoft SQL Studio.
- Connect to Migration Manager SQL database.
- Click New Query.
- Paste the queries below into the New Query window:
IF NOT EXISTS (SELECT * FROM sysindexes WHERE id=OBJECT_ID('dbo.[SKIPPED_ITEM]') AND name='IX_SKIPPED_ITEM_MULTIPLY') CREATE UNIQUE NONCLUSTERED INDEX [IX_SKIPPED_ITEM_MULTIPLY] ON [dbo].[SKIPPED_ITEM] ( [FOLDER_PROCESSING_ID] ASC, [ITEM_ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
7. Click Execute! button.
8. Restart Project Manager and all agents that have been stopped previously.