Gettings started entity framework database development (code first)

Question

Are there any heavy drawbacks of creating databases with entityframework using the code first approach regarding the fact that the goal is Azure? I know little about Azure (yet :)) but I know I will pay per transaction.

So now I am a bit worried, if I do not have to bother writing SQL statements by hand, will entity framework code first still generate "cost-friendly" SQL mappings for me? Or is code first a bad practice when it comes to Azure database?

Azure SQL Database's cost doesn't operate based on transactions unlike Azure Storage Table. ( Azure Storage Table : Data Size + Transaction Count + Out BandWidth, Azure SQL Databases : Data Size + Out BandWidth ) — Naveen Vijay
– Naveen Vijay, Commented Dec 24, 2012 at 9:44
Ah that's a good point. I just checked the online calculator and you're right (not that I doubted you :)). — bas
– bas, Commented Dec 24, 2012 at 10:57

Naveen Vijay · Accepted Answer · 2012-12-24 12:02:28Z

3

Azure SQL Database's cost doesn't operate based on transactions unlike Azure Storage Table.

Azure Storage Table : Data Size + Transaction Count + Out BandWidth

Azure SQL Databases : Data Size + Out BandWidth

answered Dec 24, 2012 at 12:02

Naveen Vijay

16.6k10 gold badges75 silver badges99 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Gettings started entity framework database development (code first)

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related