Reputation: 14982
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?
Upvotes: 1
Views: 115
Reputation: 16530
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
Upvotes: 3