A one-time upload answers a question about the data as it looked the moment you exported it. A connected source in tableArth.ai answers the same question about the data as it is right now — every time you ask — because a Workbook keeps itself synced with the source instead of waiting for someone to re-upload it.
The two ways to bring data to AI
There are only two ways to get a dataset in front of an AI analytics engine: hand it a file, or point it at the source. tableArth.ai supports both, and choosing between them isn't about which is more advanced — it's about which question you're actually asking.
Uploading a CSV or Excel file gives tableArth.ai a copy, correct the instant it's created and drifting from reality the instant anything changes upstream. Connecting a source instead — a Google Sheet, an Excel file kept live, a database such as MySQL, PostgreSQL, or MongoDB — gives it a link. The link doesn't drift, because the Workbook behind it checks in with the source directly instead of relying on someone to export a fresh copy.
Most teams default to uploading, because that's the habit a decade of spreadsheets and BI tools trained: export, attach, upload, repeat. That made sense when a reliable live connection was hard to build. It's a worse default now that connecting is the easier path for any question you'll ask more than once.
What a one-time upload really gives you
An upload is honest about what it is: a copy of the data, frozen at export time. Asked once, that's exactly what you want. The cost shows up the second time you ask.
Staleness. The answer tableArth.ai gives you is only as current as the file you handed it. If the sheet behind that export changed an hour later, every number on screen still reflects the old version — and nothing warns you.
Version drift. Ask about a file twice, a week apart, and you're really asking about two different exports. Spread that across a team each re-uploading its own copy of the "same" spreadsheet, and you get several defensible, slightly different answers to one question.
Manual toil. Someone has to notice the source changed, re-export it, and re-upload it — every time, for every file that matters. That job doesn't scale past a handful of sources, and it's the first thing skipped when a team gets busy, which is exactly when the data is moving fastest.
None of this makes uploading itself a mistake — tableArth.ai fixed the timeout issues that used to make bigger files slow to upload, so the process is smoother than it used to be. The limits above are about what happens after the file lands: nothing, until someone repeats the cycle by hand.
What connected data changes
Connect the same Google Sheet, Excel file, or database instead of uploading it, and a few concrete things change.
A Workbook holds the connection and keeps it synced automatically, so the moment the underlying sheet or table changes, your analysis reflects that — no export, no re-upload, no reminder to a teammate.
Multi-tab and multi-table data stays multi-tab and multi-table. tableArth.ai reads a workbook with several tabs, or a database with several tables, as related structures instead of one blob you flatten first. Ask a question that spans tabs or tables and it joins the related data itself, the way it would join two tables in a database — no VLOOKUPs, no combining by hand before you're even allowed to ask. Here's how those joins work.
One question can also reach every source at once: a multi-source Workbook can hold a Sheet, an Excel file, and a database side by side, and a single plain-English question pulls from all of them and returns one unified answer instead of three results you stitch together by hand. Connected sources also tend to grow, which is what "live" means — tableArth.ai is built to load and stream that scale reliably, the same reliability work that also fixed upload timeouts on the file side.
For a database, there's no export step at all. Query PostgreSQL, MySQL, MongoDB, or Druid running inside your own private environment directly, in plain English — there's no file in the loop to go stale, because there was never a copy to begin with.
The differences add up:
| Capability | One-time file upload | Connected in tableArth.ai |
|---|---|---|
| Data freshness | Frozen at export time | Live — reflects the source |
| Keeping it current | Re-upload every change | Auto-syncs, no re-uploading |
| Multiple tabs / tables | Flatten into one sheet | Understood & joinable |
| Join across sources | Not possible | Ask across all of them |
| Large datasets | Upload timeouts | Reliable, streamed loads |
| Private databases | Export required | Query in place, in your env |
When uploads are still the right call
None of this makes uploading wrong. It makes it situational, and being fair about when it's the right call is part of using tableArth.ai well.
Upload when the question is genuinely one-off — a file someone emailed you for a single gut-check before a meeting, a dataset you'll look at once and never touch again. Upload when the data is actually static, like a closed financial quarter or a survey result that won't be revised. And upload when you're just trying tableArth.ai for the first time and want to see an answer on a sample file before connecting anything real.
The test that decides it: if you expect to ask about this data more than once, or the source keeps changing underneath it, connect it instead of re-uploading it next week. If neither is true, upload it, get your answer, and move on — that's exactly what the upload path is for.
Making the switch
Moving from an upload habit to a connected one doesn't mean touching your existing files.
Start with whatever you re-upload most. If there's a Google Sheet or Excel workbook you re-export every week, connect it instead — same content, but tableArth.ai now checks it against the source rather than trusting a copy you handed it once. See the file-specific steps for Google Sheets and Excel. Pulling from a database through CSV exports today? Connect the database directly and skip the export step.
Then group related sources into a Workbook, so a Sheet, an Excel file, and a database that feed the same analysis sit together — one question can reach across all of them instead of three separate uploads stitched together by hand.
You don't need to connect everything, just the sources you'd otherwise be re-uploading. See every source you can connect.
Is uploading a file bad?
No. Uploading is the right choice for a genuine one-off — a quick check before a meeting, or trying tableArth.ai for the first time on a sample file. It becomes the wrong choice only when you keep doing it for the same source, because each upload is a fresh snapshot someone has to keep replacing by hand.
How does live sync work?
Connected sources live inside a Workbook. The Workbook keeps a link to each source — a Google Sheet, an Excel file, or a database such as MySQL or MongoDB — and checks it automatically, so as the underlying data changes your analysis stays current without anyone re-uploading anything.
Do I ever need to re-upload?
Not for a connected source — that's the point of connecting it. You'd still upload when you want a one-off look at a file that isn't connected, or when you're working with a dataset that's genuinely static and won't change again.
What about large files?
Large uploads are handled reliably. The timeout issues that used to affect bigger files are fixed, so the upload process is smoother and more consistent for large datasets — and for anything that keeps growing, connecting the source instead of re-uploading it is still the more reliable long-term path.