Building Reports That Fly
Sean Regan, salesforce.com, @SFDCSRegan
John Tan, salesforce.com, @johntansfdc
Irena Miziolek, NTT Centerstance
Jeannette Liu-Deza, NTT Centerstance
Safe Harbor
Safe harbor statement under the Private Securities Litigation Reform Act of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties
materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results
expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be
deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other
financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any
statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new
functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our
operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any
litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our
relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our
service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to
larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is
included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent
fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor
Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently
available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions
based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these
forward-looking statements.
Your company uses
Salesforce/Force.com …
You are a developer or architect
maintaining your org …
Slow reports return unreliable
data that hurts user productivity
and leads to mistakes …
You need to make these reports
faster and trusted …
Agenda - Building reports that fly!
1. Governance
• Configuration Access
• Sharing Access
• Data Architecture
2. Frequency
• Dashboard & Report Refreshes
3. Efficient Reports
• Tuning Reports
• Data Archiving/Aggregation
4. Customer Case Study
Sean Regan
Architect Evangelist
@SFDCSregan
John C. Tan
Architect Evangelist
@johntansfdc
View Our Content On Developerforce

http://developer.force.com/architect
Irena Miziolek &
Jeannette Liu-Deza
Technical & Solution Architects
NTT Centerstance
How Many Of You Have …?
Run a Salesforce report …

and waited forever?
1. Governance
Governance

Configuration access
Even Pilots Need Help
Restrict Report And List View Creation
Report & list view governance helps you …
• Increase user adoption
• Increase employee productivity
• Decrease employee mistakes
• Save money
Governance

Sharing Access
Architect Sharing Based On Business Requirements
Global Organization Sharing
What’s the impact of sharing access?
Governance

Data Architecture
Is the correct end result really enough?
Understand Your Schema
When It Isn’t Necessary, Get Rid Of it.
Architect Your Data Model For Performance

VS.
2. Frequency
Frequency

Dashboard/Report Refreshes
More Is Not Always Better
Push Data To Users: Force.com Streaming API
Workflow Email Alerts

Chatter Feeds

Scheduled Reports

Visualforce Pages
Key Takeaways
✓ Governance ensures efficiency & accuracy
✓ Know your object model
✓ Push data to users to drive workflow
✓ Architect your sharing model based on business requirements
3. Efficient reports
Efficient reports
• Tuning reports
• Data archiving/aggregation
Efficient reports

Tuning reports
What is the Force.com query optimizer?
Generates the most efficient query based on:
▪ Statistics
▪ Indexes / Skinny Tables
▪ Sharing
Best Practice: One+ Selective Filter Per report
Selective Filters: Four Components
1. Filters - add filters to reduce data
2. Operators - avoid 2 inefficient filter operators
3. Thresholds – ensure filter meets selectivity threshold
4. Index Creation - index the filter field
Filters Reduce The Scope Of Reports
Fields That Often Make Good Filters
▪ Date fields
▪ Picklists
▪ Fields with wide and even distribution of values
Non-Deterministic Formula Fields Aren’t Good Filters
Can’t index
For example:
▪ References related object
▪ CASE(MyUser__r.UserType__c,1,”Gold”,”Silver”)
▪ Create separate field and use trigger to populate

