Showing posts with label Powershell. Show all posts
Showing posts with label Powershell. Show all posts

Monday, July 20, 2015

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.

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.

Wednesday, July 15, 2015

Powershell

Powershell overview
SQL Server 2008 introduces support for Windows PowerShell. Windows PowerShell is a powerful scripting shell that lets administrators and developers automate server administration and application deployment. The Windows PowerShell language supports more complex logic than Transact-SQL scripts, giving SQL Server administrators the ability to build robust administration scripts. Windows PowerShell scripts can also be used to administer other Microsoft server products. This gives administrators a common scripting language across servers.
SQL Server provides two Windows PowerShell snap-ins that implement:
  • A SQL Server provider, which enables a simple navigation mechanism similar to file system paths. You can build paths similar to file system paths, where the drive is associated with a SQL Server management object model, and the nodes are based on the object model classes. You can then use familiar commands such as cd and dir to navigate the paths similar to the way you navigate folders in a command prompt window. You can use other commands, such as ren or del, to perform actions on the nodes in the path.
  • A set of cmdlets, which are commands used in Windows PowerShell scripts to specify a SQL Server action. The SQL Server cmdlets support actions such as running asqlcmd script containing Transact-SQL or XQuery statements.

Monday, July 13, 2015

Powershell

Powershell overview
SQL Server 2008 introduces support for Windows PowerShell. Windows PowerShell is a powerful scripting shell that lets administrators and developers automate server administration and application deployment. The Windows PowerShell language supports more complex logic than Transact-SQL scripts, giving SQL Server administrators the ability to build robust administration scripts. Windows PowerShell scripts can also be used to administer other Microsoft server products. This gives administrators a common scripting language across servers.
SQL Server provides two Windows PowerShell snap-ins that implement:
  • A SQL Server provider, which enables a simple navigation mechanism similar to file system paths. You can build paths similar to file system paths, where the drive is associated with a SQL Server management object model, and the nodes are based on the object model classes. You can then use familiar commands such as cd and dir to navigate the paths similar to the way you navigate folders in a command prompt window. You can use other commands, such as ren or del, to perform actions on the nodes in the path.
  • A set of cmdlets, which are commands used in Windows PowerShell scripts to specify a SQL Server action. The SQL Server cmdlets support actions such as running asqlcmd script containing Transact-SQL or XQuery statements.