Finally the information is public!!! You can’t image how difficult it has been to know this information but not be able to tell anyone. It’s so cool you just want to stop people on the street and tell them.
Check out this eweek article: Microsoft Releases Another SQL Server 2008 CTP. In it is the following:
“SQL Server 2008 running on Windows Server 2008 provides customers with trusted and secure access, high availability through revamped failover clustering, and simplified scripting through Powershell,” Francois Ajenstat, director of product management for SQL Server, told eWEEK here at the TechEd IT Forum conference, which starts Nov. 12.
Bob Beaucheim actually demonstrated SQL’s Powershell Provider and set of Cmdlets last week during TechEd in Barcelona. He had permission from the SQL team but I still wasn’t going to say anything until I saw the SQL team talking about it.
We should be clear – just because something ships in a CTP does not mean that it will ship in the product. There are lots of times and reasons why we’ll pull something for the final release. As such, you should get the SQL CTP, kick the tires on their PowerShell support and let the team know what you think. If you like it – let them know. If you don’t like it – let them know that as well.
The exciting news that I can’t discuss is the quiet revolution that is going on inside the company as team after team is adopting PowerShell. Those teams are making the investment and it their news to announce – we aren’t going to steal their thunder.
There are so many teams adopting PowerShell that we have had to develop an internal Cmdlet Designer tool which allows multiple teams to design their cmdlets looking at what other people have done. This helps ensure consistency and non-collision across the wide set of Cmdlets. The tool is wicked cool. It is a WPF application layered on top of PowerShell cmdlets which talk web services to a backend ASP.NET application which stores all the metadata in SQL. It then uses the metadata to generate template C# code for the cmdlets and test cases to ensure that the implementation and specifications are in sync. Later it will be able to generate the HELP files as well. Lee Holmes of the PowerShell CookBook fame, was the developer on this project.
Anyway – the point is that there is this growing wave of adoption that will take a while before you’ll see it in the shipping products. I think you are going find your investment in learning PowerShell will continue pay even larger dividends going forward.
Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx