Got a topic for discussion, I've developed an app in VB.Net, it uses SQL (any version should be compatible).
Currently I connect without any specific credentials, just using windows authentication. Which works fine as long as the SQL is installed locally. My app also creates a separate SQL instance, the database and several tables.
Currently the app is a clickonce installation, which as you may know runs under each user login separately. So if another user would login to the desktop (Windows versions), they would have to install the app again. (That will be changed later, with a setup app). The problem is that the SQL may have been installed under the other user login, so the second user has no access to SQL, Also if the user does not have SQL installed they need to get a copy of express & install it manually.
Here where things get fuzzy. If I give the user instructions on setting up SQL, should I suggest Mixed Authentication and setup my connection string with a user name and password? That would solve access to SQL for all users logging in individually, but then what if they already have a version of sql installed? Can they change it to mixed? Would that possibly cause issues with other apps that may use SQL?
Then there's the issue of SQL being installed on an other Workstation or Server. My app can browse for any SQL server & instance, but again if my connection string username & password aren't setup on the SQL Server my app will not work.
So what would some recommendations be? Trying to appease the majority of clients.