Professional SQL Server® 2008 Administration with Windows PowerShell™

Published by

Wiley Publishing, Inc.

10475 Crosspoint Boulevard

Indianapolis, IN 46256

www.wiley.com

Copyright © 2009 by Wiley Publishing, Inc., Indianapolis, Indiana

Published by Wiley Publishing, Inc., Indianapolis, Indiana

Published simultaneously in Canada

ISBN: 978-0-470-47728-1

Library of Congress Cataloging-in-Publication Data

Ananthakumar Muthusamy, 1974-

Microsoft SQL server 2008 administration with Windows Powershell / Ananthakumar Muthusamy, Yan Pan.

p. cm.

Includes index.

ISBN 978-0-470-47728-1 (paper/website)

1. SQL server. 2. Windows PowerShell (Computer program language) I. Pan, Yan, 1976- II. Title.

QA76.73.W56K96 2009

005.2'82--dc22

2009013304

No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at www.wiley.com/go/permissions.

Limit of Liability/Disclaimer of Warranty: The publisher and the author make no representations or warranties with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose. No warranty may be created or extended by sales or promotional materials. The advice and strategies contained herein may not be suitable for every situation. This work is sold with the understanding that the publisher is not engaged in rendering legal, accounting, or other professional services. If professional assistance is required, the services of a competent professional person should be sought. Neither the publisher nor the author shall be liable for damages arising herefrom. The fact that an organization or Web site is referred to in this work as a citation and/or a potential source of further information does not mean that the author or the publisher endorses the information the organization or Web site may provide or recommendations it may make. Further, readers should be aware that Internet Web sites listed in this work may have changed or disappeared between when this work was written and when it is read.

For general information on our other products and services please contact our Customer Care Department within the United States at (877) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.

Trademarks: Wiley, the Wiley logo, Wrox, the Wrox logo, Wrox Programmer to Programmer, and related trade dress are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates, in the United States and other countries, and may not be used without written permission. SQL Server and Windows PowerShell are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are the property of their respective owners. Wiley Publishing, Inc., is not associated with any product or vendor mentioned in this book.

Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books.

About the Authors

Ananthakumar Muthusamy, aka MAK (MCTS, MCITP: Database Administrator 2008), is currently the Senior SQL Server Database Engineer for a leading global financial services firm on Wall Street. He has published many online articles as a contributing columnist for DatabaseJournal.com. He also published online articles for SQL-Server-Performance.com and SQLServercentral.com. His articles can be found at www.mssqlengineering.com. He also teaches SQL Server Database Administration online at the University of West Florida.

MAK has been working in information technology for more than 10 years. He has worked in the technology side of the finance, dot com, B2B, and software industries. His past clients include Fort James, Boston Financial, PCConnection, PurchaseSoft, Merrill Lynch, and Jefferies. MAK holds an M.B.A. degree and various certifications in the computer field.

He also teaches Microsoft SQL Server and has taught many SQL Server developers and DBAs. He has master's degree in Business Administration.

MAK lives in New Jersey. He can be reached at mak_999@yahoo.com.

Yan Pan (MCITP, MCDBA, OCA) is a Senior DBA for a leading global financial services firm, where her daily duties include administering hundreds of SQL Server and Oracle servers of every possible version, working with business units, and troubleshooting database performance problems. She is also a contributing columnist for DatabaseJournal.com. Her articles can be found at www.yanpansql.com.

Previously, Yan worked as a SQL Server DBA and a .NET developer at Data Based Ads, Inc., and developed two .NET Web applications. Before that, she worked at AT&T Research Labs. She designed OLAP cubes with SQL Server Analysis Services and developed PivotTable reports for regional managers. She has master's degrees in Computer Science and Physics.

Yan lives in Chicago, IL. She can be reached at yanpansql@yahoo.com.

Credits

Executive Editor

Robert Elliott

Development Editor

Rosanne Koneval

Technical Editor

Haidong Ji

Production Editor

Daniel Scribner

Copy Editor

Luann Rouff

Editorial Manager

Mary Beth Wakefield

Production Manager

Tim Tate

Vice President and Executive Group Publisher

Richard Swadley

Vice President and Executive Publisher

Barry Pruett

Associate Publisher

Jim Minatel

Project Coordinator, Cover

