IBM and Microsoft Azure support Spectrum Symphony and Spectrum LSF

This week Microsoft and IBM have tied up an agreement that will provide an enhanced level of testing and support for both hybrid and pure IaaS deployments of Spectrum Symphony and Spectrum LSF into Microsoft&;s Azure public cloud. IBM Spectrum Symphony and Spectrum LSF provide enterprise-class workload management for distributed high performance computing and analytics and have an established brand within their respective markets.

 

The combination of these market leading solutions will provide our customers with a greater level of agility and scalability required to meet the demands of the industry. This is most apparent in financial services where the rapid developments in regulation have not only impacted the profitability of banks but also put huge strains on their aging infrastructure. As budgets get cut and risk modeling requirements increase, presenting such a partnership between IBM and Microsoft will enable our banking customers to burst from on-premises into Azure.

 

In the test chart results below, there are several different test runs being made with a varying number of tasks submitted to the available 9920 cores.

 

 

You can see that Symphony scales well and consistently over a wide range of tasks being run, from 100 all the way up to nearly one million tasks. To execute 992,000 ten second tasks took approximately 1000 seconds. The chart shows that Symphony running on a 9920 core Azure system can execute 3.4 million ten second tasks per hour.

 

For customers who bring their own Spectrum Symphony or Spectrum LSF licenses to Microsoft Azure, IBM will continue to deliver support directly just as it does when those licenses are deployed on customers’ premises. To request technical support for use of IBM software on Azure in BYOL/BYOSL scenarios, contact IBM technical support or refer to the IBM Support Handbook.

 

Join Microsoft and IBM in Salt Lake City on Wednesday 16th at 2:45pm to learn how combining these market leading solutions will provide our customers with the performance and scalability needed for their most demanding workloads. In this session we will review architecture, best practices, and a review of the scalability and performance testing results.
Quelle: Azure

The Santa Cloud

We all know Santa Claus gets help, but perhaps you didn’t realize how much and from where…

‘Twas almost October and up at the pole

The diligent elves were not reaching their goal

The IT department was working nonstop

A request for help flew to the guy at the top

The Santa Cloud poster shows how Santa and his elves use Microsoft Azure and other Microsoft cloud offerings for his annual gift deliveries on the evening of December 24.

Such an undertaking requires massive amounts of compute and storage resources and the software to:

Collect and analyze current and historical data and requests for presents from multiple sources (Azure Data Lake, SQL Data Warehouse, and Stream Analytics)

Work with vendors and partners during various parts of the manufacturing process

Perform the final determination of just who is naughty and who is nice (SQL Data Warehouse and Machine Learning)

These resources must scale to handle the data processing demands for all the world’s children up to the delivery date.

See how Microsoft Azure can tackle some of the biggest and, for the world’s children, most important processing tasks.

Poster-sized PDF (34×22)

Enjoy.
Quelle: Azure

Azure big data services host Ask Me Anything session

The big data teams on Azure will host a special Ask Me Anything session on /r/Azure, Thursday, November 17, 2016 from 10:00 am to 2:00 pm PST.

What&;s an AMA session?

We&039;ll have folks from the Azure big data engineering teams available to answer any questions you have. You can ask us anything about our products, services or even our teams!

Why are you doing an AMA?

We like reaching out and learning from our customers and the community. We want to know how you use big data in the Azure cloud and how your experience has been on Azure Data Lake, HDInsight, Data Factory and Stream Analytics services. Your questions provide insights into how we can make the service better. If this AMA session turns out to be useful, we may start doing this on a regular schedule.

Who will be there?

You, of course! We&039;ll also have PMs and Developers from the Azure Data Lake, HDInsight, R Server, Data Factory and Stream Analytics teams participating throughout the day.

Have any questions about the following topics? Bring them to the AMA.

Azure Data Lake Analytics, U-SQL
Azure Data Lake Store
Azure HDInsight
Microsoft R Server on HDInsight or standalone
Azure Data Factory
Azure Stream Analytics
Spark, Hadoop, HBase, Storm, Interactive Hive (LLAP), Jupyter, Zeppelin, Livy on HDInsight

Why should I ask questions here instead of StackOverflow, MSDN or Twitter? Can I really ask anything?

An AMA is a great place to ask us anything. StackOverflow and MSDN have restrictions on which questions can be asked while Twitter only allows 140 characters. With an AMA, you’ll get answers directly from the team and have a conversation with the people who build these products and services.

