Code Snippets stopped working in Management Studio. Only by switching the Default Key Char to a different setting, then back did it start working again. Sorry, don't have more info.

Wed Jan 02, 2008 10:04 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6579

If this occurs again, please paste relevant section of your sqlassist.sas file storing SSMS settings. To find this section, search for "MS Management Studio" text. The file is located in the C:\Program Files\SQL Assistant\Data folder

Wed Jan 02, 2008 10:11 am

judahr

Joined: 09 Mar 2007Posts: 314Country: United States

Submitted the file through support email. Closing and reopening SQL Assist resolves the issue.

Thu Jan 17, 2008 12:42 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6579

Do you still expirience this issue?

Wed Mar 12, 2008 2:22 pm

judahr

Joined: 09 Mar 2007Posts: 314Country: United States

I haven't seen it in a while. I only use the feature occasionally.

Wed Mar 12, 2008 2:32 pm

judahr

Joined: 09 Mar 2007Posts: 314Country: United States

Just had this issue this morning. Found opening a new query window and using a snippet then going back to the original query window also resolves the problem.

Tue Mar 18, 2008 6:07 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6579

Was it a code snippet that requires an active database connection, like cfetch, or an object-less snippet, like sm?

Tue Mar 18, 2008 3:54 pm

judahr

Joined: 09 Mar 2007Posts: 314Country: United States

object-less: ij -> INNER JOIN

Tue Mar 18, 2008 3:56 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6579

This seems to be a custom code snippet. Is it set to use the (Default) for the snippet activation key or some custom hotkey?

Tue Mar 18, 2008 4:03 pm

judahr

Joined: 09 Mar 2007Posts: 314Country: United States

default

Wed Mar 19, 2008 1:13 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6579

I found a way to reproduce it. This happens when a code snippet is used after connection to SQL Server is broken. In most cases SQL Assistant automatically recovers broken connections, but in that case it doesn't, and then the connection stops working affecting Intellisense (before each popup it check database context and that fails without working connection).

I submitted a bug report to have this connection handling fix.

By the way, most simple ways to workaround this issue is to use either Disconnect item in SQL Assistant menu or Refresh Cache. Either one will make it restore connection next time it needs to show a popup. Another solution is to increase timeout settings in SQL Server so that doesn't drop inactive connections when nobody is asking it to drop them.

Wed Mar 19, 2008 1:20 pm

judahr

Joined: 09 Mar 2007Posts: 314Country: United States

SysOp wrote:

By the way, most simple ways to workaround this issue is to use either Disconnect item in SQL Assistant menu or Refresh Cache. Either one will make it restore connection next time it needs to show a popup. Another solution is to increase timeout settings in SQL Server so that doesn't drop inactive connections when nobody is asking it to drop them.

I don't know that it is just that. I just added a snippet called cl that just output "Contact". Opened SSMS and typed Select * from cl<ctrl> Snippet didn't work. Tried the following:

Refreshing the cache
Disconnecting
New Query window.

Interestingly, some of the other snippets work.

Closed and reopened SSMS and it worked. Note: I don't use Add-In mode. I know we discussed this before, I thought that the disconnect/reconnect or cache refresh would reload the snippets.