Force.com SOQL Best Practices: Nulls and Formula Fields
Use Selective Operators In Filters
Avoid Negative Operators
Query for reciprocal values instead
✖ NOT EQUALS (“closed”)
✔ EQUALS (“open”, “in progress”)
Avoid Filters With A Leading % Wildcard
CONTAINS ‘%searchstring%’
✖ CONTAINS (“district”) – equivalent to LIKE ‘%district%’
✔ STARTS WITH (“district”) – equivalent to LIKE ‘district%’
Ensure Filters Meet Selectivity Thresholds
Standard Index Selectivity Threshold
A standard index is selective when it returns:
▪ < 30% of the first 1 million records
▪ < 15% of returned records after the first 1 million records
▪ No more than 1 million total records
Standard Index Selectivity Threshold
Selectivity threshold for Created Date index
Standard Index Selectivity Threshold
For 750,000 Account records
▪ < 30% of the first 1 million records
▪ 750,000 x .30 = 225,000
Standard Index Selectivity Threshold
For 3,500,000 Account records
▪ < 30% of the first 1 million records
▪ < 15% of returned records after the first 1 million records
▪ (1,000,000 x .30) + (2,500,000 x .15) = 675,000
Standard Index Selectivity Threshold
Over 5,600,000 Account records
▪ No more than 1 million records
▪ 1,000,000
Custom Index Selectivity Threshold
A custom index is selective when it returns:
▪ < 10% of the first million records
▪ < 5% of returned records after the first million records
▪ No more than 333,333 records
Create Indexes Selective Filter Fields
Trusted traveler program
Standard Fields With Indexes
▪ Id
▪ Name
▪ OwnerId
▪ CreatedDate
▪ SystemModstamp
▪ RecordType
▪ Master-detail fields
▪ Lookup fields
Custom Indexes
• Discover common filter conditions
• Determine selective fields in those conditions
• Request custom indexes
A filter condition is selective when …
… it uses an optimizable operator
… it meets the selectivity threshold
… selective fields have indexes
Skinny Tables: Last Resort For Non-optimizable Reports
Skinny Table
▪ Single Object. No cross-object joins
▪ Maximum of 100 fields
▪ Not aggregate/summary data. 1:1 recount between source
and skinny
▪ Skinny updated automatically
▪ Minimal joins
▪ salesforce.com will analyze and create
Tell me more about skinny tables …
Webinar: Inside the Force.com Query Optimizer
Efficient reports

Data Archiving/Aggregation
Data Archiving
Reduce the # of records the query optimizer needs to consider
▪ Determine strategy during design phase
▪ Move older records into a different object
▪ Soft deletes still count towards record count
Data Aggregation
▪ Report on historical data
▪ Save tabular or summary report to a custom object
▪ Use Analytic Snapshots or Batch Apex
▪ Gists:
• Batch Apex Class - https://gist.github.com/johntansfdc/7044473
• Trigger - https://gist.github.com/johntansfdc/7044570
Key Takeaways
✓ Reports should contain at least one selective filter
✓ A filter is selective if…
✓ the field is indexed
✓ the filter does not use an inefficient operator
✓ the filter meets the selectivity theshold

✓ Implement data archiving/aggregation strategies
Introducing customer case
Irena Miziolek &
Jeannette Liu-Deza
Technical & Solution Architects
NTT Centerstance
Agenda
What’s the problem
How to troubleshoot
What’s the solution
Client
Challenge
Reports & dashboards timing out
Errors in Data Loads
Information Overload
In the beginning….
Note: no real data is used in this presentation
Account information is very slow: Sales Rep
Sales information is too overwhelming: Sales Rep
Dashboards are slow or timing out: Execs
Approach to troubleshooting
Reports and dashboards are slow or timing out
Storage usage
Reduce data volume
Reduce data volume

Data Sampling
Frequency

Batch jobs
Compound keys
Workbench
Workbench, Deleted records
Update instead of delete/reload

Full Nightly Delete & Reload
Update/Insert
Upsert
Data loads failing
Error logs
Rollup summary fields
A little
housekeeping
Report tuning
Governance
In the end….
Account information is timely: Sales Rep
Sales information is useful: Sales Rep
Dashboards are responsive: Execs
Storage usage: greatly reduced
Session Summary
Building Reports That Fly
• Govern users access to reports and data
• Manage reporting frequency
• Add at least one selective filter per report
Related DevZone Hands-on, Mini-workshop

Wednesday 1:00-1:45 PM
Thursday

1:00-1:45 PM
We want to hear
from YOU!
Please take a moment to complete our
session survey
Surveys can be found in the “My Agenda”
portion of the Dreamforce app
The Need for Speed: Building Reports That Fly

