How Skinny Tables Can Help Boost Performance in Salesforce скачать в хорошем качестве

How Skinny Tables Can Help Boost Performance in Salesforce

Are your reports and listviews crawling in Salesforce? Skinny tables can be performance saviors. When we are faced with large volumes of data and complex queries, skinny tables come to the rescue. Let's dig into what they are and how we benefit from using them. Before we do, take a second to subscribe to our channel. We will keep you up to date with the latest in Salesforce. So, what is a skinny table anyway? Essentially, it's a custom table optimized for query performance. Imagine you have a Salesforce org with millions of records contained in Salesforce objects. Just like any database, as the volume increases, your performance suffers because Salesforce works harder to retrieve that data. Custom indexes alone may give you the performance boost but can only go so far. Effectively, what skinny tables are doing is harvesting those commonly used fields. They also omit the soft delete records, and they do away with those costly joins. Joins, you say. Why would I have a join against a single object in Salesforce? Isn't that data stored in the same table? Funnily enough, standard and custom fields are actually held in separate tables completely out of our view. Skinny tables create a denormalized copy of your data that is automatically kept in sync with their source tables. This results in quicker reports, listviews, and SOQL. What's not to love? As always, the devil is in the details. We want to keep a few things in mind before we take the plunge in putting skinny tables into use in our org. First, Skinny tables can’t be created by you, your admin or anyone else within your Salesforce org. Salesforce customer support has to create skinny tables once requested by the customer. Any future modifications or deletions of these skinny tables would also have to go through Salesforce support. I’d only recommend using skinny tables for mature and stable data models. Next, skinny tables are only copied to your org for Full sandboxes. Also, skinny tables have a cap on the number of columns they can contain of a 100. Skinny tables can't contain fields from other objects. Lastly, skinny tables are making a copy of those data objects so storage consumption will increase This video is brought to you by the company I work for -- Improving. We are an IT services firm serving North America. We have a bunch of brilliant Salesforce consultants who can help your team, but it doesn't stop there. Data, app modernization, AI/ML, platform engineering, agile training. You name it -- we can probably help. Please reach out to us at http://improving.com. Thanks for joining us today. I hope you’ve found this video helpful. I’ve included a link below if you’d like to read more about skinny tables on Salesforce’s website. If you found this video helpful, please like and subscribe. I'm regularly publishing new Salesforce content that I think you'll enjoy. Until then. Explore skinny tables further at Salesforce: https://developer.salesforce.com/docs... ==Related Videos PK Chunking: Fixing Salesforce Bulk API Timeouts:    • PK Chunking: Fixing Salesforce Bulk API Ti...   Combating Data Skew in Salesforce: Avoiding Performance & Locking Issues:    • Combating Data Skew in Salesforce: Avoidin...   Defining Data Quality in Salesforce:    • Defining Data Quality in Salesforce