Ah ... that's the salient bit. I don't know why it would complain (and I don't make enough use of IntelliSense to know how to advise you to improve / fix it), but the red-wiggly-line is based on some Meta Data which SQL uses to try to spot typing mistakes, in real time, and my guess is that either a) the metadata is stale / incomplete, for some reason, or b) it just isn't possible to resolve at that point or c) MS haven't made Intellisense work for that particular situation.
is just possible that putting a space between TableName and "(" might cheer it up - but if so that's a bit pants!
Of course, now I look at it through a beginner's eyes, I can see how useful it WOULD be for that red-wiggly-line to have no false-errors.
I now also see what you mean about running it and getting no errors ... definitely nothing to worry about, in this case, as your code is indeed "clean".
I use the GUI Table Designer, set up all the columns, indexes, FKeys etc. that I want but then I do NOT press "Save" but instead use the "Create Script" button. SQL then generates the script for me - which I can check / modify or just use as the basis for multiple snippets of DDL change that will form part of my release / upgrade script.
By the by, I recommend not using the "TEXT" datatype as it has been deprecated for some time. The replacement is
VARCHAR(MAX) - which has a lot more flexibility than the old TEXT datatype.