Here are some question ideas:

What is HDInsight?
What is the difference between Data Lake Analytics and Store?
What is the meaning of U in U-SQL?
How can I build my R regression model on 2 TB dataset?
What are the pros/cons of using Spark R vs R Server?
What is the easiest way to find driver logs of my Spark app?
What are the “gotchas” of geo-replication in HDInsight HBase?

Go ahead, ask us anything about our public products or the team. Please note, we cannot comment on unreleased features and future plans.

Join us! We&039;re looking forward to having a conversation with you!
Quelle: Azure

Microsoft Azure SQL Database provides unparalleled performance with In-Memory technologies

Azure SQL Database built-in In-Memory technologies are now generally available for the Premium database tier including Premium pools. In-memory technology helps optimize the performance of transactional (OLTP), analytics (OLAP), as well as mixed workloads (HTAP). These technologies allow you to achieve phenomenal performance with Azure SQL Database – 75,000 transactions per second for order processing (11X perf gain) and reduced query execution time from 15 seconds to 0.26 (57X perf). You can also use them to reduce cost – on a P2 database obtain 9X perf gain for transactions or 10X perf gain for analytics queries by implementing In-Memory technologies, without any additional cost! See below for details about these performance and cost savings results.

In-Memory OLTP increases throughput and reduces latency for transaction processing. Scenarios such as trading and gaming really see the performance benefits. Another common scenario is data ingestion from events or IoT devices. You can also use it to speed up caching, data load, and temp table and table variable scenarios.
Clustered Columnstore Indexes reduce storage footprint (up to 10X) and improve performance for reporting and analytics queries. Use it with fact tables in your data marts to fit more data in your database and improve performance. Use it with historical data in your operational database to archive and be able to query up to 10 times more data.
Non-clustered Columnstore Indexes for Hybrid Transactional and Analytical Processing (HTAP):gain real-time insights into your business by querying the operational database directly, without the need to run an expensive ETL process and wait for the data warehouse to be populated. Non-clustered Columnstore indexes allow very fast execution of analytics queries on the OLTP database, while reducing the impact on the operational workload.
In-Memory OLTP and Columnstore can also be combined: you can have a memory-optimized table with a columnstore index, allowing you to both perform very fast transaction processing and run analytics queries very fast on the same data.

Quorum Business Solutions provides innovative software as a service (SaaS) solutions for field operations in the Oil and Gas industry running on Microsoft Azure. With In-Memory OLTP they were able to grow their business by onboarding new customers and supporting organizations at much larger scale, without spending more on more database throughput.

“Scalable performance is critical with our IoT platform for oil and gas that must run 24/7/365.  The addition of In-Memory OLTP tables and native-compiled stored procedures on Azure SQL Database for a few key operations immediately reduced our overall DTU consumption by seventy percent.  Without in-memory tables, our growth would have required significant effort to multiple areas of the platform to maintain performance.  For data-centric services, in-memory support provides instant scale to existing applications with little to no changes outside of the database.” Mark Freydl, solution architect, Quorum Business Solutions 

For more details about Quorum Business Solutions’ use of Azure SQL Database and the benefits they see with In-Memory OLTP, read this case study.

Spotlight is a solution provided by Quest for the monitoring of SQL Server deployments in their customers’ data centers and in the cloud. They leverage In-Memory OLTP to speed up the processing of requests and events such that Quest’s customers learn about any potential issues in their environments very quickly.

“Quest’s customers rely on Spotlight to tell them in a timely manner about issues in their SQL Server environments. Quest relies on In-Memory OLTP in Azure SQL Database to provide a robust base on which to build Spotlight features quickly and deliver them to customers. With In-Memory OLTP, we get extremely high throughput and all the goodness of a flexible and well understood programming model based on T-SQL – this means we can deliver a high quality experience to our Spotlight customers very quickly.” Patrick O’Keeffe, executive director, software engineering (information management)

M-Files provides enterprise information management solutions that eliminate information silos and provide quick and easy access to the right content from any core business system and device. Non-clustered columnstore indexes allow running very fast analytical queries on the document data, in turn allowing M-Files’ customers to gain insights and find information much faster.

