Comments
Sort by recent activity
I can assume it would as every update is actually a reinstall of the product. You can check it easily yourself by checking the setting before and after an update. / comments
I can assume it would as every update is actually a reinstall of the product.You can check it easily yourself by checking the setting before and after an update.
Very curious to see the log of that installation if you can provide it? I'm asssuming it tries to overwrite a file or folder somewhere to which it doesn't have the rights. Did you start the installer with "run as administrator" or without? I did find that sometimes it makes a difference, even if you're full admin on the machine. / comments
Very curious to see the log of that installation if you can provide it? I'm asssuming it tries to overwrite a file or folder somewhere to which it doesn't have the rights.Did you start the installe...
You could use the 'longest running queries' tile and copy that to an Excel file. You can also email it but that is less nice if you wanna work with the data afterwards. If you want to export the 'top' view in the monitor tab I would rather download the query plan and track the query so you can follow up on performance influence by your changes. Dumping the top 50 in anyone's queue will just cause nothing to happen because nobody can tune 50 queries at the same time. Focus on 1 or 2 and than move on to the next (which would require a new top since you made some changes on server level perhaps). / comments
You could use the 'longest running queries' tile and copy that to an Excel file.You can also email it but that is less nice if you wanna work with the data afterwards.If you want to export the 'top...
Alerts should auto clear. How long ago did you fix the job? Most checks are executed a few times a day to prevent killing your server with monitor requests. / comments
Alerts should auto clear. How long ago did you fix the job?Most checks are executed a few times a day to prevent killing your server with monitor requests.
If I'm not mistaken, deactivate and active is the correct solution to go. Just make sure your old server is connected to the internet when deactivating. You could also add the key to your new server already and see what is does? As a precaution, you could already try and open a ticket with support to have somebody "on stand-by" when you do the switchover? I'm surprised though that if you switched base monitor and web server but kept your database, the license isn't present on your new server. / comments
If I'm not mistaken, deactivate and active is the correct solution to go.Just make sure your old server is connected to the internet when deactivating.You could also add the key to your new server ...
I would check to use the migration manual for your base monitor: https://documentation.red-gate.com/sm13/moving-the-base-monitor-to-a-different-machine-195790020.html / comments
I would check to use the migration manual for your base monitor:https://documentation.red-gate.com/sm13/moving-the-base-monitor-to-a-different-machine-195790020.html
Your Redgate Monitor (13.0.35) is from Oct 2023. I would recommend updating to the latest 13.0 release at the least and maybe even to version 14. If you have a virtual machine running Redgate Monitor, you should always take a snapshot before making changes. Can't find any version history, but judging by the version of your coreclr.dll , your .NET version is out of date as well. So updating both Windows and .NET is also recommended if you haven't done so. / comments
Your Redgate Monitor (13.0.35) is from Oct 2023. I would recommend updating to the latest 13.0 release at the least and maybe even to version 14.If you have a virtual machine running Redgate Monito...
Hi, first of all, please be aware that the index recommendations done by Red Gate Monitor apply to that specific query. Always confirm with general index recommendations (like not more than seven indexes on one tables) before implementing. Not all software vendors support adding own (custom) indexes, always verify with your vendor first. The code for you index would look like this: CREATE INDEX IX_NAME_OF_INDEX ON [dbname].[dbo].[tablename] ([m_type], [ms_code]) INCLUDE ([level_], [description##1], [description##2], [description##3], [item_id], [document], [type], [form_name], [edit_authority], [spare_2], [params##1], [params##2], [params##3], [params##4], [params##5], [params##6], [params##7], [params##8], [params##9], [params##10], [params##11], [params##12], [params##13], [params##14], [params##15], [posttray_name], [posttray_priority], [prev_item], [PROGRESS_RECID]) WITH (fillfactor = 90, sort_in_tempdb = on); A few important remarks: - Fields marked with include are always red from table (disk) whenever a record is found via the index - options for the indexes in the "WITH" section are generally recommended: - fillfactor = 90 : prevents filling up all pages in the index, will cause index to be a bit bigger on disk, but less page splits - sort_in_tempdb = on : Option only has effect when running on SQL developer or enterprise edition. The index will be rebuild in the tempdb and will than replace the one in the table. Reducing the lock time on your table and improving performance during rebuild. If you have any additional questions, please reach out. / comments
Hi, first of all, please be aware that the index recommendations done by Red Gate Monitor apply to that specific query.Always confirm with general index recommendations (like not more than seven in...
Are you able to do a continuous ping from the base monitor to server#3? See if that shows any connection drops. Have you looked at the logs from SQL Monitor? https://documentation.red-gate.com/sm/maintaining-and-upgrading-sql-monitor/maintaining-sql-monitor/viewing-component-information-and-log-files Do these give you any insight? If possible, turn on a SQL profiler on server#3 and see if any connections come in from the base monitor. Even if the monitor account has insufficient rights, a connection attempt should still pop up in the profiler. / comments
Are you able to do a continuous ping from the base monitor to server#3? See if that shows any connection drops.Have you looked at the logs from SQL Monitor?https://documentation.red-gate.com/sm/mai...
1. If you're running in a vCore model you can just use the requirements posted here: https://documentation.red-gate.com/sm11/installation-and-setup/planning-the-sql-monitor-infrastructure-and-installation/sql-monitor-database-requirements If your on-prem setup uses 1 core per 5 SQL servers (hypothetical example) you can just extrapolate this to the cloud. For the DTU model you can find 'converters' to a core/dtu online. A good thing, you can scale Azure SQL Database up or down, so you can play around to find the correct infrastructure for your requirements. 2. If you dive in the data I'm sure you'll find a way to export the data and import on the new location. But this will be custom and very time consuming. I would just disable the monitoring on the current location (saving you the license) and start the monitoring on the new base monitor. That way for a brief moment of time (depending on your retention settings) you can use the new base monitor for current issues and the old base monitor for history. If you disable the monitoring for a server, you keep any data history. / comments
1. If you're running in a vCore model you can just use the requirements posted here:https://documentation.red-gate.com/sm11/installation-and-setup/planning-the-sql-monitor-infrastructure-and-instal...