You are viewing limited content. For full access, please sign in.

Question

Question

SQL - Missing Indexes

asked on August 18, 2015 Show version history

Hi,

Our DBA team have recently run a missing index recommendation check on our Laserfiche DB's and came back with the below results. I would like to find out if there is any risk in them proceeding to create indexes for these?

 

Is there also perhaps some white paper available that explains from a Best Practice point of view, what are the recommended indexes to be created?

1.
/*
Missing Index Details from ExecutionPlan1.sqlplan
The Query Processor estimates that implementing the following index could improve the query cost by 99.6345%.
*/

/*
USE [AFSLaserfiche]
GO
CREATE NONCLUSTERED INDEX [<Name of Missing Index, sysname,>]
ON [dbo].[propval] ([prop_id])
INCLUDE ([tocid],[short_str_val])
GO
*/

2.
/*
Missing Index Details from ExecutionPlan1.sqlplan
The Query Processor estimates that implementing the following index could improve the query cost by 43.9698%.
*/

/*
USE [AFSLaserfiche]
GO
CREATE NONCLUSTERED INDEX [<Name of Missing Index, sysname,>]
ON [dbo].[toc] ([pset_id],[tocid])
INCLUDE ([parentid],[toc_flags])
GO
*/

3.

/*
Missing Index Details from ExecutionPlan1.sqlplan
The Query Processor estimates that implementing the following index could improve the query cost by 99.5937%.
*/

/*
USE [AFSLaserficheWF]
GO
CREATE NONCLUSTERED INDEX [<Name of Missing Index, sysname,>]
ON [dbo].[bp_step] ([bps_report_id],[bps_end_date])
INCLUDE ([bps_start_date])
GO
*/
0 0

Replies

replied on August 18, 2015

You're free to create non-unique indexes on tables without risk. We don't have any index recommendations, as the best additional indexes to create will depend on your specific workload, and many customers won't need any additional indexes for satisfactory performance.

1 0
replied on December 8, 2015

Hi,

 

Just wondering if you ever added these indexes. Did they help speed things up?

 

Thanks

 

0 0
replied on April 6, 2016

Hi Long, 

sorry for the delayed response. We did indeed implement those indexes but it did not resolve all our performance issues. After closer investigation we found that some of the standard indexes created by a fresh install of the Laserfiche Server software, was missing from our SQL instance in Production. 

Subsequently we ended up manually creating those indexes and also ended up doing a upgrade to LF 10, which fixed some of the missing index issues and seems to have address bulk of the performance issues we were having. 

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.