Learn more
 

Ready to get started?

Download a free trial of the Bing Search ODBC Driver to get started:

 Download Now

Learn more:

Bing Search Icon Bing Search ODBC Driver

Easy-to-use Bing client enables Java-based applications to easily search and filter Microsoft Bing search results.

In this article

Related articles

Replicate Bing Search Results from PowerShell


Write a quick PowerShell script to query Bing Search results. Use connectivity to the live data to replicate Bing Search results to SQL Server.



The CData ODBC Driver for Bing Search enables out-of-the-box integration with Microsoft's built-in support for ODBC. The ODBC driver instantly integrates connectivity to the real Bing Search results with PowerShell.

You can use the .NET Framework Provider for ODBC built into PowerShell to quickly automate integration tasks like replicating Bing Search results to other databases. This article shows how to replicate Bing Search results to SQL Server in 5 lines of code.

You can also write PowerShell code to download Bing Search results. See the examples below.

Create an ODBC Data Source for Bing Search

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

To connect to Bing, set the ApiKey connection property. To obtain the API key, sign into Microsoft Cognitive Services and register for the Bing Search APIs.

Two API keys are then generated; select either one.

When querying tables, the SearchTerms parameter must be supplied in the WHERE clause.

Connect to Bing Search

The code below shows how to use the DSN to initialize the connection to Bing Search results in PowerShell:

$conn = New-Object System.Data.Odbc.OdbcConnection $conn.ConnectionString = "DSN=CData Bing Source x64"

Back Up Bing Search Results to SQL Server

After you enable caching, you can use the code below to replicate data to SQL Server.

Set the following connection properties to configure the caching database:

  • CacheProvider: The name of the ADO.NET provider. This can be found in the Machine.config for your version of .NET. For example, to configure SQL Server, enter System.Data.SqlClient.

  • CacheConnection: The connection string of properties required to connect to the database. Below is an example for SQL Server:

    Server=localhost;Database=RSB;User Id=sqltest;Password=sqltest;

The SQL query in the example can be used to refresh the entire cached table, including its schema. Any already existing cache is deleted.

$conn.Open() # Create and execute the SQL Query $SQL = "CACHE DROP EXISTING SELECT * FROM " + $VideoSearch $cmd = New-Object System.Data.Odbc.OdbcCommand($sql,$conn) $count = $cmd.ExecuteNonQuery() $conn.Close()

The driver gives you complete control over the caching functionality. See the help documentation for more caching commands and usage examples. See the help documentation for steps to replicate to other databases.

Other Operations

To retrieve Bing Search results in PowerShell, call the Fill method of the OdbcDataAdapter method. To execute data manipulation commands, initialize the OdbcCommand object and then call ExecuteNonQuery. Below are some more examples commands to Bing Search through the .NET Framework Provider for ODBC:

Retrieve Bing Search Results

$sql="SELECT Title, ViewCount from VideoSearch" $da= New-Object System.Data.Odbc.OdbcDataAdapter($sql, $conn) $dt= New-Object System.Data.DataTable $da.Fill($dt) $dt.Rows | foreach { $dt.Columns | foreach ($col in dt{ Write-Host $1[$_] } }