It is definitely good to know the implications of choosing a default database.
A few years back I worked with the Remedy help desk system. I do not know if it has been changed for this issue, but back then the default database for the Remedy login had to be the Remedy database. The account also needed to be the db owner account as shown in database properties, or be set to use a default schema of dbo. This is because Remedy would create tables as required, and often used the syntax "CREATE TABLE xxx". The read statements typically took the form "SELECT FROM dbo.xxx" or "SELECT FROM remedydb.dbo.xxx", so you needed to make sure the defaults that applied to the table creates would work with the explicit names used for the select statements.
You are unlikely to have a one-size-fits-all solution to allocating the default database for a user, but you definitely need to know any special needs the user account has, and the implications around the database you choose.
Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 1 Dec 2016
: now over 39,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Quote: "When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist." - Archbishop Hélder Câmara