Basic Registrations Queries
Simple, Practical SQL for Event Management
Start here to learn the fundamentals of querying Planning Center Registrations data. These examples cover common scenarios you’ll encounter in day-to-day event management.Query Requirements
Schema Prefix
IMPORTANT: All tables in the Planning Center Registrations module live in theplanning_center
schema. Always prefix table names with planning_center.
in your queries.
✅ CORRECT: SELECT * FROM planning_center.registrations_signups
❌ INCORRECT: SELECT * FROM registrations_signups
Row Level Security (RLS)
Row Level Security automatically filters results by:- tenant_organization_id – limits data to your organization
- system_status – returns active records by default
- ❌
WHERE tenant_organization_id = 1
- ❌
WHERE system_status = 'active'
Finding Events
List All Active Events
Find Upcoming Events
Events by Category
Registration Counts
Count Attendees per Event
Recent Registrations
Waitlist Management
View Waitlisted Attendees
Events with Waitlists
Location Information
Events by Location
Campus Events
Pricing and Selection Types
View Event Pricing Options
Calculate Event Revenue Potential
Emergency Contacts
List Emergency Contacts for Event
Check Emergency Contact Coverage
Date and Time Queries
Events This Month
Registration Windows
People and Attendees
Find Person’s Registrations
Most Active Participants
Tips for Basic Queries
- Start simple - Begin with single table queries and gradually add joins
- Use DISTINCT carefully - Only when you need unique values
- Filter early - Add WHERE clauses before GROUP BY for better performance
- Test with LIMIT - Add LIMIT 10 when testing queries on large datasets
- Check for NULLs - Many fields can be NULL, use COALESCE or IS NULL checks
- Understand relationships - Always join through the relationship tables