Connect to SQL Server Management Studio [closed] - sql-server

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I'm new to this, and i don't understand how to do it, so i went through this tutorial here:
http://blogs.msdn.com/b/bethmassi/archive/2011/02/18/step-by-step-installing-sql-server-management-studio-2008-express-after-visual-studio-2010.aspx
And i installed everything i needed.
The point is when i get to the login form, i choose:
Windows Authentication
So it means i don't need to enter data. My problem is with the server name which by default is: (local).
I tried to do like this:
Go to SQL Server Configuration Manager > SQL Server Services > In Right Side window show all the servers which may stop. If you are using "SQLEXPRESS" then , Right click on SQL Server(SQLEXPRESS) and start. After try to connect server... I had same problem but I resolved by these steps.
But there was nothing under SQL Server Services. Someone please help me with this..
Thanks

It seems like you've only installed the client tools, so there is no local database engine to connect to. That tutorial assumed you had already installed SQL Server Express as part of Visual Studio setup.
You should uninstall the version of Management Studio you have now, IMHO. Then you need to download SQLEXPRWT_x64_ENU.exe from this link:
http://www.microsoft.com/en-us/download/details.aspx?id=43351
Run the installer, and on the feature selection screen, make sure you choose Database Engine Services as well as Management Tools - Complete. On the instance configuration screen, it should be pre-selected to SQLEXPRESS. On the database engine configuration screen, you want to make sure you have mixed authentication, enter a secure password for the sa account, and add your current user to the list of administrators. These steps will help prevent you from getting locked out of the instance if you log on as a different user or you forget the sa password.
(Sorry if I am remembering those screens out of order.)

Related

How to enable "sa" account in SQL Server 2019 Express after login with Windows Authentication mode [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 24 days ago.
Improve this question
I have installed SQL Server Express 2019 on my machine and after installation, I am able to login into server using the Windows Authentication method like
And as you can see the sa account has been disabled by default
So I tried to enable the sa account like
But I am getting this error message
Cannot alter the login 'sa', because it does not exist or you do not have permission.(Microsoft SQL Server, Error:15151)
Even when I tried to change the server authentication mode from Windows Authentication Mode to SQL Server and Windows Authentication Mode at
I am facing this error:
The EXECUTE permission was denied on the object 'xp_instance_regwrite', database 'mssqlsystemresource', schema 'sys'. (Microsoft SQL Server, Error; 229)
So it looks like I have no/not granted any permission to do any anything! when login with Windows which apparently is my only option to get into server!(this is also happening when I tried to create new user!)
How can I get this to act as an administrator for DB when I login?
I have already seen and tried this post.
This is poor practice in the first place. If you need a local admin account you should create a different login such that attackers and automated tools won't be able to just assume the user name.
But remember: I said, "If". You can get admin/sa rights to administer the server (or create your initial local login) by logging into the computer (not the database) with the local administrator account. Then you can use using Windows Authentication from that account to access the database server as a server administrator.

Connect to Virtual Machine using AAD Account [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last month.
Improve this question
I am unable to login my office 365 account on my virtual machine. This my logs when I run dsregcmd /status on cmd.
I tried to edit the VM using this command, still not working.
enablecredsspsupport:i:0
authentication level:i:2
Also, I added Role assignment: Virtual Machine Administrator Login and Virtual Machine User Login
And I have this on my extension: AADLoginForWindows
I tried to reproduce the same in my environment and got the results like below:
While creating virtual machine in management Make sure to check login with Azure Ad like below:
In your virtual machine check whether extension is added:
Try to assign role assignment Virtual Machine User Login or
Virtual Machine Administrator Login to user
Now, Download Rdp file and login. When I tried to check with dsregcmd /status Azure AD joined successfully:
To Login with Azure Ad credentials account try to change Network Level Authentication access in RDP to avoid an error:
In RDP -> search box type allows remote connection to this computer -> uncheck the box like below:
Now edit your RDP downloaded file, try to include
enablecredsspsupport:i:0
authentication level:i:2
username:s:xxxxx.onmicrosoft.com (Add your username here)
domain:s:AzureAD
When I try to connect with login AzureAd\UPN with user it connected successfully like below:

SSMS keeps using NTLM rather than Kerberos on one computer

On my computer SQL Server Management Studio is using NTLM rather than Kerberos as expected. Which is causing issues accessing linked servers.
I wouldn't think this would be a very hard issue to fix but there are a few weird points that prompted me to post here
If I log into another computer and launch SSMS I have kerberos
If someone else logs into my computer the auth_type is NTLM
I do get a Kerb ticket
My AD admin is assuring me that my user settings are correct and I match identically someone else that I know is not having this issue
My data architect suggested having me computer re-imaged to see if some software that I installed is making that happen but that did not help the issue if I only install SSMS on top of the fresh image.
I am currently using SSMS 2016
Any advice would be appreciated

Stuck on Initial SQL Server Configuration

I'm working with a fresh installation of Server 2008 R2. I'm new to all things administration, so this could be a simple issue.
I'm installing SQL Server 2008 R2, and I've reached a point where it's asking me to create Service Accounts. I'm really just trying to do bare minimum here to get started with SharePoint.
I'm getting an error "The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password."
I get this error for the Analysis Services service as well.
Can someone explain to me what this means and how I can proceed with the installation?
After some searching I saw that the issue might lie in the fact that I was signed in as a local Administrator, so I created another user in Users via Computer Management and the same issue is occurring.
The SQL installation is not asking to create service accounts. It is asking which service accounts it should use to execute SQL Server. If you need to create accounts for this, you will need to do that through the usual user management tools, whether Active Directory or Local Users.
Depending on the purposes of this machine, you may be fine using one of the built in accounts, such as Network Service. Not a best practice, but maybe adequate for a short lived demo/dev machine.
More details on MSDN.

How to fix Distributed Transaction Manager (MSDTC) has been disabled errors [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
We are using transaction scope features of ASP.NET to manage distributed transaction for that we need to enable distributed transaction via following link:
The partner transaction manager has disabled its support for remote/network transactions
Its works well with SQL Server 2005 and Windows Server 2003 but when it comes to Windows Server 2008 server and SQL Server 2005 we are getting following error, still we followed the same steps provided in above link:
Windows Server 2008 + SQL Server 2005
+ Network access for Distributed Transaction Manager (MSDTC) has been
disabled. Please enable DTC for
network access in the security
configuration for MSDTC using the
Component Services Administrative
tool.
On my blog I discuss a fix: Fix MSDTC (Microsoft Distributed transaction coordinator)
This post will help you how set setup and check communication of MSDTC between servers.
Please check:
Network
Firewall
ACL permission
You can config your severs and test the MSDTC by using following tool.
DTCTester: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q293799
Windows 2008 has a different security model than windows 2003, and it's driven by xml file which contains a whole shedload of security entries. I've not went into it in detail, as yet, so all I can do is give you a start.
Select Admin Tools-> Security Configuration Wizard.
Find your current security policy (don't know where it is stored, but technet will tell you).
Go down the list, and ensure Distributed Transactions are checked. They are not checked by default.
Apply the new policy.
Be careful with using this utilty, as u could serious knacker your system, or open a security hole.
Hope that helps.
Bob.

Resources