The Salesforce object model and the SOQL query language form the foundation of working with Salesforce data. While most developers are SQL-literate, there are small but important distinctions between SOQL and SQL. In this webinar, developers new to Salesforce will come to understand these differences, jumpstarting their Salesforce developer success.

1. December 1, 2015
Lorem Ipsum Dolor

2. Forward-Looking Statement
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. Go Social!
Salesforce Developers
Salesforce Developers
Salesforce Developers
The video will be posted to YouTube & the
webinar recap page (same URL as registration).This webinar is being recorded!
@salesforcedevs / #forcewebinar

4. ▪ Don’t wait until the end to ask your question!
– Technical support will answer questions starting now.
▪ Respect Q&A etiquette
– Please don’t repeat questions. The support team is working
their way down the queue.
▪ Stick around for live Q&A at the end
– Speakers will tackle more questions at the end, time-
allowing.
▪ Head to Developer Forums
– More questions? Visit developer.salesforce.com/forums
Have Questions?

5. SOQL for the SQL Developer
Look for the blog post: http://bit.ly/soql4sql

6. Agenda
▪ Data Model & Relationships
– Comparing Force.com with Relational DBMS
– Relationship Types & the Predefined Join
▪ Relationships & SOQL
– SOQL vs SQL
– Relationship Queries

7. Assumptions
▪ A basic understanding of the Force.com Platform including:
– Creating Custom Objects and Fields
– Navigating the UI
▪ Knowledge of relational database concepts
– Tables
– Primary/Foreign Keys
– Joins

8. Agenda
▪ Data Model & Relationships
▪ Relationships & SOQL

9. Data Model and the Force.com Platform
▪ SObject:
– Table-like data structure
• Records
• Fields
– Extensible
– Queryable/Updatable
– Relationships

10. SObjects Drive Customization
Property__c
Broker__c
Desktop Mobile
Business
Process
Reporting
Security Model and Sharing
/SObjects/Property__c
APIs
Programmatic Customization
Broker__c brkr = new Broker__c();

11. Standard Data Model
▪ Standard Objects
– Account
– Contact
– Lead
– Opportunity
– Case
– …
▪ Standard Fields
– Id
– Name
– CreatedBy/Date
– LastModifiedBy/Date
– OwnerId
– IsDeleted
– …

12. Extensible Data Model
▪ Custom Objects
– Property__c
– Broker__c
– Favorite__c
– …
▪ Custom Fields
– Status__c
– City__c
– Baths__c
– Beds__c
– Mobile_Phone__c
– …

13. Relationships: The Predefined Join
▪ RDBMS
– Design: Constraint
– Runtime: Query with Join
▪ Force.com
– Design: Constraint and Join
– Runtime: Relationship Query

14. Master-DetailLookup
Relationship Types
NeverOptional
Cascade
Clear
Field/Block/Cascade*
Nullability
Delete Behavior
Child Inherits from ParentIndependent Parent/Child
225
Record Sharing
Access
Max Allowed Fields

15. Demo
Dreamhouse App
Property and Broker Relationship
developer.salesforce.com/dreamhouse

16. Agenda
▪ Data Model & Relationships
▪ Relationships & SOQL

17. SOQL
▪ Salesforce Object Query Language
▪ SQL-like syntax
▪ Queries the Force.com Object Layer
▪ Used in:
– Apex
– Developer Tools (Developer Console, Eclipse, Workbench, …)
– API (REST, SOAP, Bulk, Streaming, etc.…)

18. From SQL to SOQL
▪ At first may look familiar
▪ Important differences
▪ Learn the differences
▪ Use good data design practices

19. From SQL to SOQL: The Familiar Bits
▪ Table-like structure
▪ Similar query syntax
▪ Indexed
▪ Transactional
▪ Triggers
SELECT Id, Name, Status__c
FROM Property__c
WHERE Beds__c > 2

20. From SQL to SOQL: Immediate Differences
▪ No select *
▪ No views
▪ SOQL is read-only
▪ Limited indexes
▪ Object-relational mapping is automatic
▪ Schema changes protected

21. From SQL to SOQL: Differences To Learn
▪ SObjects are not actually tables – multi-tenant environment
▪ Relationship metadata
– Management of referential integrity
– Predefines joins
– Relationship query syntax
▪ Query usage explicitly metered
– API Batch Limits
– Apex Governor Limits

22. The __c and __r Suffixes
Broker__c
Property__c
Id
Id
Broker__c
Broker__r
Properties__r
Type: List<Property__c>
Type: Id
Type: Broker__c
1-M

23. Relationship Query: Child to Parent
SELECT Id, Name, Broker__c,
Broker__r.Id,
Broker__r.Region__c
FROM Property__c
WHERE Status__c = ’Available’
[
{
"Id": "a0145000000aBf4AAE",
"Name": "82 Glen Ross Lane",
"Broker__c": "a00vn000000dU3dAAE",
"Broker__r": {
"Id": "a00vn000000dU3dAAE",
"Region__c": "North"
}
},
{
"Id": "a0145000000aBf4AAE",
"Name": "Riverside Luxury Flat",
"Broker__c": "",
"Broker__r": {...}
}, ...
]

24. Relationship Query: Parent to Child
SELECT Id, Name, Region__c,
(SELECT Id, Name, Status__c
FROM Properties__r)
FROM Broker__c
WHERE Region__c = 'North'
[{
"Id": "a00vn000000dU3dAAE",
"Name": "Shelley Levene",
"Region__c": "North,
"Properties__r": [
{
"Id": "a0145000000aBf4AAE",
"Name": "Glengarry Manor",
"Status__c": "Available"
},
{
"Id": "a0145000000aBd4AAE",
"Name": "82 Glen Ross Lane",
"Status__c": "Closed"
}
]
}, ...]

25. Querying for Intersection
Select Id, Name,
Broker__r.Name,
Broker__r.Email__c
FROM Property__c
WHERE
Broker__r.Region__c = 'North'
[
{
"Id": "a0145000000aBf4AAE",
"Name": "83 Glen Ross Lane",
"Broker__r": {
"Name": "Shelley Levene",
"Email__c":"shel@machine.com"
}
},
{...},
...
]

26. Aggregate Queries
SELECT
City__c,
COUNT(Id) houseCount,
MAX(Price__c) maxValue,
AVG(Price__c) avgValue
FROM Property__c
GROUP BY City__c
[
{
"City__c": "Reading",
"houseCount": 81,
"maxValue": 748000,
"avgValue": 569468.50
},
{
"City__c": "Windsor",
"houseCount": 46,
"maxValue": 840000,
"avgValue": 638812.50
},
...
]

27. Demo
Find the total property value currently on the market
broken down by each broker region

28. Recap
▪ Data Model &
Relationships
– Much that looks similar, but
– Many important differences
– Predefined Join
– Relationship Types
▪ Relationships & SOQL
– SOQL has relations but is
not “relational”
– Limits cannot be ignored
– Good design principles still
apply but check your
assumptions

29. Concepts to Explore Further
▪ Query Locator: database cursor abstraction
▪ Query Optimizer: translates SOQL to SQL
▪ Query Plan: examine query optimizer behavior

30. Read More
▪ Blog: Basic SOQL Relationship Queries: http://bit.ly/soqlrelationship
▪ SOQL-SOSL Guide http://bit.ly/soqlsosl
▪ Sharing http://bit.ly/sharingarch
▪ Limits http://bit.ly/apexgovlim
▪ Multi-Tenant Architecture http://bit.ly/sfmultiten

35. Q & A
Try Trailhead: trailhead.salesforce.com
Join the conversation: @salesforcedevs

36. Thank You