Potential Performance Bottleneck (and simple fix) for Team Server running on SQL Server 2014 or Later

We have encountered a few situations where Team Server performance,  when installed on SQL Server 2014, 2016, 2017  has been unusually slow when doing certain operations.  It is inconsistent but tends to manifest when publishing models and/or very slow expansion of the ERTools model explorer tree.  The underlying cause appears to be the cardinality estimator that was introduced in SQL Server 2014, which impacts the way in which access plans are calculated in the database engine.  Luckily, there are database properties that can be set to overcome this issue immediately.  We are also investigating redesign of  some SQL queries to mitigate the issues.
To fix the problem one of 2 changes can be made (only 1 is necessary since they have the same effect):
1) On the database options page in SQL Server, change the Compatibility level to be SQL Server 2012 (110) or SQL Server 2008 (100).  This option is available on SQL Server 2014 and later.
2) On the database option page for SQL Server 2016 and later, there is also an option called "Legacy Cardinality Estimation"  which can be set to ON.
For SQL Server 2014, I would recommend setting the Compatibility level.  For SQL Server 2016, 2017 I would recommend using the Legacy Cardinality Estimation property.
IMPORTANT NOTE:  If you have upgraded from previous SQL Server Versions, the compatibility level may already be set to an earlier version.  When a database is upgraded in SQL server, it retains the previous compatibility level setting unless changed by setting the property after the database version upgrade.
The Properties (options) dialog is shown here:
The benefits of setting the property will be immediate, with no need to restart the database.  Any queries executed after the setting is changed will use the new setting.