Activity overview
Latest activity by Signe
Alex B said:
Hi all, SQL Monitor version 13.0.40 is now available with a fix for this issue. You can download it here: https://download.red-gate.com/checkforupdates/SQLMonitorWeb/SQLMonitorWeb_13.0.40.27471.exe Kind regards, Alex
Finally got around to install 13.0.40 and it works like a charm! Thanks alot! Cheers//Signe / comments
Alex B said:
Hi all,SQL Monitor version 13.0.40 is now available with a fix for this issue. You can download it here: https://download.red-gate.com/checkforupdates/SQLMonitorWeb/SQLMonitorWe...
Alex B said:
Hi @Signe, I forgot to take out the "ls." when I took that subquery out of the main one above it, apologies for that. I've edited it above but it is here again corrected now: SELECT 1 FROM [msdb].[dbo].[log_shipping_secondary_databases] WHERE [secondary_database] = db.name
Are any of the databases in restoring mode that are a part of log shipping the secondary for multiple different primaries? We're trying to understand how the subquery could return more than one entry unless the seoncdary_database was in there multiple times, but that should only occur if it is the secondary for multiple primaries which, though seems possible to set, doesn't make sense. Kind regards, Alex
No worries [image] The query returns: Msg 4104, Level 16, State 1, Line 4 The multi-part identifier "db.name" could not be bound. There´s only one primary logshipping to the instance, 5 databases with transaction logshipping and one with merge replication (yes, it sucks, but I hope to get rid of it rather soon... [image] [image] Cheers//Signe / comments
Alex B said:
Hi @Signe,I forgot to take out the "ls." when I took that subquery out of the main one above it, apologies for that. I've edited it above but it is here again corrected now:SELE...
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?...
I get the same error if I run the first query and this when I run the second: Msg 4104, Level 16, State 1, Line 3 The multi-part identifier "ls.secondary_database" could not be bound. Msg 4104, Level 16, State 1, Line 3 The multi-part identifier "db.name" could not be bound. It is a named instance with logshipping, so it has a couple of databases in restoring mode. The default instance on the cluster has been uninstalled, maybe there are some remains of this that could somehow be the culprit? Cheers, Signe / 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?...
I get the same error if I run the first query an...
Hi! For me it is SQL Server 2019 CU22, but I have other instances with the same version that shows correctly. Cheers, Signe / comments
Hi!For me it is SQL Server 2019 CU22, but I have other instances with the same version that shows correctly. Cheers, Signe
Hi! I´m having the same problem after updating to 13.0.39: [image] Hoping for a fix asap as I really like the Index-tab. / comments
Hi!I´m having the same problem after updating to 13.0.39: Hoping for a fix asap as I really like the Index-tab.