This page contains frequently asked questions about dotConnect for Google BigQuery. When you have a question, check this list first. If this page does not contain the answer, refer to the support page.
Installation and deployment
Close all running IDEs and help collections, then run the installation package for the newer version. When prompted to uninstall the previous version, confirm and proceed with the installation. If you use NuGet packages, update the Devart.Data.BigQuery package and, if applicable, the Devart.Data.BigQuery.EFCore package to the new version.
To deploy an application that uses dotConnect for Google BigQuery, you need to:
For detailed instructions on each of these steps, see Deployment and Licensing.
Select the Minimal installation option when prompted by the installer. Alternatively, skip the installer at all and add the Devart.Data.BigQuery NuGet package to your project.
Yes. Add the Devart.Data.BigQuery NuGet package (and Devart.Data.BigQuery.EFCore for Entity Framework Core) to your project. Then specify the license key. Design-time features (Server Explorer integration, toolbox components, and wizards) are available only in Visual Studio.
Devart data providers share common assemblies (Devart.Data.dll and Devart.Data.SqlShim.dll), so you must install compatible versions of the providers. We release our ADO.NET data providers in a single package, so releases from the same date should be compatible. Also, Devart data providers should warn you if an incompatible version of Devart.Data.dll is detected before installation.
All upgrades to future versions are free to users with an active dotConnect for Google BigQuery subscription.
The dotConnect for Google BigQuery Subscription Program is an annual maintenance and support service for dotConnect for Google BigQuery users.
Users with a valid dotConnect for Google BigQuery Subscription receive the following benefits:
Priority Support is an advanced product support program that offers you expedited individual assistance with dotConnect for Google BigQuery-related questions from the dotConnect for Google BigQuery developers themselves. Priority Support is carried out over email and has a response time of two business days.
Yes, you can. Licenses for dotConnect for Google BigQuery are perpetual.
dotConnect for Google BigQuery uses activation-key-based licensing. To work, the provider requires a valid activation key: either a trial key or a key for the purchased license. Without a valid key, dotConnect for Google BigQuery does not work.
You can obtain a trial or activation key from the Devart website or in Visual Studio: on the Tools menu, point to Google BigQuery, then click Get Activation or Trial Key.
To activate the product on the development machine, enter the key in the installer or click Activate or Get License Information on the same menu.
If you use only NuGet packages, use the console activator included in the Tools folder of the Devart.Data.BigQuery package.
Specify the key in the License Key connection string parameter. For example:
Authentication Type=ServiceAccount;Project Id=your_project;ServiceAccount Json=key.json;License Key=**********
Alternatively, call the static BigQueryConnection.LoadLicenseKey method before opening the first connection.
This means that a valid license key cannot be found or that the key has expired. Check the following:
If you encounter licensing problems in your project, you should use the License Information dialog box to resolve them. To open it, on the Tools menu, point to Google BigQuery, then click Activate or Get License Information.
No, end users of your application don't need a license.
The connection is returned to the pool. This is how connection pooling works: the connection object, along with its authentication data, is retained for reuse by your application. As a result, the next call to Open() does not need to authenticate with Google Cloud again, which improves performance.
The full exception message is "Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached." This message indicates that no connections are available in the pool. To solve the problem, increase the Max Pool Size connection string parameter value, make sure your code closes connections after use, or clear one or all of the pools. Alternatively, you can turn off connection pooling by setting the Pooling connection string parameter to false.
You can clear the pool explicitly. To force the operation, call the ClearPool or ClearAllPools methods. Alternatively, you can turn off the pool completely by setting Pooling=false in the connection string. If this does not help, the problem is not caused by connection pooling.
There are several ways to open dotConnect for Google BigQuery documentation:
By default, Windows blocks downloaded CHM files. In most cases, it is enough to right-click the CHM file, select Properties, click Unblock, then click Apply to show the contents.
dotConnect for Google BigQuery supports Entity Framework Core versions 3, 8, 9, 10, and 11 through the Devart.Data.BigQuery.EFCore NuGet package. Classic Entity Framework (EF6) is not supported.
This can happen if an issue occurred during installation. You can add the components to the toolbox manually. For instructions, see Installation.
dotConnect for Google BigQuery assemblies are built with the /platform:anycpu option, so you can use them on both x86 or x64 platforms.