Hangfire.SqlServer
Tells the bootstrapper to use SQL Server as a job storage,
that can be accessed using the given connection string or
its name.
Configuration
Connection string or its name
Tells the bootstrapper to use SQL Server as a job storage
with the given options, that can be accessed using the specified
connection string or its name.
Configuration
Connection string or its name
Advanced options
Initializes a new instance of the class
with serialized data.
The that holds the serialized object data about the exception being thrown.
The that contains contextual information about the source or destination.
Overloaded dictionary that doesn't throw if given an invalid key
Fixes issues such as https://github.com/HangfireIO/Hangfire/issues/871
Initializes SqlServerStorage from the provided SqlServerStorageOptions and either the provided connection
string or the connection string with provided name pulled from the application config file.
Either a SQL Server connection string or the name of
a SQL Server connection string located in the connectionStrings node in the application config
argument is null.
argument is null.
argument is neither
a valid SQL Server connection string nor the name of a connection string in the application
config file.
Initializes a new instance of the class with
explicit instance of the class that will be used
to query the data.
Initializes a new instance of the class with
explicit instance of the class that will be used
to query the data, with the given options.
Initializes a new instance of the class with
a connection factory class that will be invoked
to create new database connections for querying the data.
Initializes a new instance of the class with
a connection factory class that will be invoked
to create new database connections for querying the data.
Gets or sets whether IGNORE_DUP_KEY was applied to [Hash] and [Set] tables and so MERGE
statements can be replaced by much more efficient INSERT/UPDATE pair. This option allows
to avoid deadlocks related to SERIALIZABLE-level range locks without introducing transient
errors due to concurrency.
Gets or sets the number of records deleted in a single batch in expiration manager. Default
value is 1000, but it can be configured to a higher one when processing throughput is high
enough, so expiration manager becomes the bottleneck.
Gets or sets whether to enable experimental feature of transactional acknowledge of completed
background jobs. In this case there will be less requests sent to SQL Server and better handling
of data loss when asynchronous replication is used. But additional blocking on the JobQueue table
is expected, since transaction commit requires an explicit Commit request to be sent.
Gets or sets the for creating SqlConnection instances.
Defaults to either System.Data.SqlClient.SqlClientFactory.Instance or
Microsoft.Data.SqlClient.SqlClientFactory depending on which package reference exists
on the consuming project.
Gets or sets whether to try automatically query for the current schema on application start
and enable , and
options depending on the current schema version. When storage
is inaccessible on startup, default values will be used for those options.
Gets or sets a default queue provider that will be used when no special provider was
registered for a particular queue.