Glad you got it figured out. There are "hacks" that can be used, but I don't generally post those publicly. To continue this discussion, please ask a new question.
Get answers from your peers along with millions of IT pros who visit Spiceworks. Best Answer. There are 2 ways to do it: Hold down the shift button while right-clicking on the SSMS executable or shortcut and clicking on "Run as a different user". It will then ask you for the user and password of the other user and if successful, it will launch SSMS as that user.
It will then prompt you for the password and if correct will launch SSMS as that user. View this "Best Answer" in the replies below ». Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». You can't change the sa password without access to SQL Server. Download other installer. I know, that SSMS installer is misleading You really need to download the installer with the local instance.
Show 4 more comments. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. On the Server Roles page, you can assign the server-level role to the new login by clicking the checkbox next to the role. By default, the public role is assigned to a new login. Additionally, let us assign the sysadmin role by clicking on the checkbox next to sysadmin. With sysadmin server role, user can perform any activity on the server and has full control.
It lists all the databases on the server. To map your new login, just select checkboxes next to databases for which you want map this login to access a database. In the below figure AdventureWorks database is selected. The new login is now listed under the User column for AdventureWorks You can change the user name if you want it to give a different name than your login name.
Just click on the name and re-type whichever name you want for the user. If you want more databases associated with your login, then just click the checkbox next to the database, and it will be mapped with the login. Posted yesterday priyamtheone. Add a Solution. My Guess: The credentials under which the Web server's process or thread is running must map to a valid SQL Server login in order to establish a connection. Maciej Los 22hrs ago. Bruno, it sounds like an answer.
Thank you Maciej, even it is a wild guess ;. Accept Solution Reject Solution. I would guess the problem is the account under which the web service runs.
See this Posted 22hrs ago 0x01AA. Thank you. So it took me a while to get a grab on it through other references. You need to create them explicitly. Creating them and giving them respective privileges for your database solved the problem.
0コメント