I have custom page and it has a CbQ webpart alone, it actually performs a query against a single list which has only 800 items with 15 columns but it takes 8secs to load. I suspect a slowness in SQL, how I can conclude that it is an issue with the SQL. Sometimes I could see the long running queries in the ULS log.

The filter columns are used in the CbQ webpart are not indexed, will it impact the overall performance?

If so, howmany columns can be used for Indexing that should not affect the performance again? also, how can I eusure that Index is created for that site column?

  • one more doubt, what will happen if I have there CbQ in a page, is it all those 3 queries will execute Parallelly or one by one? Commented Apr 25, 2011 at 16:44
  • They are executed one by one Commented Apr 25, 2011 at 19:31

3 Answers 3


It can be various issues that causes this. One way of getting a clue on whats going on is to enable developer dashboard.

See here for guidance on how to enable http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=189

Another option if you think this is SQL related, is to start up SQL Trace

  • Do we have the developer dashboard option in SharePoint 2007? or is there any alternative way of doing it in SharePoint 2007? Commented Apr 23, 2011 at 13:47
  • Not that i know of. But try SQL Trace Commented Apr 23, 2011 at 17:04
  • From the SQL Trace, SQL does not take much time to complete the query.. Commented Apr 25, 2011 at 16:26
  • Is the site generally slow? Are the db used for other purposes than SharePoint? Commented Apr 26, 2011 at 6:05
  • It is a shared physical machine with many SQL instances and ours is one of those..and it is just a PKS web-application which does not have data to be stored in the db..our DB size is ~1.5GB Commented Apr 26, 2011 at 18:13

I would say the issue lies with the XSL rather than the SQL.

Do you have any custom XSL, and what data types are the 15 columns?

  • ok, will check the XSL & XML. those are mostly text and time field. Commented Apr 20, 2011 at 17:43
  • this is default XSL comes with the PKS for sharepoint. Commented Apr 23, 2011 at 12:15

If you think it is a SQL bottleneck, make sure you have object caching enabled.

  • we have already enabled the site collection object caching. Commented Apr 20, 2011 at 17:41
  • it is executing the CAML Query every time though we have enabled the site collection object caching. is that an expected behavior? Commented Apr 25, 2011 at 16:46
  • CQWP will cache the requests unless you disabled cahing in web part properties Commented Apr 25, 2011 at 19:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.