6/30/2025 5:29:55 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
| |
|
Re: How many records to be in table ACCOUNT for comfortable work?
Posted: 12 Apr 10 3:39 AM
|
| Number is only limited by SQL server - and no's in M's is not an issue. Be wary of your indexes as, at this amount, they will be very important and, obviously, you'll need decent kit to support that as well - i.e. SAS 15k disks/cache/battery backup and fast networking etc etc etc. The limitation on #s won't be down to SLX as it uses "chunking" it many cases to only bring back the first 100 or so rows to satisfy grids. Updates etc. obviously happen to entire DB. I seem to recall a portion of the Australian electorate are stored in SLX - and this was 8M rows. |
|
|
|
Re: How many records to be in table ACCOUNT for comfortable work?
Posted: 12 Apr 10 5:55 AM
|
I agree with Mike, there are no limits on SLX for the Number of Rows, but you depend heavily on the hardware (specially SQL Server) that supports it.
And, not only that you need a good Hardware setup, you also need it configured properly.
In general, an Experience DBA team should be able to setup the Database and Maintain it properly to ensure ongoing performance.
Things to lookup out for:
- Indexing
- Maintenance Plans (make sure your Index and Stats are up to date, specially if you run any batch jobs into the DB).\
- Schedule of large running task. Make sure you schedule things like data Imports to the evening if possible, and make sure that it does not conflict with your maintenance plans.
Additionally, you need to make sure that any development takes is done accordingly as to minimize locks on the DB.
Bottom line, and as stated above, an experienced DBA team should be able to setup, maintain and troubleshoot a Large Database. |
|
|
|
Re: How many records to be in table ACCOUNT for comfortable work?
Posted: 12 Apr 10 9:25 AM
|
Mike, Raul, Thanks for the reply.
We use slx 7.5.2 WEB. IIS 5 version.
When the table "ACCOUNT" contains 40'000 records, the group "ALL" opens ~10 seconds.
But when we add 300'000 records in the table "ACCOUNT", the group "ALL" don't open for ~5 minutes.
Why this happens?
Do you have clients, who have more then 1'000'000 ACCOUNT's?
Sorry for my bad English. |
|
|
|
Re: How many records to be in table ACCOUNT for comfortable work?
Posted: 13 Apr 10 3:03 AM
|
The All group is pretty much what it say. It's everything with no where clause. However, that said - it should still only return the first x00 to satisfy the grid. One thing to try is this:
1) Set client to be ready to hit the database i.e. highlight the All group but don't select it
2) Run SLXProfiler - you'll find this in the program files folder
2) Hit the logo ball and have it attach to the w3p process
3) Now select the group
4) Wait for it to finish
This will give you, in profiler, the SQL requested and the SQL sent and the execution/prepare times. Let us know what the query is - as this group may have changed, invalid query or simply lack of suitable indexes etc.
The only thing to be wary of in this instance is that you say SLX 7.5.2 web - I think, unfortunately, that does suffer from performance issues (even though a lot were addressed in this release) and the upcoming release addresses those issues. I know that is of little help to you - but reversing the situation - why should you need to select the All group ? Data is searched/sorted without the need to use this group anyway ?
Mike
|
|
|
| |
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|