Add-DbaAgDatabase add option to not wait for seeding

[TiborKaraszi]

Summarize Functionality

It would be valuable if we could add a database to an AG, but not have to wait for that operation to be completed. I.e., a command-line switch for that option.

Is there a command that is similiar or close to what you are looking for?

No

Technical Details

The SQL command in the end is ALTER AVAILABILITY GROUP .. ADD DATABASE ... is immediate. It doesn't wait for the database to be seeded onto the replicas. We have deployments where we have to wait sometimes an hour for the deploy to finish, just waiting for the seeding to be completed. It would be a win for us of the could finish such deployment and start using the environment, even though the seeding is still going on (in the background). (Loking at the source code: I don't know if it is the loop in step 3/4 that should be bypassed or possibly step 5.)

[potatoqualitee]

Thank you for the request, @TiborKaraszi. @claude please review the request, pls add a NoWait.

[claude]

Claude finished @potatoqualitee's task —— View job • claude/issue-9857-20251028-0026 • Create PR ➔

---

Tasks Completed

Summary

Successfully added the -NoWait switch parameter to Add-DbaAgDatabase as requested. This allows the command to return immediately after adding a database to an Availability Group without waiting for seeding and synchronization to complete on secondary replicas.

Changes Made

1. Added -NoWait switch parameter to both parameter sets (NonPipeline and Pipeline)
2. Added comprehensive parameter documentation explaining:
   • The parameter skips Step 5 (waiting for database seeding and synchronization)
   • The underlying SQL command is immediate and doesn't wait
   • Use case: deployments where seeding takes a long time
   • Seeding continues in the background after the command returns
3. Modified Step 5 logic to skip the synchronization wait loop when -NoWait is specified
4. Updated parameter validation test in Add-DbaAgDatabase.Tests.ps1 to include the new parameter
5. Added usage example demonstrating how to use the NoWait parameter

Technical Details

The implementation adds a conditional check before Step 5's wait loop. When -NoWait is specified, the command logs a verbose message and skips the entire synchronization monitoring process. This allows users to:

• Complete deployments faster when seeding takes considerable time (up to an hour)
• Start using the environment while synchronization continues in the background
• Avoid timeout issues in automated deployment scripts

The synchronization will continue on the SQL Server side regardless of whether the PowerShell command waits for it.

Files Modified

• /home/runner/work/dbatools/dbatools/public/Add-DbaAgDatabase.ps1
• /home/runner/work/dbatools/dbatools/tests/Add-DbaAgDatabase.Tests.ps1

--- | Branch: claude/issue-9857-20251028-0026