@mjb2000 wrote:
About to implement SambaPOS, but just realized I am using the SA account to access the database. This seems a little bit extreme to use an account that has the power to drop the entire database and make pretty much and changes you can think of.
Plus, these credentials are stored unencrypted in C:\ProgramData\SambaPOS
If I was to create a new SQL user, what would be a sensible set of rights I should assign to the SQL user to be able to fully use SambaPOS? (I understand that when create a DB for the first time, perhaps we would have to use the SA account, but after everything is up and running, is it possible move to a 'safer' SQL user?
Posts: 8
Participants: 3