Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 266 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
What is faster in C/SIDE? Where's the stucking part?
aleix1979
Member Posts: 213
Big processes movin/deleting/whatevering 
hundreds of thousands records may take long long time to be executed.
I've done it few times and I guess I'm not wrong to say that in an SQL based database you save time by simply doing for instance:
IF X<>"Value" THEN X:="Value"
instead of just:
X:=Value;
The big issue cames in C/SIDE. There's both data items where you may go faster with that modification and data items where you may instead go slower.
Does it ring a bell to someone?
hundreds of thousands records may take long long time to be executed.I've done it few times and I guess I'm not wrong to say that in an SQL based database you save time by simply doing for instance:
IF X<>"Value" THEN X:="Value"
instead of just:
X:=Value;
The big issue cames in C/SIDE. There's both data items where you may go faster with that modification and data items where you may instead go slower.
Does it ring a bell to someone?
Navision Developer
0