Running Reports in GP taking a long time

(0) Share

Report

Posted on by Community Member

We have a client that has a very large database and when they run reports it tends to take a long time. Some up to 4 to 10 hours. We were thinking of possibly using Data Warehousing. Has any one went this route and what would be some pros or cons? Also what may be some other options we may want to consider?

Thanks

Tom

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Richard Wheeler 75,850 Moderator on at

Like (1)

Report

Which reports are taking a long time? Are they the historical trial balances? If so, that is normal. Before you consider data warehousing, I would run one of these reports and then have IT do some performance monitoring on your server to see what is happening. Perhaps a newer server with faster drives will make the difference.

Was this reply helpful? Yes No
Almas Mahfooz 11,009 User Group Leader on at

Like (0)

Report

I also want to know which reports are they?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

We have recently upgrade to new servers and they seem to run fine. It just seems to be for reports.

Some Reports Examples:

Accounts receivable aging - About 8 hours

Summary Trial Balance for GL - Over an Hour

Was this reply helpful? Yes No
Suggested answer

KirkLivermont 5,985 on at

Like (0)

Report

I would take a look at CDA. It will allow you to move historical records to archive databases (still accessible as other companies within GP).

How old/big is the database? I think you could see a huge burst in performance if the database is 5+ years old but would see little gain if the majority of data has been generated in the last 2-3 year.

Regards,

Kirk

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

They actually do use CDA and archive everything past 3 years. This helps some but still the databases are about 400 to 500 gig. I was looking to see if I could find another solution to help in getting the reports.

Was this reply helpful? Yes No
Richard Wheeler 75,850 Moderator on at

Like (0)

Report

I normally do not recommend this except for cases like this. If you have been archiving data over the years and your database sizes are over 400GB a lot of that is now dead space. I would consider not only shrinking the log files but also the data files. If possible do this in a completely test environment first. When doing this in production I would perform a backup first and the afterwards perform so basic SQL utilities to insure a healthy database. Check with your IT folks before doing any of this.

Was this reply helpful? Yes No