Hi Greg, The main thing I think stopping us has been on premises sql or dev edition sql. It just doesn't make sense to rely on the stability of the internet when developing, and an existing environment or dev edition is very little cost.
The other issue is that it ends up in an account belonging to a single person rather than being an organisational account. The places where we've used Azure sql is when we've all wanted to all be able to access the database remotely with simplicity. The main business driver for using sql Azure as opposed to on premises sql had been more about wanting sql to operate in a DMZ, nowhere near the organisation's confidential on premises data. That said, we've just moved one application to using Windows Azure (started with table storage, moved to blob storage) simply because of the significant drop in cost of data. Regards Tony On 28 Jan 2017 1:19 PM, "Greg Low (罗格雷格博士)" <g...@greglow.com> wrote: > To my developer buddies: I'm preparing a session for Ignite where I'm > discussing using Azure SQL DB for greenfield (new) applications. Would love > to hear opinions on if you've used it, and what you found/learned, and if > you haven't used it, what stopped you ? > > > > Regards, > > > > Greg > > > > Dr Greg Low > > > > 1300SQLSQL (1300 775 775) office | +61 419201410 <+61%20419%20201%20410> > mobile│ +61 3 8676 4913 <+61%203%208676%204913> fax > > SQL Down Under | Web: www.sqldownunder.com |http://greglow.me > > >
