SQL Server 2025 Databases
SQL Server 2025 is available on all ASP.NET (Windows) hosting plans, alongside SQL Server 2022. You create and manage SQL Server 2025 databases in Plesk exactly like your other SQL Server databases, and your applications connect to them over the public hostname below.
Server Details
| Setting | Value |
|---|---|
| Server hostname | sql2025-001.adaptivewebhosting.com |
| Port | 1433 (the default, so you do not need to add it) |
| Authentication | SQL Server Authentication, with the database user you create in Plesk |
| Encryption | Encrypt=True;TrustServerCertificate=True; |
| Compatibility level for new databases | 170 (SQL Server 2025) |
Note: Plesk lists this server as .\MSSQLSERVER2025. That is the server's internal name and only works on the server itself. From your application, SSMS or Visual Studio, always use sql2025-001.adaptivewebhosting.com.
If an existing connection string of yours uses sql2019-001.adaptivewebhosting.com, it already points to this SQL Server 2025 server and keeps working. You can switch it to sql2025-001.adaptivewebhosting.com at any time.
Creating a SQL Server 2025 Database
- Log in to Plesk
- Go to Websites & Domains and click Databases
- Click Add Database
- In the Database server dropdown, select MSSQLSERVER2025
- Enter a database name
- Create a database user with a strong password
- Click OK
Connecting with SQL Server Management Studio (SSMS)
- Use a current release of SSMS (version 21 or later) so the new SQL Server 2025 data types are shown correctly
- Server type: Database Engine
- Server name:
sql2025-001.adaptivewebhosting.com - Authentication: SQL Server Authentication
- Login / Password: the database user and password you created in Plesk
- Encryption: Mandatory, and tick Trust server certificate
- Click Connect and open your database from the list
Connection Strings
ADO.NET / ASP.NET Core (appsettings.json)
{
"ConnectionStrings": {
"DefaultConnection": "Server=sql2025-001.adaptivewebhosting.com;Database=YOUR_DATABASE;User Id=YOUR_DB_USER;Password=YOUR_PASSWORD;Encrypt=True;TrustServerCertificate=True;MultipleActiveResultSets=true;"
}
}
Entity Framework Core
builder.Services.AddDbContext<AppDbContext>(options =>
options.UseSqlServer(builder.Configuration.GetConnectionString("DefaultConnection")));
Recent versions of Microsoft.Data.SqlClient and EF Core are recommended if you want to use the new json and vector data types from your application. Older drivers still connect and work with all standard data types.
Database Users Belong to One Server
A database user is created on the server you selected in Plesk. A user created on SQL Server 2025 does not exist on SQL Server 2022, and the other way round. If you connect to the wrong server, you will see Login failed for user ... (error 18456).
Important: repeated failed logins automatically block your IP address from both SQL Servers for a period of time. If your connection suddenly starts timing out after several failed logins, double-check the hostname and user in your connection string, then open a support ticket from the same network and we will lift the block.
What's New in SQL Server 2025 That You Can Use
| Feature | Example |
|---|---|
Native json data type |
DECLARE @doc json = N'{"name":"Ada"}'; |
vector data type for AI embeddings and similarity search |
VECTOR_DISTANCE('cosine', @a, @b) |
| Regular expressions | REGEXP_LIKE, REGEXP_REPLACE, REGEXP_SUBSTR, REGEXP_COUNT, REGEXP_INSTR, REGEXP_SPLIT_TO_TABLE |
| JSON aggregates | JSON_OBJECTAGG, JSON_ARRAYAGG |
| String concatenation operator | SELECT FirstName || ' ' || LastName |
| New built-in functions | CURRENT_DATE, UNISTR, BASE64_ENCODE / BASE64_DECODE, PRODUCT() |
Compatibility level: some of these features (for example REGEXP_LIKE and REGEXP_SPLIT_TO_TABLE) need database compatibility level 170. New databases are created at level 170. A database moved from an older SQL Server keeps its previous level; open a support ticket if you would like it raised to 170.
Moving an Existing Database to SQL Server 2025
- Create a new, empty database on MSSQLSERVER2025 in Plesk (see above)
- Import your
.bakfile with Import Dump, as described in How do I upload, import, or migrate my existing SQL Database? - Update your application's connection string to
sql2025-001.adaptivewebhosting.comand the new database name and user
Good to know: SQL Server backups can only be restored to the same or a newer version. A database backed up from SQL Server 2025 cannot be restored to SQL Server 2022 or older, so keep a copy of your original database until you have tested your application on SQL Server 2025.
SQL Server 2025 or SQL Server 2022?
- SQL Server 2025 - choose it for new projects and when you want the new JSON, vector and regular expression features.
- SQL Server 2022 - fully supported; there is no need to move existing databases unless you want the new features.
Troubleshooting
| Error | Usual cause and fix |
|---|---|
| Login failed for user (error 18456) | Wrong password, or the user exists on the other SQL Server. Check that the hostname is sql2025-001.adaptivewebhosting.com for a SQL Server 2025 database. |
| Error 25 or 26, "network-related or instance-specific error" | The connection string uses .\MSSQLSERVER2025, localhost or an instance name. Replace it with sql2025-001.adaptivewebhosting.com. |
| "The certificate chain was issued by an authority that is not trusted" | Add TrustServerCertificate=True; - see Disabling SSL Verification in SQL Server Connection String. |
| Timeout (error 258) or the server cannot be reached | Your IP may have been blocked after repeated failed logins. Open a support ticket from that network. |
For more connection troubleshooting, see Troubleshooting SQL Server Connection Issues. If you have any questions, open a support ticket and we will be happy to help.
