Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 302 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
BC140 - bad performance of import via xmlport on SQL Azure (and very fast on local SQL Server)
JoshRing
Member Posts: 14
Hi there,
We are experiencing very bad performance of a xmlport that is used to import gen. ledger entries. The server and webclient (Business Central 140 - Spring release cu2) are running on a Azure VM, the dabase is on SQL Azure.
I've created some files with different sizes. A small file (50k) takes about 15 seconds to import. A bigger file (1 mb) runs for 15 minutes. The largest one (23mb) takes endlessly to process (we've aborted the import after it was running for over 30 hours already!). The system doesn't seem to hang, it's just busy doing things... slowly....
The biggest file is "done 'n dusted" within 3 minutes on one of the SQL Server instances in our own network. So running time seems to explode almost exponentially with the increase of file size. Processor and memory load on the Azure VM are normal, running the import only effects these numbers marginally.
Does anyone have a clue while this takes ages on SQL Azure and runs smoothly on our local SQL Server? Could it be just a setting setting on Azure that can speed up things?
Best regards,
Josh
We are experiencing very bad performance of a xmlport that is used to import gen. ledger entries. The server and webclient (Business Central 140 - Spring release cu2) are running on a Azure VM, the dabase is on SQL Azure.
I've created some files with different sizes. A small file (50k) takes about 15 seconds to import. A bigger file (1 mb) runs for 15 minutes. The largest one (23mb) takes endlessly to process (we've aborted the import after it was running for over 30 hours already!). The system doesn't seem to hang, it's just busy doing things... slowly....
The biggest file is "done 'n dusted" within 3 minutes on one of the SQL Server instances in our own network. So running time seems to explode almost exponentially with the increase of file size. Processor and memory load on the Azure VM are normal, running the import only effects these numbers marginally.
Does anyone have a clue while this takes ages on SQL Azure and runs smoothly on our local SQL Server? Could it be just a setting setting on Azure that can speed up things?
Best regards,
Josh
0