Open Source PowerShell is available on several operating systems, that really what’s special about the whole project! To get PowerShell to function on these various systems we need to build (compile) the software in that environment. This is what will produce the actual executable program that is powershell.
To facilitate the build process the PowerShell team has documented how to do this for the currently available platforms, Linux, MacOS and Windows.
Open Source PowerShell has been on fire, getting tons of community support and really making people think about what’s to come with a single language to manage a heterogenous data center.
To highlight this point, in my recent Pluralsight Play By Play Microsoft Open Source PowerShell on Linux and Mac with Jason Helmick and Jeffrey Snover I did a demo on using PowerShell remoting where I connected from a Linux machine to three other machines and retrieved lists of top processes from each…two Linux and one Windows.
What’s going on here? So last week you may have seen this picture on Twitter…it went a little crazy…and you may have been wondering what are we up to? Well, last week I had the pleasure of filming a Pluralsight Play By Play. A Play By Play is a course on Pluralsight but in a slightly different format than you may be used to. A Play By Play bring together industry experts to discuss and demonstrate an emerging technology.
In this post we’re going set PowerShell as your default Linux shell.
What is a shell? In Linux systems you’re given options, tons of options, you can set, reconfigure, add/remove almost anything that you want. And one of those options is your shell. The shell is the thing that you interact with when you’re typing commands at the command line. Different shells have different behaviors and characteristics. It’s a very personal choice.
Getting PowerShell on Linux Well it’s not just an announcement, you can actually get PowerShell on Linux and MacOS right now from GitHub – here!
Installing PowerShell Once you’ve downloaded an installation file you can use RPM or apt to install the package. If you’re on a Mac…well just double click on the package!
yum install powershell-6.0.0_alpha.9-1.el7.centos.x86_64.rpm
If you’re on Ubuntu, you’ll need a little more stuff read this. Running PowerShell We’ll there’s really not much to that, just type powershell at the command prompt an you’re off and running!
In this post we are going to show the implementation of a PowerShell script using SMO to move data between filegroups on SQL Server. This article is the second of our two part series on “Moving SQL Server data between filegroups – Database Structures”, you can find the first article here.
The Challenge Looking around on the web, I couldn’t find a solution to the problem of moving data between filegroups that I liked.
Why is moving data between filegroups hard?
****As a consultant its common to walk into a customer site and find databases that are contained in one very large file. For various reasons it can be beneficial to adjust the number a data files for a database. See here. However, in SQL Server moving data from a one file database into a multi-file configuration is a non-trivial task. It’s a two step process, requiring that you add a new filegroup then in the filegroup add your multi-file configuration.
