Skip to content
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

Simple recovery model #31467

Closed
LowerKees opened this issue May 17, 2019 — with docs.microsoft.com · 4 comments
Closed

Simple recovery model #31467

LowerKees opened this issue May 17, 2019 — with docs.microsoft.com · 4 comments

Comments

Copy link

Is there a way to create a Sql Database with a simple recovery model? I've noticed that Sql Data Warehouse automatically creates this setting, but I haven't yet seen where I can configure this for Sql Database during provisioning.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@SadiqhAhmed-MSFT
Copy link
Contributor

@LowerKees Thanks for the comment! We will investigate on this issue and get back to you soon.

@angoyal-msft
Copy link
Contributor

@LowerKees No we cannot create SQL database with "SIMPLE" recovery model. It is always created with "FULL" recovery Model. As in simple recovery model transaction log backups are not supported. Also, Point-in-time and page restore are not supported, only the restoration of the secondary read-only file is supported. While for SQL databases all the backups are required so that data can be restored if there is any failure or disaster.

The Recovery Model is set when the master database is created and cannot be modified because the ‘master’ database is read only for anyone but Microsoft. Furthermore, keep in mind that SQL Databases are continuously being replicated. Windows Azure keeps at least 3 copies of your SQL Database at all times.

You can refer this blog for more details.

Hope it helps.

@angoyal-msft
Copy link
Contributor

@LowerKees I hope your concern has been resolved.
We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

@LowerKees
Copy link
Author

LowerKees commented May 22, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants