June 26, 2013 at 12:10 pm
Hi Sailor,
My IT dept keeps an eye on disk space through another alerting process so I hadn't given it much thought. It would certainly be easy to do though...
btw - dbWarden 2.5.1 was just released. For those upgrading from previous versions, this release is highly recommended. It fixes a crucial bug where upgrading users were missing a couple records in the AlertSettings table which was preventing the Logfile and TempDB growth alerts to not work.
July 23, 2013 at 4:56 am
Are there any installation tips for those attempting to use dbwarden in a case sensitive environment?
July 23, 2013 at 9:54 am
Neil Cutt (7/23/2013)
Are there any installation tips for those attempting to use dbwarden in a case sensitive environment?
I've been making slow progress in getting everything case sensitive. It's something that has bothered me for a bit now and I like to try to make the script work for everyone.
July 23, 2013 at 3:16 pm
Neil and everyone else who is interested in case sensitivity, I believe I have fixed the script to work on a case sensitive server. The change will be in the next release.
If you are interested in helping me test, shoot me your email address and I'll email you a test script to try out.
July 25, 2013 at 8:51 am
Firstly let me say that this is a great tool!
However I am getting the following error whenever the jobs try to send an email.
Executed as user: NT AUTHORITY\NETWORK SERVICE. Warning: Null value is eliminated by an aggregate or other SET operation. [SQLSTATE 01003] (Message 8153) No global profile is configured. Specify a profile name in the @profile_name parameter. [SQLSTATE 42000] (Error 14636). The step failed.
It works if I add the @profile_name parameter with a value set to a Database Mail account name to the sections that send the emails.
I'm wondering if I am missing something with the way Database Mail is set up on my server. Any ideas?
July 25, 2013 at 9:27 am
You can have a profile in DBMail set to be the "Default Profile" (You can find it under Profile Security) which would allow you to send mail without specifying a profile name.
July 25, 2013 at 9:41 am
Thanks for sharing this with the community. This looks to be very useful.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 31, 2013 at 8:08 am
On the email alert for blocking, the SQL may get truncated, so I cannot see the table. So, I go into activity monitor where I can see the object id and run:
SELECT OBJECT_NAME(i.object_id), i.name, p.partition_id
FROM sys.partitions AS p
INNER JOIN sys.indexes AS i ON i.object_id = p.object_id AND i.index_id = p.index_id
order by p.partition_id
--WHERE p.partition_id = 7205794049003520
Also in activity monitor I can see the head of the chain, which the alert did not seem to show?
July 31, 2013 at 10:44 am
Sailor (7/31/2013)
On the email alert for blocking, the SQL may get truncated, so I cannot see the table. So, I go into activity monitor where I can see the object id and run:SELECT OBJECT_NAME(i.object_id), i.name, p.partition_id
FROM sys.partitions AS p
INNER JOIN sys.indexes AS i ON i.object_id = p.object_id AND i.index_id = p.index_id
order by p.partition_id
--WHERE p.partition_id = 7205794049003520
Also in activity monitor I can see the head of the chain, which the alert did not seem to show?
You can view the entire SQL_Text by querying the BlockingHistory table. Alternatively, you could also alter the trigger that sends the email to display more characters. Currently the SQL_Text is limited to 100 characters.
Same goes for the QueryHistory table and the Long running queries procedure.
Hope that helps.
July 31, 2013 at 11:05 am
Thanks, I'll do that next time.
August 1, 2013 at 4:43 pm
Just wanted to let everyone know we've released dbWarden 2.5.2. For everyone that runs CaSe SenSiTive servers, this release is for you! 🙂
August 22, 2013 at 4:37 pm
Thank you so much for this superb monitoring tool.
I assume that if I search and replace 'DBA' for 'dbWarden' in the latest uninstall script, I can remove the early version I installed (including DBA tables and SQL Agent jobs) and then proceed to install the latest version (creating dbWarden instead)?
Thanks again!
August 23, 2013 at 11:57 am
Hi Daniel,
Yes, in theory 🙂 it should work. I will admit that I haven't tested the script lately and I can't recall what changes made recently that might not be covered in the uninstall script.
I will make a note to verify it's functionality soon. If you aren't concerned with historical data, then just dropping the database and letting the script recreate it, would work too.
August 23, 2013 at 4:49 pm
Thanks, Michael. I will test the script as well and let you know how I fare. I'm not concerned with historical data, and so can also drop the database, but I'll test the script first.
I appreciate the work you've put into this, and am grateful for your sharing it.
August 29, 2013 at 7:16 am
FYI: the uninstall script worked perfectly on the old version, simply by replacing dbWarden with DBA.
Thanks again!
Viewing 15 posts - 136 through 150 (of 186 total)
You must be logged in to reply to this topic. Login to reply