Dataview problem

nfliou

Hello,

I've created a dataview in our test environment, it' working perfectly.

But when executed in the Production environement it ends with an error(see below)

Have you any idea why it's happening? is there a solution for this?

thank you for your help

Find more posts tagged with

API Usage

Accepted answers

All comments

Rees Howel

I have seen that error before but only fleetingly.

How complex is the dataview and roughly how many rows would you expect in the result set?

Stephen Cena

I've seen this as well. We are running CSI 9.01.01 and we needed to make several changes to our SQL Server configuration to deal with the large volume of data we process. If you are running on-premise, I can make some suggestions for you/your team. They solved the performance/plan issues for us but I'm sure it wouldn't be consistent across every CSI install/deployment.

nfliou

the dataview is not complex, it only collects 43 fields from the SLCoitems and SLCos IDOs. But it displays 70k rows as result.

Thanks

nfliou

Yes please, tell me what changes did you make to your SQL server configuration. Thank you

Rees Howel

That's big enough to cause performance issues. My rule of thumb for a dataview is no more than 10000 rows. Anything over 20K is usually trouble. If you want something that retrieves 70K rows on a regular basis you want that to be something that can chunter away in the background. i.e. a proper report

nfliou

OK, thank you

Legacy Contributor

I'll expand on that point. Regardless of performance issues, as a rule of thumb, any report that exceeds 200 rows is no longer a report, it's a data dump. If you regularly have reports generating more than 200 rows, I can guaranty you no one is reading them.

People don't have that large of an attention span and they are already competing attention-wise with other reports, emails, phone calls, and meetings. There is not enough time in a day to process all that information overload. Believe me, I see this all the time in the manufacturing industry. This is why BI dashboards are what people use to run a business. They need specific, point-in-time, simple indicators to determine what is going on and to alert them that some type of action needs to be taken.

DataViews are meant to be used to analyze a small sub-set of information - transaction history for a specific order, last 7 days transactions for a G/L account, for a given unit code, etc...

Beyond that, a dump of data should go to a data warehouse, cubed, and then analyzed by an analysis tool that then boils the data down into the aforementioned dashboard indicators.

Stephen Cena

I'll post what I've done in a separate discussion. While I think the database changes could help you, I agree with the rest that it may be too much for the Dataview. That isn't to say that maybe the tweaks will work for you. Who knows Anyways, I'll try to post that shortly. & put the link here.

nfliou

Yes, I also agree that's too much data for a dataview that's why i reduced the amount of data by adding filters to the DataView.

For my general knowledge it would be nice to see what kinf of database changes you've made.

Thank you very much.

Legacy Contributor

I've seen this multiple times. We usually close out of the form, and clear ido and form cache (control-u). That seems to solve our issues, but i can't seem to figure out why it happens.

Legacy Contributor

I am not sure, have you tried setting up the rows to say 500 in Dataview setup. Then Load more rows as you go.

nfliou

i added a fliter to the dataview that reduces the amount of data extracted, and it's working perfectly

Thanks

Copyright © 2025 Infor. All rights reserved.