0
I'm developing a web service using asp.net web api 2 which is to be the owner of my SQL Server database.
To simplify things, I'm writing a separate MVC site that is to use the same database, but rather than go through the api, I'm having this site connect directly to the database to manipulate data.
Separately still, I have a contractor who is developing another system which will post data to the api.
With all 3 of these things in use, is SQL Server going to have problems managing connections because so many things will be connecting to the database at once?
As long as avoid deadlocks - I don't see why it would. – Jay – 2015-09-13T20:44:59.117