LosaDev 2014 source - database setup used by the local test setup (SQL Server 2022 Express)

Order (run each file against the same instance, all scripts are in src\sql\20120504 of the source):
 1. CREATE DATABASE LosaGame and LosaLogData (LosaLogData stays empty apart from step 6).
    Create one SQL login (SQL authentication) that owns both databases.
 2. lostsaga_tb.sql   62 tables, no errors.
 3. lostsaga_sp.sql   538 of 560 procedures (22 fail: written for newer tables).
 4. lostsaga_etc.sql  functions; one view and two CREATE USER fail.
    The three scripts are UTF-16 and start with USE [LosaGame]: check the USE line first.
 5. Stub procedures in LosaGame for the ~175 queries in ls_query.ini that the 2012 scripts
    do not have (pets, costumes, accessories, league, bingo, ...):
      node make-stubs.js ls_query.ini existing-procs.txt stubs-game.sql LosaGame
    existing-procs.txt = SELECT name FROM sys.procedures (one per line) of LosaGame.
 6. The same for LosaLogData (empty existing list): every log query gets a stub there.
 7. losadev-fixes-and-accounts.sql: game_server_connection_on takes the 64-bit server ID,
    the second encryption key row, three test accounts (test1, test2, gmtest1), the
    login-key helper procedure, and the paging/extra parameters the 2014 server sends to
    game_item_extra_get_list, game_item_get_data_list and game_game_save.

ls_query.ini comes from a community-run server and does not match the source everywhere.
The one change needed for login: 7=game_login_get_data STR (that server sent five values,
the 2014 source sends one). query-check.js compares ls_query.ini with what the servers send.

Encode the SQL password for the DB agents with: ls_dbagent.exe -x yourpassword