Database Best Practices

The database module is powerful but requires responsible handling. Here you will find examples of common tasks and how to solve them safely.

Common Tasks & Examples

1. Granting money to a player (SQL Console)

Instead of searching individually in the DB editor, you can use the SQL console. Example (ESX):

UPDATE users SET bank = bank + 50000 WHERE identifier = 'steam:110000123456789';

Note: We recommend using the Live Actions in the player profile for such actions, as they automatically create a clean audit entry with a reason.

2. Filtering tables in the editor

Use the filter bar above the table to find players with a high account balance.

• Field: bank
• Operator: >
• Value: 1000000

3. Backup before script updates

Before installing a new ingame script that changes the database (e.g., a new garage system):

1. Go to "Database" -> "Backups".
2. Click on "Create instant backup".
3. Name the backup e.g., "Before Garage Update".
4. Perform your script update.
5. In case of errors, you can restore this backup with one click.

DB Connection Troubleshooting

"Access Denied for user..."

Cause: Incorrect username or password. Solution: Check your credentials in the Z-UCP settings. Make sure the SQL user has allowed the IP of our API server (whitelisting).

"Wait_timeout" or "Connection lost"

Cause: Your database server closes inactive connections too quickly. Solution: This is usually not critical. Z-UCP automatically restores the connection at the next action.

Manage Database