Hi Zono,
- You can change the parameters as per Sqlite docs (stop counterparty-server, use Sqlite CLI to change config parameters)
- PRAGMA_CHECK maybe can be replaced with PRAGMA_QUICK_CHECK (https://www.sqlite.org/pragma.html#pragma_quick_check), but it’s not something that we test. I think this check runs only rarely, for example when the DB is first deployed (if you use
counterparty-server bootstrap, for example). I don’t find it time consuming (yes, sometimes it runs for 10+ mins, but if you normally shutdown counterparty-server (using CTRL+C), it takes only 1-2 mins at startup, in my experience). I use the top command to watch if counterparty-server is stuck or active - if it’s “working”, then I just wait. The longest check I’ve seen was around 30 mins, when the entire DB had to be checked on a slow PC.
Did you use bootstrap/download the Counterparty DB, or did you let it catch up naturally?
Normally for test/dev environments it’s better to use testnet because DB is smaller and the wait is shorter, then do final testing on mainnet. Or point your counterparty-client to public Counterparty server (e.g. CoinDaddy’s servers) while the DB is catching up / checking consistency (create a different config file and use counterparty-client --config-file coindaddy.server.conf getinfo - a detailed example of using CoinDaddy’s Counterparty server can be found here)