Skip to main content

How to Create a Microsoft SQL Server Database and User in Windows Control Panel

You can create a Microsoft SQL Server database and a corresponding database user within the Windows Control Panel (WCP). This process allows you to set up the necessary infrastructure for applications requiring Microsoft SQL Server connectivity.

You can create a Microsoft SQL Server database and a corresponding database user within the Windows Control Panel (WCP). This process allows you to set up the necessary infrastructure for applications requiring Microsoft SQL Server connectivity.

Important: This feature is only available on Hostek plans that include Microsoft SQL Server support.

Before you begin

You will need:

  • An active Hostek account with Windows Control Panel access.

  • A specific database name for your project.

  • A unique username and password for the database user.

  • The specific database name and the user's permissions requirements.

Create a Microsoft SQL Server Database

  1. Log in to the Windows Control Panel.

  2. Navigate to Databases > Microsoft SQL Server.

  3. Select the Create Database option.

  4. Enter a name for the database.

  5. Select Create.

Create a Microsoft SQL Server User

  1. In the Windows Control Panel, navigate to Databases > Microsoft SQL Server.

  2. Select the Create User option.

  3. Enter a unique username for the account.

  4. Enter a secure password for the user.

  5. Select the database you created in the previous step from the dropdown menu.

  6. Select Create.

Confirm the result

  • The database will appear in the list of available Microsoft SQL Server databases.

  • The user will be listed with the associated database assigned to them.

  • You can successfully log in to the database using the credentials you created.

Limitations

This procedure only creates the database and the user within the Windows Control Panel environment. It does not automatically configure your application's connection string; you must manually update your application's configuration to use the new database name and credentials.

Did this answer your question?