-
-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BackupRestore without SetSourceReadOnly #3
Comments
Hey techop, |
Closing because I never heard back and can't repro |
dansqldba
pushed a commit
that referenced
this issue
Aug 11, 2016
Removing extra tabs/spaces, show proper addition of Exclude parameter
potatoqualitee
pushed a commit
that referenced
this issue
Jun 30, 2017
Development update fork from base repo #3
FriedrichWeinmann
pushed a commit
that referenced
this issue
Aug 2, 2017
Updating fork Development from ORIGIN
PowerDBAKlaas
pushed a commit
that referenced
this issue
Nov 18, 2017
niphlod
added a commit
to niphlod/dbatools
that referenced
this issue
Nov 27, 2017
dbaduck
referenced
this issue
in dbaduck/dbatools
May 18, 2019
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I cannot find a way to perform Start-SqlMigration with the -BackupRestore method without it trying to set the source databases to read only. I have tried not specifying -SetSourceReadOnly and I have tried -SetSourceReadOnly:$false. How do you perform a SqlMigration without it modifying anything on the source server?
Thanks!
The text was updated successfully, but these errors were encountered: