Comments
Sort by recent activity
This particular incident is meant to occur when a job didn't start beacuse the previous run of the job is still executing. SQL Agent won't start a job untill the previous run has finished - but nothing will show in the job history about that.
However as the job only runs for 48 seconds, unless you're scheduling it to run more often than that then you shouldn't be seeing it.
Could you perhaps send us some screenshots of the incidents and corresponding times from the job monitor again please?
Thanks / comments
This particular incident is meant to occur when a job didn't start beacuse the previous run of the job is still executing. SQL Agent won't start a job untill the previous run has finished - but no...
Thanks very much for trying the beta, and for your suggestions. I'll add them to the list of things to consider for the final release.
If you have have more suggestions or queries then please keep them coming. [image] / comments
Thanks very much for trying the beta, and for your suggestions. I'll add them to the list of things to consider for the final release.
If you have have more suggestions or queries then please kee...
PDinCA wrote:
Also, if the process happens to be "Red Gate SQL Response" can you give us the option to ignore it, please? After all, there's not much we can do about it... :lol:
No... but we might be able to! Could you post the SQL that we display and I can then match it to what we're doing at the time and try to optimize it. I'd rather we didn't run any long running quieries rather than just mask them from you. / comments
PDinCA wrote:
Also, if the process happens to be "Red Gate SQL Response" can you give us the option to ignore it, please? After all, there's not much we can do about it... :lol:
No... but we ...
PDinCA wrote:
It would also help if the session's prepared SQL were divulged, not just the sql as in:
Custom_IndividualSearch;1
which doesn't tell me what the parameters were, so I can't reproduce it..
The SQL text is what we get out of the SQL server's input buffer (on SQL 2000) or from the DMV sys.dm_exec_sql_text on 2005. If it's a persistant problem then you can put the server in the highest level and collect trace data as well which should then capture the profiler output (but be aware this obviously has more impact on your server) / comments
PDinCA wrote:
It would also help if the session's prepared SQL were divulged, not just the sql as in:
Custom_IndividualSearch;1
which doesn't tell me what the parameters were, so I can't reprod...
Hi - I've sent you a pm about this - thanks. / comments
Hi - I've sent you a pm about this - thanks.
Hi - and thanks for trying the beta.
SQL Response should be capturing the SQL already. If you bring up the incident and click on the process in the list in the details pane then the SQL Query Fragment should show the SQL that was running. / comments
Hi - and thanks for trying the beta.
SQL Response should be capturing the SQL already. If you bring up the incident and click on the process in the list in the details pane then the SQL Query Frag...
[image]
It would be nice to know which query was casuing that. SQL Response should have caught the SQL that was running - so if you look at that incident and select the process in the list in the details pane then the SQL query fragment area should have the SQL that was running.
If you could pm that to me using the button below I'd appreciate it.
Thanks / comments
It would be nice to know which query was casuing that. SQL Response should have caught the SQL that was running - so if you look at that incident and select the process in the list in the details...
Hi and thanks for trying the beta [image]
We don't currently have an explicit "Agent not running" incident, but at the next scheduled job run you should be getting a "Job failed to start (Agent not running)" / comments
Hi and thanks for trying the beta
We don't currently have an explicit "Agent not running" incident, but at the next scheduled job run you should be getting a "Job failed to start (Agent not running)"
The license should work just fine I think - or if it didn't then the worst should be a dialog asking for new license code.
Do you not get an error after the splash screen disappears? It's possible this could be caused by a clash with some assemblies in the GAC - try the same suggestion mentioned here http://www.red-gate.com/MessageBoard/vi ... php?t=4997 (i.e. remove the DevExpress assemblies from %systemroot%\assembly ) and see if that fixes it. (I suggest you copy them elsewhere in case it breaks something that needs them)
If it doesn't then get back to us [image] / comments
The license should work just fine I think - or if it didn't then the worst should be a dialog asking for new license code.
Do you not get an error after the splash screen disappears? It's possible...
Hi - you should ask this on the help forum at http://forums.reflector.net / comments
Hi - you should ask this on the help forum at http://forums.reflector.net