– “Lightning fast analytical queries as well as online transactions are a critical success factor in M-Files implementations. The addition of updatable non-clustered columnstore indexes in Azure SQL Database and in Microsoft SQL Server 2016 helped us to achieve over 10x faster queries in critical workloads at our customers without significant performance cost on online transaction processing. The change required no code changes in our application and provided instant performance boost both to our clients on-premises as well as to our M-Files Cloud Vault users in Azure.” Antti Nivala, founder and CTO

Performance and cost savings benefits

Both In-Memory OLTP and Columnstore Indexes achieve their respective performance benefits by utilizing resources such as CPU and IO more efficiently. Each Azure SQL Database pricing tier has a certain amount of resources allocated to it. Since In-Memory technologies are more resource-efficient, this means that you can achieve performance gains without having to increase your pricing tier. On the flip side, you can achieve the same performance level with a lower pricing tier when adopting In-Memory technologies in your database.

Some performance results for In-Memory OLTP in Azure SQL Database:

Order processing benchmark (scale factor 100, with 400 clients) on P15 (the highest tier at the time of writing): 75,000 transactions per second (TPS) with In-Memory OLTP, compared with 6,800 TPS with traditional tables and stored procedures, which translates to 11X performance gain with In-Memory OLTP.
Also lower performance tiers show impressive results. For a P2 with the same workload (scale factor 5, with 200 clients): 8,900 TPS with In-Memory OLTP, compared with 1,000.
30-40% performance gain just by replacing traditional table-valued parameters (TVPs) with memory-optimized TVPs: High Speed IoT Data Ingestion Using In-Memory OLTP in Azure

Performance results for Columnstore indexes, using the sample on this page:

Using a P15 database (the highest performance tier at the time of writing), the query runs in 0.26 seconds with Columnstore, while it runs in 15 seconds when using traditional indexes with page compression. This translates to a performance gain of 58X!
Even with lower pricing tiers you see significant performance benefits: using a P1 database, the query runs in 4.8 seconds with Columnstore, while it runs in 27 seconds using traditional indexes with page compression. A performance gain of 5.6X without increasing the pricing tier!

Try out In-Memory technologies in Azure SQL Database today

For more information about In-Memory technologies in Azure SQL Database, tips on how to get started, as well as samples, check out the SQL In-Memory documentation.

 

Stay tuned on this blog for more detailed information about the individual In-Memory technologies over the next few weeks!
Quelle: Azure

Azure Government Cloud expands P-ATO scope with addition of five new offerings

We are pleased to announce that Azure’s Government Cloud has expanded its FedRAMP Provisional Authorization to Operate (P-ATO) with the addition of five new offerings. Service Bus, Notification Hubs, Site Recovery, StorSimple, and Backup have all received Joint Authorization Board (JAB) approval for addition to Azure Government’s P-ATO at the High Impact Level.

With the addition of these five offerings, the total number of Azure Government offerings that meet the FedRAMP High baseline grows to 18. 

About our new offerings:

Azure Service Bus: Provides cloud-enabled communication with enterprise messaging and relayed communication to help connect applications, services, and devices. Service Bus connects applications running on Azure, on-premises systems, or both. A feature of Service Bus is Event Hubs which is a highly scalable, publish-subscribe service that can ingest millions of events per second and stream them into multiple applications.

Azure Notification Hubs: A massively scalable mobile push notification engine for quickly sending millions of notifications to iOS, Android, Windows, or Kindle devices, working with APNS (Apple Push Notification Services), GCM (Google Cloud Message), WNS (Windows Push Notification Services), MPNS (Microsoft Push Notification Service), and more.

Azure Site Recovery: Orchestrates replication of on-premises physical servers and virtual machines to the Azure cloud or to a secondary datacenter allowing organizations to meet BCDR (Business Continuity and Disaster Recovery) objectives.

Azure StorSimple: An integrated storage solution that manages storage tasks between on-premises devices and Microsoft Azure cloud storage. StorSimple is an efficient, cost-effective, and easily manageable storage area network (SAN) solution that eliminates many of the issues and expenses associated with enterprise storage and data protection.

Azure Backup: A simple and cost-effective backup-as-a-service solution that extends tried-and-trusted tools on-premises with rich and powerful tools in the cloud. It delivers protection for customers’ data no matter where it resides – in the enterprise data center, in remote and branch offices, or in the public cloud – while being sensitive to the unique requirements these scenarios pose. Azure Backup, now in a seamless portal experience with Azure Site Recovery, offers minimal maintenance and cost-efficiency, consistent tools for offsite backups and operational recovery, and unified application availability and data protection.

