| author | rwestMSFT | |
|---|---|---|
| ms.author | randolphwest | |
| ms.date | 11/18/2024 | |
| ms.service | sql | |
| ms.topic | include | |
| ms.custom |
|
When you connect to your [!INCLUDE ssnoversion-md] instance using the system administrator (sa) account for the first time after installation, it's important for you to follow these steps, and then immediately disable the sa account as a security best practice.
-
Create a new login, and make it a member of the sysadmin server role.
-
Depending on whether you have a container or non-container deployment, enable Windows authentication, and create a new Windows-based login and add it to the sysadmin server role.
-
Otherwise, create a login using [!INCLUDE ssnoversion-md] authentication, and add it to the sysadmin server role.
-
-
Connect to the [!INCLUDE ssnoversion-md] instance using the new login you created.
-
Disable the
saaccount, as recommended for security best practice.