X

Oracle Spatial and Graph – technical tips, best practices, and news from the product team

  • December 4, 2016

Oracle Spatial and Graph for Oracle Database 12c Release 2 (12.2) on Oracle Cloud is available!

Jean Ihm
Product Manager, Oracle Spatial and Graph


Oracle Spatial and Graph for Oracle
Database 12c Release 2 (12.2)
, the latest generation of the world’s
most popular database, is now available in the Oracle Cloud! With the 12.2 release, Oracle
Spatial and Graph introduces powerful new analytics, and features to make
spatial and graph operations faster, cloud-ready and more developer friendly. New capabilities include

  • A
    powerful new property graph analysis
    feature to address Big Data use cases such as making recommendations, finding
    communities and influencers, pattern matching, and identifying fraud and other
    anomalies
  • Native
    support for GeoJSON
  • An
    HTML5 map visualization component
  • Spatial index and partitioning
    improvements
    to
    boost performance
  • Location data enrichment services for unstructured text
    documents
  • Location tracking service
  • Enhancements for GeoRaster, Network
    Data Model, and Spatial Web Services
  • RDF Semantic Graph enhancements - SPARQL 1.1 update operations for
    pattern-matching queries, and integration with property graphs

With 12.2, we continue to deliver
the most advanced spatial and graph database platform for applications from geospatial
and location services to Internet of Things, social media, and big data.

And it runs on Oracle Database
Cloud – a great option to quickly get your environment up and running, whether
you have a sandbox prototype, small departmental application, or large, mission
critical applications.

Learn More

Oracle Spatial and Graph /
12.2 features on Oracle Cloud

Oracle Database 12c Release 2

Join the conversation:
#DB12c #FutureofDB #OracleSpatial

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.