SQLPSX v2 – PowerShell for SQL Server has been PowerShell 2’ed - Greg's Cool [Insert Clever Name] of the Day

Monday, January 04, 2010

SQLPSX v2 – PowerShell for SQL Server has been PowerShell 2’ed

CodePlex - SQL Server PowerShell Extensions

“…

The primary goal of SQL Server PowerShell Extensions (SQLPSX) is to provide intuitive functions around the SMO objects which are backward compatible with SQL 2000. A secondary goal is to provide an application which reports flatten/effective security settings for logins, users, roles, and permissions.

Installation

SQLPSX consists of a library file of PowerShell functions and several PowerShell scripts, if you've downloaded the files through Internet Explorer you'll need to unblock all Powershell files after downloading by right-clicking each PowerShell file in Windows Explorer and clicking the Unblock button. Using SQLPSX requires you've installed the SMO libraries which are included with SQL Server Management Studio.

News

See the two-part article series on SQLServerCentral describing installation and usage of SQLPSX:
SQLPSX Part1
SQLPSX Part2

…”

SQL Server PowerShell Extensions - 2.0 Production

“Released: Dec 31 2009

Updated: Dec 31 2009 by cmille19

Dev status: Stable

…

SQLPSX_2.0.zip
source code, 1268K, uploaded Dec 31 2009 …

Other Available Downloads

readme.txt
documentation, 23K, uploaded Dec 31 2009 …

screenshots_SQLPSX.docx
documentation, 1315K, uploaded Dec 31 2009 …

Release Notes

Release 2.0 re-implements SQLPSX as PowersShell version 2.0 modules. SQLPSX consists of 7 modules with 132 advanced functions, 2 cmdlets and 7 scripts for working with ADO.NET, SMO, Agent, RMO, SSIS and SQL script files. In addition an optional component of a backend database and SQL Server Reporting Services 2008 reports are provided. See readme file for details.

…”

From the readme.txt;

“…

What's New
    Version 2.0
        Converted function libraries and snapins to modules
        Created comment-based help for all functions
        Made helper functions private through use of module manifests (psd1 files)
        Converted functions to advanced functions with parameter bindings
        Refactored code to use Powershell V2 features:
            try/catch
            valuefrompipeline
            validatescript
            validateset
            new-object -property hashtable
            add-type
        Renamed Set-SqlScriptingOptions to New-SqlScriptingOptions
        Renamed Get-ReplScriptOptions to New-ReplScriptOptions
        Removed scriptopts and replscriptopts text files in favor of script option objects
        Moved Get-InvalidLogins.ps1 and Get-SessionTimeStamp.ps1 into SQLServer module
        Removed Init-SqlParser.ps1 script (not needed since SQLParser is now a module)
        Added new ADO.NET module
        Added format file for SSIS packages
        More rigorous testing was performed using PSUnit testing framework
        Fixed issues discovered in testing
        Added 5 aliases for Information_Schema and sysdatabases functions. These functions were renamed with a Get-Sql* prefix
        All parameters are strongly typed where possible

…”