Enhance setup page documentation to clarify database startup wait behavior#368
Merged
Conversation
ismcagdas
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
Documents the new startup behavior added for applications whose database server is not yet available when they start (a common case with SQL Server, whose service often runs as Automatic (Delayed Start)). Adds a "Waiting for the Database on Startup" section to the configuration guide describing the new
App:Database:StartupWaitsetting for both Web.Mvc and Web.Host, including its options, the fact that the application only waits when the database server is unreachable (a missing database goes straight to the setup page with no delay), and a note to keep the timeout below the IISstartupTimeLimit. Also clarifies in the MVC, Angular and React setup page docs that the setup page is only for applications without a database, if the database exists but the server was simply slow to start, no reinstall is needed, since the application stops redirecting to the setup page as soon as the database becomes available. Finally, notes in the rate limiting docs that a temporarily unreachable database now skips rate limiting for that request and logs a warning instead of failing it.