CODEWITHSUNDEEP
signalsazure-sql-database
dougajmcdonald
dougajmcdonald

Reputation: 20047

SignalR and SQL backplaning on Azure - Schema information

We recently attempted to configure SignalR with backplaning on SQLAzure and ran into a couple of problems.

The one which stands out was the automatic creation of the tables which SignalR requires for the backplane.

I presume we could get round this by manually adding the tables into azure, so I was hoping to gather a little information on the Schema required.

From what I can see on our local version, we have 3 tables:

SignalR.Messages_0
SignalR.Messages_0_Id
SignalR.Schema

What I'm curious about is the significance of the '0' in these tables. Would this increment with the number of hubs? or would simply creating these tables meet the need.

Any information greatly appreciated.

Upvotes: 0

Views: 1335

Answers (2)

Bart Czernicki
Bart Czernicki

Reputation: 3683

If you want to use Azure, you can use a dedicated SQL Server VM (IaaS instead of the SQL Azure DB PaaS option).

Upvotes: 1

evaristo_vidal
evaristo_vidal

Reputation: 46

If you read the signalr documentation says: Microsoft SQL Server 2005 or later. The backplane supports both desktop and server editions of SQL Server. It does not support SQL Server Compact Edition or Windows Azure SQL Database. (If your application is hosted on Windows Azure, consider the Service Bus backplane instead.)

SQL Server as Backplane is not supported on Azure, I am trying to create my own backplane in order to use my own table as central repository for signalr messages.

If you read the code of the library Microsoft.AspNet.SignalR.SqlServer, says that you can configure the number of tables to store messages in. Using more tables reduces lock contention and may increase throughput. This must be consistent between all nodes in the web farm. Defaults to 1.

Upvotes: 3

Related Questions