Rider SQL console scripts excluded from IDE settings backup

The Rider SQL console integrates query execution within the .NET IDE, offering parameterized queries, result set pagination, visual query plans, and script persistence for ad-hoc and ORM-driven investigations. Its design supports saving .sql files for reproducibility across development sessions, yet the interaction between script storage and IDE-level backup mechanisms is not explicitly documented.

A documented caution indicates that SQL console scripts are not automatically included in Rider's settings export, requiring manual intervention to preserve query files during profile migration or IDE reinstallation. This gap creates uncertainty when restoring developer environments, as saved scripts and associated query history may not be recovered automatically, potentially disrupting workflow continuity.

Which mechanisms does Rider provide to ensure script persistence across backup and restore cycles? Can saved .sql files be automatically re-integrated into a restored SQL console session, and what metadata is preserved during the process? How can recovered scripts be verified to produce consistent result sets against the original query outcomes?