April 8, 2014 at 2:33 pm
I have been asked to monitor the DRIVE space where our data (mdf) and log (ldf) files are located for each of our SQL Server installations. I have sysadmin rights to each SQL Server and am able to connect to each instance via SQL Server Management Studio. I can successfully run queries to monitor the log and data file size within the SQL Server.
I am not able to RDP into the server to look at the remaining free space on the DRIVES. I would like to know how other DBAs address this issue without being able to RDP into the host Windows Server. The server admin is reluctant to grant this right. While I can see how the data and log files are doing from a SQL point of view, I need a way to see how it affecting drive space.
Thanks for any suggestions.
April 8, 2014 at 3:12 pm
Do you have permissions to run powershell scripts?
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
April 8, 2014 at 3:19 pm
Unfortunately no I do not. Our server admin does not like to give any more permission than necessary. He feels sysadmin is enough and that it should be able to be done via SSMS. The drive space is an OS object, not a SQL object. I do not see how this can be achieved.
April 8, 2014 at 3:26 pm
Then try this
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
April 8, 2014 at 3:48 pm
Hey thanks a lot! That gets me what I need to know to watch over the drives. I can at least see when disk space is getting low.
April 8, 2014 at 3:53 pm
You're welcome
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
April 8, 2014 at 9:02 pm
defyant_2004 (4/8/2014)
Our server admin does not like to give any more permission than necessary.
This is me trying to be positive: Nice. That absolves you from a whole bunch of responsibility when the server dies.
But actually I feel that declining all access is a cop-out and one that I would fight vigorously. I guess this is an artifact of huge organizations though and I work for smaller ones (e.g < 50 employees). Maybe in those bigger environments this is the norm.
April 9, 2014 at 7:57 am
I have actually been arguing for more access for a long time now. I came real close about 3 months ago, but then he had 'change of mind'.
April 9, 2014 at 9:08 am
defyant_2004 (4/9/2014)
I have actually been arguing for more access for a long time now. I came real close about 3 months ago, but then he had 'change of mind'.
Patience, eventually it will work out for the best. When the day comes that you need to troubleshoot the server and have to wake him up, he will begin to regret you not having those permissions.
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
April 9, 2014 at 3:01 pm
defyant_2004 (4/8/2014)
Unfortunately no I do not. Our server admin does not like to give any more permission than necessary. He feels sysadmin is enough and that it should be able to be done via SSMS. The drive space is an OS object, not a SQL object. I do not see how this can be achieved.
Be aware that xp_fixeddrives does not work for mounted volumes. For reliable disk space info, from SSMS you can enable XP_Cmdshell and use the following
exec xp_cmdshell 'wmic volume get capacity, "free space", name'
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply