You're correct - the standard tabs can only hold roughly 1.2 million rows.
The way to get around that limitation is to use the Data Model within Power Pivot:
It can accept all of the data connections a standard Power Query can (ODBC, Sharepoint, Access, etc):
You build the connection in Power Pivot to your big tables and it will pull in a preview. If needed, you can build relationship between tables with the Relationship Manager. You can also use DAX to build formulas just like in a regular Excel tab (very similar to Visual Basic). You can then run Pivot Tables and charts against the Data Model to pull out the subsets of data you want to look at.
The load times are pretty decent - usually it takes 2-3 minutes to pull a table of 4 million rows from an SQL database over ODBC, but your results may vary depending on datasource. It can get memory intensive, so I recommend a machine with a decent amount of RAM if you're going to build anything for professional use.
The nice thing about building it out this way (as opposed to using independent Power Queries to bring out your data subsets) is that it's a one-button refresh, with most of the logic and formulas hidden back within the Data Model, so it's a nice way to build reports for end-users that's harder for them to fuck up by deleting a formula or hiding a column.
Seriously - I can parse multiple tables of 5+ million row each... in EXCEL... on a 10 year old desktop and not have the fan even speed up. Even the legacy Access database I work with handles multiple million+ row tables better than that.
Sounds like the kid was running his AI hamsters too hard and they died of exhaustion.
Paternity leave saved my life when I was a young father with an ill wife. Take as much time as you can.
Also, side note, the year I took off of work to care for them when my sons were small (3 and 5) I look back on as one of the best decisions I ever made. Despite the fact we were flirting with homelessness, the bonding and memories made a huge impact on them, and now that they're adults, we have an amazing relationship that far surpasses the distant bond I have with my own father.
Nah, that was appropriate after s/he spammed my account with multiple messages and reported the post. Kinda done with dumbfucks who don't know how to take a joke.
When /r/technicallythetruth tries to do a Nazi salute...
According to Musk's logic, Manson should be set free because he didn't actually participate in the slaughter of innocents in an insane attempt to start a race war. He just told his followers to do it.
First off, it's not his work. It's a parody. Political satire has been in use for thousands of years. Do we ban the Producers because it has "Springtime for Hitler"? No, because every person with half a brain cell knows that it's a joke.
Secondly, following your logic, we shouldn't discuss what these Nazi fucks do or say, because that would be platforming them. That's exactly what they want you to do - censorship is kinda the highlight of a fascist regime.
Take a breath, pull your head out of your moral panic, and laugh a little. This /c/memes, not /c/politics.
But all in all, I'd say that lemmings are much more active than Redditors - just based on responses to my posts and comments. I've earned 15k karma on this account, far more than any of my vastly older reddit accounts. Take that for what you will, but I've personally found the community here much more active, especially as of late.
You're correct - the standard tabs can only hold roughly 1.2 million rows.
The way to get around that limitation is to use the Data Model within Power Pivot:
It can accept all of the data connections a standard Power Query can (ODBC, Sharepoint, Access, etc):
You build the connection in Power Pivot to your big tables and it will pull in a preview. If needed, you can build relationship between tables with the Relationship Manager. You can also use DAX to build formulas just like in a regular Excel tab (very similar to Visual Basic). You can then run Pivot Tables and charts against the Data Model to pull out the subsets of data you want to look at.
The load times are pretty decent - usually it takes 2-3 minutes to pull a table of 4 million rows from an SQL database over ODBC, but your results may vary depending on datasource. It can get memory intensive, so I recommend a machine with a decent amount of RAM if you're going to build anything for professional use.
The nice thing about building it out this way (as opposed to using independent Power Queries to bring out your data subsets) is that it's a one-button refresh, with most of the logic and formulas hidden back within the Data Model, so it's a nice way to build reports for end-users that's harder for them to fuck up by deleting a formula or hiding a column.