Data Driver

Blog archive

PHP Developers Get SQL Server, SQL Azure Insights

Microsoft isn't letting up on its full-court press to woo PHP developers into the SQL Server world.

The company earlier this month hosted 17 PHP developers at a SQL Server JumpIn! Camp, where they learned how to incorporate SQL Server support into their apps with the help of Microsoft experts, according to a post yesterday in the Microsoft SQL Server Driver for PHP Team Blog.

Program manager Ashay Chaudhary reported that the 17 developers represented 10 PHP projects from several countries. They were treated to dinners, entertainment and more at the five-day camp, where the goal was to "listen to and learn from the PHP community and educate them about our technologies, SQL Server, SQL Azure, Windows Azure & IIS, and help them understand how they can leverage them best in the applications."

The 10 projects included content management systems, a profiling utility, an e-commerce solution, a Web application framework and more. Chaudhary said eight of the projects completed enough coding to demo their apps with SQL Server, while four actually managed to publish builds during the camp. Four projects reported improved their performance on IIS using the WinCache extension, four tested successfully on SQL Azure and three used the new PDO driver for SQL Server support.

"By adding support for SQL Server, these projects stand to gain from the broad customer base that already has SQL Server in their organizations," Chaudhary said.

"We now have a much clearer understanding about what we need to do to better support PHP applications on Windows/IIS/SQL Server and the Azure platform," he said. "The PHP participants now have a better understanding of how SQL Server works and how PHP applications can best utilize its capabilities, and understand how we are trying to add value to their applications."

Last April, Microsoft held a similar camp in Zurich, Switzerland. Chaudhary said he will write more about the November camp as he has time to reflect on the event, but he didn't indicate that any future camps were scheduled.

"For now," he said, "you can look forward to Windows, IIS, and SQL Server support in several great PHP applications with many more to come over the next few months."

One of those apps will be ImpressCMS, a content management system. Marc-Andre, CEO and founder of ImpressCMS, blogged that his goal at the camp was to "implement PDO and MSSQL support" into his product and reported it was a success. "We are still missing a few things in the installer to make our CMS install properly on MSSQL, but we will get there!" he said.

What do you think about Microsoft's overtures to the open source community? Comment here or drop me a line and share your thoughts.

Posted by David Ramel on 11/30/2010


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube