So far as I can tell, MT5 is hard-coded to cache its data in AppData\Roaming in the user's account, which will normally be on the C disk. Unless I'm missing something, there is no way to configure the data path.
Like many users, I have a small SSD drive on C to hold my apps, and I store my large data on an HDD. My SDD is nearly full, so I didn't have the space to backtest using bulky real tick data.
I've found a workaround using portable mode and a batch file, but I'm a geek and many users would struggle with this. Plus it was a tiresome waste of time.
As a developer myself adding the option to configure the data path looks like a trivial job. Checking the forums, many users seem to have struggled with this over the years. This is an ugly anti-feature - surely it's time to fix it?
Please add this to the road-map - I'm sure it would be much appreciated.
Cool idea, would be really useful, so far I solved this problem by moving the terminal folder to a big drive and using mklink:
mklink.exe /d /j "C:\Users\almighty\AppData\Roaming\MetaQuotes\Terminal\<terminal-id>" "d:\large-hard-drive\path\terminal-folder-copy"
I am not sure that it is related to "this story" sorry ... but it is my experience -
Forum on trading, automated trading systems and testing trading strategies
Where Do I start from?
Sergey Golubev, 2018.07.17 06:36
Projects and MQL5 Storage - practical explanation about how to use them (and why) - read this page:
This is the forum. Write to the Service Desk with feature requests.
No need for this!
Carl - as I said in my post I figured out how to do it. But it took a bit of research and time. And I'm a geek and know how to do this stuff.
My point is that many users will struggle with this.
Given that the data cache can grow to many gigs, giving users an easy and intuitive way to change its location seems like a sensible idea.
This is an absolutely standard feature on many apps and easy to implement. I can't see a good reason for not offering it.
Moving the position of the data cache is a security issue?
I find it hard to understand how that could be the case.
But the thread is about moving the data folder, not the executable.
Because I can't set the data folder, I've had to move the executable to a disk with free space and launch it with the portable flag.
If I could set the data path, I could have left the executable in the Program Files directory, with all the security that provides.
So by your criterion, forcing me to move the executable is actually reducing security.
Providing the option to set the data path provides a meaningful upside with no downside that I can see, particularly as it is trivial to implement.