September 14, 2016 at 8:18 am
If anyone else has experienced this, it would be interesting to know.
After upgrading to SSMS 2016, I noticed that clicking on 'New Query' would take 30 seconds to a minute to open a new tab in SSMS β even for a locally hosted instance.
I think I've found a fix β it seems to be working so far, at least.
1) Uncheck 'Enable Intellisense' under
Tools / Options / Text Editor / Transact-SQL / Intellisense
2) If you have SQL Prompt installed, uncheck 'Enable Suggestions' under the SQL Prompt menu.
Restart SSMS and now re-enable the above two options.
'New Query' is fast again!
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
September 14, 2016 at 8:34 am
Hi Phil,
are you running the latest version with the latest updates? Had this problem few updates ago and after one update it went away.
π
September 14, 2016 at 8:38 am
Eirikur Eiriksson (9/14/2016)
Hi Phil,are you running the latest version with the latest updates? Had this problem few updates ago and after one update it went away.
π
I try to keep up-to-date. Current version is 13.0.15700.28.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
September 14, 2016 at 9:22 am
Phil Parkin (9/14/2016)
Eirikur Eiriksson (9/14/2016)
Hi Phil,are you running the latest version with the latest updates? Had this problem few updates ago and after one update it went away.
π
I try to keep up-to-date. Current version is 13.0.15700.28.
That was current way back on the 22nd Aug 2016 π
π
September 14, 2016 at 9:41 am
No, and we're using exactly the same version as you. We're not using SQL Prompt.
For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
September 14, 2016 at 11:20 am
ChrisM@Work (9/14/2016)
No, and we're using exactly the same version as you. We're not using SQL Prompt.
Thanks Chris. If someone else is experiencing this problem, I hope that they find this thread useful. It's such a relief to have SSMS responsive again.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
January 6, 2017 at 1:27 pm
Phil Parkin (9/14/2016)
If anyone else has experienced this, it would be interesting to know.
Sorry for replying to an old post, but THANK YOU! This fixed the issue for me (I do not have SQL Prompt installed, only had to disable/re-enable IntelliSense)
January 6, 2017 at 1:38 pm
JasonH-ITG (1/6/2017)
Phil Parkin (9/14/2016)
If anyone else has experienced this, it would be interesting to know.Sorry for replying to an old post, but THANK YOU! This fixed the issue for me (I do not have SQL Prompt installed, only had to disable/re-enable IntelliSense)
I've since found that merely restarting SSMS also works ... maybe it will work for you too.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
January 6, 2017 at 1:49 pm
Nope, not in my case; it had persisted between restarting SSMS and reboots. It was only occurring on one of my servers; workstations and other servers did not have this issue. Since disabling/enabling Intllisense, it hasn't come back (I've closed and re-opened SSMS a few times.)
January 6, 2017 at 2:02 pm
JasonH-ITG (1/6/2017)
Nope, not in my case; it had persisted between restarting SSMS and reboots. It was only occurring on one of my servers; workstations and other servers did not have this issue. Since disabling/enabling Intllisense, it hasn't come back (I've closed and re-opened SSMS a few times.)
This problem gets stranger and stranger. Are you up to date with SSMS versions (13.0.16100.1 is current build, I believe)?
Regardless of that, glad my earlier post helped you.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
January 6, 2017 at 2:17 pm
Phil Parkin (1/6/2017)
JasonH-ITG (1/6/2017)
Nope, not in my case; it had persisted between restarting SSMS and reboots. It was only occurring on one of my servers; workstations and other servers did not have this issue. Since disabling/enabling Intllisense, it hasn't come back (I've closed and re-opened SSMS a few times.)This problem gets stranger and stranger. Are you up to date with SSMS versions (13.0.16100.1 is current build, I believe)?
Regardless of that, glad my earlier post helped you.
Yes, that's the version I'm currently on. It's been upgraded a few times (was initially installed about 6 months ago) and I believe this issue was always happening since the initial install.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply