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
SourceTablePlacement (SQL-Performance)
Sorcerer
Member Posts: 107
hello,
i have a litte problem while trying to solve some performance problems.
we have navision 2.60G with using the sql server option.
(bug or feature also in navi 4.00 so i will post it here)
as mentioned in the "performance troubleshooting guide" and the
"sql server option resource kit" from mbs:
so i have set the property for example on the forms 25 "Cutomer Ledger Entries" and 61 "Applied Customer Entries" to the option First.
after testing some things i recognized that there is no chance to see the applied entries from the customer entries. the records shown in the applied form are the first of the table, there is no chance to see the right ones. ](*,)
trying to set the property to Last doesnt seem to solve the problem. [-X
also tried this in navi 4.0 same effect. :-s
has anybody an idea how to implement this correctly? :-k
i have a litte problem while trying to solve some performance problems.
we have navision 2.60G with using the sql server option.
(bug or feature also in navi 4.00 so i will post it here)
as mentioned in the "performance troubleshooting guide" and the
"sql server option resource kit" from mbs:
If you are running on SQL Server, you must also be aware of a very specific
performance problem that applies to forms:
· Setting the SourceTablePlacement property to the default value (Saved) will often
make opening forms that display data from tables that contain many records
(1,000,000 or more), for example G/L entries, very slow. To fix this problem, set the
SourceTablePlacement property to First in these forms.
so i have set the property for example on the forms 25 "Cutomer Ledger Entries" and 61 "Applied Customer Entries" to the option First.
after testing some things i recognized that there is no chance to see the applied entries from the customer entries. the records shown in the applied form are the first of the table, there is no chance to see the right ones. ](*,)
trying to set the property to Last doesnt seem to solve the problem. [-X
also tried this in navi 4.0 same effect. :-s
has anybody an idea how to implement this correctly? :-k
0
Comments