For example you cannot take a SQL Server backup and restore it to Azure SQL or the other way round. Native automatic backup and restore is great, but on Azure SQL this also means that you cannot use it to import and export data from or to a non Azure SQL database. In case you want to get a bit deeper into how automatic backups are done, there are a couple of very interesting videosĪzure SQL – Automated Backups (Part 1) Azure SQL – Automated Backups (Part 2). If you are a full-stack developer or a back-end developer that also needs to take care of data, I’m sure you’ll love this ability as basically it means you get all the benefits with no drawbacks. That’s a great feature: as a developer I know I can rely on this native support to make sure I always have the ability to restore my database in case sometime goes wrong, but I don’t have the burden of managing this extremely important but really-not-a-dev-thing operation. Automatic BackupsĪzure SQL automatically takes care of backup for you. But if – and you should – you want to learn a bit more around backup and restore in Azure SQL, read on. That’s all you need to know to get started with Azure SQL sample databases. Long story short, restoring a database in Azure SQL is very simple, but if that’s a new thing for you, you may benefit from some script I prepared so that you can skip the trial-and-error phase and just go directly to the coding phase: Also, usually samples you can find around the web use well-known sample databases, so having it available quickly always comes handy. It will help you to have comfortable playground where you can do all the test you need to improve your skills without the need to spend time creating new data and models from scratch, so that you can focus on learning. Restoring a sample database is always useful, not matter if you are an experienced developer or a new one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |