Activity overview
Latest activity by SAY
We updated today to the latest SQL Monitor version 11.2.1.11682. SQL Monitor main dashboard then displayed a red banner error 'sql monitor 11.2.1.11682 – cannot get data from base monitors: localhost. see details' My fix was to go to the 'Base Monitor Connections' page under Configuration menu and change from 'localhost' to '127.0.0.1' This fixed it immediately. Seems strange it didn't know what localhost was? If helps others.. / comments
We updated today to the latest SQL Monitor version 11.2.1.11682. SQL Monitor main dashboard then displayed a red banner error 'sql monitor 11.2.1.11682 – cannot get data from base monitors: localho...
Does Dependancy Tracker track column dependancies? We need this as its main feature. Thanks. / comments
Does Dependancy Tracker track column dependancies? We need this as its main feature. Thanks.
Does Dependancy Tracker track column dependancies? We need this as its main feature. Thanks. / comments
Does Dependancy Tracker track column dependancies? We need this as its main feature. Thanks.
peter eh said:
Hello Russell, thank you so much for your answer. There are no dump files, no other corresponding entries in SQL or Windows log files, no jobs (except SQL Monitor) that always run at the time in question. On one server the errors stopped suddenly and without any changes, on the other one they appear in the SQL log about 200 times per day. This is really puzzling. I had already read the sqlservercentral article, but unfortunately it doesn't help because no solution is described and he doesn't write if the problem was fixed after the reboot. The recovery interval for all DB's on both servers was set to 60 from the beginning. Next week we will patch and boot both servers, see what it looks like afterwards.
Hi Peter, did you find the solution? We are also getting this error sporadically (daily) on one of our Prod 20016 Ent SQL Servers. Thanks, SImon / comments
peter eh said:
Hello Russell,thank you so much for your answer. There are no dump files, no other corresponding entries in SQL or Windows log files, no jobs (except SQL Monitor) that always r...
peter eh said:
Hello Russell, thank you so much for your answer. There are no dump files, no other corresponding entries in SQL or Windows log files, no jobs (except SQL Monitor) that always run at the time in question. On one server the errors stopped suddenly and without any changes, on the other one they appear in the SQL log about 200 times per day. This is really puzzling. I had already read the sqlservercentral article, but unfortunately it doesn't help because no solution is described and he doesn't write if the problem was fixed after the reboot. The recovery interval for all DB's on both servers was set to 60 from the beginning. Next week we will patch and boot both servers, see what it looks like afterwards.
Hi Peter, did you find the solution? We are also getting this error sporadically (daily) on one of our Prod 20016 Ent SQL Servers, thanks Simon. / comments
peter eh said:
Hello Russell,thank you so much for your answer. There are no dump files, no other corresponding entries in SQL or Windows log files, no jobs (except SQL Monitor) that always r...