Lynsey Stanford

Proofreader

Jen Larsen, Word One

Indexer

Robert Swanson

Acknowledgments

First of all, I would like to thank my fiancée, Claire Hsu. Without her moral support, this book would not have been possible. I would like to thank my mom, Jayalakshmi Muthusamy, for bringing me into this world. I still admire her for not losing her patience and always keeping her sense of humor. I would like to thank my dad, Muthusamy Srinivasan, for being a friend and a teacher. I want to take this opportunity to thank both my parents for all the compromises they made to raise both my sister and me. I would also like to thank my sister, Anuradha, for supporting me and taking care of me.

I would like to thank my co-author, Yan Pan, especially for being both very patient when needed and pushing me when necessary. She is a very good friend and colleague. She could always get me back on track when I was distracted with other projects.

I would also like to thank all my friends, current and past colleagues, and relatives for their constant inspiration.

I am very grateful to all the readers and fans of my online articles from various parts of the world. Without their support, comments, motivation, and critiques, this book wouldn't have shaped up so well.

Yan and I are both grateful to Haidong Ji, aka Alex, for introducing us to Wrox-Wiley and being our knowledgeable technical editor. We also want to thank Bob Elliot for bringing our book proposal to the executive team and making it happen.

Last but not least, we would like to thank Rosanne Koneval and Daniel Scribner. Your questioning at the right place, proper decision-making, and quick turnaround made this book much neater and clearer.

It is hoped that I haven't forgotten anyone, but if I have, it was an oversight. Honest.

—MAK

First and foremost, I would like to thank my beloved husband, Yue Guo. You have always supported and encouraged me in everything I have ever done. Thank you for your incredible patience throughout the writing of this book. I would also like to thank my parents for all they have done for me to give me the best life they could possibly give.

I would like to express my sincere appreciation to MAK for introducing me to technical writing and sharing the book idea with me. Your optimism, enthusiasm, and humor have made the book-writing journey a wonderful experience.

I am also deeply indebted to Haidong (Alex) Ji. Haidong, thank you for introducing us to Wrox. Thank you for your suggestions, guidance, and encouragement throughout the course of this book. Your technical input and attention to detail helped us improve the quality of this book greatly.

I would also like to thank Bob Elliot, Rosanne Koneval and Daniel Scribner at Wrox. Bob, thank you for believing in us. We started this project with plenty of enthusiasm and passion for new technology, but not a book contract. Thank you for making our dream come true and allowing our vision of a Windows PowerShell–powered SQL Server enterprise infrastructure to reach thousands of readers, and hopefully making their lives easier. Rosanne, thank you for your incredible patience in cleaning up the words and polishing everything up to get this book ready for the printer. Daniel, thank you for giving a final touch to this book.

Finally, I'd like to thank you, my readers, for reading what I have written! Without your support and feedback, I could not have accomplished so much.

—Yan

Introduction

Welcome to SQL Server 2008 Administration with Windows PowerShell. This book is a nuts-and-bolts guide to creating Windows PowerShell scripts that can be used to administer every aspect of the SQL Server 2008 Database Engine. Using a very hands-on approach, this book guides you through the basics of Windows PowerShell, the available Windows PowerShell components that have been integrated into SQL Server 2008, and the actual administration tasks. By providing clear, well-structured examples, SQL Server 2008 Administration with Windows PowerShell shows you how to construct effective and practical solutions that can improve SQL Server administration and monitoring at your company.

SQL Server 2008 delivers a dynamic, smart, and productive data platform for all your data-related needs. SQL Server 2008 offers secure, reliable, and consistent performance. It is also very scalable and flexible, handling any form of data. It is well known in the technology world that SQL Server 2008 is not only a RDBMS, but also has built-in features such as Integration Services for ETL, Analysis Services for Business Intelligence, Reporting Services for report management, and more. This is why Microsoft SQL Server is a cut above all other database products.

Windows PowerShell 2.0 is the new extensible command-line interface shell and scripting language that provides an environment for interactive scripting and non-interactive scripted administration of local and remote computers. Because Windows PowerShell integrates with the Microsoft .NET Framework, we can take advantage of all the features of .NET as well. Windows PowerShell 2.0 helps system administrators to automate and manage various aspects of the Windows environment. PowerShell 2.0 also has many new and useful features such as remoting, eventing, and many more. For these reasons, Windows PowerShell 2.0 stands above all the system administration products on the market.

