Author |
Message |
stephh
Joined: 29 Jul 2021 Posts: 46
|
|
[12.0.191 Pro] - SQLAssistant disable without any reasons |
|
Hi,
I don't undersdand why sometime my SQLAssistant turn off and disable ?
Can anyone help me ?
Thanks :)
Last edited by stephh on Thu Jan 20, 2022 4:12 am; edited 1 time in total |
|
Wed Jan 19, 2022 9:04 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
From the screenshot I can't say with certainty which kind of file or script is opened. So here is just an idea, whenever it "thinks" the current file is a non SQL script because it doesn't appear to have .sql or .dll extension, it turns itself off as not to interfere with file editing.
|
|
Wed Jan 19, 2022 11:05 am |
|
 |
stephh
Joined: 29 Jul 2021 Posts: 46
|
|
|
|
Yes, you're right, I did not explain the context.
It's in SSMS 18.10, and the file opened is a .sql.
But it seems that there is special and invisible character somewhere in the code and SQL Assistant turn off.
I'll continue to investigate ....
Thanks SysOp
|
|
Thu Jan 20, 2022 2:31 am |
|
 |
stephh
Joined: 29 Jul 2021 Posts: 46
|
|
|
|
Ok, I found something
Try this in SSMS , new query window
Start to comment your code with :
/**************
* comment
***************/
Then, type "sel" and SQL Assistant completion starts :
Now, add a quote in the comment :
/**************
* comment '
***************/
Then type "sel" and SQL Assistant completion is disabled, and after few minutes, turns off

|
|
Thu Jan 20, 2022 3:39 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
I tried the same with several different versions and was unable to reproduce results of your test case.
Could you please check the log file C:\Users\[your name]\AppData\Roaming\SQL Assistant\12.0\SQLAssist.log file after you reproduce the issue again? Are there any errors or exceptions at the end of the file?
Just in case, it's safe to empty that log file before testing, as it might be big and difficult to navigate. You can't delete it while SSMS is running, but you can open it Notepad or something else, and delete everything and save empty file.
Last edited by SysOp on Wed Feb 09, 2022 11:49 am; edited 1 time in total |
|
Thu Jan 20, 2022 12:58 pm |
|
 |
stephh
Joined: 29 Jul 2021 Posts: 46
|
|
|
|
Hi,
No, there is nothing suspect in the log file :-(
I ran a SQL Profiler.
When I type "select ..." the query "Objects (SSMS) + Typed Synomys" is executed.
But once I type a quote in a comment, nothing is executed....
Note that the quote must be in a comment like this : /* .... */ , and not a comment with the double dash --
|
|
Fri Jan 21, 2022 3:40 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
Thank you. Is that issue reproducible outside of SSMS in other editors?
|
|
Fri Jan 21, 2022 9:41 am |
|
 |
stephh
Joined: 29 Jul 2021 Posts: 46
|
|
|
|
Yes, same thing with "SQL Editor"
I'll try to reset my settings.
How can I do that without reinstall SQLAssistant ?
Is there a default SqlAssist.setup.sas file to import ?
Thanks.
|
|
Fri Jan 21, 2022 10:06 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
 |
 |
I'll try to reset my settings.
How can I do that without reinstall SQLAssistant ?
Is there a default SqlAssist.setup.sas file to import ?
Thanks. |
Please open the Options dialog, click Import/Export button in the left bottom corner, tick Load Default Options checkbox, and click the Import button. It won't overwrite your saved database connections and some other things, but for the most it will restore all other settings to the factory defaults.
|
|
Fri Jan 21, 2022 11:24 am |
|
 |
stephh
Joined: 29 Jul 2021 Posts: 46
|
|
|
|
Hello SysOp,
I have the same issue after restoring default settings :-(
(Sorry for the delay..)
|
|
Wed Feb 09, 2022 7:12 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
May I ask you to try reproducing it one time using different connection type? Open SQL Editor, In the connection settings choose ODBC instead of ADO.NET for the connection type, connect and try the same test with a single quote mark entered after "comment"
Also, when you test, please verify you have SQL Assistant system tray application running, that application is responsible for showing notification messages like lost connections, and exception messages when they occur.
|
|
Wed Feb 09, 2022 11:58 am |
|
 |
stephh
Joined: 29 Jul 2021 Posts: 46
|
|
|
|
Hi,
Same thing....
I tried SQL Editor x86 and x64.
SLQ Assistant in systray is running and not showing any error.
|
|
Fri Feb 11, 2022 2:55 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
I have run out of ideas and have to take this case over to the support. Could you please remind me which SQL Assistant version you are running including the build number?
|
|
Fri Feb 11, 2022 10:10 am |
|
 |
stephh
Joined: 29 Jul 2021 Posts: 46
|
|
|
|
SQLAssistant : 12.0.191
SQL Editor : 12.0.191
SSMS: 18.10
Thanks :)
|
|
Fri Feb 11, 2022 10:28 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
I've got some good news. It appears to be a know bug, which is going to be fixed in 12.1, and expected soon. We are still working on some issues that need to be resolved before the 12.1 release.
|
|
Sat Feb 12, 2022 10:00 am |
|
 |
|