Comments
Sort by recent activity
Sorry for the delay in getting back to you on this.
I'll send you an email to request more details. Thanks / comments
Sorry for the delay in getting back to you on this.
I'll send you an email to request more details. Thanks
Fantastic! Thanks for writing that up - will save me a job [image] / comments
Fantastic! Thanks for writing that up - will save me a job
I saw the other developer puzzling over your popup menu problem earlier. The testers have seen this but we find it hard to reproduce all the time.
Thanks for your suggestions - we will consider them all (I'm pretty sure that number 1 will make it as I intend makeing that change this week [image] ) / comments
I saw the other developer puzzling over your popup menu problem earlier. The testers have seen this but we find it hard to reproduce all the time.
Thanks for your suggestions - we will consider th...
No - the bug was purely client side in displaying the deadlock information.
Could you email me the relevant deadlocks from your errorlog please? I'd really like to find out how we're causing those.
Email is nigel.morse at red-gate.com / comments
No - the bug was purely client side in displaying the deadlock information.
Could you email me the relevant deadlocks from your errorlog please? I'd really like to find out how we're causing those...
Those alerts are caused by when the alert repository cannot contact the server far some reason - the error messages may have something more, but if you have a whole bunch of them this implies that it something like the network connection went down at somepoint between the alert repository machine and the SQL Server machines.
If you look at the icons next to the servers in the server list they will tell you the current connection state. For the RC if the connection is currently OK then the icon will be like a ribbon and when you hover over it it will say "This server in in trial...." otherwise it will be an error icon and the tooltip should display an error message. / comments
Those alerts are caused by when the alert repository cannot contact the server far some reason - the error messages may have something more, but if you have a whole bunch of them this implies that ...
Thanks for the suggestions [image]
Giggles220 wrote:
4. It would be nice to be able to ignore some alerts or recommendations for certain jobs or Databases. For instance, I don't care if the zATC database is backed up but I care about all the other ones on the server. I don't want to keep clearing these out. Or I don't care if the replication cleanup jobs don't start are take longer but I care about others.
You should be able to do this - if you go to the "configure a server" tab then you should be able to expand the sever, expand the alert you're interested in and then see a list of jobs or databases and then you can customize the values for ones you want to behave differently.
Giggles220 wrote:
3. When making a change to the time in the long running query (probably true in other areas too) I changed it from 10 to 30 and I had to click in another field in order to get the save button to appear.
This we'll try and fix
Giggles220 wrote:
over all I like the product alot.
Thank you - that's great to hear [image] / comments
Thanks for the suggestions
Giggles220 wrote:
4. It would be nice to be able to ignore some alerts or recommendations for certain jobs or Databases. For instance, I don't care if the zATC database...
1596 was the release candidate (i.e. we've not updated it) - This should be fixed in the final release. / comments
1596 was the release candidate (i.e. we've not updated it) - This should be fixed in the final release.
Thanks for that - I got both your emails and we've now managed to reproduce this bug locally so it will be fixed for release [image]
Thanks a lot for the help / comments
Thanks for that - I got both your emails and we've now managed to reproduce this bug locally so it will be fixed for release
Thanks a lot for the help
Just for let you know I've fixed this now (I believe). Thanks for finding it. / comments
Just for let you know I've fixed this now (I believe). Thanks for finding it.
Hmm - that's very odd (that's my controlled way of saying ARGHHHHH! [image] )..... we had this bug before, but we fixed it - or so I thought.
It was previously caused by not taking the timezone into account so i'll try and make sure that's not causing it this time - otherwise i'll need to get hold of the job schedule information and the job history for that that job please to see if we can reproduce it.
it's late now in the UK - so if you know how to get hold of those then please email them to nigel.morse@red-gate.com - or if not I'll work out a script to get what I need tomorrow and ask you to run that.
Thanks / comments
Hmm - that's very odd (that's my controlled way of saying ARGHHHHH! )..... we had this bug before, but we fixed it - or so I thought.
It was previously caused by not taking the timezone into accoun...