How to force SQL Studio not to use copy-only backups to build database restore script? I want to ommit copy-only backup (because it's not longer available) and force studio to use last full backup (I mean full without copy-only option), which was done earlier of course.

SQL Studio restore wizard

  • 2
    I've reported this on the old feedback system, among other places. To the best knowledge, nothing has been done about it, and there's no workaround. The old feedback system is retired. If you care to report it on the new system (feedback.azure.com/forums/908035-sql-server), pick back here and I'll vote. – Tibor Karaszi Oct 16 '19 at 14:39
  • Maybe I should delete such entries from backup history from MSDB? (dbo.backup% tables) – huhu78 Oct 16 '19 at 15:37
  • I'm sorry, but I can't advice you in any direction regarding deleting data from backup history. As you understand, do something bad in that clean-up code and you might trash SSMSs ability to restore at all (based on history). And, furthermore, it most probably isn't supported. Myself, I wouldn't do it. I'd just bite the bullet an accept that the restore GUI in SSMS sometimes just isn't usable... Btw, when communicating this with others, I often see the attitude something like "Who uses SSMS to do restore in the first place?" or often even harsher. Just as a heads up... – Tibor Karaszi Oct 16 '19 at 17:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.