Monitoring File Sizes in SQL Server

  • Comments posted here are about the content posted at temp

  • Roy,

    Excellent article. 

    Can this script be run for multiple servers?  Can I set the strComputer variable multiple times similar to the multiple databases?



  • Roy,

    Pretty good article.

    I have a little script I use to determine if I'm running out of space on each of the server drives and send me an email when the freespace gets below a threshold, rather than look at the space of each of the individual files.  This might be useful as well....


  • I have no VB skills.  When you say "Type cscript //H:Cscript. This will make cscript the default so that to run a vbscript all you need to type is the yourScript.vbs at the prompt without the cscript preface.".  Default of what?  Since I have no VB background I want to make sure setting this as a default does not break any existing processes.

    Thanks,    Dave


  • Good article!  You can extend this concept to store the extracted data in a Dba database and then use scheduled report server reports.  I have used this concept to email weekly report server reports on overall hard drive space and individual database stats as described in this article.

  • I moved that script into Excel, It Work like a charm!!


  • Works perfectly for smaller databases but the variables don't seem to hold GB sized files.  What is the syntax for defining a larger variable type instead of just the default?  The culprit is this line:

    strFileMB = objFile.FileSize / CONVERSION_FACTOR

    When objFile.FileSize is too big this displays blank for sime reason.  Commenting out the division part and just trying to print objFile.FileSize is also a blank so I suspect the problem is there.  How is that built in var defined and how can it be made to handle a large file size?

  • Dave,

    cscript //H:Cscript will make cscript the default script engine. Windows Script Host (WSH) is the program that runs scripts (VB scripts or javascripts) on Windows operating systems. WSH has two script engines. The default is the wscript engine and the alternate is the cscript engine. The main difference is that the wscript engine will send all of the text from a VB script WScript.Echo command to a dialog box that must be acknowledged by pressing an "OK" button while the cscript engine sends this text to the standard command line output in a cmd window (a.k.a DOS window). Setting the default engine to cscript will allow this VBScript to run without any user input.

  • Nice easy to follow article.

    I wonder if it would be possible (as I have no vb/coding experience either so going a little blind here), to monitor different instances and servers through the same page?

  • Great article. I look forward to the next in the series.

    I did have one problem. I tried the post-script code for adding the date and time to the filename, and got a Windows Script Host error.

    Line: 10

    Char: 1

    Error: 'Invalid procedure call or argument: 'DatePart'

    Code: 800A0005

    Source Microsoft VBScript runtime error


    I am running WSH v 5.6, so i am not sure what is causing the error.



    If it ain't broke, don't fix it...

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply