Huge Traffic between Share point Front End Servers to Content Database

  • HI Experts,

    We have a Customized share point application with Very minimal data usage and we have used only 5 to 6 lists and libraries only in the share point.

    Configuration is

    Clients -- fire wall --- Load Balancer ---- WF1 and WF2 --- SQL DB

    ROUTING IS VIA FIRE WALL.

    SUDDENLY THE SITE GOT DEAD SLOW AND UNABLE TO TRACE THE PROBLEM AS EVERY THING LOOKS FINE.

    Checked with the firewall Team and they stated its fine from their end & even we have verified the counters, CPU, Memory & Page life expectancy, buffer counters all looks good and even we do not have huge data in the database. We have only 50 concurrent users are working...

    It is a live application and my client is sitting next to me...

    Any Suggestions are Highly appreciated....

    Thanks

    Praveen

  • Check for WAITS, CX_PACKET WAITS and any IO issues. Also can you let us know the metrics for the CPU, Memory and the Disk counters.

    Do you also experience any blockings and index fragmentation ? Did all your DB Maintenance jobs ran successfully.

    --

    SQLBuddy

  • Possibly blocking may be the primary issue that makes you feel huge traffic in-spite of NOT HUGE data in the database.

    Do you use CAML query designer for sharepoint to read data from database?

    CAML designer by default copies all the columns even though most of them are not required for the application. Try to chose only required column from the table to populate data in sharepoint dashboard/web.

    And sharepoint, by architecture, uses MAXDOP = 1 query hint , as per my knowledge untill version sql 2008 R2.

    Hope this helps to troubleshoot.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply