Google Directory ADO.NET Provider
 
ADO.NET
Google Directory Logo

Google Directory ADO.NET Provider

SQL-based Access to Google Directory through ADO.NET for your custom .NET applications and SSAS.

download buy now

Other Google Technologies

Other Google Drivers

The Google Directory ADO.NET Data Provider enables user to easily connect to Google Directory data from .NET applications. An easy-to-use database-like interface for .NET applications access to live Google Directory data (Domains, Groups, Users, Tokens, and more).

ADO architecture

Google Directory .NET Connectivity Features

  • Connect to live Google Directory data, for real-time data access with the Google Directory ODBC Driver
  • Full support for data aggregation and complex JOINs in SQL queries
  • Secure connectivity through modern cryptography, including TLS 1.2, SHA-256, ECC, etc.
  • Seamless integration with leading BI, reporting, and ETL tools and with custom applications via the Google Directory Connector.

Target Service, API

The driver connects to Google Directory through OAuth authentication standard, providing access to domains, groups, users, tokens, and other Google Workspace directory data. The driver uses Google's OAuth authentication with support for both user account and service account authentication flows.

Schema, Data Model

The driver models Google Directory entities as relational database tables with dynamic schema discovery. Provides access to Google Directory data including Domains, Groups, Users, Tokens, and other directory objects. The driver dynamically discovers schemas to allow access to all Google Directory sources with metadata retrieval.

Key Objects

Primary objects include Domains, Groups, Users, Tokens, and other Google Workspace directory entities. The driver provides comprehensive access to all Google Directory organizational data for enterprise management and analytics use cases.

Operations

Full SQL-92 support with CRUD operations including SELECT, INSERT, UPDATE, DELETE. Features push-down query optimization for server-side processing where possible. Client-side query execution engine handles operations not available server-side. Supports complex JOINs and data aggregation.

Authentication

Uses OAuth authentication standard with support for both individual user authentication and Google Apps Domain service account authentication. Requires OAuth Client ID and OAuth Client Secret for custom OAuth app registration. Supports embedded OAuth credentials or custom OAuth application configuration.

Start a 30-day Free Trial Today

Google Directory ADO.NET Download

See what you can do with Google Directory ADO.NET provider

SSAS Cube
SSAS Cube

Use Google Directory from SQL Server Analysis Service (SSAS) multi-dimensional cubes. Keep your analytical data modeling and access to any source including cloud and on-premises.

Custom .NET Application
Custom .NET Application

The Google Directory ADO.NET Provider allows developers to build applications that connect to Google Directory using familiar SQL and Entity Framework. Integrate Google Directory to your mission -critical applications or create easy side-by-side applications.

Reporting & BI
Low-Code Dev Platforms

You can connect from ADO.NET compliant low-code development tools:

Reporting & BI
Reporting Tools

You can connect Google Directory from .NET-based reporting and analytics tools:

Standard ADO.NET Access to GoogleDirectory

The Google Directory ADO.NET Provider offers the most natural way to access Google Directory data from any .NET application. Simply use Google Directory Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the Google Directory Data Provider through Visual Studio Server Explorer, in code through familiar classes, and in data controls like DataGridView, GridView, DataSet, etc.

The CData ADO.NET Provider for Google Directory hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.

Working with DataAdapters, DataSets, DataTables, etc.

The Google Directory Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: GoogleDirectoryConnection, GoogleDirectoryCommand, GoogleDirectoryDataAdapter, GoogleDirectoryDataReader, GoogleDirectoryDataSource, GoogleDirectoryParameter, etc. Because of this you can now access Google Directory data in an easy, familiar way.

For example:

using (GoogleDirectoryConnection conn = new GoogleDirectoryConnection("...")) {
	string select = "SELECT * FROM Domains";
	GoogleDirectoryCommand cmd = new GoogleDirectoryCommand(select, conn);
	GoogleDirectoryDataAdapter adapter = new GoogleDirectoryDataAdapter(cmd);
	using (adapter) {
		DataTable table = new DataTable();
		adapter.Fill(table);		
		...
	}
}

More Than Read-Only: Full Update/CRUD Support

Google Directory Data Provider goes beyond read-only functionality to deliver full support for Create, Read, Update, and Delete operations (CRUD). Your end-users can interact with the data presented by the Google Directory Data Provider as easily as interacting with a database table. 

using (GoogleDirectoryConnection connection = new GoogleDirectoryConnection(connectionString)) {
	GoogleDirectoryDataAdapter dataAdapter = new GoogleDirectoryDataAdapter(
	"SELECT Id, Where FROM Domains", connection);
  
	dataAdapter.UpdateCommand = new GoogleDirectoryCommand(
		"UPDATE Domains SET Where = @Where " +
		"WHERE Id = @ID", connection);

	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");

	DataTable DomainsTable = new DataTable();
	dataAdapter.Fill(DomainsTable);

	DataRow firstrow = DomainsTable.Rows[0];
	firstrow["Where"] = "New Location";

	dataAdapter.Update(DomainsTable);
}

ADO.NET Provider Performance

With traditional approaches to remote access, performance bottlenecks can spell disaster for applications. Regardless if an application is created for internal use, a commercial project, web, or mobile application, slow performance can rapidly lead to project failure. Accessing data from any remote source has the potential to create these problems. Common issues include:

  1. Network Connections - Slow network connections and latency issues are common in mobile applications.
  2. Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
  3. Large Data - Intentional or unintentional requests for large amounts of data.
  4. Disconnects - Complete loss of network connectivity.

The CData ADO.NET Provider for Google Directory solves these issues by supporting powerful smart caching technology that can greatly improve the performance and dramatically reduce application bottlenecks.

Smart Caching

Smart caching is a configurable option that works by storing queried data into a local database. Enabling smart caching creates a persistent local cache database that contains a replica of data retrieved from the remote source. The cache database is small, lightweight, blazing-fast, and it can be shared by multiple connections as persistent storage.

Caching with our ADO.NET Providers is highly configurable, including options for:

  • Auto Cache - Maintain an automatic local cache of data on all requests. The provider will automatically load data into the cache database each time you execute a SELECT query. Each row returned by the query will be inserted or updated as necessary into the corresponding table in the cache database.
  • Explicit Cache - Cache only on demand. Developers decide exactly what data gets stored in the cache and when it is updated. Explicit caching provides full control over the cache contents by using explicit execution of CACHE statements.
  • No Cache - All requests access only live data and no local cache file is created.

This powerful caching functionality increases application performance and allows applications to disconnect and continue limited functioning without writing code for additional local storage and/or data serialization/deserialization.

More information about ADO.NET Provider caching and best caching practices is available in the included help files.

Visual Studio Integration & Server Explorer

Working with the new Google Directory ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the Google Directory Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.

As an ADO.NET Data Provider, Google Directory ADO.NET Provider can be used to access and explore Google Directory data directly from the Visual Studio Server Explorer.

It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to Google Directory ADO.NET Provider just like connecting to any standard database.

  • Add a new Data Connection from the Server Explorer and select the Google Directory Data Source
  • Configure the basic connection properties to access your Google Directory account data.

Explore all of the data available! Google Directory ADO.NET Provider makes it easy to access live Google Directory data from Visual Studio.

  • After configuring the connection, explore the feeds, views, and services provided by the Google Directory Data Source.
  • These constructs return live Google Directory data that developers can work with directly from within Visual Studio!

Developer Integration: Databind to Google Directory

Connecting Web, Desktop, and Mobile .NET applications with Google Directory is just like working with SQL Server. It is even possible to integrate Google Directory ADO.NET Provider into applications without writing code.

Developers are free to access the Google Directory ADO.NET Provider in whatever way they like best. Either visually through the Visual Studio Winforms or Webforms designers, or directly through code.

  • Developers can connect the Google Directory Data Source directly to form components by configuring the object's smart tags.
  • Add a new Data Connection from the Server Explorer and select the Google Directory Data Source. Then, select the feed, view, or services you would like to connect the object to.

Done! It's just like connecting to SQL Server.

  • Once the object is bound to the data source, applications can easily interact with Google Directory data with full read/write (CRUD) support.

Popular ADO Videos:

Connecting to Live Data from ADO Apps

Download the Google Directory ADO.NET driver today!

download
buy now