Learn from the community and our team. Follow these best practices to get the most out of suparbase and avoid common pitfalls.
Name your connections clearly: "Production DB", "Staging DB", "Dev Local". This helps avoid mistakes.
Do
Production - Main App
Don't
DB1, DB2, test
Group connections by environment type. Use tags or naming conventions to keep things organized.
Do
Use consistent prefixes: prod-, staging-, dev-
Don't
Mix environments randomly
Periodically test your connections to ensure they're still valid and accessible.
Do
Test monthly or after password changes
Don't
Assume connections never break
For large databases, schedule syncs during low-traffic periods to avoid performance impact.
Do
Schedule syncs for nights/weekends
Don't
Sync during peak usage times
Always preview changes with dry-run mode before executing actual syncs.
Do
Dry-run → Review → Execute
Don't
Execute syncs blindly
For large databases, sync tables in batches rather than all at once.
Do
Sync 5-10 tables at a time
Don't
Sync 100+ tables simultaneously
Always run schema validation to catch incompatible changes early.
Do
Validate → Fix issues → Sync
Don't
Skip validation steps
Keep track of schema changes using version control or migration tools.
Do
Document schema changes
Don't
Make undocumented changes
Always test schema changes in development before syncing to production.
Do
Dev → Staging → Production
Don't
Test directly in production
Ensure your database passwords are strong and unique for each environment.
Do
Complex passwords, different per env
Don't
Weak or reused passwords
Periodically review who has access to your connections and remove unused ones.
Do
Audit access quarterly
Don't
Keep old connections forever
Set up email notifications to be alerted of sync failures or security issues.
Do
Enable all critical notifications
Don't
Ignore security alerts
Only sync tables you actually need. Unnecessary syncs waste time and resources.
Do
Sync only required tables
Don't
Sync everything "just in case"
Keep an eye on your usage to avoid hitting monthly limits unexpectedly.
Do
Check usage dashboard weekly
Don't
Ignore limit warnings
Archive or delete old sync jobs to keep your dashboard clean and organized.
Do
Archive completed syncs monthly
Don't
Keep thousands of old syncs
Always backup your target database before syncing major schema changes.
Do
Backup → Validate → Sync
Don't
Sync without backups
Periodically test that you can restore from backups to ensure they work.
Do
Test restores quarterly
Don't
Assume backups always work
Maintain backups from different points in time, not just the latest.
Do
Daily + Weekly + Monthly backups
Don't
Single backup point
suparbase creates backup snapshots before every sync. If sync fails, it can restore automatically.
Do
Let rollback complete before retrying
Don't
Interrupt rollback mid-process
Backup snapshots are stored for 7 days. Monitor storage usage for large databases.
Do
Check storage usage weekly
Don't
Ignore storage limit warnings
Monitor real-time throughput, rows/second, and table progress during syncs.
Do
Watch for rate limiting indicators
Don't
Ignore slow performance warnings
Use distributed tracing to identify bottlenecks and optimize slow syncs.
Do
Analyze traces for slow operations
Don't
Skip trace analysis for failed syncs
Start Small
Begin with a single table sync to understand the process before scaling up.
Use Keep-Alive Wisely
Enable keep-alive only for databases you actively use to avoid unnecessary requests.
Monitor Regularly
Check your sync history and logs weekly to catch issues early and optimize performance.
Start implementing these best practices today and optimize your database synchronization workflow.