Hangfire.SqlServer 1.7.28

SQL Server 2008+ (including Express), SQL Server LocalDB and SQL Azure storage support for Hangfire (background job system for ASP.NET applications).

Showing the top 20 packages that depend on Hangfire.SqlServer.

Packages Downloads
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring long-running, short-running, CPU or I/O intensive tasks inside ASP.NET application. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. http://hangfire.io/
5
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring long-running, short-running, CPU or I/O intensive tasks inside ASP.NET application. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. http://hangfire.io/
6
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring long-running, short-running, CPU or I/O intensive tasks inside ASP.NET application. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. http://hangfire.io/
7
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring, long-running, short-running, CPU or I/O intensive tasks inside ASP.NET applications. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. https://www.hangfire.io/
3
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring, long-running, short-running, CPU or I/O intensive tasks inside ASP.NET applications. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. https://www.hangfire.io/
5
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring, long-running, short-running, CPU or I/O intensive tasks inside ASP.NET applications. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. https://www.hangfire.io/
6
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring, long-running, short-running, CPU or I/O intensive tasks inside ASP.NET applications. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. https://www.hangfire.io/
10
Hangfire
Incredibly easy and reliable way to perform fire-and-forget, delayed and recurring long-running, short-running, CPU or I/O intensive tasks inside ASP.NET application. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. http://hangfire.io/
7
Hangfire
Incredibly easy and reliable way to perform fire-and-forget, delayed and recurring long-running, short-running, CPU or I/O intensive tasks inside ASP.NET application. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. http://hangfire.io/
6

https://www.hangfire.io/blog/ Please see https://docs.hangfire.io/en/latest/upgrade-guides/upgrading-to-hangfire-1.7.html to learn how to upgrade from 1.6.X. 1.7.28 • Fixed – Possibly fixed CPU consumption problems and high amounts of fetching queries after deploys to IIS. • Fixed – No more than a single long-polling query is allowed per storage instance when using sub-second polling. • Fixed – Don't depend on thread pool when sending heartbeats for active jobs to avoid problems when it's starved. 1.7.25 • Fixed – Avoid any blocked rows when removing inactive servers from the `Server` table. 1.7.24 • Changed – Don't use the `readcommittedlock` table hint when not required. • Project – Stop using `TransactionScope` class in tests, re-create database instead. • Project – Make it possible to run SQL Server tests on Mono on Linux. 1.7.23 • Fixed – `NotImplementedException` in `Transaction.EnlistPromotableSinglePhase` when running on Mono. 1.7.21 • Fixed – Ensure connection is released when exception is thrown when during lock release. • Fixed – "A network-related or instance-specific error" when using `DisableConcurrentExecution` for long-running jobs. 1.7.20 Please see https://www.hangfire.io/blog/2021/03/19/hangfire-1.7.20.html for details, manual changes required for those who already migrated to Schema 6 and 7. This problem will be also fixed in a new migration in Hangfire 1.8.0. • Fixed – `Schema 6` migration now fixes problem that prevents 2,147,483,648th job from being enqueued. 1.7.19 • Fixed – Return `null` instead of throwing FormatException when job id can't be parsed. • Project – Run the entire Hangfire.SqlServer test suite against the new Microsoft.Data.SqlClient package. 1.7.18 • Added – `SqlServerStorageOptions.DeleteExpiredBatchSize` option to remove more expired records in a single pass. • Fixed – Don't throw from `SqlServerStorage.ToString` method when using custom factory or existing connection. 1.7.17 • Fixed – SqlException "Incorrect syntax near 'throw'" after upgrading to 1.7.15 when using SQL Server 2008 or 2008R2. 1.7.16 • Fixed – Blocking problems when using multiple storages with the same queue names in the same process (appeared in 1.7.9). 1.7.15 • Fixed – Avoid deadlocks when using the `SetJobParameter` method without introducing issues for older schemas. • Fixed – Remove duplicate sorting in the `SqlServerMonitoringApi.GetJobs` method which is used by a lot of queries. 1.7.14 • Fixed – Duplicate entries in the `JobParameters` table after upgrading to version 1.7.13. • Fixed – Extensive retries on a method that has a retry attribute after upgrading to 1.7.13. • Fixed – "ArgumentException: An item with the same key has already been added. Key: RetryCount" in `SqlServerMonitoringApi`. 1.7.13 • Added – `UseIgnoreDupKeyOption` for SQL Server storage configuration (changes to [Set] and [Hash] tables required). • Fixed – Don't truncate too long keys silently, throw exceptions instead. • Fixed – Add missing null checks for methods in the `SqlServerWriteOnlyTransaction` class. • Fixed – Change `holdlock` hint to `xlock` in `merge` statements in transaction to prevent deadlocks. • Fixed – Don't rethrow "Lock request time out period exceeded" exceptions from expiration manager. • Fixed – Increase [Server].[Id] column's length to 200 for new installations. 1.7.10 • Changed – Use `XACT_ABORT` option for `ExpirationManager` queries. • Changed – Don't rely on implicit rollback when disposing transactions. • Fixed – `NullReferenceException` in logs thrown from `SqlInternalTransaction.Rollback` method. 1.7.9 • Changed – Implement long polling fetch for sub-second polling delays without `sp_getapplock`. • Fixed – Don't leak `DbConnection` instance when an exception occurs during its opening. • Fixed – Can not obtain connection from the pool exception after database was offline. • Fixed – High number of waits in SQL Server when Hangfire Servers are idle. 1.7.8 • Added – Support for Microsoft.Data.SqlClient package when using a custom connection factory (Part II). • Fixed – Remove `System.Data.SqlClient` dependency from `SqlCommandBatch` and `ExpirationManager`. 1.7.7 • Added – Add support for Microsoft.Data.SqlClient package when using custom connection factory (Part I). • Added – Add `UseFineGrainedLocks` option to avoid deadlocks in some theoretical cases. • Added – Add missing overload for `UseSqlServerStorage` with connection factory parameter only. • Added – Expose the SqlServerObjectsInstaller.GetInstallScript method (by @altso). • Fixed – Make command batching working on .NET Core when using System.Data.SqlClient 4.7.0 and higher. • Fixed – Permit dash characters (`-`) in schema names (by @kendaleiv). • Fixed – Escape square bracket characters in schema names. • Project – Add support for `netcoreapp3.0` target in Hangfire.SqlServer.Tests. • Project – Take schema name from constant in Hangfire.SqlServer.Tests (by @kendaleiv). • Project – Make Hangfire.SqlServer.Tests work on Linux in Travis CI environment. 1.7.4 • Fixed – Potential deadlocks cause by suboptimal queries when using `SlidingInvisibilityTimeout` fetching. • Fixed – Prevent zero delays between fetch retry attempts when lock acquisition failed without blocking. • Fixed – Specify float precision explicitly for the `Score` column in the `AddToSet` method. 1.7.3 • Fixed – Wrong error message in migration script, when @CurrentSchemaVersion has a NULL value (by @penenkel). 1.7.2 • Fixed – Occasional "DataException: Error parsing column" error when using blocking fetch. 1.7.1 • Changed – Use blocking fetch implementation only for sub-second polling intervals. • Fixed – Don't fail with an exception when can't connect to MSSQL instance during start-up. • Fixed – Don't access the `JobQueue` table when using blocking query and don't have results. 1.7.0 • Added – Full .NET Core 2.0 support by explicitly targeting .NET Standard 2.0. • Added – `Schema 7` migration to fix the `IX_HangFire_Set_Score` index to include the `Key` column. • Added – `Schema 6` migration with less indexes, better physical layout and `bigint` support (disabled by default). • Added – Blocking fetch support for sliding expiration-based fetch to avoid excessive polling. • Added – `SqlServerStorageOptions.EnableHeavyMigrations` switch to automatically install even heavy migrations. • Added – `SqlServerStorageOptions.DisableGlobalLocks` property to avoid custom locking scheme. • Added – `SqlServerStorageOptions.UsePageLocksOnDequeue` property to use less CPU consuming fetch. • Added – Callback method to allow to open the database with impersonation (by @BjoernHund). • Added – `SqlServerStorageOptions.UseRecommendedIsolationLevel` option to set the minimum possible level. • Changed – Identity columns either converted to the `bigint` type, or entirely removed. • Changed – Clustered indexes were organized according to the access patterns of their tables. • Changed – Most of secondary indexes were either removed or made filtered. • Changed – Optimize sliding-expiration-based fetching to use even less CPU time. • Changed – Use write reordering and fine-grained locking scheme to improve parallelism. • Changed – Monitoring API doesn't check state data to see state transition time. • Changed – Allow to use zero-based poll interval when sliding invisibility timeout. • Changed – Short paths for the `CreateExpiredJob` method to avoid some round-trips. • Changed – Set `SqlParameter` types explicitly to not to duplicate query plans. • Changed – Batch support for `AddToQueue` method when default provider is used. • Changed – Check `FetchedAt` has expected value to prevent prolonging others' work. • Changed – Use more recent Dapper 1.50.7 on all platforms except .NET Framework 4.5. • Changed – Dapper package is internalized now even on .NET Core to avoid possible conflicts. • Fixed – Avoid unnecessary waits in state changer when job was already expired. • Fixed – Cannot resolve the collation conflict in `CountersAggregator`. • Fixed – Background processing stops when identity columns exceed the `Int32.MaxValue`. • Fixed – Slowdown of scheduled jobs due to the missing index on the `[Set]` table.

.NET Framework 4.5

.NET Standard 1.3

.NET Standard 2.0

Version Downloads Last updated
1.8.12 6 05/28/2024
1.8.11 3 05/28/2024
1.8.10 3 05/28/2024
1.8.9 3 05/28/2024
1.8.7 2 05/28/2024
1.8.6 2 05/28/2024
1.8.5 4 05/28/2024
1.8.4 2 05/28/2024
1.8.3 4 07/12/2023
1.8.2 2 05/28/2024
1.8.1 2 05/28/2024
1.8.0 4 05/28/2024
1.7.37 3 05/28/2024
1.7.36 2 05/28/2024
1.7.35 2 05/28/2024
1.7.34 4 05/28/2024
1.7.33 2 05/28/2024
1.7.32 3 05/28/2024
1.7.31 2 05/28/2024
1.7.30 2 05/28/2024
1.7.29 3 05/28/2024
1.7.28 2 05/28/2024
1.7.27 2 05/28/2024
1.7.26 2 05/28/2024
1.7.25 4 05/28/2024
1.7.24 1 05/28/2024
1.7.23 3 05/28/2024
1.7.22 3 05/28/2024
1.7.21 2 05/28/2024
1.7.20 2 05/28/2024
1.7.19 4 05/28/2024
1.7.18 5 05/28/2024
1.7.17 3 05/28/2024
1.7.16 3 05/28/2024
1.7.15 3 05/28/2024
1.7.14 3 05/28/2024
1.7.13 3 05/28/2024
1.7.12 10 04/10/2023
1.7.11 1 05/28/2024
1.7.10 1 05/28/2024
1.7.9 2 05/28/2024
1.7.8 2 05/28/2024
1.7.7 2 05/28/2024
1.7.6 2 05/28/2024
1.7.5 2 05/28/2024
1.7.4 2 05/28/2024
1.7.3 4 05/28/2024
1.7.2 4 05/28/2024
1.7.1 2 05/28/2024
1.7.0 4 05/28/2024
1.6.30 3 05/28/2024
1.6.29 2 05/28/2024
1.6.28 2 05/28/2024
1.6.27 2 05/28/2024
1.6.26 2 05/28/2024
1.6.25 1 05/28/2024
1.6.24 5 05/28/2024
1.6.23 3 05/28/2024
1.6.22 2 05/28/2024
1.6.21 3 05/28/2024
1.6.20 2 05/28/2024
1.6.19 4 05/28/2024
1.6.18 2 05/28/2024
1.6.17 2 05/28/2024
1.6.16 4 05/28/2024
1.6.15 3 05/28/2024
1.6.14 4 05/28/2024
1.6.13 4 05/28/2024
1.6.12 3 05/28/2024
1.6.11 2 05/28/2024
1.6.10 2 05/28/2024
1.6.9 2 05/28/2024
1.6.8 2 05/28/2024
1.6.7 2 05/28/2024
1.6.6 4 05/28/2024
1.6.5 2 05/28/2024
1.6.4 2 05/28/2024
1.6.3 3 05/28/2024
1.6.2 2 05/28/2024
1.6.1 2 05/28/2024
1.6.0 6 05/28/2024
1.5.9 3 05/28/2024
1.5.8 2 05/28/2024
1.5.7 3 05/28/2024
1.5.6 2 05/28/2024
1.5.5 2 05/28/2024
1.5.4 2 05/28/2024
1.5.3 3 05/28/2024
1.5.2 3 05/28/2024
1.5.1 2 05/28/2024
1.5.0 5 05/28/2024
1.4.7 2 05/28/2024
1.4.6 3 05/28/2024
1.4.5 2 05/28/2024
1.4.3 3 05/28/2024
1.4.2 2 05/28/2024
1.4.1 3 05/28/2024
1.3.3 3 05/28/2024
1.3.2 2 05/20/2024
1.3.1 2 05/28/2024
1.3.0 5 05/28/2024
1.2.2 2 05/28/2024
1.2.1 2 05/28/2024
1.2.0 2 05/28/2024
1.1.1 2 05/28/2024
1.1.0 5 05/28/2024
1.0.2 1 05/28/2024
1.0.1 1 05/28/2024
1.0.0 3 05/17/2024
0.9.1 2 05/28/2024
0.9.0 4 05/20/2024
0.8.3 2 05/28/2024
0.8.2 2 05/28/2024
0.8.1 4 05/17/2024
0.8.0 2 05/28/2024
0.7.5 3 05/28/2024
0.7.4 4 05/28/2024
0.7.3 3 05/28/2024
0.7.1 3 05/28/2024
0.7.0 2 05/28/2024