Duh! Of course SQL Server doesn't apply settings on the fly (it's a Microsoft product). Shutting down the server and restarting fixed the problem.