Turn off Predictive Typing

Question

Post reply

Turn off Predictive Typing

brunm

SSCommitted

Points: 1792
More actions
November 12, 2010 at 3:09 am

#242793

Hi,
There does anyone know how to turn of the Predictive Typing feature in SQL Server 2008 and 2008 R2 when typing in a query analyser window
This has to be the worst feature i have ever seen, it now takes longer to type a piece of SQL as i keep having to correct what it assumed i wanted to type.
Thanks in advance for any help
Cheers,
Brunzire

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Henrico Bekker One Orange Chip Points: 27652 More actions · Answer 1

It's called IntelliSense.

Check you SSMS Options.

"Worst feauture" ?:w00t:

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

brunm SSCommitted Points: 1792 More actions · Answer 2

Thanks for the response i found an icon on the toolbar that allows me to turn it off.

Yes it is 'the worst' feature as some of us who use computers for a living have taught themselves to touch type. This combined with a sensible database naming convention means we do not need to be prompted with key words or column names when writing queries

Henrico Bekker One Orange Chip Points: 27652 More actions · Answer 3

Well, every one is entitled to their opinions, but I have to disagree.

IntelliSense is a great feature and cuts dev time in half over a long period for us who also type alot, and who have also been using computers daily for a long time....and dont want to type out schemaname.verylongtablenamewithunderscores.columname....

see? 😉

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

nigelrivett SSCertifiable Points: 5362 More actions · Answer 4

For those of us who are in the habit of using s and i for column names it's a bit of a pain.

Cursors never.
DTS - only when needed and never to control.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

Personally I find the SSMS built in intellisense terrible. I spend more time fixing what it thought I meant than I would have spent just writing the query. A certain 3rd party vendor's intellisense however works very well, partially because there are pages of options that let me configure exactly how I want it to behave

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Henrico Bekker One Orange Chip Points: 27652 More actions · Answer 6

GilaMonster (11/12/2010)
Personally I find the SSMS built in intellisense terrible. I spend more time fixing what it thought I meant than I would have spent just writing the query. A certain 3rd party vendor's intellisense however works very well, partially because there are pages of options that let me configure exactly how I want it to behave

I do agree on that certain 3rd party tool being better, I also use and prefer it to MS.

But at the end of the day, IntelliSense is better than NO IntelliSense...for me..

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

nigelrivett SSCertifiable Points: 5362 More actions · Answer 7

Usually goes something like

select s<space>

s<space>

s<space>

s<right arrow>

The for anything within 15 mins I'll correct it on the first attempt. After a 15 min gap brain gets reset.

Cursors never.
DTS - only when needed and never to control.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 8

nigelrivett (11/12/2010)
Usually goes something like
select s<space>
<delete the word>
s<space>
<delete the word>
s<space>
<delete the word>
s<right arrow>

Exactly. I can write queries faster without the built-in intellisense. With the aforementioned 3rd party version, I have <space> disabled as a completion character so that unwanted completions don't happen.

I'd like the MS version more if there were any configuration options.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

SYounger Valued Member Points: 59 More actions · Answer 9

Is there an option for sorting. When writing queries, often we will see tables with extended names being returned initially:-

ie "tbl_customer_reports" is returned before "tbl_customer" is viewable in the list.

bsenior SSC Journeyman Points: 83 More actions · Answer 10

LOL! gotta laugh at column names that are S and I. The thing with intellisense is it allows you to use more descriptive naming of columns without the hassle of having to rewrite the full column name out (depending on the name).

While its far from perfect, I find the intellisense to be very useful.

It just means your touch typing has to include one more keypress. Esc 🙂

I do that a lot. When I'm typing in something that perhaps is not coming up correctly, I'll just hit esc to stop the somewhat-intelligent sensing of the word I want to use 🙂

Thats not to say I'm getting it to work 100% of the time, but its definitely better than nothing.

Jeff Moden SSC Guru Points: 1003851 More actions · Answer 11

Henrico Bekker (11/12/2010)
Well, every one is entitled to their opinions, but I have to disagree.
IntelliSense is a great feature and cuts dev time in half over a long period for us who also type alot, and who have also been using computers daily for a long time....and dont want to type out schemaname.verylongtablenamewithunderscores.columname....
see? 😉

In that case, I have to agree with the first person that disagreed with your agreement. 😀

I hate Intellisense. Try typing t.N and see what you get. Try typing IDENTITY or just ID. Huge PITA for me. I love the part that matches parenthesis but hate pretty much everything else about it.

Of course, like you said, to each their own. I would never forbid someone in my shop from using it. Some folks that can't touch type swear by it. Heh... since I can touch type, I just swear at it. 😛

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)