BigQuery Fintech Dataset
Comprehensive fintech data for loan and customer analysis.
@kaggle.mustafakeser4_bigquery_fintech_dataset
Comprehensive fintech data for loan and customer analysis.
@kaggle.mustafakeser4_bigquery_fintech_dataset
Dataset: cloud-training-demos.fintech
This dataset, hosted on BigQuery, is designed for financial technology (fintech) training and analysis. It comprises six interconnected tables, each providing detailed insights into various aspects of customer loans, loan purposes, and regional distributions. The dataset is ideal for practicing SQL queries, building data models, and conducting financial analytics.
customer:
Contains records of individual customers, including demographic details and unique customer IDs. This table serves as a primary reference for analyzing customer behavior and loan distribution.
loan:
Includes detailed information about each loan issued, such as the loan amount, interest rate, and tenure. The table is crucial for analyzing lending patterns and financial outcomes.
loan_count_by_year:
Provides aggregated loan data by year, offering insights into yearly lending trends. This table helps in understanding the temporal dynamics of loan issuance.
loan_purposes:
Lists various reasons or purposes for which loans were issued, along with corresponding loan counts. This data can be used to analyze customer needs and market demands.
loan_with_region:
Combines loan data with regional information, allowing for geographical analysis of lending activities. This table is key for regional market analysis and understanding how loan distribution varies across different areas.
state_region:
Maps state names to their respective regions, enabling a more granular geographical analysis when combined with other tables in the dataset.
loan_count_by_year table to observe how lending patterns evolve over time.This dataset is ideal for those looking to enhance their skills in SQL, financial data analysis, and BigQuery, providing a comprehensive foundation for fintech-related projects and case studies.
CREATE TABLE customer (
"customer_id" VARCHAR,
"emp_title" VARCHAR,
"emp_length" VARCHAR,
"home_ownership" VARCHAR,
"annual_inc" DOUBLE,
"annual_inc_joint" DOUBLE,
"verification_status" VARCHAR,
"zip_code" VARCHAR,
"addr_state" VARCHAR,
"avg_cur_bal" DOUBLE,
"tot_cur_bal" DOUBLE
);CREATE TABLE loan (
"loan_id" BIGINT,
"customer_id" VARCHAR,
"loan_status" VARCHAR,
"loan_amount" DOUBLE,
"state" VARCHAR,
"funded_amount" DOUBLE,
"term" VARCHAR,
"int_rate" DOUBLE,
"installment" DOUBLE,
"grade" VARCHAR,
"issue_d" VARCHAR,
"issue_date" VARCHAR,
"issue_year" DOUBLE,
"pymnt_plan" BOOLEAN,
"type" VARCHAR,
"purpose" VARCHAR,
"description" VARCHAR,
"notes" VARCHAR
);CREATE TABLE loan_count_by_year (
"issue_year" DOUBLE,
"loan_count" BIGINT
);CREATE TABLE loan_purposes (
"unnamed_0" VARCHAR -- Unnamed: 0,
"ur" VARCHAR,
"ose" VARCHAR
);CREATE TABLE loan_with_region (
"loan_id" BIGINT,
"loan_amount" DOUBLE,
"region" VARCHAR
);CREATE TABLE state_region (
"state" VARCHAR,
"subregion" VARCHAR,
"region" VARCHAR
);Anyone who has the link will be able to view this.