Skip to Content
avatar image
Former Member

XL reporter disk usage

hi,

We are currently experiencing hangups while generating reports via XL reporter,

noticed that DISK WRiTE and READ is way up during this process, Ruled out CPU, memory and network issues.

currently running on RAID 10 configuration. we are planning to migrate SAPB1 and XLR databases to a storage to utilize multiple spindles.

has any body had the same experience? any suggestion?or will the migration work.

I would appreciate any input

thanks

newbie here!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Aug 16, 2007 at 09:08 PM

    Hi Jeffrey,

    My guess would be that poor indexing on the part of XL Reporter or SBO is causing the extra workload for the database server. Have you run SQL Profiler while generating a report to analyse what is happening (...I'm assuming you are using SQL Server 😉 )? It shouldn't cause XL Reporter to actually hang though. Has this only started happening?

    I'm not sure what you mean about moving to multiple spindles from RAID 10 because RAID 10 uses multiple spindles. How many disks in the array and how many arrays in the server? In my experience RAID 10 is only necessary at the high end of SBO and most of our customers get good performance out of RAID 1 or 5, including XL Reporter. If disk I/O is the problem then I'd be recommending having separate RAID 10 arrays for DBs, logs and RAID 1 for the tempdb. Having said that, sizing the right hardware needs proper analysis of the requirements so I'd recommend you contact someone who specialises in this area.

    Kind Regards,

    Owen

    P.S. Welcome to the forums 😊

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Also I would recommend running a XLR Log or SQL Profiler and look at the SQL statements. XLR runs off independent SQL statements that get INSERT INTO the tempdb. If users do not write reports correctly if can overload system. I have also seen issues if DBA have the Tempdb in full recovery mode. If you have everything in Simple mode and do transaction backups your system will be fine. I have seen very large system without issues on XLR.

      Jim Hummer

      XLR Consultant