Comments
Sort by recent activity
See my reply on viewtopic.php?f=173&t=79009 / comments
See my reply on viewtopic.php?f=173&t=79009
It seems that there are two problems.
1. If you are running the latest "non full release" of sql monitor (in my case 4.3.0.132, which fixed a log out bug) you need to alter the database to get the install to work (make it think it is running the previous full release). The SQL I was given by support is:
BEGIN TRANSACTION
DROP PROC [settings].[SetKeyValuePair]
DELETE FROM versioning.SchemaVersionHistory
WHERE SchemaVersion IN ( 'Seq95', 'Seq96' )
COMMIT TRANSACTION
Needless to say backup your database FIRST, and disable the SQL Monitor service whist you are doing the change. You can then install the update (don't access the website until afterwards or it will upgrade to the unsupported version again!).
2. Once I installed the update I discovered that SQL Mon 5 actually requires .Net 4.0.2 not .NET 4. There is a patch at http://blogs.technet.com/b/mdegre/archi ... ntent.aspx. Again provided by support.
The above is given as a help to the community; it was advice given by Dan from redgate support. So I take no responsibility for it! / comments
It seems that there are two problems.
1. If you are running the latest "non full release" of sql monitor (in my case 4.3.0.132, which fixed a log out bug) you need to alter the database to get the...
On top of this (I experience the same); the new UI is so "big" that I have to zoom out to see things correctly (especially the analysis page) even using a screen res of 1920x1080! / comments
On top of this (I experience the same); the new UI is so "big" that I have to zoom out to see things correctly (especially the analysis page) even using a screen res of 1920x1080!