Activity overview
Latest activity by rsocol
I have the same problem, but the error appears intermittently. If I apply the sugesstion in the previous comment (deleting the SQLHistory.db file), I lose a lot of history. In my case, I had a 80MB SavedTabs.db file last modified on 30 September 2022 and a 200MB SqlHistory.db file last modified today. If I delete the SqlHistory.db and restart SSMS, the file SqlHistory.db is recreated using the data from SavedTabs.db, which is more than one month old. @redgate, please advise. / comments
I have the same problem, but the error appears intermittently.If I apply the sugesstion in the previous comment (deleting the SQLHistory.db file), I lose a lot of history. In my case, I had a 80MB ...
The bug is that SQL Prompt shows the warning about default values when adding a computed column (if the PERSISTENT keyword is used). We do not need a default value (and cannot add a default value) for a computed column. / comments
The bug is that SQL Prompt shows the warning about default values when adding a computed column (if the PERSISTENT keyword is used). We do not need a default value (and cannot add a default value) ...
This issue was fixed in SQL Prompt version 9.0.7.3692 (released in January 2018). / comments
This issue was fixed in SQL Prompt version 9.0.7.3692 (released in January 2018).
I have posted the suggestion here: https://redgate.uservoice.com/forums/94 ... single-row
Thanks,
Razvan / comments
I have posted the suggestion here: https://redgate.uservoice.com/forums/94 ... single-row
Thanks,
Razvan
UPDATE without WHERE clause warning for single-row tables
We have several tables with various configuration settings, which will always have a single row. To ensure this, we always use some constraints, like these:CREATE TABLE ConfigurationTable (
DummyI...