We have locally installed SQL Express, the one installed by Veeam B&R at setup time.
We are also planning on going back to 2012R2, we can't use the fix because of the memory issues and we can't not use it because of the deduplication corruption.
Gostev wrote:Never mind, we seem to have found the root cause. With a high probability, leaking is System.Data.dll, which KB3216755 happens to replace of course.
We were even able to reproduce the issue without Veeam in the picture, by creating a test tool that does nothing except bombing SQL Server with large queries from multiple threads.This tool has also consumed all available system memory very fast and produced a crash dump that is identical to ones submitted by our customers. After uninstalling the update, memory consumption of the test tool remains steady at 26-28MB.
Microsoft has been notified.
Does this mean that if we move the Veeam DB to an remote SQL server and uninstall SQL from the B&R server the issue will be resolved for us?