Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 5
    Looks like you need to apply either [MaxLength] or [StringLength] attributes. Some additional possible negative factors of too wide columns are mentioned in @PaulWhite's answer here Commented Aug 20, 2013 at 21:57
  • I know it does hurt performance. When I define my own tables with SQL I use varchar(n). My question was more about how much it hurts performance(though I realize as posted that wasn't explicitly clear). Commented Aug 21, 2013 at 14:30
  • I would also be concerned about the memory requirement, if you have a non-trivial query i.e. with a GROUP BY, when many rows are expected to be part of the query. SQL Server will only run 3 big-memory queries simultaneously. The rest will be queued. Commented Sep 23, 2024 at 9:33