[Edi]

Actually, what you should use as the base tables are the BaseU, BaseW and BaseA tables from the Dom3DB (name them whatever you want, though), because those are complete and accurate, barring the known issue of Firelord not having magic (F2) listed.

Alternatively, do the tbUnitSprite table in a spreadsheet and then copypaste the contents of the BaseU table so that the sprite columns are either right after the unit number column or the unit name column and use that as base.

OR, list unit sprites on a separate table with sprite number column being from 0 to wherever and add spr1 and spr2 columns to the BaseU table and then fill those with the appropriate entries.

The Dom3DB was designed with basic DB design principles in mind so that if desired, it could be ported to SQL almost as is. Besides, not all of the sprites are used and some have been changed, so having them in a separate table and having each unit have two columns for the normal and attack sprites that reference the sprite table would make for a more structurally sound database.

However, bear in mind that I do NOT do database work at my job, so if you can take those suggestions and improve on them, feel free to do so. I'm coming at it from the angle that since the unit database itself is basically complete already except for the sprite information, it would be a complete and utter waste of effort to duplicate that from the ground up when just a minor tweak would get the whole thing going.