Clearing the NinjaTrader cache forces NinjaTrader to discard its locally stored historical data and re-download it from the data provider. This is a procedural reference — use it only when you've been directed to do so (by Vector support, or because you're following an article that calls for it). Cache clearing is not a general fix for slow performance and shouldn't be done on a whim.
Documents\NinjaTrader 8\db\cache.cache folder. Select all files and delete them. Do not delete the cache folder itself — only its contents.Cache clearing is a narrow procedure with a specific purpose. It is not the same as:
Control Center → Tools → Database Management). That is a much broader action that affects more than the cache and should only be done in specific situations the team will direct you through (for example, contract rollover handling — see: Why Didn't My Strategy Fire Today?).If you're unsure whether cache clearing is the right step for your situation, open a ticket first — the team will tell you what to do.
Separate from the NinjaTrader cache, there's another cache at the Windows level — the DNS cache — that occasionally causes issues with network lookups. When a persistent connection issue to a broker or data provider doesn't resolve after the usual steps (reconnect, check data feed status), flushing the Windows DNS cache on the VPS can help clear stale network records.
This is a separate action from clearing the NinjaTrader cache above.
To flush the Windows DNS cache:
cmd and press Enter to open the Command Prompt.ipconfig /flushdns and press Enter.This is non-destructive — it doesn't touch NinjaTrader, your strategies, or any trading settings. It simply forces Windows to drop any stored DNS lookups and fetch them fresh on the next connection attempt.
As with the NinjaTrader cache, this is only a useful step in specific scenarios. If you're not sure whether it applies to your issue, open a ticket first.