Azure is dedicated to expanding the number of offerings available to government customers and will continue to provide updates through our blog as well as adding covered offerings to the Microsoft Trust Center.
Quelle: Azure

What’s brewing in Visual Studio Team Services – November 2016 Digest

This post series provides the latest updates and news for Visual Studio Team Services and is a great way for Azure users to keep up-to-date with new features being released every three weeks. Visual Studio Team Services offers the best DevOps tooling to create an efficient continuous integration and release pipeline to Azure. With the rapidly expanding list of features in Team Services, teams can start to leverage it more efficiently for all areas of their Azure workflow, for apps written in any language and deployed to any OS.

Team Services integrates with Microsoft Teams

Microsoft Teams is a new chat-based workspace in Office365 that makes collaborating on software projects with Team Services a breeze. Team Services integrates with Microsoft Teams to provide a comprehensive chat and collaboration experience for your agile team across the development lifecycle.

Code Search is generally available and now Java friendly

Code Search is now available as a free extension to Team Services and Team Foundation Server for all basic access users in your account. In addition to C#, C, C++, and Visual Basic code, you can now do semantic searches across Java code.

 

Exploratory Testing extension is now Test & Feedback and generally available

Exploratory Testing has already become one of the most loved extensions for Team Services and one that we rely on heavily for bug bashing Team Services and the Visual Studio website. It is now Generally Available at no additional cost. It also has a new name and new superpowers, Test & Feedback. Read the announcement post to see how your team can use it to capture findings from exploratory sessions, create artifacts and work-items and collaborate with your team.

Automate code analysis with Maven and Gradle build tasks

The Maven and Gradle build tasks now have additional code analysis features that make it easier to understand and control technical debt.

New extensions for Rugged Devops

Whitesource, HPE Security Fortify and Checkmarx are three Team Services extensions that add support for OSS security and license validation, as well as code scanning, to ‘shift left’ your security and assist you in spending less time to build more secure software.

 

Devops with feature flags and Team Services

Feature flags are a powerful way to manage exposing new features as you deploy your application every sprint. See how the Team Services team uses feature flags to release every three weeks, and how you too can use feature flags with Team Services.

New features released in October 2016

Several new Git features, ability to schedule multiple releases triggers and a simpler way to create an Azure endpoint highlight the October release of Team Services. Oh, and did you know Team Services is included as part of a Visual Studio subscription? If a Visual Studio subscriber logs in to your Team Services account, they’re automatically recognized – making it even easier for you to manage subscribers in your team.

 

Keep up with the full list of new features with the Team Services product updates page and don’t forget to tune into the sessions streaming from Connect() 2016 on November 16 and 17. Happy coding!
Quelle: Azure

Azure Container Service: the cloud’s most open option for containers

Containers are the next evolution in virtualization, enabling organizations to be more agile than ever before. I see this from customers every day! They can write their app once and deploy everywhere, whether dev, test or production. Containers can run on any hardware, on any cloud, and in any environment without modification. In short, they offer a truly open and portable solution for agile DevOps.

With Azure Container Service (ACS), we provide customers a unique approach to managing containers in the cloud by offering a simple way for them to scale containers in production through proven open source container orchestration technology. Today we are announcing a series of updates to ACS that continue to demonstrate ACS is the most streamlined, open and flexible way to run your container applications in the cloud — providing even more customer choice in their cloud orchestrator. These updates, available today, include:

Kubernetes on Azure Container Service (preview): In July 2014, roughly a month after Kubernetes became publicly available, we announced support for Kubernetes on Azure infrastructure. Kubernetes 1.4 offered support for native Azure networking, load-balancer and Azure disk integration. Today, we are taking this support even further and announcing the preview release of Kubernetes 1.4 on Azure Container Service. This deeper and native support of Kubernetes will provide you another fully open source choice for your container orchestration engine on Azure. Now, customers will have more options to choose their cloud orchestrator with ACS providing support for three fully open source solutions in DC/OS, Docker Swarm and Kubernetes. You can read more here from Brendan Burns, one of the founders of Kubernetes, for his view on Kubernetes on ACS.
DC/OS Upgrade to 1.8.4: We’re pleased to share we have upgraded ACS support for DC/OS to version 1.8.4. This new version includes flexible new virtual networking capabilities along with job-scheduling and Marathon-based container orchestration baked right into the DC/OS UI. In addition, GitLab, Artifactory, Confluent Platform, DataStax Enterprise and our own Operations Management Suite are now available for one-click installation from the DC/OS Universe app store.
Open Source Azure Container Service Engine: Today, we are releasing the source code for the ACS Engine we use to create Azure Container Service deployments in Azure. This new open source project on GitHub will allow us to share with the community how we deploy DC/OS, Swarm and Kubernetes and collaborate on best practices for orchestrating containers on Azure, both public and on Azure Stack. Furthermore, with the ACS Engine, you can modify and customize deployments of the service beyond what is possible today. Finally, with your help, we can take contributions from the community and improve the service running in Azure.

