Can you help me understand how max rows works? I usually run queries to get the SQL right and then move the query to another tool like Excel or Power BI. As such, the default max rows of 500 is fine. Occasionally I want to export all the rows. It looks like I have to change max rows to do this? In my testing, the "Fetch and save all" button seems to really be "Fetch and save all up to max rows." If that's the case, I know I'm going to bump up max rows and forget to change it back.
Typically my exports are ~50,000 rows but could be as high a couple million. If I set max rows to 2 million and forget about it, how will it affect query run time and database load for my query development when I just need to see a little data? Will this cause my development queries to run slower and cause more database load? I don't really understand how paging works. Does it download all the data, or only when I page forward? If a high max rows hurts, it would be nice to have a button to fetch and save all that ignores max rows.