cancel
Showing results for 
Search instead for 
Did you mean: 

XL reporter disk usage

Former Member
0 Kudos

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!

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member201110
Active Contributor
0 Kudos

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

Former Member
0 Kudos

hi owen,

thank you very much for the quick response,

<b>I'd be recommending having separate RAID 10 arrays for DBs, logs and RAID 1 for the tempdb.</b>

Yes I also think so, I am planning to migrate SAP component databases and TEMPDB to a NetApp storage to offload the server of READ/WRITE issues by utilizing all spindles of the storage system.

just want to get inputs if this works

hope this will also eliminate the DISK IO errors I am getting when genrating reports

Again, thankyou very much!

Jeff

Former Member
0 Kudos

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