This book brings together the best of both worlds—namely, the database world and the administration world—to help you manage, automate, and control your environment. This book combines three technologies—SQL Server 2008, the .NET Framework, and Windows PowerShell 2.0—and guides SQL Server database administrators in managing a server plant using Windows PowerShell 2.0.

We've provided a wide range of material in a tutorial-based book to get you over the learning curve of Windows PowerShell 2.0 and SQL Server 2008 database administration.

Who This Book Is For

Whether you are a SQL Server database administrator, a developer, or a systems administrator, at some point you probably have had to develop or administer the system or the database in your organization. It is also common for the people in these roles to wear each other's hats in order to get things done.

If you are a Microsoft SQL Server database administrator, you know that you cannot manage and access all the system resources from SQL Server. Because SQL Server runs on top of the Windows operating system and relies on the health of the system, you need information from the system side as well. This book will teach you to manage both SQL Server and system resources using Windows PowerShell 2.0.

If you are a systems administrator and would like to know more about SQL Server database administration, this book introduces you to the features in SQL Server 2008 and provides plenty of examples demonstrating how to manage SQL Server 2008 using Windows PowerShell 2.0.

This book is also appropriate for those who have some exposure to systems administration and SQL Server administration, or for those who want to expand their skill set to include administration.

What This Book Covers

This book covers the fundamentals of Windows PowerShell 2.0 cmdlets. It includes programming, scripting, debugging, and error handling in PowerShell. It covers all Windows administration related to SQL Server 2008 using Windows PowerShell 2.0.

It also introduces Windows Management Instrumentation (WMI) and explains how to write WMI scripts in Windows PowerShell to perform system and SQL Server 2008 administrative tasks.

This book also covers the WMI providers for SQL Server. These useful providers enable you to manage SQL Server services and network connectivity, and proactively monitor SQL Server events. You will also discover the new Eventing feature in Windows PowerShell 2.0.

Additionally, the new SQL Server 2008 support for Windows PowerShell is presented. It illustrates the SQL Server PowerShell provider and SQLSERVER: drive. You will also learn how to manage SQL Server objects, including the new policy objects.

One more important topic this book covers is using SQL Server Management Objects (SMO) to create databases and tables and perform backups and restores. The SMO scripts shown in this book are all written in Windows PowerShell 2.0.

This book also explains the need for SQL Server standards; and you will learn how to build a SQL Server inventory over an existing or new environment.

Finally, you will learn how to perform the various SQL Server administrative tasks on servers in the inventory, such as installation, monitoring, performance data collection, policy definition, backups, restores, database scripting, and more, using Windows PowerShell 2.0.

How This Book Is Structured

Windows PowerShell 2.0 is introduced in the first eight chapters. If you do not have any background in Windows PowerShell 2.0, these chapters are critical. They help you understand the basics of writing Windows PowerShell 2.0 scripts, and you will learn how to use the scripts to administer the overall operating system.

Chapter 1 covers installation of prerequisites, and installation and configuration of Windows PowerShell 2.0.

Chapters 2, 3, and 4 cover the various cmdlets available in Windows PowerShell, and the various programming features such as inputs, outputs, debugging, error handling, functions, profiles, and so on.

Chapters 5, 6, 7, and 8 cover the various systems administration features, including accessing file systems, registry information, variables, and Event logs. It also explains the Windows Management Instrumentation (WMI) model and shows you how to use WMI to manage system resources.

Chapters 9 and 10 show you how to access the WMI providers for SQL Server. You will learn how to use the WMI Provider for Configuration Management to manage SQL Server services and network connectivity, and the WMI Provider for Server Events to manage SQL Server events. You will also discover the new Eventing feature in Windows PowerShell 2.0.

Chapters 11 and 12 take on the Windows PowerShell support that has been integrated into SQL Server 2008, namely, the SQLSERVER: drive. These two chapters will focus on the SQL and SQLPolicy folders separately.

Chapter 13 shows you how to write SQL Server Management Objects (SMO) programs in Windows PowerShell 2.0. This chapter covers various tasks such as creating a database and database objects, and backing up and restoring a database.

