Automating the world one-liner at a time…
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 ArchitectVisit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShellVisit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
PingBack from http://msdnrss.thecoderblogs.com/2007/11/13/sql-server-support-for-powershell/
I och med ITForum i Barcelona så händer det välldigt mycket i Microsoftvärlden just nu. Och för oss som
Entre las cosas por las que espero con ansiedad la salida de SQL Server 2008 estan sin duda entre las
Any hope of seeing Powershell integration inside Visual Studio? I want to run scripts that that are part of a solution or project that will interact with VSTS and then let Visual Studio know to update it's view of VSTS.
Tout d'abord, une nouvelle version de PowerGUI est disponible, avec notamment l'apparition du debugger
I have tried to run this PowerInitSMO.psl but it is not giving any effect. what can be the cause.
Wow!! You are SO cool for having information that we don't, and you're so coy about letting us know that you have this information that we dont.
I also like how you elude to the fact that you have even MORE information, "but can't tell us". So shut up already, why even say that?
People in this industry measure self-worth by letting others know they have information, but won't tell others what that informations is. I'mn fo frickin sick of it! Shut up already!!!
> I'mn fo frickin sick of it! Shut up already!!!
Having a bad day? :-)
I didn't mean to be teaser. I wanted to convey the fact that there is strong internal adoption but I can't announce other people's confidential information. You are right though - that combination turned the entry into a tease.
All that said, you can all get in on these secrets and more by joining Microsoft and getting on the internal mailing lists. (Let's see if I can turn this into a recruiting opportunity :-) ).
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
How do I go about getting recruited?
I am trying to use Powershell SQL script and invoke it from C#.
First, I initialize sql provider using Initialize-SqlpsEnvironment.ps1 (http://blogs.technet.com/patricg/attachment/3121583.ashx). Then I cd to sql\localhost and getting sql instance. Everything works perfectly from command line, but when I am using C# like next, I got no results back.
sRc = RunspaceConfiguration.Create();
sInvoker = new RunspaceInvoke(sRc);
string script = @".\sqlProvider.ps1";
Collection<PSObject> results = sInvoker.Invoke(script);
I know that I can do this from C# itself, but need to use script as script will be used in different places by sysadmins.
Am I missing something that this code doesn't work?
Thanks for help,