Hi Greg,
The issue that you're facing is latency. You are correct in assuming that the way you're used to doing it is not really appropriate for Azure. For example: I have script to contain a DB and insert about 20MB of data. To run it locally takes 50 seconds. Point the connection at SQL Azure and the same script runs in 14 minutes. However, if I export the DB to a BACPAC in Azure Storage, then import it to a SQL Database, the whole process takes about 1 minute. We've found a need to modify much of what we'd normally do on-premises when working in this environment. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: <http://www.sqldownunder.com/> www.sqldownunder.com From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Sunday, 14 April 2013 5:57 PM To: ozDotNet Subject: SQL Azure insert speed Folks, I'm using EF4 to insert 3900 rows in to a table. Due to a performance quirk/bug in EF I have to insert them in groups of 50 with a fresh context for each group. In SQL Server and SQLite all rows insert in about 2 minutes. With an identical table in SQL Azure the same inserts take about 20 minutes. Now either SQL Azure has insert performance problems, or my insertion technique is not valid for Azure. If anyone here is using SQL Azure in anger then I'm keen to hear of any performance problems and/or workarounds you've found. Greg K
