Simone Bizzotto

sorry @rferraton , I'd say this is not a bug anymore but rather an enhancement request .... I'm not an avid "replaceinname" user, but sticking to the documentation I'd say...

I mean, everything *can* be done, but if in some years this is the first time it pops up, I think it'll be too much of a hassle to set...

@ReeceGoding / @userwiths : dbatools uses SMO, and that command uses dependency tracking via SMO just like SSMS does. This means that if SMO is able to trace dependencies dbatools...

@ReeceGoding , something like https://learn.microsoft.com/en-us/dotnet/api/microsoft.sqlserver.management.smo.dependencywalker.discoverdependencies?view=sql-smo-160 or https://github.com/microsoft/sqlmanagementobjects/blob/main/src/Microsoft/SqlServer/Management/Smo/DependencyWalker.cs is okay ? dunno how much "clear" it'd be , even linking it.

does it happen every time or once in a while ?

then it's something else with sysadmin privileges doing things on the database, with -Force we TRY to kill sessions, but there's nothing else we can do. You should put `Restore-DbaDbSnapshot`...

hum, the single exported file before had issues ? if not, is this just a reorder of the statements (and an enlargement if counting lines and statements) to make sure...

okay, then maybe it's good to put a regression test into tests/Export-DbaUser.Tests.ps1 to avoid this "way" getting reverted by a next edit.

`has now grown into a collection of [over 700 commands]` to `has now grown into a collection of [nearly 700 commands]` ;-)

dunno what to do except approve all of the above ... let's not keep PRs around for weeks ;-)