In Salesforce, the foundation of reporting is the retrieval of an organization's data. If your data is not retrieved efficiently, your reports can be incredibly slow and might time out, which will frustrate your users. Join us to learn the techniques every expert architect should know in order to build reports that fly--and to ensure that your data is at your users fingertips. We'll spend the vast majority of our time covering specific performance-related techniques, such as using reporting governance, as well as what you need to know about the Force.com query optimizer to write reports that are both fast and selective. Note that this session assumes you already understand the basic principles behind building queries and reports.

1. Building Reports That Fly
Sean Regan, salesforce.com, @SFDCSRegan
John Tan, salesforce.com, @johntansfdc
Irena Miziolek, NTT Centerstance
Jeannette Liu-Deza, NTT Centerstance

2. 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.

3. Your company uses
Salesforce/Force.com …

4. You are a developer or architect
maintaining your org …

5. Slow reports return unreliable
data that hurts user productivity
and leads to mistakes …

6. You need to make these reports
faster and trusted …

7. 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

8. Sean Regan
Architect Evangelist
@SFDCSregan

9. John C. Tan
Architect Evangelist
@johntansfdc

10. View Our Content On Developerforce
http://developer.force.com/architect

11. Irena Miziolek &
Jeannette Liu-Deza
Technical & Solution Architects
NTT Centerstance

12. How Many Of You Have …?
Run a Salesforce report …
and waited forever?

13. 1. Governance

14. Governance
Configuration access

15. Even Pilots Need Help

16. Restrict Report And List View Creation

17. Report & list view governance helps you …
• Increase user adoption
• Increase employee productivity
• Decrease employee mistakes
• Save money

18. Governance
Sharing Access

19. Architect Sharing Based On Business Requirements

20. Global Organization Sharing

21. What’s the impact of sharing access?

22. Governance
Data Architecture

23. Is the correct end result really enough?

24. Understand Your Schema

25. When It Isn’t Necessary, Get Rid Of it.

26. Architect Your Data Model For Performance
VS.

27. 2. Frequency

28. Frequency
Dashboard/Report Refreshes

29. More Is Not Always Better

30. Push Data To Users: Force.com Streaming API
Workflow Email Alerts
Chatter Feeds
Scheduled Reports
Visualforce Pages

31. 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

32. 3. Efficient reports

33. Efficient reports
• Tuning reports
• Data archiving/aggregation

34. Efficient reports
Tuning reports

35. What is the Force.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: 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

38. Filters Reduce The Scope Of Reports

39. Fields That Often Make Good Filters
▪ Date fields
▪ Picklists
▪ Fields with wide and even distribution of values

40. 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

41. Use Selective Operators In Filters

42. Avoid Negative Operators
Query for reciprocal values instead
✖ NOT EQUALS (“closed”)
✔ EQUALS (“open”, “in progress”)

43. Avoid Filters With A Leading % Wildcard
CONTAINS ‘%searchstring%’
✖ CONTAINS (“district”) – equivalent to LIKE ‘%district%’
✔ STARTS WITH (“district”) – equivalent to LIKE ‘district%’

44. Ensure Filters Meet Selectivity Thresholds

45. 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

46. Standard Index Selectivity Threshold
Selectivity threshold for Created Date index

47. Standard Index Selectivity Threshold
For 750,000 Account records
▪ < 30% of the first 1 million records
▪ 750,000 x .30 = 225,000

48. 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

49. Standard Index Selectivity Threshold
Over 5,600,000 Account records
▪ No more than 1 million records
▪ 1,000,000

50. 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

51. Create Indexes Selective Filter Fields
Trusted traveler program

52. Standard Fields With Indexes
▪ Id
▪ Name
▪ OwnerId
▪ CreatedDate
▪ SystemModstamp
▪ RecordType
▪ Master-detail fields
▪ Lookup fields

53. Custom Indexes
• Discover common filter conditions
• Determine selective fields in those conditions
• Request custom indexes

54. A filter condition is selective when …
… it uses an optimizable operator
… it meets the selectivity threshold
… selective fields have indexes

55. Skinny Tables: Last Resort For Non-optimizable Reports

56. 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

57. Tell me more about skinny tables …
Webinar: Inside the Force.com Query Optimizer

58. Efficient reports
Data Archiving/Aggregation

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
▪ 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

61. 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

62. Introducing customer case

63. Irena Miziolek &
Jeannette Liu-Deza
Technical & Solution Architects
NTT Centerstance

64. Agenda
What’s the problem
How to troubleshoot
What’s the solution

65. Client

66. Challenge
Reports & dashboards timing out
Errors in Data Loads
Information Overload

67. In the beginning….
Note: no real data is used in this presentation

68. Account information is very slow: Sales Rep

69. Sales information is too overwhelming: Sales Rep

70. Dashboards are slow or timing out: Execs

71. Approach to troubleshooting

72. Reports and dashboards are slow or timing out

73. Storage usage

74. Reduce data volume

75. Reduce data volume
Data Sampling
Frequency
Batch jobs

76. Compound keys

77. Workbench

78. Workbench, Deleted records

79. Update instead of delete/reload
Full Nightly Delete & Reload
Update/Insert
Upsert

80. Data loads failing

81. Error logs

82. Rollup summary fields

83. A little
housekeeping

84. Report tuning

85. Governance

86. In the end….

87. Account information is timely: Sales Rep

88. Sales information is useful: Sales Rep

89. Dashboards are responsive: Execs

90. Storage usage: greatly reduced

92. Session Summary

93. Building Reports That Fly
• 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 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