Database Users
Begin your SEI installation by creating dedicated database users. Secure database access is essential for reliable and maintainable deployments. SEI provides scripts to help you set up users for both Oracle and SQL Server, ensuring each account has the necessary—and only the necessary—permissions.
Choose your environment to get started:
| Platform | Instructions |
|---|---|
| Oracle | Create Oracle users and tablespaces. |
| SQL Server | Create SQL Server users. |
Recommendations for Production environments
Reduce risk and minimize performance impact on your ERP by connecting SEI to a replicated (duplicate) database, rather than the production database itself. This approach isolates analytics workload, improves security, and prevents reporting activity from affecting daily operations.
Keep in mind:
- Offload SEI queries to a replica to avoid extra load on production.
- Database replication adds complexity and ongoing maintenance costs.
- Ensure your SEI server is sized appropriately for its workload.
- For Sage X3 on SQL Server, use DataSync for ERP replication.
Log Shipping and Limitations (SQL Server)
If you plan to use SQL Server Log Shipping:
- Expect a delay in reporting data, since updates to the replica are not instantaneous.
- Users may occasionally experience UI connection losses during replica updates, though these are usually brief.
- OLAP Manager is not compatible with log-shipped (read-only) databases, as it requires a writable replica for trigger and tracking table management.