We are seeing organizations of every size move their container-based solutions from dev/test environments to production in the cloud, especially as they discover the business agility opportunities containers make possible. In addition to delivering more choice and flexibility on ACS, we’re also enabling more streamlined agile development and container management through new updates, including these:

Azure Container Registry: Available in preview on Nov. 14, the Azure Container Registry is a private repository for hosting container images for use on Azure. Using the Azure Container Registry, you can store Docker-formatted images for all types of container deployments. In addition, the Azure Container Registry integrates well with the orchestrator offered by the Azure Container Service. When you use the Azure Container Registry, you will find it compatible with the open source Docker Registry v2 so you can use the same tools on ACR.
VS, VSTS and VS Code integration and deployment to Azure Container Service: Also on Nov. 14, we will release a new experience to enable you to easily set up continuous integration and deployment of multicontainer Linux applications using Visual Studio, Visual Studio Team Services and the open source Visual Studio Code. To continue enabling deployment agility, we expect to invest heavily in excellent dev-to-test-to-prod deployment experiences for container workloads using a choice of development and CI/CD solutions.

Azure is the only public cloud with a container service that offers a choice of open source orchestration technologies, DC/OS, Docker Swarm and Kubernetes, making it easier for you and your team to adopt containers in the cloud using the tools you love. You can get these agile benefits and more! Go try out DC/OS, Swarm or Kubernetes, on Azure Container Service today! If you want to see more, make sure you watch Microsoft Connect(); next week!

See ya around,

Corey
Quelle: Azure

Azure Container Registry preview

In today’s cloud-first world, applications are the vital ingredients that fuel innovation and productivity. Whether you are lifting and shifting apps to the cloud or building new cloud-native apps, containers are an attractive option to efficiently package software applications and deploy them as quickly as the business demands. Containers empower engineers to focus on innovation and new features rather than worry about how their code will be deployed. Containers also enable IT pros to easily adjust to seasonal demand fluctuations by easily enabling upward and downward scaling. In a nutshell, containers, and the ecosystem that is developing around them, will empower organizations to create the next generation of applications experiences and ship those innovations at the speed of business. A critical component of this container ecosystem is the container registry, which lets users store, manager and retrieve containers.

April 2016, Microsoft made Azure Container Service (ACS) generally available. June 2016 Microsoft announced container support for Azure Batch and Azure Service Fabric container support. Today, we are announcing major upgrades to Azure Container offerings, thereby making Azure the cloud with the broadest support for container deployments. This includes a preview of Azure Container Registry (ACR). ACR is a private registry for hosting container images. Using the Azure Container Registry, customers can store Docker-formatted images for all types of container deployments. Azure Container Registry integrates well with orchestrators hosted in Azure Container Service, including Docker Swarm, DC/OS and Kubernetes. Users can benefit from using familiar tooling capable of working with the open source Docker Registry v2.

Use cases for the Azure Container Registry include these:

Store and manage images for all types of container deployments

Docker is becoming the new binary format for deployments. Development and operations teams can manage the configuration of their app, isolated from the configuration of the hosting environment. Containers aren&;t just deployed to highly scalable orchestration systems like Mesosphere DC/OS, Docker Swarm and Kubernetes, but all types of deployments. Azure App Services, Azure Batch, Service Fabric and other services are coming online that support containers as their deployment model. Regardless of where you deploy containers, you&039;ll need a place to store and manage the images. Using the Azure Container Registry, you can store your images for all types of container deployments.

Automated Container Builds, Testing and Security Scanning

