Comments
Sort by recent activity
Thanks for the log files. I've had a look through them but unfortunately I can't see anything that would obviously cause this issue.
Is there any chance that you could test modifying alert settings on a browser other than Internet Explorer? This will help us to narrow down the cause of the issue. I am trying to reproduce this internally and seeing a similar issue on Internet Explorer (similar as in I can get it to error when saving - error message is different though)
Thanks
Chris / comments
Thanks for the log files. I've had a look through them but unfortunately I can't see anything that would obviously cause this issue.
Is there any chance that you could test modifying alert settings...
Hi Harold
Apologies for this. Is this happening to all alerts or just a few? Does it happen only when you make changes to an alert or every time the Save Settings button is clicked?
It would also be interesting to know what browser you are using?
Many Thanks
Chris / comments
Hi Harold
Apologies for this. Is this happening to all alerts or just a few? Does it happen only when you make changes to an alert or every time the Save Settings button is clicked?
It would also b...
Hi Kevan
I've investigated this and have raised a bug report SRP-2489. I'm fairly sure that the data is still being collected, we're just not presenting it in the UI.
We'll be fixing it for the next release.
Thanks
Chris / comments
Hi Kevan
I've investigated this and have raised a bug report SRP-2489. I'm fairly sure that the data is still being collected, we're just not presenting it in the UI.
We'll be fixing it for the nex...
I've raised a bug report (SRP-2547) regarding SQL 2000 trace data not displaying for various alerts. This will be investigated and fixed in a future release.
Many Thanks
Chris / comments
I've raised a bug report (SRP-2547) regarding SQL 2000 trace data not displaying for various alerts. This will be investigated and fixed in a future release.
Many Thanks
Chris
xexex wrote:
I got the same problem.
I'm using SQL 2000 ent. and installed on [image]
I've enable TRACE function but SQL monitor report that TRACE is disable.
How is SQL Monitor reporting the trace being disabled? Is it the Deadlock trace flag disabled alert? The Configuration > Trace page can be used to start a trace on the server but it currently doesn't give any feedback as to whether the trace is running.
I'm going to investigate running trace on SQL Server 2000 to see if I can reproduce these issues. I'll post here if I find something.
Thanks
Chris / comments
xexex wrote:
I got the same problem.
I'm using SQL 2000 ent. and installed on
I've enable TRACE function but SQL monitor report that TRACE is disable.
How is SQL Monitor reporting the trace b...
Hi Sam
Thanks for the logs. They seem to suggest that data collection is in a healthy state.
Luckily they're not the only logs we produce. Would it be possible for you to zip up and send the log files at this location C:\ProgramData\Red Gate\Logs\SQL Monitor 2 (or C:\Documents and Settings\All Users\Application Data\Red Gate\Logs\SQL Monitor 2 on pre-Vista OS) to chris.spencer@red-gate.com ?
Note that if you have a distributed setup the log files will be created on the different machines - we’d be interested in the base monitor ones as well as website.
Many thanks
Chris / comments
Hi Sam
Thanks for the logs. They seem to suggest that data collection is in a healthy state.
Luckily they're not the only logs we produce. Would it be possible for you to zip up and send the log fi...
Hi Sam
Thanks for sending the results. The output confirms that SQL Monitor is running trace on the 2000 server. Can you check to see if new Blocked Process or Long Running Query alerts have started displaying SQL Processes and trace information?
SQL Response and SQL Monitor should be able to run side-by-side so you don't have to remove Response. As far as I know, the only issue with both products running trace on the same server would be the performance overhead. For this reason we recommend using the trace options for diagnostic purposes only.
Thanks
Chris / comments
Hi Sam
Thanks for sending the results. The output confirms that SQL Monitor is running trace on the 2000 server. Can you check to see if new Blocked Process or Long Running Query alerts have starte...
I don't think the trace would even start up if that path didn't exist on the database server but it's worth double checking.
It looks like the trace-running mechanism is working correctly. If you're still not seeing trace on the Blocked Process alert details then it's likely to be an issue further down the line. Are there any connection issues on Configuration > Managed Servers page? If you click the 'Show Log' link for [servername] then it'll take you to a useful diagnostic page. Any data collection errors would appear here.
Thanks
Chris / comments
I don't think the trace would even start up if that path didn't exist on the database server but it's worth double checking.
It looks like the trace-running mechanism is working correctly. If you'r...
It would be useful to know if trace is running on the 2000 server. This t-sql snippet should display all defined traces SELECT * FROM :: fn_trace_getinfo(DEFAULT)
If SQL Monitor is still collecting trace, the results should include a trace specific to our product. The value of property 2 will end with "..MONITOR.trc". If our trace doesn't appear then the trace will have either not started correctly or started then terminated.
You could maybe try switching trace off for that server (in the SQL Monitor UI > Configuration > Trace), saving settings and then switching it back on again and seeing if a trace does get started.
Note that it might take a few minutes from starting trace for the information to actually start appearing in the details of new alerts.
Hope this helps
Chris / comments
It would be useful to know if trace is running on the 2000 server. This t-sql snippet should display all defined tracesSELECT * FROM :: fn_trace_getinfo(DEFAULT)
If SQL Monitor is still c...
In v2.0 we only support the single password log-in so I'm afraid it'll have to be shared.
You'll be glad to know that we're planning improvements to this in future releases and you'll get much finer control over website access.
Thanks for the feedback
Chris / comments
In v2.0 we only support the single password log-in so I'm afraid it'll have to be shared.
You'll be glad to know that we're planning improvements to this in future releases and you'll get much fine...