Stop Overwriting Existing Features With new Alternatives that Aren't Merely Updates
The recent roll-out of SQL History was handled very poorly. SQL History isn't simply an update to Tab history else there would not have been the need for a name change. SQL History is an alternative feature meant to do what Tab History does (I hope) and more but on roll-out it made many of your paying customers not only angry because you replaced Tab history with it but because it wasn't ready for roll-out.
In the future when you feel the need to replace an existing beloved feature with something different and not just an update, DON'T! Instead roll it out as something new leaving what it's planning to replace alone and let your paying customers decided which one they want to use.
The problem currently is that those who uninstalled the latest version of SQL prompt and installed an older version so they could get back the tab history, are going to be unlikely to test and provide feedback on SQL History as it's updated (fixed to work like it should) because the only way to do that is to loose Tab History which does work. Had SQL History been rolled out as a new feature so both were in place than those who have problems with SQL History could still test and provide feedback as it's updated.
In summary, in the future when a feature is being replaced and not just updated leave both in place and over time slowly phase out the old as the new gets better and eventually becomes a suitable replacement.