16 December 2014

Lync Response Group Usage Report very slow or not completing

In Lync 2013 it's possibly to generate reports in SQL reporting services. This works fine for all except the "Response Group Usage Report".

The problem is that the report never finish unless it's given a very short time window. I posted this in the Lync forum here and a very kind person who been in contact with Microsoft support posted the SQL script below.

The script creates two index that help speed up the stored procedure that fetch the data for the report.

Someone asked if this can be made more visibly so I created this blog / post. Enjoy!!
Please provide any feedback as this is my first blog / post about anything.

/*
USE [LcsCDR]
GO
DROP INDEX [IX_SessionDetails_CorrelationId_SessionIdTime] ON [dbo].[SessionDetails]
GO
*/

CREATE NONCLUSTERED INDEX [IX_SessionDetails_CorrelationId_SessionIdTime] ON [dbo].[SessionDetails]
(
 [CorrelationId] ASC,
 [SessionIdTime] ASC,
 [ReplacesDialogIdTime] ASC,
 [ReplacesDialogIdSeq] ASC,
 [CallFlag] ASC,
 [MediaTypes] ASC,
 [User1ClientVerId] ASC,
 [User2ClientVerId] ASC,
 [SessionIdSeq] ASC,
 [SessionStartedById] ASC,
 [User1Id] ASC,
 [User2Id] ASC,
 [ReferredById] ASC
)
INCLUDE (  [TargetUserId],
 [ResponseTime],
 [ResponseCode],
 [SessionEndTime]) WITH (SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY]
go

/*
USE [LcsCDR]
GO
DROP INDEX [IX_SessionDetails_ReplacesDialogIdTime_SessionIdTime] ON [dbo].[SessionDetails]
GO
*/

CREATE NONCLUSTERED INDEX [IX_SessionDetails_ReplacesDialogIdTime_SessionIdTime] ON [dbo].[SessionDetails]
(
 [ReplacesDialogIdTime] ASC,
 [SessionIdTime] ASC,
 [ReplacesDialogIdSeq] ASC,
 [CallFlag] ASC,
 [MediaTypes] ASC,
 [User1ClientVerId] ASC,
 [User2ClientVerId] ASC,
 [SessionIdSeq] ASC,
 [SessionStartedById] ASC,
 [User1Id] ASC,
 [User2Id] ASC,
 [CorrelationId] ASC,
 [ReferredById] ASC
)
INCLUDE (  [TargetUserId],
 [ResponseTime],
 [ResponseCode],
 [SessionEndTime]) WITH (SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY]
go

 

No comments:

Post a Comment