February 22, 2012 at 12:36 pm
Eugene - I am unable to duplicate this issue. I created a VM named 1SQLSVR, installed SQL 2008 R2 on it, and loaded my routines. Everything worked correctly.
February 22, 2012 at 5:31 pm
That's odd, it worked correctly for me with servers without numbers in front, but not if there were numbers. Could you send me a link to your routines? Maybe I'm using a different version of your sproc.
February 22, 2012 at 10:10 pm
Sure. The latest version can always be found here: http://shaunjstuart.com/archive/2011/07/drive-space-monitoring-page/
March 4, 2012 at 6:50 pm
Thanks Shaun! The latest script works without error.
How do you normally display the data in a report? I'm currently running the sproc without using the powershell script.
March 5, 2012 at 12:49 pm
I created an SSRS report that reads the data table and makes graphs off of that.
August 30, 2013 at 2:50 am
Browsing around on his home page, it looks like he lives in Arizona.
So we (in Europe?) need to give him time to wake up. :hehe:
August 30, 2013 at 2:55 am
Ooops, just realized this is an old discussion...
August 30, 2013 at 6:01 am
Will this run ok on SQL 2012 or are there any updates to this to support SQL 2012?
August 30, 2013 at 6:50 am
Hi,
After adding the database and then I run the power shell script but its shows an error - so please sugget error message is - "cannot be loaded because the execution of scripts is di
sabled on this system"
August 30, 2013 at 8:12 am
My question is would your "monitor" be better off using:
1. dynamically created & remotely executed openquery(s)
2. using existing linked server coded (lazy DBA's need look no further this dude did it for you)
3. using Service Broker queue based push approach via service broker based asynchronous messaging.
August 30, 2013 at 8:56 am
It should run OK on SQL 2012.
August 30, 2013 at 8:58 am
Pradeept - That sounds like a Windows security setting issue. It sounds like Windows is configured to not allow execution of PowerShell scripts. Check with your network guys and see if perhaps there is AD policy in place that prevents this.
August 30, 2013 at 9:04 am
Does this script handle mount points and C: drives on passive nodes in a cluster?
August 30, 2013 at 9:08 am
thadeushuck - Define "better off."
1. That's your call. It depends on your environment. This is a monitoring routine that I run overnight during a period of little system activity. Performance is not an issue for me in this situation. If you are concerned about optimizing performance, sure, go ahead and use openquery.
2. Not sure what you a referring to here.
3. Service broker was not introduced until SQL 2005. My code is written so that is will also work with SQL 2000 servers, as I still have a handful of those in production.
August 30, 2013 at 9:16 am
It does not handle mount points. I do not have any servers utilizing those in my environment, so I have nothing to test against. Sorry.
Have not tried it with C: drives on a passive node in a cluster, but it probably wouldn't work as-is because it assumes the server name in the server list table is running sql server. If you put a passive node machine name in there, other parts would fail. You could probably modify the server list table to add a machine name flag and have the PowerShell script check those drives, but have the T-SQL code portion ignore those entries. In that case, you've just created a disk space monitoring routine for all computers, not just SQL Servers 🙂
Viewing 15 posts - 46 through 60 (of 64 total)
You must be logged in to reply to this topic. Login to reply