Chapters 14 and 15 provide you with ample examples of building a SQL Server tasks inventory over an existing or new environment, and how to define various standards. Standards include both SQL Server standards and Windows PowerShell standards.

The remaining chapters explain installation, data collection, monitoring, and how to create Windows PowerShell scripts to handle a wide range of SQL Server administrative tasks for servers in the inventory.

Chapter 16 illustrates the installation of SQL Server 2008. Chapter 17 covers tasks related to collecting SQL Server host and server performance data. Chapters 18 and 19 cover monitoring aspects of SQL Server 2008 administration. Chapter 20 defines policies to enforce SQL Server standards, and Chapter 21 generates various scripts at both the database level and the database object level.

What You Need to Use This Book

This book covers SQL Server 2008 administration with Windows PowerShell 2.0. In order to use this book, you need both a server-side component and client-side components:

For the server-side component, you need SQL Server 2008 Developer or Enterprise or Standard edition.

For client-side components, you need Windows PowerShell 2.0 CTP3. To install Windows PowerShell 2.0 CTP3, the operating system of your computer needs to be either Windows XP Service Pack 3, Windows 2003 Service Pack 2, Windows Vista Service Pack 1, or Windows Server 2008. You also need to pre-install the following components on your computer:

Microsoft .NET Framework 2.0 or greater

Windows Remote Management 2.0 CTP3 for Windows PowerShell remoting and background jobs

We discuss the prerequisites of Windows PowerShell 2.0 in Chapter 1 in detail.

All the scripts and codes in the book have been tested on SQL Server 2008 with .NET Framework 3.5 and Windows PowerShell 2.0 CTP3. We tested all the scripts on Windows XP, Windows Server 2008, and Windows Vista. Most of the scripts and code illustrated here work under Windows PowerShell 1.0 as well, although you may notice that the output of such scripts and codes differs slightly, and that remoting under Windows PowerShell 1.0 is not possible unless you use WMI objects.

In order to install Windows PowerShell 2.0 and Windows Remote Management, and to store all the scripts provided in the book, you need a minimum of 100MB of hard disk space.

Conventions

To help you get the most from the text and keep track of what's happening, we've used a number of conventions throughout the book.

Notes, tips, hints, tricks, and asides to the current discussion are offset and placed in italics like this.

As for styles in the text:

We highlight new terms and important words when we introduce them.

We show filenames, URLs, and code within the text like so: persistence.properties.

We present code like this:

We use a monofont type with no highlighting for most code examples.

Source Code

As you work through the examples in this book, you may choose either to type in all the code manually or to use the source code files that accompany the book. All of the source code used in this book is available for download at www.wrox.com. Once at the site, simply locate the book's title (either by using the Search box or by using one of the title lists) and click the Download Code link on the book's detail page to obtain all the source code for the book.

Because many books have similar titles, you may find it easiest to search by ISBN; this book's ISBN is 978-0-470-47728-1.

Once you download the code, just decompress it with your favorite compression tool. Alternately, you can go to the main Wrox code download page at www.wrox.com/dynamic/books/download.aspx to see the code available for this book and all other Wrox books.

Errata

We make every effort to ensure that there are no errors in the text or in the code. However, no one is perfect, and mistakes do occur. If you find an error in one of our books, such as a spelling mistake or a faulty piece of code, we would be very grateful for your feedback. By sending in errata, you may save another reader hours of frustration, and at the same time you will be helping us provide even higher quality information.

To find the errata page for this book, go to www.wrox.com and locate the title using the Search box or one of the title lists. Then, on the book details page, click the Book Errata link. On this page you can view all errata submitted for this book and posted by Wrox editors. A complete book list, including links to each book's errata, is also available at www.wrox.com/misc-pages/booklist.shtml.

If you don't spot “your” error on the Book Errata page, go to www.wrox.com/contact/techsupport.shtml and complete the form there to send us the error you have found. We'll check the information and, if appropriate, post a message to the book's errata page and fix the problem in subsequent editions of the book.

p2p.wrox.com

For author and peer discussion, join the P2P forums at p2p.wrox.com. The forums are a Web-based system for you to post messages relating to Wrox books and related technologies and interact with other readers and technology users. The forums offer a subscription feature to e-mail you topics of interest of your choosing when new posts are made to the forums. Wrox authors, editors, other industry experts, and your fellow readers are present on these forums.

