Quartz.Net 2.0 Database Providers
Quartz.Net supports quite a few different database providers. This information is embedded inside the Quartz.dll file, but I think it is useful to have it handy. I’ve created a table with the names of all the (as of now) supported database providers. If you would like the full details on the providers, take a look at the dbproviders.properties file.
Here is a summary of all the supported providers along with the key name that you will need to use in your configuration file.
|Microsoft SQL Server, provider V18.104.22.168 in framework .NET V2.0||SqlServer-20|
SQL Server CE
|Microsoft SQL Server Compact Edition, provider V22.214.171.124 in framework .NET V2.0||SqlServerCe-351|
|Microsoft SQL Server Compact Edition, provider V126.96.36.199 in framework .NET V2.0||SqlServerCe-352|
|Microsoft SQL Server Compact Edition, provider V188.8.131.52 in framework .NET V4.0||SqlServerCe-400|
|Oracle, Oracle provider V184.108.40.206||OracleODP-20|
|MySQL, MySQL provider 220.127.116.11||MySql-10|
|MySQL, MySQL provider 18.104.22.168||MySql-109|
|MySQL, MySQL provider 22.214.171.124||MySql-50|
|MySQL, MySQL provider 126.96.36.199||MySql-51|
|OleDb, provider V188.8.131.52 in framework .NET V2||OleDb-20|
If you would like to use a database provider that is not included in the Quartz.Net distribution, you have a couple of options:
- Add your provider to the dbprovider.properties file and recompile the binaries. If you decide to go down this route, please contribute your changes back to the project!
- If you just want to use a different (newer or older) version of a provider that is already included in the distribution, and the providers are compatible, you can use assembly redirection to point Quartz.Net to a specific version of the dll for your provider.
- You can programmatically add the provider. This option however is not available unless you are running the scheduler embedded in your application or have your own windows service for running Quartz.Net.