One choice in the configuration wizard follows you for years: which database holds everything SEPM knows. This page makes that choice with Broadcom's own numbers.
The SEPM database is not a detail. It stores your policies, your client list, your security events, your logs and your reports, which is a complete description of your office's security memory. The configuration wizard offers a default that suits most offices and an alternative that suits big ones, and Broadcom draws the line clearly. Choosing wrong is not fatal, but fixing it later is a migration project, not a toggle.
The two documented paths. Your client count and your resilience needs pick the row, not fashion.
When an admin says "the manager is down", they usually mean the console or the database stopped answering, because the database is the manager's memory. Every group, policy, client record, virus event and report you have ever run is rows in that database. Two consequences follow. Performance problems in SEPM are often database problems in disguise, and backups that skip the database are not backups of anything that matters. Keep both facts in mind for every card below.
Since release 14.3 RU1, the default database installed automatically with SEPM is Microsoft SQL Server Express, which replaced the older embedded database. You do nothing to get it: the configuration wizard installs it, creates the database and wires it up. Broadcom documents this default as supporting up to about 500 clients, which covers the overwhelming majority of single-office installs. It is free, it is supported, and for a few hundred endpoints it is the correct, boring choice. Boring is a compliment in infrastructure.
Three signals say the default is not enough. Client count: beyond roughly 500 clients, Broadcom's guidance is a full SQL Server database, with a single management server on SQL Server documented up to about 18,000 clients. Resilience: failover and load-balancing arrangements between management servers need the full database. Replication: multiple sites that replicate to each other are a SQL Server story too. If none of those describe you, they are not a reason to buy and babysit a SQL Server for a 60-PC office.
The database is chosen in the Management Server Configuration Wizard, at birth. Switching later from Express to full SQL Server is a documented but real migration: new database, data moved, manager repointed, downtime scheduled. Nobody has ever described that weekend as fun. So make the call with your three-year client count, not next month's. If the honest forecast crosses the 500 line or a second site is planned, start on SQL Server and skip the migration entirely.
The order matters. For the full database route, SQL Server and its Native Client are installed and configured before SEPM setup, locally or on a remote server, and the configuration wizard is then pointed at it. The SEPM server will need the right database permissions and network path to that SQL instance, and where your environment enforces TLS 1.2, the SQL side must support it. None of this is hard; all of it is miserable to discover mid-wizard. Prepare the database first, test the connection, then run the manager install.
The fork in the wizard. The second row is powerful and completely unforgiving of late decisions.
Whichever database you choose, its growth is driven by logs. Every client event lands in the database, and the retention settings decide how long it stays. Offices that "run out of disk on the SEPM server" almost always mean the database ate the disk one event at a time. Set log sizes and retention deliberately during your first week, schedule the built-in database maintenance, and watch the database size monthly like you watch any other production system. The database you sized for day one is not the database you will have in year two.
The video shows the wizard where this choice is made. Watch that section twice before your own install day.
▶️ Watch Full VideoYes, Broadcom documents the migration, but it is a planned project with downtime, not a setting you flip. If you already know you will outgrow Express, start on SQL Server.
It is Broadcom's documented guidance for the default database, not a wall the software hits at client 501. Performance and supportability are the real boundaries, and both get worse past it.
Very often, yes. A growing database without maintenance tasks and sensible log retention is the classic cause. Broadcom documents database maintenance scheduling inside SEPM for exactly this reason.