Do you use a long list of filters in your reports or SOQL statements to exclude “noisy” data from your query results? Do you wonder why your requests take so long to run, even when they return only a few hundred rows? You might be able to overcome your performance issue with indexed formula fields, which this blog post explains in detail.
If you’ve built an application on the Force.com platform, you want to deliver a great experience to your users. But how can you tell if your applications are performing well and will continue to perform well? Using the Developer Console, you can use “performance profiling” to identify and fix performance hotspots, and ensure that your applications are both fast and scalable.
Managing your Salesforce organization’s data is a crucial part of keeping your organization healthy, and you might have heard about one tool that can help it stay fit: skinny tables. Read this post to learn how skinny tables work, how they can help you with large volumes of data, and what you should consider before using them.
In Blog: engineering
| Also tagged architecture, LDV
Best practices for building Salesforce SOQL queries on large data volumes (LDV) included avoiding filtering on fields with nulls, and formula fields. If you’re implementing new queries—or want to clean up some of the workarounds you implemented prior to the Winter ’13 release—consider these updates related to filtering on nulls and formula fields.
Salesforce uses a central Group object to manage visibility related to the Role Hierarchy, Territory Hierarchy, Public Groups and Queues. When administrative changes occur in these areas a group membership lock is taken to ensure data integrity is
The Developer Console is quickly becoming the easiest and most powerful place to work with Apex and Visualforce code. If you haven’t tried it lately, log in to an organization and click Your Name > Developer Console to see how the Developer Con
Salesforce customers who manage large data volume in their orgs must architect record ownership carefully to ensure peak performance. When you have a large number of records owned by a single user in Salesforce, we call that an “ownership skew”