The Need for Speed: Building Reports That Fly

  • 1.
    Building Reports ThatFly Sean Regan, salesforce.com, @SFDCSRegan John Tan, salesforce.com, @johntansfdc Irena Miziolek, NTT Centerstance Jeannette Liu-Deza, NTT Centerstance
  • 2.
    Safe Harbor Safe harborstatement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
  • 3.
  • 4.
    You are adeveloper or architect maintaining your org …
  • 5.
    Slow reports returnunreliable data that hurts user productivity and leads to mistakes …
  • 6.
    You need tomake these reports faster and trusted …
  • 7.
    Agenda - Buildingreports that fly! 1. Governance • Configuration Access • Sharing Access • Data Architecture 2. Frequency • Dashboard & Report Refreshes 3. Efficient Reports • Tuning Reports • Data Archiving/Aggregation 4. Customer Case Study
  • 8.
  • 9.
    John C. Tan ArchitectEvangelist @johntansfdc
  • 10.
    View Our ContentOn Developerforce http://developer.force.com/architect
  • 11.
    Irena Miziolek & JeannetteLiu-Deza Technical & Solution Architects NTT Centerstance
  • 12.
    How Many OfYou Have …? Run a Salesforce report … and waited forever?
  • 13.
  • 14.
  • 15.
  • 16.
    Restrict Report AndList View Creation
  • 17.
    Report & listview governance helps you … • Increase user adoption • Increase employee productivity • Decrease employee mistakes • Save money
  • 18.
  • 19.
    Architect Sharing BasedOn Business Requirements
  • 20.
  • 21.
    What’s the impactof sharing access?
  • 22.
  • 23.
    Is the correctend result really enough?
  • 24.
  • 25.
    When It Isn’tNecessary, Get Rid Of it.
  • 26.
    Architect Your DataModel For Performance VS.
  • 27.
  • 28.
  • 29.
    More Is NotAlways Better
  • 30.
    Push Data ToUsers: Force.com Streaming API Workflow Email Alerts Chatter Feeds Scheduled Reports Visualforce Pages
  • 31.
    Key Takeaways ✓ Governanceensures efficiency & accuracy ✓ Know your object model ✓ Push data to users to drive workflow ✓ Architect your sharing model based on business requirements
  • 32.
  • 33.
    Efficient reports • Tuningreports • Data archiving/aggregation
  • 34.
  • 35.
    What is theForce.com query optimizer? Generates the most efficient query based on: ▪ Statistics ▪ Indexes / Skinny Tables ▪ Sharing
  • 36.
    Best Practice: One+Selective Filter Per report
  • 37.
    Selective Filters: FourComponents 1. Filters - add filters to reduce data 2. Operators - avoid 2 inefficient filter operators 3. Thresholds – ensure filter meets selectivity threshold 4. Index Creation - index the filter field
  • 38.
    Filters Reduce TheScope Of Reports
  • 39.
    Fields That OftenMake Good Filters ▪ Date fields ▪ Picklists ▪ Fields with wide and even distribution of values
  • 40.
    Non-Deterministic Formula FieldsAren’t Good Filters Can’t index For example: ▪ References related object ▪ CASE(MyUser__r.UserType__c,1,”Gold”,”Silver”) ▪ Create separate field and use trigger to populate Force.com SOQL Best Practices: Nulls and Formula Fields
  • 41.
  • 42.
    Avoid Negative Operators Queryfor reciprocal values instead ✖ NOT EQUALS (“closed”) ✔ EQUALS (“open”, “in progress”)
  • 43.
    Avoid Filters WithA Leading % Wildcard CONTAINS ‘%searchstring%’ ✖ CONTAINS (“district”) – equivalent to LIKE ‘%district%’ ✔ STARTS WITH (“district”) – equivalent to LIKE ‘district%’
  • 44.
    Ensure Filters MeetSelectivity Thresholds
  • 45.
    Standard Index SelectivityThreshold A standard index is selective when it returns: ▪ < 30% of the first 1 million records ▪ < 15% of returned records after the first 1 million records ▪ No more than 1 million total records
  • 46.
    Standard Index SelectivityThreshold Selectivity threshold for Created Date index
  • 47.
    Standard Index SelectivityThreshold For 750,000 Account records ▪ < 30% of the first 1 million records ▪ 750,000 x .30 = 225,000
  • 48.
    Standard Index SelectivityThreshold For 3,500,000 Account records ▪ < 30% of the first 1 million records ▪ < 15% of returned records after the first 1 million records ▪ (1,000,000 x .30) + (2,500,000 x .15) = 675,000
  • 49.
    Standard Index SelectivityThreshold Over 5,600,000 Account records ▪ No more than 1 million records ▪ 1,000,000
  • 50.
    Custom Index SelectivityThreshold A custom index is selective when it returns: ▪ < 10% of the first million records ▪ < 5% of returned records after the first million records ▪ No more than 333,333 records
  • 51.
    Create Indexes SelectiveFilter Fields Trusted traveler program
  • 52.
    Standard Fields WithIndexes ▪ Id ▪ Name ▪ OwnerId ▪ CreatedDate ▪ SystemModstamp ▪ RecordType ▪ Master-detail fields ▪ Lookup fields
  • 53.
    Custom Indexes • Discovercommon filter conditions • Determine selective fields in those conditions • Request custom indexes
  • 54.
    A filter conditionis selective when … … it uses an optimizable operator … it meets the selectivity threshold … selective fields have indexes
  • 55.
    Skinny Tables: LastResort For Non-optimizable Reports
  • 56.
    Skinny Table ▪ SingleObject. No cross-object joins ▪ Maximum of 100 fields ▪ Not aggregate/summary data. 1:1 recount between source and skinny ▪ Skinny updated automatically ▪ Minimal joins ▪ salesforce.com will analyze and create
  • 57.
    Tell me moreabout skinny tables … Webinar: Inside the Force.com Query Optimizer
  • 58.
  • 59.
    Data Archiving Reduce the# of records the query optimizer needs to consider ▪ Determine strategy during design phase ▪ Move older records into a different object ▪ Soft deletes still count towards record count
  • 60.
    Data Aggregation ▪ Reporton historical data ▪ Save tabular or summary report to a custom object ▪ Use Analytic Snapshots or Batch Apex ▪ Gists: • Batch Apex Class - https://gist.github.com/johntansfdc/7044473 • Trigger - https://gist.github.com/johntansfdc/7044570
  • 61.
    Key Takeaways ✓ Reportsshould contain at least one selective filter ✓ A filter is selective if… ✓ the field is indexed ✓ the filter does not use an inefficient operator ✓ the filter meets the selectivity theshold ✓ Implement data archiving/aggregation strategies
  • 62.
  • 63.
    Irena Miziolek & JeannetteLiu-Deza Technical & Solution Architects NTT Centerstance
  • 64.
    Agenda What’s the problem Howto troubleshoot What’s the solution
  • 65.
  • 66.
    Challenge Reports & dashboardstiming out Errors in Data Loads Information Overload
  • 67.
    In the beginning…. Note:no real data is used in this presentation
  • 68.
    Account information isvery slow: Sales Rep
  • 69.
    Sales information istoo overwhelming: Sales Rep
  • 70.
    Dashboards are slowor timing out: Execs
  • 71.
  • 72.
    Reports and dashboardsare slow or timing out
  • 73.
  • 74.
  • 75.
    Reduce data volume DataSampling Frequency Batch jobs
  • 76.
  • 77.
  • 78.
  • 79.
    Update instead ofdelete/reload Full Nightly Delete & Reload Update/Insert Upsert
  • 80.
  • 81.
  • 82.
  • 83.
  • 84.
  • 85.
  • 86.
  • 87.
    Account information istimely: Sales Rep
  • 88.
    Sales information isuseful: Sales Rep
  • 89.
  • 90.
  • 92.
  • 93.
    Building Reports ThatFly • Govern users access to reports and data • Manage reporting frequency • Add at least one selective filter per report
  • 94.
    Related DevZone Hands-on,Mini-workshop Wednesday 1:00-1:45 PM Thursday 1:00-1:45 PM
  • 95.
    We want tohear from YOU! Please take a moment to complete our session survey Surveys can be found in the “My Agenda” portion of the Dreamforce app