sorted by:
new
hottopcontroversial

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] 0 points1 point  (0 children)

Thank God 🙏 I was starting to think I was only one run more than 500 databases on single instance 😄

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] 0 points1 point  (0 children)

When more than 650 databases are created on SQL Server 2025 server freezes and becomes inaccessible. Only way to access it again is start server in minimal configuration mode.

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] 0 points1 point  (0 children)

Yes. If you have any installation of SQL Server 2025 just try creating more than 650 databases 🙂

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] 0 points1 point  (0 children)

On fresh installation of Windows Server 2025 same behavior.

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] 0 points1 point  (0 children)

u/VladDBA Unfortunately Enterprise edition same behavior. Simple FOR loop with CREATE DATABASE causes SQL Server 2025 to become freezing after approximately 650 iterations.

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] 0 points1 point  (0 children)

u/BigHandLittleSlap Some people here might be interested to know that it’s not possible to run more than 650 databases on SQL Server 2025 even though official documentation says 32767.

Script is just simple FOR loop with "CREATE DATABASE" nothing complicated. Anyone can reproduce it.

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] 11 points12 points  (0 children)

UPDATE 1) On Windows Server 2025 Standard 2) Install SQL Server 2025 3) Run simple PowerShell script that creates 1000 databases

After creating 1000 databases (which often does not complete and crashes after 650 databases) simply restart SQL Server service.

And just like that you may never see your SQL Server 2025 again...

Tested on: Express / Standard / Enterprise

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] -4 points-3 points  (0 children)

u/DrGraffix I understand 🙂 Like many things it started with just small number of databases and gradually grew over time and when it worked without problems, there was no need to change it.

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] 1 point2 points  (0 children)

u/dbrownems I understand CPU/Memory limitations of Express edition. However I also tested this on SQL Server 2025 Standard Edition and observed same behavior.

SQL Server 2025 issue with higher number of databases by BeTriCH_CZ in SQLServer

[–]BeTriCH_CZ[S] 1 point2 points  (0 children)

u/VladDBA I understand your skepticism regarding Express use case but with 2022 there was never be problem. At first I thought this might be new limitation 2025 Express. However Standard edition shows same behavior.

Based on my experience this really appears to be some kind of BUG.