Posts
Sort by recent activity
Feature Request: Usability Enhancement for "Clear Alert"
I'm aware of the configuration option to require a comment when clearing an alert. However, leaving the "Enable comments..." option still means that the dialog box pops up in the same place every ...
CHM - option to manage the font SIZE please
For whatever reason, and I've yet to find a way to change the font SIZE, the chm is showing as if I'm strongly vision-impaired! Typesize is MASSIVE in the content pane, compared to "very normal" i...
CHM doesn't work with IE8 beta
Any idea when a SQL Doc version will be ready (beta even) that will work with IE8 as the underpinning of the .chm file explorer? It's not only SQL Doc's .chm that's unusable with IE8, btw. And "w...
Love the live update of descriptions to the DB - suggestion
Great job on the ease with which I can add extended properties in bulk - I can FINALLY see myself documenting the database!
In keeping with the concept of templates or datatypes, we have, like othe...
2 Databases Stuck "In Progress" - NOT a "VERIFY" issue
1 Transaction Log backup on a single DB and 1 FULL backup on a different DB are showing as "In Progress" and have been for about 3 weeks... ZERO Bytes for both.
There is NO Job defined for the dat...
Build 520: Erroneous "Blocked SQL Process" incident?
The .Net query cited as the Blocked process (yes, don't use SELECT *... legacy code :oops: ) is
SELECT * FROM Individual WHERE Email = 'name@domain.org' AND IsActive = 1 AND SiteID = 4
with the B...
Improvement: Attempt repository reconnection periodically
When the client's network connection goes down (for example, when a colleague unplugs the network hub!) it would be great if the client had an "Automatically attempt reconnection" feature. As an e...
Build 520: Service went fatal - couldn't talk to server(s)
As I don't read .Net log files with much understanding, I need to have you unravel it... The salient points being:
1. Our Tech guys replaced a UPS, during which a few machines were moved around, b...
Build 520 - erroneous "Job did not start" persists
When the Job or Step duration is 00:00:00, it means the Job/Step very swiftly found "nothing to do". This is not a "Job did not start" incident.
Job History clearly shows successful execution.
How to stop SQL Response being "Blocker", causing Deadlock?
SQL Response was identified as the "Blocker" for my scheduled "Shrink DB" Job - so my job was nixed... I marked the SR command in blue below...
I don't want Jobs nixed due to a monitoring tool's a...