DV-Team does not use SQL Server: the database is a MySQL / MariaDB dump (Navicat), databases muonline (127 tables) and log (22 tables). There is no MEMB_INFO and no stored procedure, so SQL Server guides and MEMB_INFO queries do not apply.
- Accounts:
accounts(guid, account, password varchar(255), email, blocked, web_admin, ban_time, creation_counter ...) - Online state:
accounts_status(account_id, online, current_server, last_ip, last_online ...) - Bans:
accounts_banned(account_id, unban_date), accounts.blocked - VIP and currencies:
account_data(vip_status, vip_duration, credits, web_credits, goblin_points, expanded_warehouse ...) - Characters:
character_info(guid, account_id, authority, admin_flags, name, level, level_master, level_majestic, points, reset, money, ruud_money, online ...) - Vault:
account_warehouse(account_id, warehouse_id, money, password, inventory varbinary(55000)) - Guilds: guild_list, guild_members; Gens: character_gens; daily_reset_data
The dump also holds WebEngine tables ported to MySQL (webengine_credits_config, webengine_bans ...).
Example, server closed, backup first (mysqldump), always with WHERE:
SELECT guid, account_id, name, level, reset FROM character_info WHERE name = 'CharName';The meaning of authority / admin_flags values is not documented in the dump.
Source: DV-Team MU Server 19 2-3 (19.10.25.2.2.2.2) DataBase/muonline.sql and log.sql, New Update 2.2.2.3 DataBase/, db_update 2.sql, warehouse_update.sql, daily_reset.sql.