Our team finally got upgraded to SSMS2012!
-
(From 2k8)
But now our entire team's intellisense is slow as melting glass on a warm day.
Does anybody know if there's a fix? VS 2k8 was more or less instant pops for database.schema.table.field, and each one of those items is now taking visible seconds to populate.
HALP! The internets only recommend refreshing local cache, which does absolutely nothing to help with this issue.
-
You know the official answer's going to be "buy a faster computer, chump," right?
-
Yep. Get a faster hamster for the wheel.
-
SSMS's intellisense is so annoying that I turn it off. Auto indenting is crap and it makes you hit tab to complete. Plus, the way SQL is written, you need to put something stupid in the SELECT clause, like "SELECT 1", so you can go on and write the FROM clause while not invalidating the syntax, then you can go back up and get intellisense in the SELECT clause.
-
So I think I know what's happening.
The old servers were located on site, in the same building. The new server we're migrating to is on the opposite coast (literal west coast to east coast move).
So looks like intellisense isn't going to be a thing any more.
-
But now our entire team's intellisense is slow as melting glass on a warm day.
I've also given up on Intellisense. I'm normally halfway done with whatever I'm typing before it pops up anything.
-
Don't any of the Intellisense generators cache schema information? I use SQL Complete, and I think it does that. At least, that would explain why it never notices when I change the schema outside of SSMS. I more like that it auto-generates join statements for our join-heavy database, though.
-
Theoretically it does, in practice the cache is absolute shit.
-
Change database, spam ctrl+shift+R, leave it for a few minutes, hope the cache has updated because the red squiggles under tables I know exist just piss me off
-
The objects are fine. Intellisense auto complete is broken.