Subject: RE: Used Azure SQL DB? Why or why not?
Hi Glav,
One caught my eye there. Can’t admit to like using schemas for tenants. I live
in a world where “performance aside” isn’t an aside. That has way to much
impact on query plans, caching, memory, etc. for my liking.
Regards,
Greg
7 3:58 PM
To: 'ozDotNet'
Subject: RE: Used Azure SQL DB? Why or why not?
Hey Greg,
Use it all the time, and am working with a customer which is a greenfield
project.
Things to note:
· Getting a good idea of performance related to what size/number of
DTU’s. Initially, it is a pretty
In the enterprise space, technology is 10% of the cost, and people/process is
the other 90%.
BUs might go to random cloud providers, because they don’t understand the
implications, or they just outsource the work to some agency. But for an
enterprise platform, we have the whole gamut of conside
...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of DotNet Dude
Sent: Tuesday, 31 January 2017 1:36 PM
To: ozDotNet
Subject: Re: Used Azure SQL DB? Why or why not?
They are definitely the same ones who are the gatekeepers for the decisions.
I've seen that the most. Protecting their
care and
finance are definitely industries in that bucket.
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Tuesday, 31 January 2017 3:53 PM
To: ozDotNet
Subject: Re: Used Azure SQL DB? Why or why not?
Another argument we got from the DBAs
That sounds like the app that I'm fighting with each day.
I wish they would give us the time to sort it out and migrate to azure, perhaps
then I would be able to work from home more often.
Davy
Sent from my iPhone
> On 31 Jan 2017, at 05:24, Greg Low (罗格雷格博士) wrote:
>
> Recently I saw one w
>
> Another argument we got from the DBAs was "we are responsible for the
> integrity of the data so we're not relying on some thing in the cloud we
> know nothing about."
>
A major Melbourne hospital network said that to us recently. They demanded
that the ASP.NET app be installed by their IT sta
otNet Dude mailto:adotnetd...@gmail.com>>
Sent: Tuesday, January 31, 2017 7:22:25 AM
To: ozDotNet
Subject: Re: Used Azure SQL DB? Why or why not?
The arguments are everything they can come up with even if they're not true.
Eg. Pricing. It's just people who have been here the longest tr
gt;> 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
>>
>> ----------
>> *From:* ozdotnet-boun...@ozdotnet.com
ttp://www.sqldownunder.com/>
|http://greglow.me<http://greglow.me/>
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Craig van Nieuwkerk
Sent: Saturday, 28 January 2017 4:50 PM
To: ozDotNet
Subject: Re: Used Azure SQL DB? Why or why not?
I have been using S
; 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.sqldownun
ttp://www.sqldownunder.com>
From: ozdotnet-boun...@ozdotnet.com on behalf
of DotNet Dude
Sent: Tuesday, January 31, 2017 7:22:25 AM
To: ozDotNet
Subject: Re: Used Azure SQL DB? Why or why not?
The arguments are everything they can come up with even if they're no
r.com |http://greglow.me
>
>
>
> *From:* ozdotnet-boun...@ozdotnet.com
> [mailto:
> ozdotnet-boun...@ozdotnet.com
> ] *On
> Behalf Of *DotNet Dude
> *Sent:* Saturday, 28 January 2017 12:44 PM
> *To:* ozDotNet >
> *Subject:* Re: Used Azure SQL DB? Why or why not?
>
&g
I have been using SQL Azure for about 4 years for our SAAS app. All
development is done against an on premise SQL Server so there is no problem
if we lose internet. Developing against a remote DB would be painfully slow
anyway.
The biggest issue I find is that SQL Azure will highlight any performa
I haven't used SQL Azure in a live app yet, but have some personal and
testing DBs up there. In a couple of weeks I'll share a DB with another
developer who lives over an hour drive away, so instead of swapping zips of
DB backups, we'll now connect to the same Azure DB, which is really
convenient a
Hey Greg,
Use it all the time, and am working with a customer which is a greenfield
project.
Things to note:
* Getting a good idea of performance related to what size/number of
DTU’s. Initially, it is a pretty rough guess at best of times. Also, assuming
all the queries written
913> fax
>
> SQL Down Under | Web: www.sqldownunder.com |http://greglow.me
>
>
>
> *From:* ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-bounces@
> ozdotnet.com] *On Behalf Of *Tony Wright
> *Sent:* Saturday, 28 January 2017 12:31 PM
> *To:* ozDotNet
> *Subject:* Re: Used Azur
zdotnet-boun...@ozdotnet.com] On
Behalf Of Tony Wright
Sent: Saturday, 28 January 2017 12:31 PM
To: ozDotNet
Subject: Re: Used Azure SQL DB? Why or why not?
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 stabilit
e/>
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of DotNet Dude
Sent: Saturday, 28 January 2017 12:44 PM
To: ozDotNet
Subject: Re: Used Azure SQL DB? Why or why not?
Everything Tony said plus politics :p
On Saturday, 28 January 2017, Tony Wright
mailto:tonyw.
Everything Tony said plus politics :p
On Saturday, 28 January 2017, Tony Wright wrote:
> 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 environme
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
21 matches
Mail list logo
