Remove irrelevant caveat- the classic provider did not include hub names in the table names, so there can't be conflicts.

Author: ascott18

README.md

@@ -79,8 +79,6 @@ services.Configure<SqlServerOptions>(Configuration.GetSection("SignalR:SqlServer
 
 As mentioned above, if SQL Server Service Broker is not available, messages will not always be transmitted immediately since a fallback of periodic querying must be used.
 
-While this uses the same table schema as the classic ASP.NET SignalR SQL Server backplane, the message payloads are completely different. If you are migrating, consider configuring a different `SchemaName` to prevent conflicts.
-
 ### Performance
 
 This is not the right solution for applications with a need for very high throughput, or very high degrees of scale-out. Consider Redis or Azure SignalR Service instead for such cases. You should always do an appropriate amount of testing to determine if a particular solution is suitable for your application.