News

Windows Azure Now Supports Oracle Virtual Machines

There are plenty of limitations, though, including no support for Oracle Database clustering.

Developers who rely on Oracle databases rather than SQL Server now have the option to use Microsoft's cloud architecture.

Microsoft and Oracle have released previews of virtual machine (VM) images that enable Oracle workloads to run on Windows Azure.

The two companies announced their partnership on Azure in late June, but the VM images apparently weren't available at that time. The preview images, which come prebuilt and which include the Oracle licensing, were either released on September 24 or yesterday, according to Microsoft's blog announcements. Using the previews isn't exactly free as there are Windows Azure compute and storage costs incurred, but there are no Oracle licensing charges to use the images during the preview period, according to Microsoft. It's not clear how long they will stay at the preview stage, however.

To run the images, users need to have a Windows Azure account. They can set up the VMs by selecting the images from the Windows Azure Virtual Machines image gallery, as described here. The list of Oracle VM images includes Oracle Database 12c, Oracle WebLogic Server 12c and Java Platform Standard Edition 6 or 7 on Windows Server 2012.

Microsoft is not recommending using the image previews in production environments. There are plenty of other caveats to consider, too.

For instance, Oracle Database clustering isn't currently supported on Windows Azure. Microsoft also cautions that Windows Azure produces dynamic IP addresses for the Oracle Databases that are hosted, instead of the static IP addresses expected by the application, which "may result in unintended side effects."

Another limitation is that Oracle WebLogic Server images support clustering on the Enterprise edition only. Connection pools will time out after four minutes of inactivity, which could affect applications that rely on connection pools, Microsoft warns. See all of Microsoft's caveats regarding the use of the preview images at this MSDN library page.

The idea behind this collaboration between Microsoft and Oracle is that organizations can get support from both companies when running Oracle workloads on Windows Azure, as explained by Brad Anderson, Microsoft's corporate vice president for cloud and enterprise, during his Oracle OpenWorld keynote address. That speech marked the first-time keynote appearance of a Microsoft executive at the annual Oracle event.

It is now possible to run Oracle Linux on Windows Azure, according to Microsoft, and Java is supported on Microsoft's cloud platform. Oracle, for its part, is supporting Microsoft's Hyper-V hypervisor for its products.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

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