- Campaign v7 documentation
- Latest updates
- Release Notes
- Get started
- Start with Adobe Campaign
- Privacy
- Profile management
- Import and export data
- Filter data
- Create queries
- Permissions
- Data packages and enumerations
- Connectors
- Create and send messages
- Get started with messages
- Key steps when creating a delivery
- Send emails
- Send SMS
- Send LINE messages
- Send push notifications
- Send direct mail
- Use delivery templates
- Personalize deliveries
- Use seed addresses
- A/B testing
- Services and subscriptions
- Monitor deliveries
- Track messages
- Deliverability management
- Content management module
- Orchestrate marketing campaigns
- Marketing Resource Management
- Distributed marketing
- Response manager
- Design and share reports
- Design web content
- Create online surveys
- Integrate with Adobe Experience Cloud
- Automate with workflows
- Get started with workflows
- Execute a workflow
- Targeting activities
- Flow control activities
- Action activities
- About action activities
- Delivery
- Delivery control
- Continuous delivery
- Recurring delivery
- Cross-channel deliveries
- Local approval
- Data loading (RDBMS)
- Loading (SOAP)
- Data loading (file)
- Content Management
- Data extraction (file)
- SQL code and JavaScript code
- SQL Data Management
- Nlserver module
- Update aggregate
- Event activities
- Use cases
- Monitor workflows
- Advanced management
- Manage Offers
- Transactional Messaging
- Integrate with social media
- Installation and configuration guide
- Architecture principles
- Deployment types
- Security and privacy settings
- Install Campaign (on-premise)
- Deploy Campaign (on-premise)
- Configure Campaign
- Connect to Campaign
- Connect Campaign to external systems
- Configure external accounts
- Configure Federated Data Access
- Get started with Federated Data Access
- Best practices and limitations
- Configuration guidelines
- Configuration steps
- Configure Amazon Redshift
- Configure Azure Synapse
- Configure Google BigQuery
- Configure Hadoop
- Configure Microsoft SQL Server
- Configure Netezza
- Configure Oracle
- Configure PostgreSQL
- Configure SAP HANA
- Configure Snowflake
- Configure Sybase IQ
- Configure Teradata
- Configure Vertica Analytics
- Remote access rights
- Connect to the database
- Create the data schema
- Define data mapping
- Appendices
- Monitoring guide
- Developers guide
- Technotes
- Campaign Control Panel
Database performance
Most performance issues are linked to database maintenance. Here are four main leads to help you find the cause of slow performance:
- Configuration
- Installation and configuration of the Adobe Campaign platform
- Database maintenance
- Real-time diagnosis
Configuration
Check that the initial Adobe Campaign platform configuration is still valid and if necessary, reassess your customer’s needs in terms of deliverability or database size. We also recommend running a full hardware check (CPU, RAM, IO system).
You can refer to Adobe Campaign Hardware Sizing guide for insights.
Platform configuration
Inappropriate configuration may affect platform performance. We recommend that you check network configuration, platform deliverability options as well as MTA configuration in the serverConf.xml file.
Database maintenance
Database cleanup task
Please make sure the database cleanup task is operational. To do this, view the log files to see if they contain any errors. For more on this, refer to this section.
Maintenance plans
Make sure database maintenance is correctly scheduled and executed. To do this, please contact your database administrator to learn more about:
- Their maintenance schedule
- Previously executed maintenance plans
- Viewing the script logs
For more on this, refer to this section.
If you are using a mid-sourcing configuration, it is essential for databases to be maintained on a regular basis. When analyzing a delivery on the marketing platform, the marketing instance sends information to the mid-sourcing instance. If the process is slowed down, the marketing instance will be impacted.
Managing work tables
Please check the number and size of work tables. When they exceed a certain size, database performance is affected. These tables are created by workflows and deliveries. They remain in the database while workflows and deliveries are active. To limit the size of work tables, you can carry out the following operations:
- Stop or delete deliveries with the following statuses: Failed, In progress, Ready for delivery, or Paused.
- Stop or delete workflows which are paused due to an error.
- Stop all workflows used for tests which do not contain an End activity and whose status therefore remains Paused.
If the operation takes a long time and frees up a lot of space, this means that in-depth maintenance is necessary (index rebuilding, etc.). For more on this, refer to this section.
Adobe Campaign process monitoring
Depending on Adobe Campaign installation settings, two tools can be used for platform monitoring:
- The instance production page. For more on this, refer to Manual monitoring.
- The netreport script. For more on this, refer to Automatic monitoring via Adobe Campaign scripts.
Specifics
It may become necessary to run a real-time diagnosis to identify the cause of the issue. Start by checking the process and platform log files, then monitor database activity while recreating the issue. Pay particular attention to the following:
- The maintenance execution plan
- SQL queries being executed
- Whether or not external processes are running at the same time (cleansing, imports, aggregate calculation, etc.).
Resources
Adobe Account