At http://p2p.wrox.com you will find a number of different forums that will help you not only as you read this book, but also as you develop your own applications. To join the forums, just follow these steps:

1. Go to p2p.wrox.com and click the Register link.

2. Read the terms of use and click Agree.

3. Enter the required information to join as well as any optional information you wish to provide and click Submit.

4. You will receive an e-mail with information describing how to verify your account and complete the joining process.

You can read messages in the forums without joining P2P but in order to post your own messages, you must join.

Once you join, you can post new messages and respond to messages other users post. You can read messages at any time on the Web. If you would like to have new messages from a particular forum e-mailed to you, click the Subscribe to this Forum icon by the forum name in the forum listing.

For more information about how to use the Wrox P2P, be sure to read the P2P FAQs for answers to questions about how the forum software works, as well as many common questions specific to P2P and Wrox books. To read the FAQs, click the FAQ link on any P2P page.

Chapter 1

What is Windows PowerShell?

Windows PowerShell is the extensible command-line interface shell and scripting language that provides a command-line environment for interactive exploration and administration of computers. In addition, it provides developers with an opportunity to script these commands, enabling them to be automated, scheduled, and run multiple times.

This chapter covers the following topics:

A brief overview of command-line interfaces

Prerequisites for installing PowerShell

Installing PowerShell 2.0 CTP3.

Command-Line Interfaces versus Graphical User Interfaces

Before UNIX, Linux, and Windows surfaced in the information technology market, input media such as punched card and punched tape were used. All the input and instructions to the computer used command lines.

When UNIX and Linux were released, administrators started managing the operating system using command-line interfaces, which were also used by the day-to-day users and programmers to interact with the operating system.

UNIX and Linux are built on command-line interfaces, so there has always been administrative scripting and different shells, such as the Korn shell, the C shell, and the Bourne shell. Programming languages such as TCL and PERL were immediately available.

Originally, when Microsoft released MS-DOS, it was not used as a shell. It was entirely a standalone operating system. The initial and original Microsoft Windows release was a graphical shell that sat on top of the MS-DOS operating system. Once Windows NT was introduced, this situation was reversed. MS-DOS became the shell in the graphical Windows operating system.

Graphical user interfaces (GUIs) were basically developed for users with less technical background who were looking for a friendly interface. Because graphical interfaces are limited to fewer functions, once you hit their limitations you will start relying on the command-line interface. For example, with a GUI, if you want to rename all the extensions of a group of files and suffix each file with the current day's timestamp, it will take a while because you have to select and rename each file individually.

Therefore, command-line interfaces and their commands are very commonly used for administrative tasks and automation. They also help to consolidate functionality in batches, through MS-DOS batch files.

command.com was used as the command-line user interface in early versions of Microsoft Windows. cmd.exe was introduced in Windows NT.

When administrators reached the limit of command-line batch files, they started looking for a language that could do both command shell functions and programming. Microsoft introduced the Visual Basic scripting language, which helped administrators initially. However, there were limitations in VBScript as well. Administrators started relying on Windows Management Instrumentation (WMI) and COM objects introduced later by Microsoft for many other administrative functions.

The administrative command-line interface started becoming more complicated with internal DOS commands, external DOS commands, batch files, executables, VBScripts, WMI, and so forth.

It was with all of this in mind that Microsoft developed and introduced Windows PowerShell.

Prerequisites for Installing Windows PowerShell 2.0

Windows PowerShell can be installed and run on Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008. Although Windows PowerShell is included as part of Windows Server 2008, it is not installed by default on Windows XP, Windows 2003, or Windows Vista. At the time of writing, Windows PowerShell 1.0 is visible as a feature in Windows Server 2008 that can be turned on.

Windows PowerShell 1.0 is also installed with Exchange Server 2007, System Center Operations Manager 2007, System Center Data Protection Manager V2, and System Center Virtual Machine Manager because they leverage Windows PowerShell to improve administrator control, efficiency, and productivity.

This book uses Windows PowerShell 2.0 CTP3. Before installing Windows PowerShell 2.0 CTP3, you should ensure that your system has the following software programs it requires:

Windows XP Service Pack 3, Windows 2003 Service Pack 2, Windows Vista Service Pack 1, or Windows Server 2008

