Activity overview
Latest activity by TeunvdBiggelaar
Yes that is happening when im already logged in. I will create a new topic. / comments
Yes that is happening when im already logged in. I will create a new topic.
I still receive these kinds of errors when im trying to open alerts and i'm on version 13.0.51.53 in our development environment. / comments
I still receive these kinds of errors when im trying to open alerts and i'm on version 13.0.51.53 in our development environment.
What i also noticed is that the new version consumes way less CPU and Memory on the Basemonitor server! / comments
What i also noticed is that the new version consumes way less CPU and Memory on the Basemonitor server!
Only for the Basemonitor server. / comments
Only for the Basemonitor server.
Hi Alex. I installed it on our development environment and i can confirm it solved the issue. One small remark, since a few releases the finish button stays greyed out if you patch the basemonitor server. Maybe something for a next release as well [image] ? [image] Keep up the good work! / comments
Hi Alex. I installed it on our development environment and i can confirm it solved the issue.One small remark, since a few releases the finish button stays greyed out if you patch the basemonitor s...
Alex B said:
Hi all, Do you get the error if you run this query against the target SQL instance that you see the error for in SQL Monitor? SELECT db.name ,
db.state_desc ,
db.is_auto_create_stats_on ,
db.is_auto_shrink_on ,
db.collation_name ,
db.compatibility_level ,
db.create_date ,
db.page_verify_option_desc ,
db.recovery_model_desc ,
db.database_id ,
db.source_database_id ,
db.is_in_standby ,
db.is_read_only,
ISNULL((SELECT 1 FROM [msdb].[dbo].[log_shipping_secondary_databases] WHERE ls.[secondary_database] = db.name),0) AS is_log_shipping_secondary,
SUSER_SNAME(owner_sid) [owner]
FROM sys.databases db
LEFT OUTER JOIN [msdb].[dbo].[log_shipping_secondary_databases] AS ls
ON ls.[secondary_database] = db.name
ORDER BY db.name
And if so, what is returned by the subquery here: SELECT 1 FROM [msdb].[dbo].[log_shipping_secondary_databases] WHERE [secondary_database] = db.name
And how have you configured things to get this result? Kind regards, Alex
Hi Alex, The first query returned the same error as in SQL Monitor. The 2nd query doesn't work on it's own because its missing the db.name reference from the other part of the query, and in my case I have 3 logshipped databases on that host which are in a (Standby / Read-Only) state therefor. Thanks, Teun / comments
Alex B said:
Hi all,Do you get the error if you run this query against the target SQL instance that you see the error for in SQL Monitor?SELECT db.name ,
db.state_desc ,
db.i...
Alex B said:
Hi all, What version of SQL Server are these instances you are seeing the problem with? Kind regards, Alex
Hi Alex. It happens to one of the servers running on 2019, others seem to be fine. Microsoft SQL Server 2019 (RTM-CU22-GDR) (KB5029378) - 15.0.4326.1 (X64) Aug 18 2023 14:05:15 Copyright (C) 2019 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor) / comments
Alex B said:
Hi all,What version of SQL Server are these instances you are seeing the problem with?Kind regards,Alex
Hi Alex. It happens to one of the servers running on 2019, others seem to...
Monitor error, SqlDatabaseSampler
Hi all, Last week i've updated to version 13.0.39 and I noticed that a few servers are getting a "monitoring error" on the Overview page. When i click on the message this is the error message:
Sub...
Can you show your queryplan? and some more decent specs? Overall 8GB memory is not much specially if this is shared with your windows OS. / comments
Can you show your queryplan? and some more decent specs? Overall 8GB memory is not much specially if this is shared with your windows OS.
To resolve this issue do the following: First, take a backup of the
data repository (RedGateMonitor database by default) in case anything should go
awry.
Then, we will need to find the entry for that instance in the repository in the
settings.SqlServers table - which will look like: SELECT * FROM settings.SqlServers AS ss
WHERE Name = 'FirstNodeName\' OR Name = 'SecondNodeName\'; And then you would want to
delete by Id the entry in that table that has name that matches the two nodes
that no longer exist (which represents the default instance on that server, if
it was a named instance it would have the instance name after the backslash
e.g. serverName\instanceName) DELETE FROM settings.SqlServers
WHERE Id = '<theIdFromFirstNodeAbove>' OR
Id = '<theIdFromSecondNodeAbove>'; This worked for me and was given as a solution by the support team in the past. Good luck! / comments
To resolve this issue do the following:First, take a backup of the
data repository (RedGateMonitor database by default) in case anything should go
awry.
Then, we will need to find the entry for tha...