Ok, some time ago, I've posted about how you can set limits to connections on SQL Server using the Resource Governor. But what if you can't use it? You always can block logins using a login trigger, but I don't like the idea of having selects running on every login …