Retrieving VERY LARGE SQL Database table

[marty0315]

Hello;

I am trying to retrieve a very large SQL table, the table is approximatly 1.2million entrys(rows) and growing every day. I have no problem retrieving normal size data of approximatly 25,000 entrys but when I try to get the large database it crashes my Labview and generates an error message " LABVIEW: MEMORY IS FULL. VI "SQL Read.vi" was stopped at unknown, at a call to "Rec Fetch Recordset Data(R).vi", has anyone ran into this problem or heard about this? If so is there any way around it without splitting up the original database table?

Thanks,
Martin L.

[yenknip]

The query results probably filled up your user memory then filled up your virtual memory. Why are you attempting to retrieve so much data at once?

[marty0315]

The database I am trying to retrieve has two pieces of information I need. What happens is when you scan the UUT Serial number it requires to go in this database and pull out the "Card ID" from the SN, then it will have to pass the UUT serial number, Card ID, Status (Pass/Fail) and the time and date to a seperate database. All this information will be taken and passed on to the our company database and automate the pass and fails so there could be no user error from scanning a card pass while it's actually a fail.

So in short form I need to find a serial number that was scanned and read back the card ID.

If I set up the VI to search for a specific number instead of displaying everything in a table would the same error occur where the memory gets full?

[johnsold]

Why not have the database find the ONE record which matches the UUT ID and return only that data?  That is what databases do best.  

Lynn 

[yenknip · Accepted solution]

The more criteria you include in a query, the fewer results are returned.

something like "SELECT card_id FROM table WHERE serial_number = 123" would return one result from the id card table

[marty0315]

Hello Ed & Lynn;

Thanks, for the response and the solution it works great and much quicker then to retrieve an entry the way I was trying before. Thanks for the advice.

Martin L