Skip to main content

Hi,

We are currently investigating the performance differences between Vision files and a SQL database.  We wrote a small program to do writes, key reads, read next and re-writes.   Testing with 40000 records, the vision file system gets all this done in 4.5 seconds.  The same test on a SQL database takes 4 minutes and 44 seconds.  This is a major drop in performance.   

I am attaching the program we used to see if anyone can help us solve the issue with performance.  We a not a database shop, so our knowledge of the database setup is not great.   Any help we can get would be appreciated.  We have to have to make a decision on adding a SQL solution to our product line by the end of the year.

Thanks. 

 

Hi,

We are currently investigating the performance differences between Vision files and a SQL database.  We wrote a small program to do writes, key reads, read next and re-writes.   Testing with 40000 records, the vision file system gets all this done in 4.5 seconds.  The same test on a SQL database takes 4 minutes and 44 seconds.  This is a major drop in performance.   

I am attaching the program we used to see if anyone can help us solve the issue with performance.  We a not a database shop, so our knowledge of the database setup is not great.   Any help we can get would be appreciated.  We have to have to make a decision on adding a SQL solution to our product line by the end of the year.

Thanks. 

 

I believe based on your test program that your results are accurate. I don't think there is a configuration variable that will improve that. I don't think you would use a customer facing program to load 40,000 records into the database.