What is the Apex Database Class?<\/h2>\n\n\n\n
The Apex Database Class is a built-in class with static methods for working with the database. Database.insert, Database.update, Database.upsert, Database.delete and Database.undelete do the same jobs as DML statements. However, they accept an extra allOrNone flag and return result objects for every record.<\/p>\n\n\n\n
Think of a teacher collecting 30 homework books. With plain DML, one missing name means she rejects the whole pile. With the Database class, she accepts the 29 good books and returns one with a note saying “name missing”. Everyone else’s work still counts.<\/p>\n\n\n\n
Why the Apex Database Class Matters<\/h2>\n\n\n\n
Real data is messy, especially from integrations and imports. Here is why the Apex Database Class matters at Bright Path Tutors.<\/p>\n\n\n\n
- \n
- First, the nightly import has 500 enrolments, and a few always fail validation.<\/li>\n\n
- Also, the business wants the good records saved, not the whole batch lost.<\/li>\n\n
- Next, the support team needs a list of failed rows with reasons.<\/li>\n\n
- An integration must know which records were created and which were updated.<\/li>\n\n
- Finally, some loads must bypass duplicate rules or allow long text to be cut.<\/li>\n<\/ul>\n\n\n\n
So the Database class turns all-or-nothing saves into controlled, reportable loads.<\/p>\n\n\n\n
How the Apex Database Class Works<\/h2>\n\n\n\n
The Apex Database Class follows a clear pattern. First, you call a method such as Database.insert with a list and allOrNone set to false. Next, Salesforce tries to save each record. Then valid records are saved, while invalid ones are skipped. After that, the method returns one result per record, in the same order as your list. Finally, your code loops through the results and handles each error.<\/p>\n\n\n\n
![\"Apex](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/11\/apex-database-class-partial-success-diagram-1-1024x640.png\")
How partial success saves good records and reports bad ones.<\/figcaption><\/figure>\n\n\n\n The allOrNone Parameter<\/h3>\n\n\n\n
When allOrNone is true, the default, any error fails the whole call, just like plain DML. When it is false, Salesforce saves the good records and reports the bad ones.<\/p>\n\n\n\n
Result Objects<\/h3>\n\n\n\n
Each method returns its own result type. Insert and update return SaveResult, upsert returns UpsertResult, delete returns DeleteResult and undelete returns UndeleteResult.<\/p>\n\n\n\n
Database.Error<\/h3>\n\n\n\n
Each failed result holds one or more Database.Error objects. They give the message, the status code and the fields that caused the problem.<\/p>\n\n\n\n
DMLOptions<\/h3>\n\n\n\n
Database.DMLOptions sets extra behaviour, such as allowing field truncation or saving despite duplicate rule alerts. You pass it to the method instead of the allOrNone flag.<\/p>\n\n\n\n
Access Level<\/h3>\n\n\n\n
Database methods can also take AccessLevel.USER_MODE, so the save respects the running user’s object and field permissions.<\/p>\n\n\n\n
Apex Database Class Methods at a Glance<\/h2>\n\n\n\n
The table below lists the main methods and their results.<\/p>\n\n\n\n
Method<\/th> Result type<\/th> Useful result methods<\/th><\/tr><\/thead> Database.insert<\/td> SaveResult<\/td> isSuccess(), getId(), getErrors()<\/td><\/tr> Database.update<\/td> SaveResult<\/td> isSuccess(), getErrors()<\/td><\/tr> Database.upsert<\/td> UpsertResult<\/td> isCreated(), isSuccess()<\/td><\/tr> Database.delete<\/td> DeleteResult<\/td> isSuccess(), getErrors()<\/td><\/tr> Database.undelete<\/td> UndeleteResult<\/td> isSuccess(), getErrors()<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n DML Statements vs the Apex Database Class<\/h2>\n\n\n\n
The table below compares plain DML with Database methods.<\/p>\n\n\n\n
Feature<\/th> DML statement<\/th> Database method<\/th><\/tr><\/thead> Partial success<\/td> No<\/td> Yes, with allOrNone false<\/td><\/tr> Error handling<\/td> Catch DmlException<\/td> Read result objects<\/td><\/tr> Returns results per record<\/td> No<\/td> Yes<\/td><\/tr> Extra options<\/td> No<\/td> DMLOptions and AccessLevel<\/td><\/tr> Code length<\/td> Shorter<\/td> A little longer<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n When to use which depends on the data. Use plain DML when every record must save together. Use the Database class for imports, integrations and any load where partial success is acceptable.<\/p>\n\n\n\n
![\"Apex](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/11\/apex-database-class-partial-success-diagram-2-1024x640.png\")
DML statement vs Database method.<\/figcaption><\/figure>\n\n\n\n A Real Apex Database Class Example<\/h2>\n\n\n\n
Let’s import enrolments at Bright Path Tutors with partial success. One record is missing its course, so it should fail without stopping the others.<\/p>\n\n\n\n
Step 1: Insert with allOrNone False<\/h3>\n\n\n\n
List<Enrolment__c> rows = new List<Enrolment__c>{\n new Enrolment__c(Course__c = 'a015g00000AbC12AAB', Status__c = 'Active'),\n new Enrolment__c(Course__c = null, Status__c = 'Active'), \/\/ will fail\n new Enrolment__c(Course__c = 'a015g00000AbC12AAB', Status__c = 'Active')\n};\n\nList<Database.SaveResult> results = Database.insert(rows, false);<\/code><\/pre>\n\n\n\nThe second record has no course, which breaks a validation rule. Because allOrNone is false, the other two records still save. Use real course Ids from your org when you run this.<\/p>\n\n\n\n
Step 2: Read the Results<\/h3>\n\n\n\n
Integer okCount = 0;\nList<String> failures = new List<String>();\n\nfor (Integer i = 0; i < results.size(); i++) {\n Database.SaveResult sr = results[i];\n if (sr.isSuccess()) {\n okCount++;\n } else {\n for (Database.Error err : sr.getErrors()) {\n failures.add('Row ' + (i + 1) + ': ' + err.getStatusCode()\n + ' - ' + err.getMessage() + ' ' + err.getFields());\n }\n }\n}\nSystem.debug('Saved: ' + okCount + ', failed: ' + failures.size());\nSystem.debug(String.join(failures, '\\n'));<\/code><\/pre>\n\n\n\nWith the Apex Database Class, results come back in the same order as the input list. So index i tells us which row failed. For each failure, we record the status code, message and fields, ready for an error log or email.<\/p>\n\n\n\n
Step 3: Read the Output<\/h3>\n\n\n\n
Here is an example of the debug log.<\/p>\n\n\n\n
USER_DEBUG [15]|DEBUG|Saved: 2, failed: 1\nUSER_DEBUG [16]|DEBUG|Row 2: FIELD_CUSTOM_VALIDATION_EXCEPTION - Course is required [Course__c]<\/code><\/pre>\n\n\n\nStep 4: Upsert and Check What Was Created<\/h3>\n\n\n\n
List<Database.UpsertResult> ur = Database.upsert(coursesFromSystem, Course__c.Course_Code__c, false);\nfor (Database.UpsertResult r : ur) {\n if (r.isSuccess()) {\n System.debug(r.getId() + (r.isCreated() ? ' created' : ' updated'));\n }\n}<\/code><\/pre>\n\n\n\nDatabase.upsert takes the external ID field as a field token. Then isCreated tells you whether each record was new or updated, which integrations often need to report.<\/p>\n\n\n\n
Step 5: Use DMLOptions<\/h3>\n\n\n\n
Database.DMLOptions opts = new Database.DMLOptions();\nopts.allowFieldTruncation = true;\nopts.optAllOrNone = false;\n\nDatabase.insert(rows, opts);<\/code><\/pre>\n\n\n\nallowFieldTruncation cuts text that is too long for a field instead of failing. optAllOrNone works like the allOrNone flag.<\/p>\n\n\n\n
Partial Success and Triggers<\/h2>\n\n\n\n
Partial success in the Apex Database Class has one detail that surprises many developers. When some records fail, Salesforce may roll back and run triggers again for the records that succeed. So triggers should give the same result if they run twice, and they should not send emails or callouts directly.<\/p>\n\n\n\n
Common Mistakes with the Apex Database Class<\/h2>\n\n\n\n
- \n
- Calling Database.insert without false, then expecting partial success.<\/li>\n\n
- Ignoring the result list, so failures go unnoticed.<\/li>\n\n
- Losing the link between results and input rows by changing list order.<\/li>\n\n
- Logging only the first error when a record has several.<\/li>\n\n
- Using partial success where all records must save together.<\/li>\n<\/ul>\n\n\n\n
Best Practices for the Apex Database Class<\/h2>\n\n\n\n
- \n
- Use allOrNone false for imports and integrations.<\/li>\n\n
- Always loop through results and log every failure.<\/li>\n\n
- Keep the input list order unchanged until you read results.<\/li>\n\n
- Store errors in a custom log object for support teams.<\/li>\n\n
- Use AccessLevel.USER_MODE when saves must respect user permissions.<\/li>\n<\/ul>\n\n\n\n
Practice Task<\/h2>\n\n\n\n
Write code that updates the fee on ten courses with Database.update and partial success. Then build a map of course Id to error message for the failed rows. Hint: use the input list index to get each failed record’s Id.<\/p>\n\n\n\n
Most Asked Interview Questions on the Apex Database Class<\/h2>\n\n\n\n
The Apex Database Class is a very common interview topic, especially for integration roles. Here are the 20 questions asked most.<\/p>\n\n\n\n
Basic Questions on the Apex Database Class<\/h3>\n\n\n\n
Q1: What is the Database class in Apex?<\/strong><\/p>\n\n\n\n
It is a built-in class with methods for DML and queries. Its DML methods can allow partial success and return result objects.<\/p>\n\n\n\n
Q2: What is partial success?<\/strong><\/p>\n\n\n\n
It means good records save even when some records fail. You get it by passing allOrNone as false.<\/p>\n\n\n\n
Q3: What is the default value of allOrNone?<\/strong><\/p>\n\n\n\n
True. So without false, Database methods behave like plain DML.<\/p>\n\n\n\n
Q4: What does Database.insert return?<\/strong><\/p>\n\n\n\n
A list of Database.SaveResult objects, one per record, in the same order as the input.<\/p>\n\n\n\n
Q5: What does Database.upsert return?<\/strong><\/p>\n\n\n\n
A list of Database.UpsertResult objects, which also tell you if each record was created or updated.<\/p>\n\n\n\n
Q6: How do you check if a record saved?<\/strong><\/p>\n\n\n\n
Call isSuccess() on its result. If it is false, read getErrors().<\/p>\n\n\n\n
Q7: What information does Database.Error give?<\/strong><\/p>\n\n\n\n
The message, the status code and the fields involved in the error.<\/p>\n\n\n\n
Code and Scenario Questions on the Apex Database Class<\/h3>\n\n\n\n
Q8: How do you find which input row failed?<\/strong><\/p>\n\n\n\n
Use the result index. For example, results[i] matches rows[i], because order is kept.<\/p>\n\n\n\n
Q9: When would you choose Database.insert over insert?<\/strong><\/p>\n\n\n\n
For imports and integrations, where saving good records and reporting bad ones is better than failing everything.<\/p>\n\n\n\n
Q10: Does Database.insert throw an exception with allOrNone false?<\/strong><\/p>\n\n\n\n
Not for record errors. Instead, errors appear in the results. However, some system errors can still throw exceptions.<\/p>\n\n\n\n
Q11: What is Database.DMLOptions?<\/strong><\/p>\n\n\n\n
It is a class that sets extra options, such as allowFieldTruncation, optAllOrNone and duplicate rule settings.<\/p>\n\n\n\n
Q12: How do you allow saving despite duplicate rules?<\/strong><\/p>\n\n\n\n
Set opts.DuplicateRuleHeader.allowSave = true on DMLOptions, then pass the options to the save.<\/p>\n\n\n\n
Q13: How do you save in user mode?<\/strong><\/p>\n\n\n\n
Pass AccessLevel.USER_MODE, for example Database.insert(rows, false, AccessLevel.USER_MODE).<\/p>\n\n\n\n
Q14: How do you know if an upserted record was new?<\/strong><\/p>\n\n\n\n
Call isCreated() on its UpsertResult.<\/p>\n\n\n\n
Advanced Questions on the Apex Database Class<\/h3>\n\n\n\n
Q15: Do triggers run for failed records?<\/strong><\/p>\n\n\n\n
Triggers run during the attempt. However, failed records are not saved, and Salesforce may run triggers again for the successful ones.<\/p>\n\n\n\n
Q16: Why should triggers be safe to run twice?<\/strong><\/p>\n\n\n\n
Because partial success can re-run them for successful records. So avoid direct emails or counters that double.<\/p>\n\n\n\n
Q17: Do Database methods count against DML limits?<\/strong><\/p>\n\n\n\n
Yes. Each call counts as one DML statement, and each record counts toward the 10,000 row limit.<\/p>\n\n\n\n
Q18: How would you report import failures to users?<\/strong><\/p>\n\n\n\n
Collect errors from the results, save them in a log object, and send a summary email or show them in a component.<\/p>\n\n\n\n
Q19: Can you mix allOrNone false with a savepoint?<\/strong><\/p>\n\n\n\n
Yes. You can set a savepoint, save with partial success, and roll back if too many records fail.<\/p>\n\n\n\n
Q20: What is the difference between getErrors() and DmlException methods?<\/strong><\/p>\n\n\n\n
getErrors() reads errors from result objects in partial saves. In contrast, DmlException methods read errors after a failed DML statement.<\/p>\n\n\n\n
Official Resources<\/h2>\n\n\n\n