Microsoft .NET Framework 2.0 or greater

Windows Remote Management 2.0 CTP3 for Windows PowerShell remoting and background jobs

Microsoft .NET Framework 3.5 Service Pack 1 for Windows PowerShell Integrated Scripting Environment (ISE) and the Out-GridView cmdlet

If .NET Framework 2.0 is not installed on your computer, the error message shown in Figure 1.1 will pop up when you try to install Windows PowerShell 2.0 CTP3.

Figure 1.1

After installing the .NET Framework, if you continue to install on a non-standard operating system such as Windows Server 2000, Windows NT, and so on, you may get the error shown in Figure 1.2.

Figure 1.2

Although Figure 1.2 shows v1.0 in the title bar and file path, it is actually PowerShell 2.0 CTP3. Community Technology Preview, also known as CTP3, is basically the bug fix that Microsoft relies on, adding new features based on feedback from the technology community. The folder may be changed to v2.0 once the release to manufacturing (RTM) version is released.

In order to check the prerequisites for the PowerShell installation, we created a batch file to run all the necessary checks. Listing 1-1 shows the MS-DOS batch script, CheckPowershellPreqs.bat, which uses Windows Management Instrumentation Command-line (WMIC) to check the requirements before you install Windows PowerShell. WMIC enables you to access WMI information via the command line. In some respects, you can think of WMIC as an early prototype of PowerShell. However, WMIC can only output its results as text. It doesn't return programming objects that can be further processed, as Window PowerShell does, and as you will see later.

Listing 1.1: CheckPowershellPreqs.bat

@ECHO Off

REM *****************************************************************

REM *Objective: TO check if the current windows version is          *

REM *           Compatible for PowerShell 2.0 and its pre-requisites*

REM *Created by: Yan and MAK                                        *

REM *Created Date: 2008/09/01                                       *

REM *                                                               *

REM *****************************************************************

SET OS_VERSION=

SET Service_Pack=

REM Find OS version

FOR /F “delims== tokens=2” %%i IN (‘wmic os get Version /value’)

   DO SET OS_VERSION=%%i

IF NOT DEFINED OS_VERSION (

    ECHO WMIC is not installed on this system.

    GOTO :END_SCRIPT

)

REM Find service pack value

FOR /F “delims== tokens=2” %%i IN (‘wmic os get ServicePackMajorVersion /value’)

   DO SET Service_Pack=%%i

REM Windows XP

IF “%OS_VERSION%”==“5.1.2600” (

    @IF “%Service_Pack%” LSS “3” (

       ECHO %OS_NAME% Service Pack 3 is required

       GOTO :END_SCRIPT

    )

    GOTO :DOTNETFRAMEWORK_CHECK

)

REM Windows Server 2003

IF “%OS_VERSION%”==“5.2.3790” (

    @IF “%Service_Pack%” LSS “2” (

       ECHO %OS_NAME% Service Pack 2 is required

       GOTO :END_SCRIPT

    )

    GOTO :DOTNETFRAMEWORK_CHECK

)

REM Windows Vista

IF “%OS_VERSION%”==“6.0.6001” (

    @IF “%Service_Pack%” LSS “1” (

       ECHO %OS_NAME% Service Pack 1 is required

       GOTO :END_SCRIPT

    )

    GOTO :DOTNETFRAMEWORK_CHECK

)

IF “%OS_VERSION%” GTR “5.2.3790” (

    GOTO :DOTNETFRAMEWORK_CHECK

)

ELSE (

    GOTO :END_SCRIPT

)

REM Check .NET framework

:DOTNETFRAMEWORK_CHECK

wmic product where (caption like “Microsoft .NET Framework%%”) get Version /value |

   findstr “=[2-9]\.*” > nul

IF “%ERRORLEVEL%”==“1” (

    ECHO .NET Framework 2.0 or greater is required

    GOTO :END_SCRIPT

)

REM Check Windows remote management

:WINRMCHECK

wmic path Win32_service where caption=“Windows Remote Management (WS-Management)” |

   findstr /i “(WS-Management)” > nul

IF “%ERRORLEVEL%”==1 (

    ECHO Windows Remote Management is required

    GOTO :END_SCRIPT

)

ECHO Your system meets the requirements

