First, I'll give some background and I'll try to keep this short.
Like many companies, pre-pandemic we didn't have any cloud deployments. Then COVID hit, everyone went home and suddenly we starting to move what we could to the cloud. However, for us that hasn't been very successful. I believe the reason why it failed so badly is because we didn't have the experience/skills to migrate databases and applications to the cloud. Additionally, the concept of going to the cloud (regardless of which cloud) was only thought of as lift-and-shift. i.e.: Infrastructure as a Service. I believe the reason for this is because the operations people have lots of experience managing hundreds of VMs on-prem. And that is the ONLY way they want to manage the cloud. The IaaS approach is, so I understand, one of the most expensive ways of doing cloud. I've advocated for a long time that we need to modernize our applications and use a Platform as a Service (PaaS) approach, which, so I understand, is cheaper than an IaaS approach. However, my single voice is overwhelmed by the very large multitude of operations people, managers, developers, etc. who only know how "to do what we've always done". As a consequence, our new CIO is considering abandoning the cloud (Azure in our case) because of cost.
Personally, and professionally, I don't believe this approach will be good for my career. Going back to doing things as they were done 20 years ago isn't of any interest to me at all. I've done that; I want to move on. So, I've thought that what I could do is migrate one of the apps I'm responsible for, into an Azure instance, using my Visual Studio Subscription monthly credits. Four or five years ago I had migrated a different SQL Server database to Azure SQL, with a similar idea in mind. However, that's all been lost. (Long story, which I won't go into. Just accept the fact that all the resource groups I'd created with everything in them, have permanently disappeared.) So, I'm having to start over again. I'm sure that the approach I took 5 years ago no longer works or at least has been superseded by some better approach. This time around I want to migrate a smaller app and database to Azure, starting with the database. This database is small. It is less than 25 MB in size. However, it's on an old SQL Server instance; it is in SQL Server 2012. I know I'm going to have to convert that to something newer. I forget what it was called, but I simply cannot do a backup, then copy the .bak to Azure Storage and restore into an Azure SQL database. What do I do, in order to prepare this database (I'll make a copy of it) to migrate to Azure SQL? (This is a warehouse database, so no PII or PHI.)
Second, how do I keep my cost down? When I tried doing this before I put a larger database into Azure SQL, and it would easily burn through more than half my monthly VS Subscription with me doing nothing at all with it. That could happen to me now. There are times when my job requires a lot of attention, so I have to ignore this database for weeks at a time. At the moment, I have the time to work on it, but that isn't always the case. Is there a way of putting an Azure SQL Database to sleep, or inactive, until I'm ready to work on it?
Kindest Regards, Rod Connect with me on LinkedIn.