NServiceBus.SqlServer provides support for sending messages using Microsoft SQL Server or PostgreSQL without the use of a service broker.
It is part of the Particular Service Platform, which includes NServiceBus and tools to build, monitor, and debug distributed systems.
See the SQL Server transport documentation and PostgreSQL transport documentation for more details on how to use it.
Before doing anything else, make sure you have SQL Server up and running in your environment. Also, make sure it is accessible from all the machines in your setup.
<connectionStrings> <add name="NServiceBus/Transport" connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=nservicebus;Integrated Security=True;TrustServerCertificate=true"/> </connectionStrings>
var transport = new PostgreSqlTransport("User ID=<user>;Password=<pwd>;Host=localhost;Port=5432;Database=nservicebus;Pooling=true;Connection Lifetime=0;");
Deployments with multiple endpoints running on PostgreSQL require external connection pooling e.g. using pgBouncer
Consider creating a RAM drive or using a temporary one when running in a cloud VM and hosting your databases to reduce the time required to run acceptance tests.
The tests expect a SQL Server instance to be available.
All tests use the default connection string Data Source=.\SQLEXPRESS;Initial Catalog=nservicebus;Integrated Security=True;TrustServerCertificate=true
. This can be changed by setting the SqlServerTransportConnectionString
environment variable. The initial catalog, nservicebus
, is hardcoded in some tests and cannot be changed.
nservicebus
nservicebus1
nservicebus2
nservicebus
database
receiver
owner db_owner
sender
owner db_owner
db@
owner db_owner
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4