SQLA: 13.5 "Recent Documents"

It does not appear that 13.5 w/ SSMS 21 brings over "recent documents".

I would think that this might be a 32-bit vs 64-bit issue? Maybe the SQLLite (or whatever you use to store document history) is where the issue lay?

This stuff is stored in the History folder which isn't version specific.
Looking into that...

I thought at one point it got converted to a database, because I remember running into an unescaped apostrophe bug when that happened. It used to be stored in a folder, I do remember that.

Actually, could you please check if you got two saDocMng.* files in %APP_DATA%\Roaming\SQL Assistant\13.5 folder? If you don't, or they are small, please copy them from 13.0 folder

The 13.0 had a "saDocMng.db.bak" file, I copied that into the 13.5 folder and renamed the current .db to db- and renamed the .bak to .db (being careful it didn't end up .db.db), but that did not fix it. I closed SSMS before hand to avoid any file locking.

The saDocMng.db.bak was about 2MB and had a modified date from earlier this morning.

There was also a saDocMng.xml.bak, but I did not copy it as it had a last modified date from quite a bit back.

Update:
Bringing over the saDocMng.xml did not help.

saDocMng.db is the only one that matters, but there could be also and .log file for the same. 2MB is promising, it's a good sign there is something.
The .xml file is an artifact from some older version

Yeah unfortunately moving the .db.bak over and renaming it didn't help.

I'm off for a week, so I guess I'll try again the week after next.

Here is what we uncovered. The issue is reproducible and a result of the 13.5 setup while upgrading SQL Editor naming the new executable as SQLEditor.exe or SqlEditor.exe, while the older setups installed it as sqleditor.exe all lower case. The name is important for the Recent Documents relying on features which are name case sensitive. Which is what made it not to see older documents and changes.

A fix has been applied to 13.5.71 setup to revert name changes back to lowercase. After that it can find again previous document history for the SQL Editor.

Thanks. Updating didn't fix it, but I suspect I'd probably need to copy my saDocMgr.db file back over, and haven't tried that yet.

The installer was updated in 13.5.72 not to change the file name case.
You may need to rename 2 files in bin and also in bin64 subfolders, SQLEditor.exe -> sqleditor.exe, to help it find old records, the match is by the file name, and it's case sensitive on purpose. Changes in the installation process were not expected to have this side effect.

I think saDocMgr.db is ok, it's the file name matching. You can connect to that file From SQLEditor with SQLite connections and review what's inside.

Would the case sensitivity in sqleditor.exe impact me, even though my missing documents are related to SSMS?

I'm sorry I was under impression you were having an issue with SQLEditor.

Did you have SSMS recently upgraded too? Does the ssms.exe file name match what's in the doc history db?

	SysOp wrote:
	I'm sorry I was under impression you were having an issue with SQLEditor. Did you have SSMS recently upgraded too? Does the ssms.exe file name match what's in the doc history db?

I did upgrade SSMS recently, but IIRC I did that in conjunction with the SQL Assistant version bump that supported the latest SSMS. I'll have to check on the file names and such.

*Edit: Looked at my original post I did indeed mention SSMS 21 in that.... so maybe it's a two fold problem?

The name case has changed in SSMS 21 as well as a few other things that required a new plugin.