Category
TrueData™ Velocity 2.0
Comments
6
Subscribers
5
Views
4611
data2.fdb - size checking
Under Consideration
Performance of Velocity improved significantly after the support team deleted data2.fdb (which was 1.5GB).
Velocity should check for itself the size if more than a threshold and indicate through notification.
Another idea is optionally (velocity should ask for any RAM drive if available through configuration) and place data2.fdb in that drive at the start. And should transfer to main drive on exit.
thanks
Yes ! Deleting the file will remove all the data which has been stored in Velocity and will speed up load times but will also cause Velocity to throw up an error when it is next started for the first time as it won't be able to find the database and would need to create a fresh one.
The solution for you is like this:-
1. Delete the file today and restart Velocity. It may throw an error but will also create a data2.fdb file. There will be no error in the next restart.
2. Save this empty data2.fdb., in some other folder.
3. Instead of deleting the file daily, replace it with a copy of this empty db file.
This should work wonderfully for you.
Yes ! Deleting the file will remove all the data which has been stored in Velocity and will speed up load times but will also cause Velocity to throw up an error when it is next started for the first time as it won't be able to find the database and would need to create a fresh one.
The solution for you is like this:-
1. Delete the file today and restart Velocity. It may throw an error but will also create a data2.fdb file. There will be no error in the next restart.
2. Save this empty data2.fdb., in some other folder.
3. Instead of deleting the file daily, replace it with a copy of this empty db file.
This should work wonderfully for you.
Data gets added into Velocity and builds up over time. Velocity can never know which data you need and which you don't. You could have added additional data to Velocity manually and Velocity should not delete that.
It is recommended to remove the dta2.fdb file from time to time to clean up the database. This helps in improving performance for sure and also helps in loading Velocity much faster. If you don't remove the data, Velocity needs to load up these files into memory which could make Velocity take a long time to start as it needs to load up all this data into memory.
This is a very small maintenance you need to do yourself.
Data gets added into Velocity and builds up over time. Velocity can never know which data you need and which you don't. You could have added additional data to Velocity manually and Velocity should not delete that.
It is recommended to remove the dta2.fdb file from time to time to clean up the database. This helps in improving performance for sure and also helps in loading Velocity much faster. If you don't remove the data, Velocity needs to load up these files into memory which could make Velocity take a long time to start as it needs to load up all this data into memory.
This is a very small maintenance you need to do yourself.
>>You could have added additional data to Velocity manually and Velocity should not delete that.
Not sure if any where on the truedata site, this has been suggested. If not, can you please add.
>> If I do not add any thing new manually, can it be deleted every day? So, that I can add this step in a batch file during boot.
>>You could have added additional data to Velocity manually and Velocity should not delete that.
Not sure if any where on the truedata site, this has been suggested. If not, can you please add.
>> If I do not add any thing new manually, can it be deleted every day? So, that I can add this step in a batch file during boot.
Yes ! Deleting the file will remove all the data which has been stored in Velocity and will speed up load times but will also cause Velocity to throw up an error when it is next started for the first time as it won't be able to find the database and would need to create a fresh one.
The solution for you is like this:-
1. Delete the file today and restart Velocity. It may throw an error but will also create a data2.fdb file. There will be no error in the next restart.
2. Save this empty data2.fdb., in some other folder.
3. Instead of deleting the file daily, replace it with a copy of this empty db file.
This should work wonderfully for you.
Yes ! Deleting the file will remove all the data which has been stored in Velocity and will speed up load times but will also cause Velocity to throw up an error when it is next started for the first time as it won't be able to find the database and would need to create a fresh one.
The solution for you is like this:-
1. Delete the file today and restart Velocity. It may throw an error but will also create a data2.fdb file. There will be no error in the next restart.
2. Save this empty data2.fdb., in some other folder.
3. Instead of deleting the file daily, replace it with a copy of this empty db file.
This should work wonderfully for you.
HiI get this error data2.fdb does not exist on a daily basis. Tried what you wrote above. And every time I have to ask the support team to check. Please resolve
HiI get this error data2.fdb does not exist on a daily basis. Tried what you wrote above. And every time I have to ask the support team to check. Please resolve
Seems like a unique issue. Need to check access, permissions etc.. Please connect with Live Chat support !
Seems like a unique issue. Need to check access, permissions etc.. Please connect with Live Chat support !
Replies have been locked on this page!