:END_SCRIPT

From a Windows command console, run CheckPowershellPreqs.bat from the script directory C:\DBAScripts. You should get a message similar to the one shown in Figure 1.3 if your system meets the requirements for a PowerShell installation.

Figure 1.3

You may run into an error as follows on Windows Server 2003:

ERROR:

Code = 0x80041010

Description = Invalid class

Facility = WMI

This means that you need to install the WMI Windows Installer Provider in order for WMIC to work. To do so, open Control Panel ⇒ Add/Remove Programs. Select Add/Remove Windows Components. Double-click Management and Monitoring Tools. Select WMI Windows Installer Provider, and then click OK to install.

If your operating system is Windows XP Service Pack 2 and you install Windows PowerShell 2.0 CTP3, it may or may not work. The officially supported service pack for Windows XP when installing Windows PowerShell 2.0 CPT3 is Service Pack 3, so when executing C:\DBAScripts\CheckPowershellPreqs.bat it will complain that Service Pack 3 is required.

Installing the Microsoft .NET Framework

Windows PowerShell integrates with the .NET Framework and provides a shell environment to perform administrative tasks. PowerShell exposes the .NET classes as built-in commands, and when these commands are executed they produce one or more structured objects as output.

Download the .NET Framework from http://download.microsoft.com and install .NET Framework 2 or later. It is recommended that you use .NET 3.5, although all the code in this book works on .NET Framework 2 and later. In Chapter 11, you will see that an SQL Server 2008 installation installs .NET 3.5 by default.

Installing Windows Remote Management

Another prerequisite is to install Windows Remote Management (WinRM). WinRM is required for Windows PowerShell remoting and background jobs. You can download WinRM 2.0 CTP3 (also known as Ws-Management) from https://connect.microsoft.com/WSMAN/Downloads for Windows Vista and Windows Server 2008. The installation procedures of the executable Windows6.0-KB950099-x86.msu for 32-bit and Windows6.0-KB950099-x64.msu for 64-bit are shown in Figure 1.4 and Figure 1.5.

Double-click on Windows6.0-KB950099-x86.msu if you are installing WinRM on a 32-bit Windows operating system. Double-click on Windows6.0-KB950099-x64.msu if you are installing it on a 64-bit Windows operating system.

Figure 1.4

Figure 1.5

If you already have Windows PowerShell 1.0 installed on your machine, then you have to uninstall PowerShell 1.0 first and then install PowerShell 2.0 CTP3.

To uninstall Windows PowerShell 1.0, follow these steps:

1. Click Start → Run, type appwiz.cpl, and then click OK.

2. Select the Show Updates check box (on the top in the middle).

3. In the list of currently installed programs, click Windows PowerShell(TM) 1.0, and then click Remove. If you don't see Windows PowerShell(TM) 1.0, please look for Windows Hotfix 926139, 926140, or 926141.

4. Follow the instructions to remove Windows PowerShell(TM) 1.0.

If you already have Windows PowerShell 2.0 CTP1 or CTP2, you have to uninstall them also. They appear as “Windows PowerShell V2 (TM)” in the program list.

In Windows 2008, Windows PowerShell 1.0 is made visible as a Windows feature. You can disable and uninstall the PowerShell feature as described here:

1. Click Start at the Windows taskbar.

2. Click Server Manager ⇒ Features ⇒ Add Feature, and uncheck the Windows PowerShell check box.

3. Click Next to uninstall.

Now that you have the acceptable operating system, the .NET Framework, and Windows Remote Management, the next section provides the steps needed to actually install Windows PowerShell 2.0 CTP3.

Installing Windows PowerShell

To install Windows PowerShell on Windows XP or Windows 2003 systems, do the following:

1. Download the Windows PowerShell 2.0 CTP3 installation file from www.Microsoft.com/downloads. The name of the installation file varies according to platform, operating system, and language pack. Choose the appropriate version for your operating system. If you have a 64-bit Windows operating system, then please download PowerShell_Setup_amd64.msi, as shown in Figure 1.6. If you have a 32-bit Windows operating system, then please download PowerShell_Setup_x86.msi, as shown in Figure 1.7.

Figure 1.6

Figure 1.7

2. After downloading the appropriate version for your operating system, you will see the initial screen of the installation wizard, similar to the one shown in Figure 1.8. Click Next.

