I think you already know my answer--Yes PowerShell has been neglected in SQL Server 2008 R2 with almost no changes and we can only hope we see changes in Denali....

No problem, glad its working for you.

The scripts have several write-verbose statements which you can thing of as PRINT statements only that you need to "turn them on" in PowerShell. Here's how you would do that:

Open...

They still exist, but the company has gone through some turmoil: first Precise was acquired by Veritas, then Symantec acquired Veritas. Symantec divested the Precise product line and now the...

The solution relies on SQL-DMO and Excel. SQL-DMO is deprecated class for managing SQL Server. SQL-DMO is install with SQL Server 2000, but not with SQL Server 2005 or higher....

Keep in mind Red Gate has a wonderful tool, Sql Compare and if you have the professional edition it comes with a command-line utility, sqlcompare.exe (I'm not sure why you...

The capacity report/query calculates an average growth rate over a given period, so in order for the query to return results you must have at least two days of collected...

PowerShell. There are two applications I have open all day--SSMS and PowerShell.

You shouldn't paste the Powershell script in the command windows. Instead for SQL 2008 setup a job with a Powershell command step and only have the path to the script...

This is an older article I wrote. The underlying code relies on SQL-DMO which is installed with SQL Server 2000 Client Tools. I suspect you may not have SQL-DMO installed...

Although I don't see anything wrong with this line. The error message pertains to it, so change this:

$da.fill($dt) > $null

to this

[void]$da.fill($dt)

Interesting article, you've obviously put some thought into how to architect a robust logging environment. I wish someone had done the same in my environment, instead hundreds of programs use...

bartusp (11/20/2009)

When executing the powershell script for Write-DbSpaceToDb.ps1 i get the following error :

PS SQLSERVER:\SQL\JHB-BARTUSD\DEFAULT> param($destServer, $destdb)

The term 'param' is not recognized as a cmdlet, function, operable program, or

script file....

Win32_Volume class isn't available on XP. It is on Server 2003 and Vista and above. Change the vol script o use Win32_LogicalDisk instead.

I don't see anything in the code where system databases are excluded. I would suggest running this query on the instances where the system databases are not reporting as successfully...