3 ms·
Hm. Here's the various limits for Excel: https://support.microsoft.com/en-us/office/excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3 https:
by tyingq 6y ago
Hm. Here's the various limits for Excel:
https://support.microsoft.com/en-us/office/excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3 https://support.microsoft.com/en-us/office/excel-specificati...
Everything from Excel 2007 and up supports 1,048,576 rows by 16,384 columns, if you use the XLSX format. The older XLS format tops out at 65536 rows and 256 columns.
You can, of course, "shard" worksheets ;)
- deleted 6y ago[deleted]
- dopidopHN 6y agoWhat I was getting it at exactly. What prevent a user to split data in thousand of spreadsheet? Given how the corporate world run on excel... someone has done it, somewhere.
- chrismarlow9 6y agoI'm sure it happens all the time from a logical perspective without the user even knowing what a shard is. Example: Too many rows? Okay let's just break it up into monthly sheets and then change this formula to look up the value based on the month. Maybe just use a drop-down for the sheet selection. I think most people could arrive at this answer intuitively who have enough excel experience.
- conductr 6y agoIn practice, excel has all types of issues as you approach a fraction of the available row/column maximums. Your files will be crashing, corrupting, or just impossible to use. If any of your rows or columns have formulas it’s order of magnitude worse at high volumes. That said. Excel has power query/pivot and connects to a large number of external databases, flat files, etc. and it’s best to just never import the entire dataset into excel. That’s my view as a tenured financial analyst working with excel professionally since version 2003.
- AstralStorm 6y agoYup, Excel easily interacts with SQL databases, some of which can handle really big data pretty nicely.
- EvanAnderson 6y agoA fun-to-troubleshoot "stupid Excel trick" that I ran into, arguably "caused" by the increased row limit in >2007 versions: User typically drags formatting and "default" values down to row 65535 in Excel 2003-based "data collection" spreadsheet. Does the same thing in a >2007 spreadsheet, except they drag it down to row 1,048,576. The file size doesn't take a dramatic "hit" (since XLSX files are really ZIP archives), but performance goes in the toilet. Knowing enough to unzip XLSX and DOCX files any eyeball the XML directly can often identify fun corner cases. (There's probably a ton of fuzzing fruit to be picked in the Office products using "malformed" documents, too.)
- zulfazli 6y agoNever thought about examining the XML before... I wonder how feasible it is to create a script that checks excel for optimizations related to this...
- m463 6y agoI wonder if excel could get cuda support...
- carl_dr 6y agoAs the UK found out just recently : https://www.bbc.com/news/technology-54423988 https://www.bbc.com/news/technology-54423988
- rvba 6y agoThey added a new column for each new chunk of data. In this scenario Excel, with its 16 384 columns is better than say PostgreSQL which has a limit of only 16 000 :) If they stored the data in rows with some additonal column(s) to mark date and source, they would probably run out of rows in Excel... but here is a clear example of someone not knowing how to use the tool. So they could also make errors in a real database. Also who knows if this wasnt done on purpose to show better numbers and later blame it on a "computer bug".