locked
Blocking on a database causing SharePoint to crash RRS feed

  • Question

  • We're running SharePoint 2007 on Windows 2003 and SQL Server 2005.  Within the past month we've been having numerous instances during the day where our SharePoint sites go down completely.  We've seen that this is being caused by blocking on the SQL Server, here is process which is causing the blocking:

    SharePoint_Content_Database.dbo.proc_ListUrls;1

    When this block occurs, it creates a cascading effect of other blocks stemming from it, which eventually takes down all our sites.  When we terminate the block, the cascading blocks go away and the sites come back up.

    Is there any way to tell what's causing this block?

    Any help would be most appreciated. 

    Tuesday, May 14, 2013 7:04 PM

Answers

  • Hi bdicer,

    This can happen with large lists, multi-lookup columns in lists or other custom created bottlenecks.

    To find large lists, you may use custom code similar like the code provided in the following blog, then take actions on it.
    http://www.sharepointdiary.com/2012/02/find-large-lists-in-sharepoint.html

    Here is the boundaries and limitations on SharePoint 2007, you may also refer to it.
    http://technet.microsoft.com/en-us/library/cc262787.aspx

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please click here.


    Emir Liu
    TechNet Community Support


    • Edited by Emir Liu Wednesday, May 15, 2013 3:36 AM
    • Marked as answer by Emir Liu Thursday, May 23, 2013 7:02 AM
    Wednesday, May 15, 2013 3:32 AM
  • From the Reply above you get more insight if you can take a SQL profiler trace along with ULS Verbose logs around the time when the issue occured.

    If you have crossed the Capacity planning as per the MS Guide line please try to split the database using Merge contentDB command to split the Site collection on indivudial Content DB.

    Also if you have a Problem with Large list you can try creating Views in SharePoint for that list or trying the nested Folder options.


    Regards MuSa


    • Edited by MuuSaa Friday, May 17, 2013 2:43 AM
    • Marked as answer by Emir Liu Thursday, May 23, 2013 7:02 AM
    Wednesday, May 15, 2013 2:06 PM

All replies

  • We're running SharePoint 2007 on Windows 2003 and SQL Server 2005.  Within the past month we've been having numerous instances during the day where our SharePoint sites go down completely.  We've seen that this is being caused by blocking on the SQL Server, here is process which is causing the blocking:

    SharePoint_Content_Database.dbo.proc_ListUrls;1

    When this block occurs, it creates a cascading effect of other blocks stemming from it, which eventually takes down all our sites.  When we terminate the block, the cascading blocks go away and the sites come back up.

    Is there any way to tell what's causing this block?

    Any help would be most appreciated. 

    • Merged by Emir Liu Wednesday, May 15, 2013 1:47 AM duplicate thread
    Tuesday, May 14, 2013 7:05 PM
  • Hi bdicer,

    This can happen with large lists, multi-lookup columns in lists or other custom created bottlenecks.

    To find large lists, you may use custom code similar like the code provided in the following blog, then take actions on it.
    http://www.sharepointdiary.com/2012/02/find-large-lists-in-sharepoint.html

    Here is the boundaries and limitations on SharePoint 2007, you may also refer to it.
    http://technet.microsoft.com/en-us/library/cc262787.aspx

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please click here.


    Emir Liu
    TechNet Community Support


    • Edited by Emir Liu Wednesday, May 15, 2013 3:36 AM
    • Marked as answer by Emir Liu Thursday, May 23, 2013 7:02 AM
    Wednesday, May 15, 2013 3:32 AM
  • From the Reply above you get more insight if you can take a SQL profiler trace along with ULS Verbose logs around the time when the issue occured.

    If you have crossed the Capacity planning as per the MS Guide line please try to split the database using Merge contentDB command to split the Site collection on indivudial Content DB.

    Also if you have a Problem with Large list you can try creating Views in SharePoint for that list or trying the nested Folder options.


    Regards MuSa


    • Edited by MuuSaa Friday, May 17, 2013 2:43 AM
    • Marked as answer by Emir Liu Thursday, May 23, 2013 7:02 AM
    Wednesday, May 15, 2013 2:06 PM