Using Visual Studio Team Services developers can automate the process for compiling their code, in containers, building Docker images and deploying them to the Azure Container Registry. With partners like TwistLock, you can rest assured that your image-building process will produce secure images as they get deployed to the Azure Container Registry, as well as protect your deployment environments like ACS by securing each node in the cluster.

Store your container image in local, network-close storage on Azure

The Azure Container Registry provides local, network-close storage of your container images. By instancing a registry in the same datacenter as your deployments, your network latency will be reduced, without incurring ingress/egress charges.

Use Common Command Line Interface (CLI) to interact with the registry

Benefit from using familiar and open source CLI tools like Docker login, push and pull. You don’t need to learn new APIs or commands to work with the registry. Users can benefit from using familiar tooling capable of working with the open source Docker Registry.

Use Azure Active Directory to manage access, including Service Principals for headless connections like automated CI/CD and vulnerability scanning

Rest assured your credentials are safely managed using Azure Active Directory. The Public Preview will support Azure Active Directory Service Principal-backed authentication for basic auth flows, including role-based access for read-only, write and owner permissions.

Manage Windows and Linux container images in a single registry

Azure container registry can manage both Windows and Linux images, giving you the flexibility to choose the platform and workloads to run within the containers.

These innovations demonstrate our continued investment in the container ecosystem and highlight our unique strategy of offering the only public cloud container orchestration service that offers a choice of open source orchestration technologies — DC/OS, Docker Swarm and Kubernetes. The support for Azure Container Registry amplifies our strategy to make it easier for organizations to adopt containers in the cloud.

Customers will be able to access the preview of Azure Container Registry on Nov. 16 — watch for more details at Microsoft Connect();!
Quelle: Azure

Azure DocumentDB updates: quick start experience, backup and restore, and firewall support

Over the past couple weeks we released a number of improvements to the developer experience and capabilities of  DocumentDB. We added a new quick start experience helping you to get up and running with a working app on DocumentDB in seconds. We launched a preview for backup/restore and inbound firewall capabilities, as well as released numerous runtime improvements including expanded support for geospatial types.

Quick start

One important characteristic of any service is the time it takes to get a working app up and running. We released a new quick start experience that gives you a personalized ready-to-run sample app connected to your newly created DocumentDB account in seconds. Create a new DocumentDB account and click on the quick start menu item in your existing account and give it a try.

For accounts with MongoDB API support, we had added a handy code snippet for all major platforms, with all the necessary configuration to get you started, including what connection string to use.

Backup and restore

DocumentDB is built with high availability and global distribution at its core – it allows you to scale throughput across multiple Azure regions along with policy driven failover and transparent multi-homing APIs. As a database system offering 99.99 availability SLAs, all the writes in DocumentDB are durably committed by a quorum of replicas within a local data center, and replicated across all the regions associated with your DocumentDB account.

DocumentDB also automatically takes backup of all your data at regular intervals. The backups are taken without affecting the performance or availability of your database operations. All your backups are stored separately in another storage service and are further globally replicated for resiliency against regional disasters. Customers can now request to restore their databases and collections from a backup by contacting Azure support. Below is an illustration of periodic backups to GRS Azure Storage performed by DocumentDB for all entities.

Learn more about backup and restore for DocumentDB.

Firewall support

Due to popular customer request, we recently offered support for IP filtering and firewall rules in DocumentDB for both DocumentDB and MongoDB APIs. Customers can configure their DocumentDB account to allow traffic only from a specified list of the individual IP addresses and IP address ranges. Once this configuration is applied, all requests originating from machines outside this allowed list will be blocked by DocumentDB. The connection processing flow for the IP-based access control is described in the following diagram.

Learn more about DocumentDB firewall support.

Expanded geospatial support

With a recent service update, Azure DocumentDB now supports geospatial indexing and querying of Polygon and LineString objects, in addition to the Point object. DocumentDB can automatically detect GeoJSON fragments that contain Polygon and LineString objects within your documents, and index them for efficient spatial proximity queries.

Spatial querying of Polygon and LineString objects is commonly used to detect "geo-fences" in IoT, telematics, gaming, and mobile applications. You can enable or disable spatial indexing by changing the indexing policy on a per-collection basis. Read more about working with geospatial data in DocumentDB.

 

We hope you find this new functionality useful as you build your solutions on top of DocumentDB. As always, let us know how we are doing and what improvements you&;d like to see going forward through UserVoice,  StackOverflow azure-documentdb, or Twitter @DocumentDB.
Quelle: Azure