Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #2261
| From | Anton Shepelev <anton.txt@g{oogle}mail.com> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Re: No covering indices for table types? |
| Date | 2024-07-15 14:27 +0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <20240715142708.72511985f0c9753807aa6357@g{oogle}mail.com> (permalink) |
| References | <20240712151501.d23ddf433e73ae41365603cf@g{oogle}mail.com> <XnsB1ADF2304F6C3Yazorman@127.0.0.1> |
Erland Sommarskog to Anton Shepelev: > > For efficient querying and joining, I need a covering > > index on the [moment] field that includes [value], but > > the INCLUDE keyword does not seem to be suported: > > Starting with SQL 2019, it is: > > CREATE TYPE series_t AS TABLE > ( moment DATETIME NOT NULL, > value FLOAT, > INDEX Main(moment) > INCLUDE (value) > ) Glad to know MSSQL is improving, although I am using an older version. > If you are an older version, I would suggest adding value > as an index key is the best in most situations. Indeed. That's that I did. > I will submit an edit to the CREATE TYPE topic. Thank you. I myself have fixed a few of their documentation articles about .NET, including those describing the connection-string syntax. How strange that Microsoft has decidied to let the community wrote their documentation... -- () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments
Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Find similar
No covering indices for table types? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-07-12 15:15 +0300
Re: No covering indices for table types? Erland Sommarskog <esquel@sommarskog.se> - 2024-07-12 23:48 +0200
Re: No covering indices for table types? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-07-15 14:27 +0300
csiph-web