This month’s T-SQL Tuesday presents a challenge: become a speaker. The introvert in me thinks thats terrifying, but it’s not out of the question. Since I’ve started my professional career over 15 years ago, I’ve naturally become a better speaker. I’ve presented many things to my co-workers, held plenty of training sessions, and speak with management at ease. On the other hand, speaking to a room full of peers who I don’t know (and probably know more than me) - that’s a different story.
I've been trying to make it a point to learn more about Azure offerings since I do believe it is changing the IT landscape and has some great benefits. In my opinion one of the best (and probably easiest) Azure services available is Azure SQL Databases.
One of the things found really interesting is that for "mission critical" applications you still need to use replication and, more importantly, PAY for more than one instance.
According to this link:
When moving a database to Azure SQL Databases one of the things that must be addressed is timezones. Azure PaaS databases always use UTC as the time zone so that a service can be moved between data centers in different time zones without a change in functionality.