Figure 1.8

3. Accept the license agreement, as shown in Figure 1.9, and click Next.

Figure 1.9

4. It takes a few minutes to complete the install. As shown in Figure 1.10, click Install to begin the installation process. You will see the progress of the installation, as shown in Figure 1.11.

Figure 1.10

Figure 1.11

5. When installation is completed successfully, you will see a screen similar to the one shown in Figure 1.12. Click Finish.

On 32-bit versions of Windows, Windows PowerShell is installed by default in the %SystemRoot%\System32\WindowsPowerShell\v1.0 directory.

On 64-bit versions of Windows, a 32-bit version of Windows PowerShell is installed in the %SystemRoot%\SystemWow64\WindowsPowerShell\v1.0 directory and a 64-bit version of Windows PowerShell is installed in the %SystemRoot%\System32\WindowsPowerShell\v1.0 directory.

Figure 1.12

This book covers Windows PowerShell 2.0 CTP3. The installation file replaces the executables in the v1.0 folder. The actual folders for Windows PowerShell may change to v2.0 when PowerShell 2.0 RTM is released.

Launching Windows PowerShell

Windows PowerShell can be launched in several ways. This section describes the different methods. No method is superior to the others. It is just a matter of preference.

Using the Command console

To launch Windows PowerShell using the command console, open the command console and then type powershell, as shown in Figure 1.13.

Figure 1.13

Using All Programs

You can also click Start ⇒ All Programs ⇒ Windows PowerShell V2 (CTP3), and then select and click Windows PowerShell V2 (CTP3), as shown in Figure 1.14.

Figure 1.14

You may also see Windows PowerShell ISE (CTP3) in the Windows Program menu. The Windows PowerShell Integrated Scripting Environment (ISE) is a host application for Windows PowerShell. In Windows PowerShell ISE, you can run commands and write, test, and debug scripts in a single Windows graphical user interface. This book illustrates all Windows PowerShell-related cmdlets and scripts using a command-line interface. It does not illustrate PowerShell scripts using the ISE.

Once PowerShell is launched, you can see the command prompt. The prompt in the PowerShell command window varies according to the operating system used.

To be consistent with the PowerShell window title, you could update the shortcut, as illustrated in Figure 1.15. Right-click on the Windows PowerShell V2 (CTP3) shortcut, click Properties, and under the General tab, update the title to “Windows PowerShell” and click OK.

Figure 1.15

Using Start Run

You can also launch PowerShell by clicking Start ⇒ Run and typing the following: %systemroot%\system32\windowsPowerShell\v1.0\PowerShell.exe. Then click OK, as shown in Figure 1.16.

Figure 1.16

Alternatively, you can also launch PowerShell by clicking Start ⇒ Run and typing PowerShell.

Windows finds the PowerShell.exe executable from the environment PATH variable and then launches it.

This opens the PowerShell command console, shown in Figure 1.17.

Figure 1.17

If you are using 64-bit PowerShell, then you can launch PowerShell by clicking Start ⇒ Run and typing the following: %systemroot%\SysWOW64\WindowsPowerShell\v1.0\PowerShell.exe. Then click OK, as shown in Figure 1.18.

Figure 1.18

This opens the PowerShell command console, as shown in Figure 1.19.

Figure 1.19

Summary

This chapter discussed the prerequisites for Windows PowerShell, described how to install Windows PowerShell 2.0 CTP3, and showed various methods to launch PowerShell.

The next chapter covers the various command types and commonly used cmdlets that appear throughout the book. A Windows PowerShell cmdlet is a simple command used for interaction with any managed application, including the Windows operating system and applications such as SQL Server, Microsoft Exchange, and so on.

Chapter 2

Windows PowerShell Command Types, Snap-ins, and cmdlets

Now that you've installed Windows PowerShell on your computer, I bet you can't wait to start running your own commands to unravel the power of Microsoft's new command shell. This chapter introduces you to the new PowerShell commands, or cmdlets. It also introduces you to the collections of cmdlets called snap-ins. By following all of the examples in this book, you will become comfortable working with the cmdlets, and you will even be able to tweak the output to your liking. First, however, this chapter gives you a quick-start on how to run PowerShell commands interactively.

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!