Closed maxpatiiuk closed 4 years ago
Here is the number of results in that table:
@maxpatiiuk It seems the TestBiology8 database does not have the 450mb of data that you tested with. If you still have that database can you put in a directory on the file share?
That is because I made Sp7 delete auditing data older than one month. Apparently that feature worked
I created TestBiology9
out of the same SQL file
I am not able to save the query
The results start to get shown but then it throws an error
can you put that sql file in the file share?
If that is fictional log data with record ids, parent ids, and values that are from another database then it is probably not good for anything but testing the culling process. It seems like queries would be OK (especially saving them), and problem showing results could be a case of a bug Yvonne reported with formatted audit log results, but any problems querying with fictional log data should be reproduced in real data before they are filed as bugs.
@benanhalt The database is located at Specify6/max_data/DBs/SP6/2020_03_13_14_06_51.sql
@timo11 Ok, I will create half a million auditing records in BatchEdit in Sp6 and will try to query it in Sp7
Tested with KU Entro (2 375 359 auditing records) Works fine I guess that auditing file was the cause of the issue
Lock wait timeout exceeded when running a query on SpAuditLog There is about 450 mb of data in the SpAuditLog table Error happens even if there is just 1 column selected in the query Is there a way to change the limit on the duration of the lock when running a query via global prefs?