Database and AutoSQL

• AutoSQL & Schema
• Core Tables Explained
• Database Safety

AutoSQL & Schema

AutoSQL & Schema

Nord Garages automatically creates and migrates its schema during resource startup.

The stabilization line includes a schema migration that also verifies the Vehicle OS auxiliary tables/columns/indexes, which helps repair older or partially upgraded installations.

Core tables

• nord_garages
• nord_garage_points
• nord_garage_vehicles
• nord_garage_history
• nord_garage_schema

Vehicle OS tables

• nord_garage_plate_aliases
• nord_garage_vehicle_snapshots
• nord_garage_vehicle_access
• nord_garage_vehicle_collections
• nord_garage_reservations
• nord_garage_slots
• nord_garage_analytics

Normal users should let AutoSQL manage these tables.

Core Tables Explained

Core Tables Explained

nord_garages

Stores garage definition data: identifier, name, garage type, categories, access, settings, blip/NPC data and published state.

nord_garage_points

Stores world points linked to a garage identifier, including position, point type and metadata.

nord_garage_vehicles

Stores Nord's normalized vehicle state including owner, plate, model/type, garage assignment, state, properties, health, fuel, mileage, last position, sharing/metadata and current tracking identifiers.

Vehicle OS extends this table with VIN, slot, service, insurance, EV and stolen-state fields.

nord_garage_history

Append-style operational history for vehicle state/actions.

nord_garage_schema

Tracks migration/schema version. Do not manually reduce the version number on a live database.

Database Safety

Database Safety

Do not edit active state casually

Directly changing a vehicle row while the resource is running can desynchronize:

• Framework ownership state
• OneSync entity tracking
• Keys
• Phone/Staff caches
• Impound rules
• Vehicle OS history

Use server exports wherever possible.

Backups

Before a major upgrade, back up both:

1. Your framework ownership table (owned_vehicles or player_vehicles).
2. All nord_garage_* tables.

Stale spawning state

Startup SQL repairs stale spawning rows back to stored so a crash/restart does not permanently lock a vehicle.

Legacy showroom points

Older showroom and camera point types are removed because v2 uses the native showroom implementation.