Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #1912
| From | Michael Cole <noone@invalid.com> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Best Practices for Wide Columns in Tables |
| Date | 2015-04-30 19:46 +1000 |
| Organization | A noiseless patient Spider |
| Message-ID | <mhstjv$v1d$1@dont-email.me> (permalink) |
This is one where there seems to be a lot of conflicting advice out there in google-land. If we have tables with one or more wide columns - VarChar with size of over 8K in total - should these columns be moved to their own wide-column table with the initial table simply linking to them? Is there much of an advantage/disadvantage to this, or does it actually depend on how much is stored in them, not the empty column widths? -- Michael Cole
Back to comp.databases.ms-sqlserver | Previous | Next — Next in thread | Find similar
Best Practices for Wide Columns in Tables Michael Cole <noone@invalid.com> - 2015-04-30 19:46 +1000
Re: Best Practices for Wide Columns in Tables Erland Sommarskog <esquel@sommarskog.se> - 2015-04-30 12:29 +0000
Re: Best Practices for Wide Columns in Tables rja.carnegie@gmail.com - 2015-05-06 19:46 -0700
Re: Best Practices for Wide Columns in Tables Erland Sommarskog <esquel@sommarskog.se> - 2015-05-07 21:29 +0200
csiph-web