Invalid Column Name issue with SSMS 18

Question

I just installed SQL Server 2019 Express, and SSMS (18.9). I also downloaded the AdventureWorksDW2019 Database from Microsoft. I successfully set up my connection.

I've already tried doing this -> Enable IntelliSense: For all query windows, please go to Tools >> Options >> Text Editor >> Transact-SQL >> IntelliSense, and select Enable IntelliSense. For each opening query window, please go to Query >> IntelliSense Enabled. Enable statement completion: please go to Tools >> Options >> Text Editor >> Transact-SQL >> General, and check on Auto list members and Parameter information boxes. Refresh IntelliSense local cache: please go to >> Edit >> IntelliSense >>Refresh Local Cache or use the CTRL+Shift+R keyboard shortcut to refresh. Wait a minute or two for the Refresh to finish before trying again.

The Issue: I am able to select a table, right-click and 'Select Top 1000 Rows' and the query runs fine, displaying the results as expected. However, for some reason, each column is underlined red stating 'Invalid column name'.

Because of this, I am unable to use IntelliSense when writing my own queries. I have checked that the correct IntelliSense settings are checked.

See screenshots below:

Right-click -> 'Select Top 1000' works, but still no IntelliSense and same red underline 'Invalid Column Name'

Manually wrote own query, results show as expected, but still no IntelliSense and same red underline 'Invalid Column Name'

/****** Script for SelectTopNRows command from SSMS  ******/
SELECT TOP (1000) [DateKey]
  ,[FullDateAlternateKey]
  ,[DayNumberOfWeek]
  ,[EnglishDayNameOfWeek]
  ,[SpanishDayNameOfWeek]
  ,[FrenchDayNameOfWeek]
  ,[DayNumberOfMonth]
  ,[DayNumberOfYear]
  ,[WeekNumberOfYear]
  ,[EnglishMonthName]
  ,[SpanishMonthName]
  ,[FrenchMonthName]
  ,[MonthNumberOfYear]
  ,[CalendarQuarter]
  ,[CalendarYear]
  ,[CalendarSemester]
  ,[FiscalQuarter]
  ,[FiscalYear]
  ,[FiscalSemester]
FROM [AdventureWorksDW2019].[dbo].[DimDate]

Any help is greatly appreciated!

Answer 1

This is a known issue with SSMS 18.9, and a hotfix is currently being developed.

https://twitter.com/SysAdminDrew/status/1382869366702624774?s=20