{"id":57416,"date":"2021-12-30T11:00:00","date_gmt":"2021-12-30T16:00:00","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=57416"},"modified":"2024-02-08T11:39:29","modified_gmt":"2024-02-08T16:39:29","slug":"domainless-access-to-ms-sql-server-tutorial","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/domainless-access-to-ms-sql-server-tutorial","title":{"rendered":"Domainless Access to MS SQL Server Tutorial"},"content":{"rendered":"\n

Traditionally, there have been two options to authenticate into Microsoft\u2019s SQL Server: Integrated Windows Authentication (managed by Active Directory) or SQL Server\u2019s built-in authentication scheme. The first requires a domain controller, while the latter sends (encrypted) credentials over the wire when its \u201cForce Encryption\u201d flags are configured. In both cases, there is additional IT management overhead required to get users access to this particular server. <\/p>\n\n\n\n

There\u2019s now a third method: local group access through JumpCloud and Integrated Windows Authentication. It enables remote users to work with SQL Server without passing credentials around the web and<\/em> without the need for users to run their access requests over a VPN and through the domain controller.<\/p>\n\n\n\n

This article is a follow-up to a previous example that discusses domainless Windows File Sharing<\/a>. The methods are similar, except in this example IT administrators in smaller organizations gain the additional advantage of enabling DBAs to work with SQL Server without having to stand up a domain controller. The DBA gains access to SQL Server with the same credentials they use to log into their devices and cloud services, with a single managed identity that integrates with fully-supported Windows authentication methods and SQL Server. This is all possible without the introduction of any software other than the JumpCloud agent.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This tutorial outlines the steps involved to create and manage local user groups for SQL Server through the JumpCloud console in addition to outlining how to harden Integrated Windows Authentication (NTLM) for better security. You can also monitor access logs for any suspicious events with Directory Insights<\/a>. JumpCloud accounts are a prerequisite for this workflow.<\/p>\n\n\n\n

Prerequisites<\/h3>\n\n\n\n