Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
MS SQL SERVER 2008
I have a database. Several operators via my program can interact with it. Each operator have its own name. At present, I create a login and corresponding user name for each operator. Is it good idea ? Number of operators can grow …
maybe, there’s some good practices about it ?
If you’re are talking about database users… No, that is just a really bad ideia!
Application Users are not the same as Database users. You should really have your user tables with authentication and access control. This is a module of your application.
Database user’s and roles and schemas are used to distinguish between functional modules of your projects, to give structure to your enterprise and to separate environments such as testing, pre-production, production and so forth.