# Dataset size and time coverage This is a multi-table dataset with five tables, not a single one. The tables differ in size and in how they cover time. ## Rows and columns per table | Table | Rows | Columns | |---|---|---| | raw_kaggle | 237,205 | 17 | | return_kaggle | 237,196 | 17 | | serve_kaggle | 237,185 | 17 | | players_tournament_man_ | 6,422 | 4 | | players_man_ | 462 | 3 | The three large tables hold about 237,000 rows each, and the row counts differ by only a few rows. The two players tables are much smaller. ## Time period - **The three main tables** (`raw_kaggle`, `return_kaggle`, `serve_kaggle`) each have a `Date` column stored as text. All rows parsed as dates in every table (for example 237,205 of 237,205 in `raw_kaggle`). Each table spans **2001-08-13 to 2024-10-28**, about 23 years. - **`players_tournament_man_`** has a numeric `year` column ranging from **2002 to 2024**, with no nulls. - **`players_man_`** has a `playing_years` text column. I did not get its range, so I can't say what period it covers. ## Caveats - I did not check whether the three main tables contain the same matches, so I can't say whether they overlap. The near-identical row counts suggest they are related. Adding the counts together would probably double-count. - I did not check whether the coverage is continuous. The min and max dates don't show gaps, such as off-season periods or missing years. - Any total row count across all tables would depend on how the tables relate, so I'm not giving one. **Summary:** The main tables have about 237,200 rows and 17 columns each, covering August 2001 to October 2024. The two smaller player tables have 6,422 rows by 4 columns and 462 rows by 3 columns.