Thank you very much brother. Its working now. Glad it helps! You're welcome.. Sandeep Mewara Jun am. Thank you Sandeep! Manas Bhardwaj Jun am. Thank you Manas! Posted Jun pm Vani Kulkarni. Add your solution here. OK Paste as. Treat my content as plain text, not as HTML. Existing Members Sign in to your account.
This email is in use. Do you need your password? Submit your solution! Privacy policy. This topic describes how to create the most common types of database users. There are eleven types of users. All varieties of SQL Server support database users, but not necessarily all types of users. Management Studio presents 6 options when creating a database user. The following graphic shows the 6 options in the green box, and indicates what they represent.
If you are new to SQL Server, it can be difficult to determine what type of user you want to create. First ask yourself, does the person or group that needs to access the database have a login? Logins in the master database are common for the people who manage the SQL Server and for people who need to access many or all of the database on the instance of SQL Server. For this situation, you will create a SQL user with login. The database user is the identity of the login when it is connected to a database.
The database user can use the same name as the login, but that is not required. This topic assumes that a login already exists in SQL Server. For information about how to create a login, see Create a Login. If the person or group that needs to access the database does not have a login and if they only need access to one or few databases, create a Windows user or a SQL user with password. Also called a contained database user, it is not associated with a login in the master database.
This is an excellent choice when you want to be able to easily move your database between instances of SQL Server. To use this option on SQL Server When connecting as a contained database user you must provide the name of the database as part of the connection string. To specify the database in Management Studio, in the Connect to dialog box, click Options , and then click the Connection Properties tab. This is common when people outside of your organization for example customers are connecting to your SQL Server.
For people inside your organization, Windows authentication is a better choice, because they won't have to remember an additional password, and because Windows authentication offers additional security features such as Kerberos. A user is a database level security principal. Logins must be mapped to a database user to connect to a database. Or is there a better solution exists? Assuming you are a member of the Windows Admininstrator group, you can put the server in Single User mode, you could try this -.
My read of the question was that the server is set up to use SQL authentication only, and perhaps you don't know the sa password or any other SQL login credentials? If so, you might be able to change the authentication mode.
For SQL Server default instances, it's stored in the registry at:. You can try changing it to 2, restart the MSSQL service, then try to get into the SQL management studio after logging into the machine as an administrator. How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.
Learn more. How to create a new instance of Sql Server Ask Question. Asked 13 years, 4 months ago.
0コメント