Comments
Sort by recent activity
Other than configuring this for each alert, there's currently no quick way to do this.
However, this is a popular suggestion on our UserVoice feedback forum. Could I suggest you contribute your views (& votes) to that discussion? https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/2005299-allow-emails-to-be-sent-based-upon-alert-priority
Thanks,
Colin. / comments
Other than configuring this for each alert, there's currently no quick way to do this.
However, this is a popular suggestion on our UserVoice feedback forum. Could I suggest you contribute your vi...
Tjay, I've put a copy in my dropbox account, which you can get at: https://dl.dropboxusercontent.com/u/10715620/SqlMonitorWeb_4.0.0.1728.exe [EDIT: this is now removed from DropBox.]
It would be interesting to see whether you get download issues from here, which would suggest to me that it's something about your network connectivity, rather than something about our download servers.
Thanks,
Colin. / comments
Tjay, I've put a copy in my dropbox account, which you can get at:https://dl.dropboxusercontent.com/u/10715620/SqlMonitorWeb_4.0.0.1728.exe[EDIT: this is now removed from DropBox.]
It would be inte...
Hi Tjay,
Can you tell us what the upgrade link URL is please?
Thanks,
Colin. / comments
Hi Tjay,
Can you tell us what the upgrade link URL is please?
Thanks,
Colin.
Thanks Tjay. Something odd is going on, I've tried that download link on both my work and home PC, and can run through most of the installation process with the resulting .exe (I've stopped short of actually installing). I take it this is further than you've been able to get?
Does the size of the executable on disk look right? It should be 21.3 MB (22,343,680 bytes).
Thanks,
Colin. / comments
Thanks Tjay. Something odd is going on, I've tried that download link on both my work and home PC, and can run through most of the installation process with the resulting .exe (I've stopped short ...
Hi John,
Assuming you're actively monitoring the server(s) with the databases of interest, then SQL Monitor captures this information automatically for you. We capture total size, as well as data and log size (as separate metrics).
These are accessible via the "Analysis" tab. You can also export the data to .csv files, to do further analysis (such as capacity planning).
Is this the information you're after?
Best regards,
Colin. / comments
Hi John,
Assuming you're actively monitoring the server(s) with the databases of interest, then SQL Monitor captures this information automatically for you. We capture total size, as well as data ...
Can you try putting sqlbackup in the second box, as this tends to appear in the SQL command. In fact, to be on the safe side, you could put all three in both boxes, although this may not be strictly necessary.
Thanks,
Colin. / comments
Can you try putting sqlbackup in the second box, as this tends to appear in the SQL command. In fact, to be on the safe side, you could put all three in both boxes, although this may not be strict...
Hi,
I'm pretty sure the name of the SQL process you want to exclude is sqlbackup
This would go into the top box on the Alert configuration settings for Long-Running Query.
Thanks,
Colin. / comments
Hi,
I'm pretty sure the name of the SQL process you want to exclude is sqlbackup
This would go into the top box on the Alert configuration settings for Long-Running Query.
Thanks,
Colin.
To add to Chris' comment, it's important to retain the indentation in the output. You should be able to see this indentation in the content of the Output tab for the deadlock alert, and this is what we're after.
Thanks,
Colin. / comments
To add to Chris' comment, it's important to retain the indentation in the output. You should be able to see this indentation in the content of the Output tab for the deadlock alert, and this is wh...
dewet wrote:
Hi Colin,
as I could see in code (caught in dm_exec_requests) the frequency is 200ms (run in 5 minutes cycles).
Is it possible to configure this frequency or the length of cycle?
Yes, this is possible. On the SQL Server hosting SQL Monitor's Data Repository, you need to change a value in the table 'settings.KeyValuePairs'. For eg, assuming your Data Repository database is named "RedGateMonitor", then this T-SQL...
USE [RedGateMonitor]
UPDATE [settings].[KeyValuePairs]
SET KeyValue = 500
WHERE KeyName = 'WaitStatsCollection-QueryWaitInterval'
... would change the default from 200ms to 500ms (for example).
Note that you need to restart the "SQL Monitor 4 Base Monitor" service for this change to take effect. / comments
dewet wrote:
Hi Colin,
as I could see in code (caught in dm_exec_requests) the frequency is 200ms (run in 5 minutes cycles).
Is it possible to configure this frequency or the length of cycle?
Y...
Hi Brent,
Thanks for the questions. Let me try to shed some further light:
Firstly, I can confirm that there is no agent installed on the monitored servers.
The 6-7ms values you've referenced aren't waits, but are the average duration per query. These are generated statistically, so don't require sampling at a very high frequency: for eg, if we burn 6 seconds of CPU on a query that runs 1,000 times in a minute, we’d generate a Duration value of 6ms in the "Affected queries" table.
We're not sampling waits every 5ms, but they are sampled very frequently. We're combining data from different places and with different sampling frequencies to generate the data. In general we're careful to show where the data is estimated because it's sampled, particular around wait times. We've done lots of testing, and we’re confident our approach will have minimal impact on performance.
Happy to talk this through in more detail, but would need to take this offline, because it's too complex for a forum exchange, and strays into areas of commercial sensitivity. Message me back if you want to dig into this further.
Cheers,
Colin. / comments
Hi Brent,
Thanks for the questions. Let me try to shed some further light:
Firstly, I can confirm that there is no agent installed on the monitored servers.
The 6-7ms values you've referenced aren...