Comments
1 comment
-
Hi @Bev
Thank you for reaching out on the Redgate forums regarding your SQL Prompt > History inquiry.
There are some settings that can be tweaked around this, but at present it is limited.
In the SQL Prompt settings section, there is a limit that can be placed on the individual query size. Reducing this can help with the side of the dB.
There is an automated process that runs behind the scene after 7 days some snapshots are removed (query edited and connection changed) and then VACUUM is run on the SqlHistory.db file which rebuilds the database file, repacking it into a minimal amount of disk space.
I have searched through our UserVoice feature request page and found some existing requests that look to align with the type of settings you're requesting.
It would be a good suggestion to look at these links and upvote any ideas that would be useful for your requirements. Providing comments on how it impacts your usage of SQL Prompt & History are welcomed and ensure appropriate visibility for our development team to implement into future releases- Too many versions of changes stored in SQL History
https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/46236559-sql-history
- SQL History dB is grown very large
https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/46279948-sql-history
Add comment
Please sign in to leave a comment.