Apr 12, 2012 at 1:18 PM
Edited Apr 12, 2012 at 1:24 PM
|
I was looking through the expensive query s and its suggesting a few indexes, wondered if this is due to our development or just due to the database size? Feedback appriciated!
/* Missing Index Details from ExecutionPlan3.sqlplan The Query Processor estimates that implementing the following index could improve the query cost by 82.9451%.*/
GO
CREATE NONCLUSTERED INDEX [<Name of Missing Index, sysname,>]
ON [dbo].[n2Detail] ([DetailCollectionID])
GO
/* Missing Index Details from ExecutionPlan2.sqlplan The Query Processor estimates that implementing the following index could improve the query cost by 98.128%. */
GO
CREATE NONCLUSTERED INDEX [<Name of Missing Index, sysname,>]
ON [dbo].[n2Detail] ([ItemID],[DetailCollectionID])
GO
|
|
Coordinator
Apr 17, 2012 at 10:09 PM
|
This depends a bit on database size, type of content and how it's queried. I've seen various indexes being suggested and I'd like to put some good suggestions in the performance section of the docuementation.
The schema generation tool used by the installer doesn't create optimized indexes. On the other hand it creates schema for many different databases which is quite nifty.
|
|
|
|
Thanks Libardo. We implemented N2 on our brouchure site, mostly static content witha couple of pages that are updates daily. It has beenm heavily customised from the mvc template content. The site has been running since August and the database
has grown to 11GB.
I recently asked a question about the database size
http://n2cms.codeplex.com/discussions/350611 and used the script to clear out expired items.
I have decided to run a trace for a few hours and run through the optimisation wizard see what it recommends.
|
|
Coordinator
Apr 22, 2012 at 1:35 PM
|
I'm interested in whatever you come up with including comparisons before and after.
|
|