Connect Google Play Review to Azure SQL

Start with a connected Google Play Review source and an existing Azure SQL database. Create a datastream between them, then configure the accounts, fields, schedule, and "ratings" table.

Select concrete Google Play Review fields such as Average Rating, Helpful Votes, Rating, and Day of the year. You can rename the chosen columns, preview the result, and write them to Azure SQL tables such as review sources, locations, and reviews.

Set an initial fetch period for Google Play Review, then choose the frequency and lookback window for the job writing to "ratings". Catchr rewrites that selected period on each run.

The partition field tells Catchr which Google Play Review rows in "ratings" belong to the period being refreshed. If you omit it, every run appends records rather than updating them.

With Google Play Review data, an Azure SQL query can summarize review volume and average rating by location over the last 30 days. A query built around Average Rating and Helpful Votes can support trend reviews, account comparisons, and operational reporting.

Yes. Connect an existing Azure SQL  database first. The Catchr job creates and populates the destination table you configure inside that database.

Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.