From e919c11f59ba1845a31b199d2518f89069671413 Mon Sep 17 00:00:00 2001
From: Ivan Koptiev <ivan@firebolt.io>
Date: Mon, 7 Apr 2025 23:42:22 +0300
Subject: [PATCH 1/4] feat: first version

---
 .github/workflows/release.yaml                |   43 +
 .gitignore                                    |    2 +
 .goreleaser.yaml                              |   82 +
 Dockerfile                                    |    5 +
 README.md                                     |  184 +++
 Taskfile.yaml                                 |   37 +
 cmd/docs-scrapper/README.md                   |    4 +
 .../fireboltdocs/api_reference.md             |   90 ++
 .../api_reference_using_async_queries.md      |  119 ++
 .../api_reference_using_sync_queries.md       |   88 +
 cmd/docs-scrapper/fireboltdocs/docs.go        |    6 +
 cmd/docs-scrapper/fireboltdocs/guides.md      |   15 +
 .../guides_developing_with_firebolt.md        |   23 +
 ...loping_with_firebolt_connecting_with_go.md |  195 +++
 ...ping_with_firebolt_connecting_with_jdbc.md |  183 +++
 ...g_with_firebolt_connecting_with_net_sdk.md |   96 ++
 ...ng_with_firebolt_connecting_with_nodejs.md |  132 ++
 ...ng_with_firebolt_connecting_with_python.md |    7 +
 ...ith_firebolt_connecting_with_sqlalchemy.md |   11 +
 .../fireboltdocs/guides_exporting_data.md     |   90 ++
 .../fireboltdocs/guides_getting_started.md    |   16 +
 ...ng_started_get_started_load_data_wizard.md |   48 +
 ...guides_getting_started_get_started_next.md |   28 +
 .../guides_getting_started_get_started_sql.md |  373 +++++
 .../guides_integrations_airbyte.md            |   94 ++
 .../guides_integrations_airflow.md            |  413 +++++
 ...egrations_connecting_to_apache_superset.md |  105 ++
 ...des_integrations_connecting_to_paradime.md |   82 +
 ...uides_integrations_connecting_to_preset.md |   66 +
 ...guides_integrations_connecting_with_dbt.md |  213 +++
 .../guides_integrations_cube_js.md            |   98 ++
 .../guides_integrations_dbeaver.md            |   59 +
 .../guides_integrations_estuary.md            |  127 ++
 .../guides_integrations_integrations.md       |   16 +
 .../guides_integrations_metabase.md           |   56 +
 .../guides_integrations_otel_exporter.md      |    9 +
 .../guides_integrations_tableau.md            |   79 +
 ...onfiguring_aws_role_to_access_amazon_s3.md |  163 ++
 ...s_loading_data_creating_access_keys_aws.md |  107 ++
 .../guides_loading_data_loading_data.md       |   48 +
 .../guides_loading_data_loading_data_sql.md   |  497 ++++++
 ...guides_loading_data_loading_data_wizard.md |  185 +++
 ...ading_data_working_with_external_tables.md |   87 +
 ...ith_semi_structured_data_load_json_data.md |  193 +++
 ..._semi_structured_data_load_parquet_data.md |  179 +++
 ...emi_structured_data_working_with_arrays.md |  387 +++++
 ..._data_working_with_semi_structured_data.md |   21 +
 .../guides_managing_your_organization.md      |   20 +
 ...ides_managing_your_organization_billing.md |   33 +
 ...r_organization_creating_an_organization.md |   36 +
 ...ing_your_organization_managing_accounts.md |   89 +
 ...aging_your_organization_managing_logins.md |   80 +
 ...naging_your_organization_managing_users.md |  355 ++++
 ...ging_your_organization_service_accounts.md |  219 +++
 .../guides_operate_engines_operate_engines.md |   10 +
 ...guides_operate_engines_rbac_for_engines.md |   59 +
 .../guides_operate_engines_sizing_engines.md  |   45 +
 .../guides_operate_engines_system_engine.md   |  111 ++
 ..._engines_working_with_engines_using_ddl.md |  204 +++
 .../fireboltdocs/guides_query_data.md         |   10 +
 .../guides_query_data_using_the_api.md        |  121 ++
 ..._query_data_using_the_develop_workspace.md |  157 ++
 .../fireboltdocs/guides_security.md           |   12 +
 .../guides_security_enabling_mfa.md           |   36 +
 .../guides_security_network_policies.md       |  101 ++
 .../fireboltdocs/guides_security_ownership.md |   77 +
 .../guides_security_privatelink.md            |  117 ++
 .../fireboltdocs/guides_security_rbac.md      |  194 +++
 .../fireboltdocs/guides_security_sso.md       |   28 +
 .../fireboltdocs/guides_security_sso_auth0.md |   99 ++
 .../guides_security_sso_custom_sso.md         |  161 ++
 .../fireboltdocs/guides_security_sso_okta.md  |   95 ++
 .../guides_security_sso_onelogin.md           |   92 ++
 .../guides_security_sso_pingfederate.md       |   74 +
 .../guides_security_sso_salesforce.md         |   83 +
 cmd/docs-scrapper/fireboltdocs/index.md       |   47 +
 cmd/docs-scrapper/fireboltdocs/overview.md    |   14 +
 .../overview_architecture_overview.md         |   39 +
 .../fireboltdocs/overview_billing.md          |  164 ++
 .../overview_billing_compute_cost.md          |  144 ++
 .../overview_billing_storage_cost.md          |  164 ++
 .../fireboltdocs/overview_data_management.md  |  161 ++
 .../overview_engine_consumption.md            |   86 +
 .../overview_engine_fundamentals.md           |  164 ++
 .../overview_indexes_aggregating_index.md     |   75 +
 .../overview_indexes_primary_index.md         |  122 ++
 .../overview_indexes_using_indexes.md         |  446 ++++++
 .../overview_organizations_accounts.md        |  228 +++
 .../fireboltdocs/overview_queries.md          |   25 +
 ...ueries_understand_query_performance_hbs.md |   58 +
 ..._understand_query_performance_subresult.md |   81 +
 .../overview_queries_understand_spilling.md   |   47 +
 ..._security_role_based%20access%20control.md |   60 +
 ...%20access%20control_account_permissions.md |  105 ++
 ...sed%20access%20control_check_privileges.md |   81 +
 ...20access%20control_database_permissions.md |   59 +
 ...database_permissions_schema_permissions.md |   99 ++
 ..._database_permissions_table_permissions.md |  101 ++
 ...l_database_permissions_view_permissions.md |   45 +
 ...d%20access%20control_engine_permissions.md |   54 +
 ...role_based%20access%20control_ownership.md |   62 +
 ...ased%20access%20control_role_management.md |   10 +
 ...%20control_role_management_custom_roles.md |    7 +
 ...%20control_role_management_system_roles.md |   15 +
 ...sed%20access%20control_role_permissions.md |   17 +
 ...sed%20access%20control_user_permissions.md |   19 +
 .../overview_security_security.md             |  197 +++
 cmd/docs-scrapper/fireboltdocs/product.md     |   87 +
 .../fireboltdocs/product_product_platform.md  |   33 +
 cmd/docs-scrapper/fireboltdocs/reference.md   |   12 +
 .../reference_available_regions.md            |    7 +
 .../fireboltdocs/reference_help_menu.md       |  108 ++
 .../reference_interval_arithmetic.md          |   96 ++
 .../reference_object_identifiers.md           |   55 +
 .../reference_proof_of_concept_guide.md       |   60 +
 .../reference_release_notes_release_notes.md  |   39 +
 ...nce_release_notes_release_notes_archive.md | 1425 +++++++++++++++++
 .../fireboltdocs/reference_reserved_words.md  |  117 ++
 .../fireboltdocs/reference_system_settings.md |  218 +++
 .../fireboltdocs/sql_reference.md             |   12 +
 .../sql_reference_bytea_data_type.md          |  130 ++
 .../fireboltdocs/sql_reference_commands.md    |   91 ++
 .../sql_reference_commands_access_control.md  |   21 +
 ...nce_commands_access_control_alter_login.md |   44 +
 ...nds_access_control_alter_network_policy.md |   52 +
 ...ence_commands_access_control_alter_role.md |   17 +
 ...ds_access_control_alter_service_account.md |   49 +
 ...ence_commands_access_control_alter_user.md |   59 +
 ...ce_commands_access_control_create_login.md |   29 +
 ...ds_access_control_create_network_policy.md |   26 +
 ...nce_commands_access_control_create_role.md |   33 +
 ...s_access_control_create_service_account.md |   38 +
 ...nce_commands_access_control_create_user.md |   29 +
 ...ence_commands_access_control_drop_login.md |   25 +
 ...ands_access_control_drop_network_policy.md |   25 +
 ...rence_commands_access_control_drop_role.md |   35 +
 ...nds_access_control_drop_service_account.md |   25 +
 ...rence_commands_access_control_drop_user.md |   27 +
 ...reference_commands_access_control_grant.md |  103 ++
 ...eference_commands_access_control_revoke.md |   96 ++
 .../sql_reference_commands_data_definition.md |   26 +
 ..._commands_data_definition_alter_account.md |   23 +
 ...commands_data_definition_alter_database.md |   40 +
 ...ands_data_definition_alter_organization.md |   42 +
 ...e_commands_data_definition_alter_schema.md |   20 +
 ...ce_commands_data_definition_alter_table.md |   87 +
 ...nce_commands_data_definition_alter_view.md |   19 +
 ...commands_data_definition_create_account.md |   26 +
 ...ata_definition_create_aggregating_index.md |  186 +++
 ...ommands_data_definition_create_database.md |   27 +
 ...s_data_definition_create_external_table.md |  327 ++++
 ..._definition_create_fact_dimension_table.md |  129 ++
 ...n_create_fact_dimension_table_as_select.md |   32 +
 ...ommands_data_definition_create_location.md |  225 +++
 ...ands_data_definition_create_table_clone.md |  102 ++
 ...ce_commands_data_definition_create_view.md |   38 +
 ...e_commands_data_definition_drop_account.md |   28 +
 ..._commands_data_definition_drop_database.md |   15 +
 ...nce_commands_data_definition_drop_index.md |   13 +
 ..._commands_data_definition_drop_location.md |   97 ++
 ...nce_commands_data_definition_drop_table.md |   13 +
 ...ence_commands_data_definition_drop_view.md |   13 +
 ...e_commands_data_definition_use_database.md |   46 +
 .../sql_reference_commands_data_management.md |   11 +
 ...ence_commands_data_management_copy_from.md |  530 ++++++
 ...erence_commands_data_management_copy_to.md |  240 +++
 ...ference_commands_data_management_delete.md |   57 +
 ...ference_commands_data_management_insert.md |   45 +
 ...commands_data_management_truncate_table.md |   44 +
 ...ference_commands_data_management_update.md |   73 +
 ...ference_commands_data_management_vacuum.md |  111 ++
 .../sql_reference_commands_engines.md         |   14 +
 ...reference_commands_engines_alter_engine.md |  106 ++
 ...eference_commands_engines_create_engine.md |  107 ++
 ..._reference_commands_engines_drop_engine.md |   21 +
 ...reference_commands_engines_start_engine.md |   21 +
 ..._reference_commands_engines_stop_engine.md |   40 +
 ...l_reference_commands_engines_use_engine.md |   33 +
 .../sql_reference_commands_metadata.md        |   12 +
 ...ql_reference_commands_metadata_describe.md |   25 +
 ..._reference_commands_metadata_show_cache.md |   23 +
 ...ference_commands_metadata_show_catalogs.md |   25 +
 ...eference_commands_metadata_show_columns.md |   23 +
 ...eference_commands_metadata_show_engines.md |   17 +
 ...eference_commands_metadata_show_indexes.md |   25 +
 ...reference_commands_metadata_show_tables.md |   25 +
 ..._reference_commands_metadata_show_views.md |   17 +
 .../sql_reference_commands_queries.md         |    9 +
 .../sql_reference_commands_queries_cancel.md  |   45 +
 .../sql_reference_commands_queries_explain.md |  298 ++++
 .../sql_reference_commands_queries_pipe.md    |  240 +++
 ...eference_commands_queries_recommend_ddl.md |   66 +
 .../sql_reference_commands_queries_select.md  |  623 +++++++
 .../fireboltdocs/sql_reference_data_types.md  |  167 ++
 .../sql_reference_date_data_type.md           |   95 ++
 ...ference_functions_reference_aggregation.md |   29 +
 ...nctions_reference_aggregation_any_value.md |   47 +
 ...rence_aggregation_approx_count_distinct.md |   77 +
 ...nctions_reference_aggregation_array_agg.md |   53 +
 ...nce_functions_reference_aggregation_avg.md |   46 +
 ...functions_reference_aggregation_bit_and.md |   64 +
 ..._functions_reference_aggregation_bit_or.md |   65 +
 ...functions_reference_aggregation_bit_xor.md |  102 ++
 ...unctions_reference_aggregation_bool_and.md |   34 +
 ...functions_reference_aggregation_bool_or.md |   34 +
 ...e_functions_reference_aggregation_count.md |   77 +
 ...unctions_reference_aggregation_hash_agg.md |   59 +
 ...s_reference_aggregation_hll_count_build.md |   68 +
 ...eference_aggregation_hll_count_distinct.md |   53 +
 ...s_reference_aggregation_hll_count_merge.md |   30 +
 ...nce_functions_reference_aggregation_max.md |   53 +
 ..._functions_reference_aggregation_max_by.md |   68 +
 ..._functions_reference_aggregation_median.md |   50 +
 ...nce_functions_reference_aggregation_min.md |   51 +
 ..._functions_reference_aggregation_min_by.md |   68 +
 ...s_reference_aggregation_percentile_cont.md |   91 ++
 ...ctions_reference_aggregation_stddev_pop.md |   41 +
 ...tions_reference_aggregation_stddev_samp.md |   43 +
 ...nce_functions_reference_aggregation_sum.md |   59 +
 ...ions_reference_aggregation_variance_pop.md |   41 +
 ...ons_reference_aggregation_variance_samp.md |   43 +
 ...sql_reference_functions_reference_array.md |   19 +
 ..._functions_reference_array_array_concat.md |   62 +
 ...unctions_reference_array_array_contains.md |   42 +
 ...e_functions_reference_array_array_count.md |   37 +
 ...ns_reference_array_array_count_distinct.md |   25 +
 ...unctions_reference_array_array_distinct.md |   28 +
 ..._functions_reference_array_array_length.md |   35 +
 ...nce_functions_reference_array_array_max.md |   28 +
 ...nce_functions_reference_array_array_min.md |   28 +
 ...functions_reference_array_array_reverse.md |   37 +
 ...ions_reference_array_array_reverse_sort.md |   37 +
 ...ce_functions_reference_array_array_sort.md |   37 +
 ...nce_functions_reference_array_array_sum.md |   26 +
 ...nctions_reference_array_array_to_string.md |   48 +
 ...rence_functions_reference_array_flatten.md |   33 +
 ...ence_functions_reference_array_index_of.md |   28 +
 ...sql_reference_functions_reference_bytea.md |    7 +
 ..._functions_reference_bytea_convert_from.md |   77 +
 ...erence_functions_reference_bytea_decode.md |   48 +
 ...erence_functions_reference_bytea_encode.md |   48 +
 ...reference_conditional_and_miscellaneous.md |   17 +
 ...ence_conditional_and_miscellaneous_case.md |   51 +
 ...ence_conditional_and_miscellaneous_cast.md |   31 +
 ...conditional_and_miscellaneous_city_hash.md |   31 +
 ..._conditional_and_miscellaneous_coalesce.md |   27 +
 ..._conditional_and_miscellaneous_greatest.md |   25 +
 ...ence_conditional_and_miscellaneous_hash.md |   31 +
 ...erence_conditional_and_miscellaneous_if.md |   34 +
 ...ce_conditional_and_miscellaneous_ifnull.md |   32 +
 ...nce_conditional_and_miscellaneous_least.md |   25 +
 ...ce_conditional_and_miscellaneous_nullif.md |   45 +
 ..._conditional_and_miscellaneous_try_cast.md |   29 +
 ...ce_conditional_and_miscellaneous_typeof.md |   27 +
 ...e_conditional_and_miscellaneous_version.md |   18 +
 ...erence_functions_reference_datasketches.md |   13 +
 ...asketches_apache_datasketches_hll_build.md |   99 ++
 ...etches_apache_datasketches_hll_estimate.md |   43 +
 ...asketches_apache_datasketches_hll_merge.md |   38 +
 ...rence_functions_reference_date_and_time.md |   17 +
 ...ns_reference_date_and_time_current_date.md |   35 +
 ...rence_date_and_time_current_timestamptz.md |   34 +
 ..._functions_reference_date_and_time_date.md |   38 +
 ...ctions_reference_date_and_time_date_add.md |   19 +
 ...tions_reference_date_and_time_date_diff.md |   27 +
 ...ions_reference_date_and_time_date_trunc.md |   47 +
 ...nctions_reference_date_and_time_extract.md |   40 +
 ..._reference_date_and_time_localtimestamp.md |   32 +
 ...nctions_reference_date_and_time_to_char.md |   39 +
 ...nctions_reference_date_and_time_to_date.md |   39 +
 ...ns_reference_date_and_time_to_timestamp.md |   70 +
 ...tions_reference_date_and_time_to_yyyymm.md |   32 +
 ...ons_reference_date_and_time_to_yyyymmdd.md |   32 +
 ..._functions_reference_functions_glossary.md |    5 +
 ...functions_reference_functions_reference.md |   32 +
 ...eference_functions_reference_geospatial.md |   19 +
 ...ctions_reference_geospatial_st_asbinary.md |   29 +
 ...unctions_reference_geospatial_st_asewkb.md |   29 +
 ...tions_reference_geospatial_st_asgeojson.md |   35 +
 ...unctions_reference_geospatial_st_astext.md |   29 +
 ...ctions_reference_geospatial_st_contains.md |   78 +
 ...unctions_reference_geospatial_st_covers.md |   66 +
 ...ctions_reference_geospatial_st_distance.md |   34 +
 ...reference_geospatial_st_geogfromgeojson.md |   35 +
 ...ns_reference_geospatial_st_geogfromtext.md |   29 +
 ...ons_reference_geospatial_st_geogfromwkb.md |   29 +
 ...tions_reference_geospatial_st_geogpoint.md |   29 +
 ...ions_reference_geospatial_st_intersects.md |   36 +
 ...ference_geospatial_st_s2cellidfrompoint.md |   43 +
 ...nce_functions_reference_geospatial_st_x.md |   29 +
 ...nce_functions_reference_geospatial_st_y.md |   29 +
 .../sql_reference_functions_reference_json.md |  117 ++
 ...e_functions_reference_json_json_extract.md |   92 ++
 ...tions_reference_json_json_extract_array.md |  101 ++
 ...eference_json_json_pointer_extract_keys.md |   66 +
 ...eference_json_json_pointer_extract_text.md |   80 +
 ...erence_json_json_pointer_extract_values.md |   66 +
 ...nce_functions_reference_json_json_value.md |   63 +
 ...nctions_reference_json_json_value_array.md |   43 +
 ...ql_reference_functions_reference_lambda.md |   12 +
 ...ctions_reference_lambda_array_all_match.md |   53 +
 ...ctions_reference_lambda_array_any_match.md |   59 +
 ..._functions_reference_lambda_array_first.md |   28 +
 ...ce_functions_reference_lambda_array_sum.md |   28 +
 ...rence_functions_reference_lambda_filter.md |   57 +
 ...ce_functions_reference_lambda_transform.md |   85 +
 ...l_reference_functions_reference_numeric.md |   32 +
 ...ference_functions_reference_numeric_abs.md |   21 +
 ...erence_functions_reference_numeric_acos.md |   21 +
 ...tions_reference_numeric_array_enumerate.md |   31 +
 ...erence_functions_reference_numeric_asin.md |   21 +
 ...erence_functions_reference_numeric_atan.md |   21 +
 ...rence_functions_reference_numeric_atan2.md |   21 +
 ...ctions_reference_numeric_bit_shift_left.md |   31 +
 ...tions_reference_numeric_bit_shift_right.md |   31 +
 ...erence_functions_reference_numeric_ceil.md |   51 +
 ...ference_functions_reference_numeric_cos.md |   23 +
 ...ference_functions_reference_numeric_cot.md |   21 +
 ...nce_functions_reference_numeric_degrees.md |   21 +
 ...rence_functions_reference_numeric_floor.md |   42 +
 ...ns_reference_numeric_hll_count_estimate.md |   36 +
 ...e_functions_reference_numeric_is_finite.md |   23 +
 ...functions_reference_numeric_is_infinite.md |   23 +
 ...eference_functions_reference_numeric_ln.md |   25 +
 ...ference_functions_reference_numeric_log.md |   29 +
 ...ference_functions_reference_numeric_mod.md |   21 +
 ...rence_functions_reference_numeric_param.md |   54 +
 ...eference_functions_reference_numeric_pi.md |   17 +
 ...ference_functions_reference_numeric_pow.md |   23 +
 ...nce_functions_reference_numeric_radians.md |   21 +
 ...ence_functions_reference_numeric_random.md |   19 +
 ...rence_functions_reference_numeric_round.md |   23 +
 ...ference_functions_reference_numeric_sin.md |   23 +
 ...erence_functions_reference_numeric_sqrt.md |   27 +
 ...ference_functions_reference_numeric_tan.md |   23 +
 ...l_reference_functions_reference_session.md |    8 +
 ...tions_reference_session_current_account.md |   15 +
 ...ions_reference_session_current_database.md |   15 +
 ...ctions_reference_session_current_engine.md |   15 +
 ...unctions_reference_session_session_user.md |   33 +
 ...ql_reference_functions_reference_string.md |   31 +
 ...erence_functions_reference_string_btrim.md |   43 +
 ...rence_functions_reference_string_concat.md |   50 +
 ...s_reference_string_gen_random_uuid_text.md |   23 +
 ...erence_functions_reference_string_ilike.md |   49 +
 ...rence_functions_reference_string_length.md |   31 +
 ...ference_functions_reference_string_like.md |   83 +
 ...erence_functions_reference_string_lower.md |   36 +
 ...ference_functions_reference_string_lpad.md |   34 +
 ...erence_functions_reference_string_ltrim.md |   58 +
 ...functions_reference_string_octet_length.md |   29 +
 ...nce_functions_reference_string_position.md |   40 +
 ...nctions_reference_string_regexp_extract.md |   48 +
 ...ons_reference_string_regexp_extract_all.md |   44 +
 ..._functions_reference_string_regexp_like.md |   48 +
 ...ctions_reference_string_regexp_like_any.md |   53 +
 ...nctions_reference_string_regexp_replace.md |   99 ++
 ...ence_functions_reference_string_replace.md |   42 +
 ...ference_functions_reference_string_rpad.md |   26 +
 ...erence_functions_reference_string_rtrim.md |   58 +
 ...e_functions_reference_string_split_part.md |   75 +
 ...ctions_reference_string_string_to_array.md |   58 +
 ...rence_functions_reference_string_strpos.md |   40 +
 ...ce_functions_reference_string_substring.md |   61 +
 ...ference_functions_reference_string_trim.md |   77 +
 ...erence_functions_reference_string_upper.md |   36 +
 ...e_functions_reference_string_url_decode.md |   31 +
 ...e_functions_reference_string_url_encode.md |   37 +
 ...erence_functions_reference_table_valued.md |   18 +
 ..._reference_table_valued_generate_series.md |   29 +
 ...ons_reference_table_valued_list_objects.md |  122 ++
 ...nctions_reference_table_valued_read_csv.md |  110 ++
 ...ons_reference_table_valued_read_parquet.md |   87 +
 ...ql_reference_functions_reference_vector.md |   12 +
 ...e_functions_reference_vector_vector_add.md |   35 +
 ...reference_vector_vector_cosine_distance.md |   35 +
 ...ference_vector_vector_cosine_similarity.md |   59 +
 ...erence_vector_vector_euclidean_distance.md |   35 +
 ...s_reference_vector_vector_inner_product.md |   61 +
 ...erence_vector_vector_manhattan_distance.md |   35 +
 ...ector_vector_squared_euclidean_distance.md |   59 +
 ...ctions_reference_vector_vector_subtract.md |   35 +
 ...ql_reference_functions_reference_window.md |  117 ++
 ...e_functions_reference_window_avg_window.md |   38 +
 ...functions_reference_window_count_window.md |   35 +
 ...e_functions_reference_window_dense_rank.md |   37 +
 ..._functions_reference_window_first_value.md |   53 +
 ...eference_functions_reference_window_lag.md |   34 +
 ...ference_functions_reference_window_lead.md |   34 +
 ...e_functions_reference_window_max_window.md |   37 +
 ...e_functions_reference_window_min_window.md |   33 +
 ...erence_functions_reference_window_ntile.md |   42 +
 ...functions_reference_window_percent_rank.md |   36 +
 ...ference_functions_reference_window_rank.md |   37 +
 ...e_functions_reference_window_row_number.md |   36 +
 ...e_functions_reference_window_sum_window.md |   39 +
 .../sql_reference_geography_data_type.md      |  173 ++
 .../sql_reference_information_schema.md       |   41 +
 ...l_reference_information_schema_accounts.md |   20 +
 ...nce_information_schema_applicable_roles.md |   22 +
 ...l_reference_information_schema_catalogs.md |   18 +
 ...ql_reference_information_schema_columns.md |   18 +
 ...erence_information_schema_enabled_roles.md |   20 +
 ...rence_information_schema_engine_history.md |   18 +
 ...ormation_schema_engine_metering_history.md |   18 +
 ...formation_schema_engine_metrics_history.md |   19 +
 ...information_schema_engine_query_history.md |   25 +
 ...formation_schema_engine_running_queries.md |   18 +
 ...mation_schema_engine_user_query_history.md |   25 +
 ...ql_reference_information_schema_engines.md |   20 +
 ...ence_information_schema_engines_billing.md |   16 +
 ...ql_reference_information_schema_indexes.md |   22 +
 ..._reference_information_schema_locations.md |   39 +
 ...sql_reference_information_schema_logins.md |   20 +
 ...nce_information_schema_network_policies.md |   18 +
 ...ce_information_schema_object_privileges.md |   56 +
 ...l_reference_information_schema_routines.md |   36 +
 ...l_reference_information_schema_schemata.md |   18 +
 ...nce_information_schema_service_accounts.md |   22 +
 ...ence_information_schema_storage_billing.md |   16 +
 ...ence_information_schema_storage_history.md |   38 +
 ...rmation_schema_storage_metering_history.md |   16 +
 ...sql_reference_information_schema_tables.md |   18 +
 ...tion_schema_transitive_applicable_roles.md |   24 +
 .../sql_reference_information_schema_users.md |   20 +
 .../sql_reference_information_schema_views.md |   18 +
 .../sql_reference_numeric_data_type.md        |   77 +
 .../fireboltdocs/sql_reference_operators.md   |  242 +++
 .../sql_reference_timestampntz_data_type.md   |   93 ++
 .../sql_reference_timestamptz_data_type.md    |  160 ++
 cmd/docs-scrapper/main.go                     |   39 +
 cmd/docs-scrapper/scrapper.go                 |   97 ++
 cmd/firebolt-mcp-server/main.go               |  159 ++
 go.mod                                        |   48 +
 go.sum                                        |  310 ++++
 pkg/clients/database/connection.go            |  149 ++
 pkg/clients/database/connection_test.go       |  215 +++
 .../database/databasemock/connection.go       |   57 +
 pkg/clients/database/databasemock/pool.go     |  115 ++
 pkg/clients/database/params.go                |   67 +
 pkg/clients/database/params_test.go           |  161 ++
 pkg/clients/database/pool.go                  |  132 ++
 pkg/clients/database/pool_test.go             |  225 +++
 pkg/clients/discovery/client.go               |  132 ++
 pkg/clients/discovery/client_test.go          |  284 ++++
 pkg/clients/discovery/discoverymock/client.go |   36 +
 pkg/helpers/args/args.go                      |   70 +
 pkg/helpers/args/args_test.go                 |   89 +
 pkg/helpers/itertools/map.go                  |   25 +
 pkg/helpers/itertools/map_test.go             |   47 +
 pkg/helpers/mimetype/mime_type.go             |    6 +
 pkg/prompts/firebolt.go                       |   38 +
 pkg/prompts/firebolt.md                       |   35 +
 pkg/resources/accounts.go                     |   90 ++
 pkg/resources/accounts_test.go                |  298 ++++
 pkg/resources/databases.go                    |  100 ++
 pkg/resources/databases_test.go               |  307 ++++
 pkg/resources/docs.go                         |  137 ++
 pkg/resources/docs_overview.md                |  208 +++
 pkg/resources/docs_proof.md                   |    3 +
 pkg/resources/docs_reference.md               |    6 +
 pkg/resources/docs_test.go                    |  144 ++
 pkg/resources/engines.go                      |  100 ++
 pkg/resources/engines_test.go                 |  313 ++++
 pkg/server/server.go                          |  211 +++
 pkg/server/server_test.go                     |  130 ++
 pkg/tools/connect.go                          |  188 +++
 pkg/tools/connect_test.go                     |  311 ++++
 pkg/tools/docs.go                             |  110 ++
 pkg/tools/docs_test.go                        |  246 +++
 pkg/tools/query.go                            |  113 ++
 pkg/tools/query_test.go                       |  270 ++++
 pkg/version/version.go                        |   27 +
 473 files changed, 34531 insertions(+)
 create mode 100644 .github/workflows/release.yaml
 create mode 100644 .gitignore
 create mode 100644 .goreleaser.yaml
 create mode 100644 Dockerfile
 create mode 100644 README.md
 create mode 100644 Taskfile.yaml
 create mode 100644 cmd/docs-scrapper/README.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/api_reference.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/api_reference_using_async_queries.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/api_reference_using_sync_queries.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/docs.go
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_go.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_jdbc.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_net_sdk.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_nodejs.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_python.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_sqlalchemy.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_exporting_data.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_getting_started.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_load_data_wizard.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_next.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_sql.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_airbyte.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_airflow.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_apache_superset.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_paradime.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_preset.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_with_dbt.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_cube_js.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_dbeaver.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_estuary.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_integrations.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_metabase.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_otel_exporter.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_integrations_tableau.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_configuring_aws_role_to_access_amazon_s3.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_creating_access_keys_aws.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data_sql.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data_wizard.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_external_tables.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_load_json_data.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_load_parquet_data.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_working_with_arrays.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_working_with_semi_structured_data.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_billing.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_creating_an_organization.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_accounts.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_logins.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_users.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_service_accounts.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_operate_engines_operate_engines.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_operate_engines_rbac_for_engines.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_operate_engines_sizing_engines.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_operate_engines_system_engine.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_operate_engines_working_with_engines_using_ddl.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_query_data.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_query_data_using_the_api.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_query_data_using_the_develop_workspace.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_enabling_mfa.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_network_policies.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_ownership.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_privatelink.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_rbac.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_sso.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_sso_auth0.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_sso_custom_sso.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_sso_okta.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_sso_onelogin.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_sso_pingfederate.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/guides_security_sso_salesforce.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/index.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_architecture_overview.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_billing.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_billing_compute_cost.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_billing_storage_cost.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_data_management.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_engine_consumption.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_engine_fundamentals.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_indexes_aggregating_index.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_indexes_primary_index.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_indexes_using_indexes.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_organizations_accounts.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_queries.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_queries_understand_query_performance_hbs.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_queries_understand_query_performance_subresult.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_queries_understand_spilling.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_account_permissions.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_check_privileges.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_schema_permissions.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_table_permissions.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_view_permissions.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_engine_permissions.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_ownership.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management_custom_roles.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management_system_roles.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_permissions.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_user_permissions.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/overview_security_security.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/product.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/product_product_platform.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference_available_regions.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference_help_menu.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference_interval_arithmetic.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference_object_identifiers.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference_proof_of_concept_guide.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference_release_notes_release_notes.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference_release_notes_release_notes_archive.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference_reserved_words.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/reference_system_settings.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_bytea_data_type.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_login.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_network_policy.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_role.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_service_account.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_user.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_login.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_network_policy.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_role.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_service_account.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_user.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_login.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_network_policy.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_role.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_service_account.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_user.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_grant.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_revoke.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_account.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_database.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_organization.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_schema.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_table.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_view.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_account.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_aggregating_index.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_database.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_external_table.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_fact_dimension_table.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_fact_dimension_table_as_select.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_location.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_table_clone.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_view.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_account.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_database.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_index.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_location.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_table.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_view.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_use_database.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_copy_from.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_copy_to.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_delete.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_insert.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_truncate_table.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_update.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_vacuum.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_alter_engine.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_create_engine.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_drop_engine.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_start_engine.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_stop_engine.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_use_engine.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_describe.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_cache.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_catalogs.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_columns.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_engines.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_indexes.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_tables.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_views.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_cancel.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_explain.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_pipe.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_recommend_ddl.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_select.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_data_types.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_date_data_type.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_any_value.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_approx_count_distinct.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_array_agg.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_avg.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_and.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_or.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_xor.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bool_and.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bool_or.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_count.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hash_agg.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_build.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_distinct.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_merge.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_max.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_max_by.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_median.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_min.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_min_by.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_percentile_cont.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_stddev_pop.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_stddev_samp.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_sum.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_variance_pop.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_variance_samp.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_concat.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_contains.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_count.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_count_distinct.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_distinct.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_length.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_max.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_min.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_reverse.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_reverse_sort.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_sort.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_sum.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_to_string.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_flatten.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_index_of.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_convert_from.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_decode.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_encode.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_case.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_cast.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_city_hash.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_coalesce.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_greatest.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_hash.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_if.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_ifnull.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_least.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_nullif.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_try_cast.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_typeof.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_version.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_build.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_estimate.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_merge.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_current_date.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_current_timestamptz.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_add.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_diff.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_trunc.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_extract.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_localtimestamp.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_char.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_date.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_timestamp.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_yyyymm.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_yyyymmdd.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_functions_glossary.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_functions_reference.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asbinary.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asewkb.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asgeojson.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_astext.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_contains.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_covers.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_distance.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromgeojson.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromtext.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromwkb.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogpoint.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_intersects.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_s2cellidfrompoint.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_x.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_y.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_extract.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_extract_array.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_keys.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_text.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_values.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_value.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_value_array.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_all_match.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_any_match.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_first.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_sum.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_filter.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_transform.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_abs.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_acos.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_array_enumerate.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_asin.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_atan.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_atan2.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_bit_shift_left.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_bit_shift_right.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_ceil.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_cos.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_cot.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_degrees.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_floor.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_hll_count_estimate.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_is_finite.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_is_infinite.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_ln.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_log.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_mod.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_param.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_pi.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_pow.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_radians.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_random.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_round.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_sin.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_sqrt.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_tan.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_account.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_database.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_engine.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_session_user.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_btrim.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_concat.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_gen_random_uuid_text.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_ilike.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_length.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_like.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_lower.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_lpad.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_ltrim.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_octet_length.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_position.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_extract.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_extract_all.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_like.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_like_any.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_replace.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_replace.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_rpad.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_rtrim.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_split_part.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_string_to_array.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_strpos.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_substring.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_trim.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_upper.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_url_decode.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_url_encode.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_generate_series.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_list_objects.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_read_csv.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_read_parquet.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_add.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_cosine_distance.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_cosine_similarity.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_euclidean_distance.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_inner_product.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_manhattan_distance.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_squared_euclidean_distance.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_subtract.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_avg_window.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_count_window.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_dense_rank.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_first_value.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_lag.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_lead.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_max_window.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_min_window.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_ntile.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_percent_rank.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_rank.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_row_number.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_sum_window.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_geography_data_type.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_accounts.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_applicable_roles.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_catalogs.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_columns.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_enabled_roles.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_history.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_metering_history.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_metrics_history.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_query_history.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_running_queries.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_user_query_history.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engines.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engines_billing.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_indexes.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_locations.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_logins.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_network_policies.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_object_privileges.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_routines.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_schemata.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_service_accounts.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_billing.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_history.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_metering_history.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_tables.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_transitive_applicable_roles.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_users.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_views.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_numeric_data_type.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_operators.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_timestampntz_data_type.md
 create mode 100644 cmd/docs-scrapper/fireboltdocs/sql_reference_timestamptz_data_type.md
 create mode 100644 cmd/docs-scrapper/main.go
 create mode 100644 cmd/docs-scrapper/scrapper.go
 create mode 100644 cmd/firebolt-mcp-server/main.go
 create mode 100644 go.mod
 create mode 100644 go.sum
 create mode 100644 pkg/clients/database/connection.go
 create mode 100644 pkg/clients/database/connection_test.go
 create mode 100644 pkg/clients/database/databasemock/connection.go
 create mode 100644 pkg/clients/database/databasemock/pool.go
 create mode 100644 pkg/clients/database/params.go
 create mode 100644 pkg/clients/database/params_test.go
 create mode 100644 pkg/clients/database/pool.go
 create mode 100644 pkg/clients/database/pool_test.go
 create mode 100644 pkg/clients/discovery/client.go
 create mode 100644 pkg/clients/discovery/client_test.go
 create mode 100644 pkg/clients/discovery/discoverymock/client.go
 create mode 100644 pkg/helpers/args/args.go
 create mode 100644 pkg/helpers/args/args_test.go
 create mode 100644 pkg/helpers/itertools/map.go
 create mode 100644 pkg/helpers/itertools/map_test.go
 create mode 100644 pkg/helpers/mimetype/mime_type.go
 create mode 100644 pkg/prompts/firebolt.go
 create mode 100644 pkg/prompts/firebolt.md
 create mode 100644 pkg/resources/accounts.go
 create mode 100644 pkg/resources/accounts_test.go
 create mode 100644 pkg/resources/databases.go
 create mode 100644 pkg/resources/databases_test.go
 create mode 100644 pkg/resources/docs.go
 create mode 100644 pkg/resources/docs_overview.md
 create mode 100644 pkg/resources/docs_proof.md
 create mode 100644 pkg/resources/docs_reference.md
 create mode 100644 pkg/resources/docs_test.go
 create mode 100644 pkg/resources/engines.go
 create mode 100644 pkg/resources/engines_test.go
 create mode 100644 pkg/server/server.go
 create mode 100644 pkg/server/server_test.go
 create mode 100644 pkg/tools/connect.go
 create mode 100644 pkg/tools/connect_test.go
 create mode 100644 pkg/tools/docs.go
 create mode 100644 pkg/tools/docs_test.go
 create mode 100644 pkg/tools/query.go
 create mode 100644 pkg/tools/query_test.go
 create mode 100644 pkg/version/version.go

diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
new file mode 100644
index 0000000..530c603
--- /dev/null
+++ b/.github/workflows/release.yaml
@@ -0,0 +1,43 @@
+name: release
+
+on:
+  pull_request:
+  push:
+    # run only against tags
+    tags:
+      - "*"
+
+permissions:
+  contents: write
+  packages: write
+  id-token: write
+
+jobs:
+
+  goreleaser:
+    runs-on: ubuntu-latest
+    steps:
+
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version-file: go.mod
+
+      - name: Run GoReleaser
+        uses: goreleaser/goreleaser-action@v6
+        with:
+          version: "~> v2"
+          args: release --clean
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Upload assets
+        uses: actions/upload-artifact@v4
+        with:
+          name: firebolt-mcp-server
+          path: dist/*
\ No newline at end of file
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..5444d11
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,2 @@
+.idea/
+dist/
diff --git a/.goreleaser.yaml b/.goreleaser.yaml
new file mode 100644
index 0000000..a5938bf
--- /dev/null
+++ b/.goreleaser.yaml
@@ -0,0 +1,82 @@
+version: 2
+project_name: firebolt-mcp-server
+
+before:
+  hooks:
+    - go mod tidy
+
+builds:
+  - main: ./cmd/firebolt-mcp-server
+    mod_timestamp: "{{ .CommitTimestamp }}"
+    buildmode: pie
+    env:
+      - CGO_ENABLED=0
+    goos:
+      - linux
+      - darwin
+      - windows
+    goarch:
+      - amd64
+      - arm64
+
+archives:
+  - formats: [tar.gz]
+    # This name template makes the OS and Arch
+    # compatible with the results of `uname`.
+    name_template: >-
+      {{ .ProjectName }}-
+      {{- title .Os }}-
+      {{- if eq .Arch "amd64" }}x86_64
+      {{- else if eq .Arch "386" }}i386
+      {{- else }}{{ .Arch }}{{ end }}
+      {{- if .Arm }}v{{ .Arm }}{{ end }}
+    # Use zip for windows archives
+    format_overrides:
+      - goos: windows
+        formats: [zip]
+
+dockers:
+  - use: buildx
+    image_templates:
+      - "ghcr.io/firebolt-db/mcp-server:{{ .Version }}-amd64"
+    skip_push: true
+    build_flag_templates:
+      - --platform=linux/amd64
+      - --label=org.opencontainers.image.title={{ .ProjectName }}
+      - --label=org.opencontainers.image.description={{ .ProjectName }}
+      - --label=org.opencontainers.image.url=https://github.com/firebolt-db/mcp-server
+      - --label=org.opencontainers.image.source=https://github.com/firebolt-db/mcp-server
+      - --label=org.opencontainers.image.version={{ .Version }}
+      - --label=org.opencontainers.image.created={{ time "2006-01-02T15:04:05Z07:00" }}
+      - --label=org.opencontainers.image.revision={{ .FullCommit }}
+      - --label=org.opencontainers.image.licenses=MIT
+  - use: buildx
+    image_templates:
+      - "ghcr.io/firebolt-db/mcp-server:{{ .Version }}-arm64v8"
+    goarch: arm64
+    skip_push: true
+    build_flag_templates:
+      - --platform=linux/arm64/v8
+      - --label=org.opencontainers.image.title={{ .ProjectName }}
+      - --label=org.opencontainers.image.description={{ .ProjectName }}
+      - --label=org.opencontainers.image.url=https://github.com/firebolt-db/mcp-server
+      - --label=org.opencontainers.image.source=https://github.com/firebolt-db/mcp-server
+      - --label=org.opencontainers.image.version={{ .Version }}
+      - --label=org.opencontainers.image.created={{ time "2006-01-02T15:04:05Z07:00" }}
+      - --label=org.opencontainers.image.revision={{ .FullCommit }}
+      - --label=org.opencontainers.image.licenses=MIT
+
+docker_manifests:
+  - name_template: ghcr.io/firebolt-db/mcp-server:latest
+    image_templates:
+      - ghcr.io/firebolt-db/mcp-server:{{ .Version }}-amd64
+      - ghcr.io/firebolt-db/mcp-server:{{ .Version }}-arm64v8
+  - name_template: ghcr.io/firebolt-db/mcp-server:{{ .Version }}
+    image_templates:
+      - ghcr.io/firebolt-db/mcp-server:{{ .Version }}-amd64
+      - ghcr.io/firebolt-db/mcp-server:{{ .Version }}-arm64v8
+
+release: {}
+
+npm:
+  - name: "@firebolt-db/mcp-server"
diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 0000000..27bd63e
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,5 @@
+# syntax=docker/dockerfile:1
+
+FROM gcr.io/distroless/base:debug
+COPY ./firebolt-mcp-server /usr/local/bin/firebolt-mcp-server
+ENTRYPOINT ["/usr/local/bin/firebolt-mcp-server"]
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..0e9eb85
--- /dev/null
+++ b/README.md
@@ -0,0 +1,184 @@
+<h1 align="center">
+  <br>
+  <a href="https://www.firebolt.io"><img src="https://cdn.prod.website-files.com/5e8a264ceaf4870394477fc7/5e8a264ceaf4879f75477fdd_logo_website.svg" alt="Firebolt" width="300"></a>
+  <br>
+  Firebolt MCP Server
+  <br>
+</h1>
+
+<h4 align="center">
+A Model Context Protocol implementation that connects your LLM to Firebolt's cloud data warehouse
+</h4>
+
+<p align="center">
+  <a href="https://github.com/firebolt-db/mcp-server/releases">
+    <img src="https://img.shields.io/github/v/release/firebolt-db/mcp-server" alt="Release">
+  </a>
+  <a href="https://github.com/firebolt-db/mcp-server/blob/main/LICENSE">
+    <img src="https://img.shields.io/github/license/firebolt-db/mcp-server" alt="License">
+  </a>
+  <a href="https://go.dev">
+    <img src="https://img.shields.io/badge/go-1.24.1-blue" alt="Go Version">
+  </a>
+  <a href="https://github.com/firebolt-db/mcp-server/actions/workflows/build.yml">
+    <img src="https://img.shields.io/github/actions/workflow/status/firebolt-db/mcp-server/build.yml" alt="Build Status">
+  </a>
+</p>
+
+<p align="center">
+  <a href="#key-features">Key Features</a> |
+  <a href="#how-to-use">How To Use</a> |
+  <a href="#requirements">Requirements</a> |
+  <a href="#architecture">Architecture</a> |
+  <a href="#development">Development</a> |
+  <a href="#license">License</a>
+</p>
+
+![screenshot](https://img.example.firebolt.io/mcp-server-demo.gif)
+
+## Key Features
+
+* **LLM Integration with Firebolt** - Connect your AI assistants directly to your data warehouse
+  - Enable AI agents to autonomously query your data and build analytics solutions
+  - Provide LLMs with specialized knowledge of Firebolt's capabilities and features
+
+* **SQL Query Execution** 
+  - Direct query execution against Firebolt databases
+  - Support for multiple query types and execution modes
+
+* **Documentation Access**
+  - Comprehensive Firebolt documentation available to the LLM
+  - SQL reference, function reference, and more
+
+* **Account Management**
+  - Connect to different accounts and engines
+  - Manage authentication seamlessly
+
+* **Multi-platform Support**
+  - Run on any platform supporting Go binaries
+  - Docker container support for easy deployment
+
+## How To Use
+
+To get started with the Firebolt MCP Server, you'll need a Firebolt service account. If you don't have a Firebolt account yet, [sign up here](https://www.firebolt.io/signup).
+
+### Option 1: Use the Docker image
+
+```bash
+# Run with Docker
+docker run -p 8080:8080 \
+  -e FIREBOLT_MCP_CLIENT_ID=your-client-id \
+  -e FIREBOLT_MCP_CLIENT_SECRET=your-client-secret \
+  -e FIREBOLT_MCP_TRANSPORT=sse \
+  firebolt/mcp-server:latest
+```
+
+### Option 2: Download and run the binary
+
+```bash
+# Download the latest release for your platform from:
+# https://github.com/firebolt-db/mcp-server/releases
+
+# Run the server
+./firebolt-mcp-server \
+  --client-id your-client-id \
+  --client-secret your-client-secret \
+  --transport sse
+```
+
+### Connecting your LLM
+
+Once the server is running, you can connect to it using any MCP-compatible client. For example:
+
+```bash
+# Using the OpenAI API with MCP extension
+curl -X POST https://api.openai.com/v1/chat/completions \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer $OPENAI_API_KEY" \
+  -d '{
+    "model": "gpt-4",
+    "messages": [
+      {"role": "system", "content": "You are a data analyst working with Firebolt."},
+      {"role": "user", "content": "How many users did we have last month?"}
+    ],
+    "tools": [
+      {
+        "type": "mcp",
+        "mcp": {
+          "endpoint": "http://localhost:8080",
+          "auth": {
+            "type": "bearer",
+            "token": "YOUR_TOKEN"
+          }
+        }
+      }
+    ]
+  }'
+```
+
+## Requirements
+
+- Firebolt service account credentials (client ID and client secret)
+- For development: Go 1.24.1 or later
+- For deployment: Docker (optional)
+
+## Architecture
+
+The Firebolt MCP Server implements the [Model Context Protocol](https://github.com/anthropics/anthropic-cookbook/tree/main/model_context_protocol) specification, providing:
+
+1. **Tools** - Task-specific capabilities provided to the LLM:
+   - `Connect`: Establish connections to Firebolt engines and databases
+   - `Docs`: Access Firebolt documentation
+   - `Query`: Execute SQL queries against Firebolt
+
+2. **Resources** - Data that can be referenced by the LLM:
+   - Documentation articles
+   - Account information
+   - Database schema
+   - Engine statistics
+
+3. **Prompts** - Predefined instructions for the LLM:
+   - Firebolt Expert: Prompts the model to act as a Firebolt specialist
+
+## Development
+
+To set up the development environment:
+
+```bash
+# Clone this repository
+git clone https://github.com/firebolt-db/mcp-server.git
+
+# Go into the repository
+cd mcp-server
+
+# Install Task (if you don't have it already)
+go install github.com/go-task/task/v3/cmd/task@latest
+
+# Update Go dependencies
+task mod
+
+# Build the application
+task build
+```
+
+### Running tests
+
+```bash
+go test ./...
+```
+
+### Building Docker image
+
+```bash
+docker build -t firebolt-mcp-server .
+```
+
+## License
+
+MIT
+
+---
+
+> [firebolt.io](https://www.firebolt.io) &nbsp;&middot;&nbsp;
+> GitHub [@firebolt-db](https://github.com/firebolt-db) &nbsp;&middot;&nbsp;
+> Twitter [@FireboltDB](https://twitter.com/FireboltDB)
diff --git a/Taskfile.yaml b/Taskfile.yaml
new file mode 100644
index 0000000..097af17
--- /dev/null
+++ b/Taskfile.yaml
@@ -0,0 +1,37 @@
+version: 3
+
+tasks:
+
+  help:
+    desc: Display this help screen
+    silent: true
+    cmds:
+      - task --list
+
+  mod:
+    desc: tidy Go modules, download dependencies
+    silent: true
+    cmd: |
+      go mod tidy
+      go mod download
+
+  build:
+    desc: Build application binary
+    silent: true
+    deps:
+      - task: goreleaser
+        vars:
+          CLI_ARGS: build --clean --snapshot --single-target
+
+  goreleaser:
+    desc: Build application binary
+    silent: true
+    cmd: |
+      docker run --rm --privileged \
+        -v $PWD:/src \
+        -v /var/run/docker.sock:/var/run/docker.sock \
+        -w /src \
+        -e GOOS={{OS}} \
+        -e GOARCH={{ARCH}} \
+        goreleaser/goreleaser:v2.8.2 \
+        {{.CLI_ARGS}}
diff --git a/cmd/docs-scrapper/README.md b/cmd/docs-scrapper/README.md
new file mode 100644
index 0000000..fa4582a
--- /dev/null
+++ b/cmd/docs-scrapper/README.md
@@ -0,0 +1,4 @@
+# Firebolt Documentation Scrapper
+
+This tools scrapes Firebolt documentation website and puts content to a local directory.
+This is a temporary solution until we rework our documentation to be LLM-friendly.
diff --git a/cmd/docs-scrapper/fireboltdocs/api_reference.md b/cmd/docs-scrapper/fireboltdocs/api_reference.md
new file mode 100644
index 0000000..92af181
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/api_reference.md
@@ -0,0 +1,90 @@
+# [](#api-reference)API reference
+
+The Firebolt API enables programmatic interaction with Firebolt databases for running SQL statements, retrieving data, and managing engines. Use API calls to submit queries, retrieve results, and perform administrative tasks without the user interface (UI).
+
+Firebolt offers official SDKs and drivers to simplify API usage. These drivers interface between your application and Firebolt, handling authentication, SQL statement submission, and result processing.
+
+![Use a service account and a driver to connect to the Firebolt API which returns a result.](../assets/images/API-workflow.png)
+
+To submit an API request, set up a Firebolt driver and use it to send a query to Firebolt, as explained in the following sections.
+
+**Topics:**
+
+- [Prerequisites](#prerequisites) – Set up your account and credentials before submitting an API request.
+- [Set up a driver](#set-up-a-driver) – Download, install, and configure a Firebolt driver to send queries using the Firebolt API.
+- [Submit a query](#submit-a-query) – Use a driver to connect to Firebolt and submit a query.
+
+## [](#prerequisites)Prerequisites
+
+Before you submit API queries, you need the following:
+
+1. **A Firebolt account** – Ensure that you have access to an active Firebolt account. If you don’t have access, you can [sign up for an account](https://www.firebolt.io/sign-up). For more information about how to register with Firebolt, see [Get started with Firebolt](/Guides/getting-started/).
+2. **A Firebolt service account** – You must have access to an active Firebolt [service account](/Guides/managing-your-organization/service-accounts.html), which facilitates programmatic access to Firebolt.
+3. **A user associated with the Firebolt service account** – You must associate a [user](/Guides/managing-your-organization/managing-users.html#-users) with your service account, and the user must have the necessary permissions to run the query on the specified database using the specified engine.
+4. **Sufficient permissions** If you want to query user data through a specific engine, you must have sufficient permissions on the engine, as well as on any tables and databases you access.
+
+## [](#set-up-a-driver)Set up a driver
+
+Drivers are software components that facilitate communication between applications and databases. Use a Firebolt driver to connect to a Firebolt database, authenticate securely, and run SQL statements with minimal setup.
+
+Use a Firebolt driver for the following:
+
+- **Simplified API access** – Manage authentication and request formatting, eliminating the need for manual API calls. Requires only installation and basic configuration to connect and run SQL statements.
+- **Optimized performance** – Improve query processing and connection management for faster response times.
+- **Secure authentication** – Use service accounts and industry-standard methods to ensure secure access.
+
+Firebolt provides multiple drivers and SDKs. Refer to the following [driver documentation](/Guides/integrations/integrations.html) for installation instructions:
+
+- [Node.js SDK](/Guides/developing-with-firebolt/connecting-with-nodejs.html) – For JavaScript-based applications.
+- [Python SDK](/Guides/developing-with-firebolt/connecting-with-Python.html) – For Python-based applications and data workflows.
+- [JDBC Driver](/Guides/developing-with-firebolt/connecting-with-jdbc.html) – For Java applications.
+- [SQLAlchemy](/Guides/developing-with-firebolt/connecting-with-sqlalchemy.html) – For ORM-based integrations in Python.
+- [.NET SDK](/Guides/developing-with-firebolt/connecting-with-net-sdk.html) – For applications running on the .NET framework.
+- [Go SDK](/Guides/developing-with-firebolt/connecting-with-go.html) – For applications using the Go programming language.
+
+## [](#submit-a-query)Submit a query
+
+After setting up a Firebolt driver, submit a query to verify connectivity and validate your credentials.
+
+Submitting a query through a Firebolt drivers and SDKs have similar formats. The following code example shows how to submit a query using the [Python SDK](/Guides/developing-with-firebolt/connecting-with-Python.html). For other languages, consult the specific driver for details:
+
+```
+from firebolt.db import connect
+from firebolt.client.auth import ClientCredentials
+
+id = "service_account_id"
+secret = "service_account_secret"
+engine_name = "your_engine_name"
+database_name = "your_test_db"
+account_name = "your_account_name"
+
+firstQuery = """
+    SELECT 42;
+    """
+secondQuery = """
+    SELECT 'my second query';
+"""
+    
+with connect(
+    engine_name=engine_name,
+    database=database_name,
+    account_name=account_name,
+    auth=ClientCredentials(id, secret),
+) as connection:
+    cursor = connection.cursor()
+    cursor.execute(firstQuery)
+    for row in cursor.fetchall():
+        print(row)
+    # The cursor can be reused for multiple queries.
+    cursor.execute(secondQuery)
+    for row in cursor.fetchall():
+        print(row)
+```
+
+### [](#query-types)Query types
+
+Firebolt supports two types of query modes: **synchronous** and **asynchronous** queries.
+
+A [synchronous query](/API-reference/using-sync-queries.html) waits for a response before proceeding. This mode is ideal for interactive queries that require immediate results, such as dashboard queries or user-initiated requests. Firebolt maintains an open HTTP connection for the duration of the query and streams results back as they become available.
+
+An [asynchronous query](/API-reference/using-async-queries.html) runs in the background, allowing your application to continue executing other tasks. This is useful for long-running queries, such as [INSERT](/sql_reference/commands/data-management/insert.html), or [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html), where waiting for a response is unnecessary. The query status can be checked periodically using a query token.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/api_reference_using_async_queries.md b/cmd/docs-scrapper/fireboltdocs/api_reference_using_async_queries.md
new file mode 100644
index 0000000..1fb0c73
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/api_reference_using_async_queries.md
@@ -0,0 +1,119 @@
+# [](#asynchronous-queries)Asynchronous queries
+
+An asynchronous query runs in the background and returns a successful response once it is accepted by the computing cluster, so that a client can proceed with other tasks without waiting for the statement to finish. The status of an asynchronous query can be checked at specified intervals, which provides flexibility, so that you can check the query’s status at meaningful times based on the expected duration of the operation. For example, a user can avoid unnecessary resource consumption by only checking the status periodically, rather than maintaining an open connection for the entire duration of the query, which might be unreliable or unnecessary for certain tasks.
+
+Asynchronous queries are ideal for long-running SQL statements, such as `INSERT`, `STOP ENGINE`, and `ALTER ENGINE`, where keeping an HTTP connection open is both unreliable and unnecessary, and where the statement might return zero rows. In addition, tracking them can be challenging. Using an asynchronous query allows you to check the status of operations at intervals, based on the expected duration.
+
+You should use asynchronous queries for any supported operation that may take more than a few minutes for which there are no results.
+
+**Supported asynchronous queries**
+
+- [INSERT](/sql_reference/commands/data-management/insert.html) – Inserts one or more values into a specified table.
+- [COPY FROM](/sql_reference/commands/data-management/copy-from.html) – Loads data from an Amazon S3 bucket into Firebolt.
+- [COPY TO](/sql_reference/commands/data-management/copy-to.html) – Copies the result of a `SELECT` query to an Amazon S3 location.
+- [VACUUM](/sql_reference/commands/data-management/vacuum.html) – Optimizes tablets for query performance.
+- [CREATE AGGREGATING INDEX](/sql_reference/commands/data-definition/create-aggregating-index.html) – Creates an index for precomputing and storing frequent aggregations.
+- [CREATE AS SELECT](/sql_reference/commands/data-definition/create-fact-dimension-table-as-select.html) – Creates a table and loads data into it based on a `SELECT` query.
+- [Engine commands](/sql_reference/commands/engines/) including [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html), [STOP ENGINE](/sql_reference/commands/engines/stop-engine.html), and [START ENGINE](/sql_reference/commands/engines/start-engine.html). By default, Firebolt engines finish running queries before returning results, which can take significant time. Starting an engine can also take more than a few minutes.
+
+## [](#how-to-submit-an-asynchronous-query)How to submit an asynchronous query
+
+You can only submit a synchronous query programmatically using the Firebolt API or the following listed drivers. Every SQL statement submitted using the Firebolt **Develop Space** user interface is a synchronous query.
+
+The following are required prerequisites to submit a query programmatically:
+
+1. **A Firebolt account** – Ensure that you have access to an active Firebolt account. If you don’t have access, you can [sign up for an account](https://www.firebolt.io/sign-up). For more information about how to register with Firebolt, see [Get started with Firebolt](/Guides/getting-started/).
+2. **A Firebolt service account** – You must have access to an active Firebolt [service account](/Guides/managing-your-organization/service-accounts.html), which facilitates programmatic access to Firebolt.
+3. **A user associated with the Firebolt service account** – You must associate a [user](/Guides/managing-your-organization/managing-users.html#-users) with your service account, and the user must have the necessary permissions to run the query on the specified database using the specified engine.
+4. **Sufficient permissions** If you want to query user data through a specific engine, you must have sufficient permissions on the engine, as well as on any tables and databases you access.
+
+To submit an asynchronous query via a raw HTTP request, you must use Firebolt protocol version 2.3 or later, while query status can be checked with any client. You can verify the protocol version by checking the X-Firebolt-Protocol-Version header in API response.
+
+## [](#use-a-firebolt-driver)Use a Firebolt Driver
+
+Use a Firebolt driver to connect to a Firebolt database, authenticate securely, and run SQL statements with minimal setup. The driver provides built-in methods for running SQL statements, handling responses, and managing connections. Only some Firebolt drivers support synchronous queries. See the documentation for each driver for specific details on how to submit asynchronous queries programmatically:
+
+- [Python SDK](/Guides/developing-with-firebolt/connecting-with-Python.html) – Firebolt Python SDK
+- [Node.js](/Guides/developing-with-firebolt/connecting-with-nodejs.html) – Firebolt Node SDK
+
+## [](#submit-a-query)Submit a query
+
+Submitting a query through a Firebolt drivers and SDKs have similar formats. The following code example shows how to submit an asynchronous query using the [Python SDK](/Guides/developing-with-firebolt/connecting-with-Python.html). For other languages, consult the specific driver for details:
+
+The following code example establishes a connection to a Firebolt database using a service account, submits an asynchronous `INSERT` statement that groups generated numbers, periodically checks its run status, and then retrieves the row count from the `example` table:
+
+```
+from time import sleep
+
+from firebolt.db import connect
+from firebolt.client.auth import ClientCredentials
+
+id = "service_account_id"
+secret = "service_account_secret"
+engine_name = "your_engine_name"
+database_name = "your_test_db"
+account_name = "your_account_name"
+
+query = """
+    INSERT INTO example SELECT idMod7 as id
+    FROM (
+        SELECT id%7 as idMod7
+        FROM GENERATE_SERIES(1, 10000000000) s(id)
+    )
+    GROUP BY idMod7;
+    """
+
+with connect(
+    engine_name=engine_name,
+    database=database_name,
+    account_name=account_name,
+    auth=ClientCredentials(id, secret),
+) as connection:
+    cursor = connection.cursor()
+
+    cursor.execute_async(query) # Needs firebolt-sdk 1.9.0 or later
+    # Token lets us check the status of the query later
+    token = cursor.async_query_token
+    print(f"Query Token: {token}")
+
+    # Block until the query is done
+    # You can also do other work here
+    while connection.is_async_query_running(token):
+        print("Checking query status...")
+        sleep(5)
+
+    status = "Success" if connection.is_async_query_successful(token) else "Failed"
+    print(f"Query Status: {status}")
+
+    cursor.execute("SELECT count(*) FROM example;")  # Should contain 7 rows
+    for row in cursor.fetchall():
+        print(row)
+```
+
+### [](#check-query-statusy)Check query statusy
+
+The query status token is included in the initial response when the query is submitted. If needed, you can also retrieve the token from the [engine\_running\_queries](/sql_reference/information-schema/engine-running-queries.html) view.
+
+To check the status of an asynchronous query, use the token with the `CALL fb_GetAsyncStatus` function as follows:
+
+```
+CALL fb_GetAsyncStatus('<async_token>');
+```
+
+The previous code example returns a single row with the following schema:
+
+Column Name Data Type Description account\_name TEXT The name of the account where the asynchronous query was submitted. user\_name TEXT The name of the user who submitted the asynchronous query. request\_id TEXT Unique ID of the request which submitted the asynchronous query. query\_id TEXT Unique ID of the asynchronous query. status TEXT Current status of the query: SUSPENDED, RUNNING, CANCELLED, FAILED, SUCCEEDED or IN\_DOUBT. submitted\_time TIMESTAMPTZ The time the asynchronous query was submitted. start\_time TIMESTAMPTZ The time the async query was most recently started. end\_time TIMESTAMPTZ If the asynchronous query is completed, the time it finished. error\_message TEXT If the asynchronous query failed, the error message from the failure. retries LONG The number of times the asynchronous query has retried. scanned\_bytes LONG The number of bytes scanned by the asynchronous query. scanned\_rows LONG The number of rows scanned by the asynchronous query.
+
+### [](#cancel-a-query)Cancel a query
+
+A running asynchronous query can be cancelled using the [CANCEL](/sql_reference/commands/queries/cancel.html) statement as follows:
+
+```
+CANCEL QUERY '<query_id>';
+```
+
+In the previous code example, retrieve the query ID from the [engine\_running\_queries](/sql_reference/information-schema/engine-running-queries.html) view or from the original query submission response.
+
+## [](#error-handling)Error handling
+
+Error Type Cause Solution **Protocol version mismatch** Using an outdated Firebolt protocol version. Make sure your driver supports async queries. **Query failure** The query encounters an execution error. Check the error message in `fb_GetAsyncStatus` and validate the query syntax. **Token not found** The provided async query token is invalid or expired. Verify that the correct token is being used and that the query has not expired. **Engine does not exist or you don’t have permission to access it** The specified Firebolt engine is not running or you don’t have permission to access it. Start the engine before submitting the query and double check permissions.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/api_reference_using_sync_queries.md b/cmd/docs-scrapper/fireboltdocs/api_reference_using_sync_queries.md
new file mode 100644
index 0000000..181b5f6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/api_reference_using_sync_queries.md
@@ -0,0 +1,88 @@
+# [](#synchronous-queries)Synchronous queries
+
+Synchronous queries in Firebolt process SQL statements and wait for a response before proceeding with other operations. These queries are best suited for interactive analytics, dashboards, and data retrieval where low-latency performance is essential. Synchronous queries complete within a single request-response cycle.
+
+Synchronous queries are the default query mode for submitting SQL statements in Firebolt. All statements in the [SQL reference](/sql_reference/) guide can be used inside a synchronous query.
+
+## [](#how-to-submit-a-synchronous-query)How to submit a synchronous query
+
+You can submit a synchronous query using the user interface (UI) in the Firebolt **Develop Space**. Every SQL statement submitted using the UI is a synchronous query. For more information about how to submit a SQL statement using the UI, see [Get started using SQL](/Guides/getting-started/get-started-sql.html).
+
+You can also submit a synchronous query programmatically using the Firebolt API. The following are required prerequisites to submit a query programmatically:
+
+1. **A Firebolt account** – Ensure that you have access to an active Firebolt account. If you don’t have access, you can [sign up for an account](https://www.firebolt.io/sign-up). For more information about how to register with Firebolt, see [Get started with Firebolt](/Guides/getting-started/).
+2. **A Firebolt service account** – You must have access to an active Firebolt [service account](/Guides/managing-your-organization/service-accounts.html), which facilitates programmatic access to Firebolt.
+3. **A user associated with the Firebolt service account** – You must associate a [user](/Guides/managing-your-organization/managing-users.html#-users) with your service account, and the user must have the necessary permissions to run the query on the specified database using the specified engine.
+4. **Sufficient permissions** If you want to query user data through a specific engine, you must have sufficient permissions on the engine, as well as on any tables and databases you access.
+
+To submit a synchronous query programatically, use a Firebolt Driver to send an HTTP request with the SQL statement to Firebolt’s API endpoint.
+
+### [](#use-a-firebolt-driver)Use a Firebolt driver
+
+Use a Firebolt driver to connect to a Firebolt database, authenticate securely, and run SQL statements with minimal setup. The driver provides built-in methods for running SQL statements, handling responses, and managing connections. All Firebolt drivers support synchronous queries. See the documentation for each driver for specific details on how to submit synchronous queries programmatically:
+
+- [Node.js SDK](/Guides/developing-with-firebolt/connecting-with-nodejs.html) – Firebolt Node.js SDK
+- [Python SDK](/Guides/developing-with-firebolt/connecting-with-Python.html) – Firebolt Python SDK
+- [JDBC Driver](/Guides/developing-with-firebolt/connecting-with-jdbc.html) – Firebolt JDBC Driver
+- [SQLAlchemy](/Guides/developing-with-firebolt/connecting-with-sqlalchemy.html) – Firebolt SQLAlchemy adapter
+- [.NET SDK](/Guides/developing-with-firebolt/connecting-with-net-sdk.html) – Firebolt .NET SDK
+- [Go SDK](/Guides/developing-with-firebolt/connecting-with-go.html) – Firebolt Go SDK
+
+### [](#submit-a-query)Submit a query
+
+After setting up a Firebolt driver, submit a query to verify connectivity and validate your credentials.
+
+Submitting a query through a Firebolt drivers and SDKs have similar formats. The following code example shows how to establish a connection to a Firebolt database using a service account’s credentials, runs a simple `SELECT` statement, retrieves and prints the result using the [Python SDK](/Guides/developing-with-firebolt/connecting-with-Python.html). For other languages, consult the specific driver for details.
+
+```
+from firebolt.db import connect
+from firebolt.client.auth import ClientCredentials
+
+id = "service_account_id"
+secret = "service_account_secret"
+engine_name = "your_engine_name"
+database_name = "your_test_db"
+account_name = "your_account_name"
+
+query = """
+    SELECT 42;
+    """
+
+with connect(
+    engine_name=engine_name,
+    database=database_name,
+    account_name=account_name,
+    auth=ClientCredentials(id, secret),
+) as connection:
+    cursor = connection.cursor()
+
+    cursor.execute(query)
+    for row in cursor.fetchall():
+        print(row)
+```
+
+#### [](#handling-long-running-synchronous-queries)Handling long-running synchronous queries
+
+Synchronous queries maintain an open HTTP connection for the duration of the query, and stream results back as they become available. While there is no strict time limit, queries running longer than one hour may experience connectivity interruptions. If the HTTP connection is lost, some SQL statements, including `INSERT`, continue to run by default, while `SELECT` statements are cancelled. You can modify this behavior using the [cancel\_query\_on\_connection\_drop](/Reference/system-settings.html#query-cancellation-mode-on-connection-drop) setting.
+
+To avoid connection issues, consider submitting long-running queries as [asynchronous](/API-reference/using-async-queries.html) queries.
+
+#### [](#check-query-status)Check query status
+
+The queries running on an engine are available in the [engine\_running\_queries](/sql_reference/information-schema/engine-running-queries.html) view.
+
+#### [](#cancel-a-query)Cancel a query
+
+A running synchronous query can be cancelled using the [CANCEL](/sql_reference/commands/queries/cancel.html) statement as follows:
+
+```
+CANCEL QUERY '<query_id>';
+```
+
+Use the query ID retrieved from the [engine\_running\_queries](/sql_reference/information-schema/engine-running-queries.html) view to cancel a specific query.
+
+## [](#error-handling)Error handling
+
+Common errors and solutions when using synchronous queries:
+
+Error Type Cause Solution **Connection loss** The HTTP connection is interrupted. Depending on the type of query, the query may still be running. Check [engine\_running\_queries](/sql_reference/information-schema/engine-running-queries.html) to verify, and use the `cancel_query_on_connection_drop` setting to modify behavior. **Engine does not exist or you don’t have permission to access it** The user lacks required permissions. Ensure the user has `USAGE` permission on the engine and that the engine exists.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/docs.go b/cmd/docs-scrapper/fireboltdocs/docs.go
new file mode 100644
index 0000000..351c44e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/docs.go
@@ -0,0 +1,6 @@
+package fireboltdocs
+
+import "embed"
+
+//go:embed *.md
+var FS embed.FS
diff --git a/cmd/docs-scrapper/fireboltdocs/guides.md b/cmd/docs-scrapper/fireboltdocs/guides.md
new file mode 100644
index 0000000..4912fde
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides.md
@@ -0,0 +1,15 @@
+# [](#guides)Guides
+
+Learn how to configure, govern, develop and query with Firebolt.
+
+* * *
+
+- [Manage organization](/Guides/managing-your-organization/)
+- [Get started](/Guides/getting-started/)
+- [Operate Engines](/Guides/operate-engines/operate-engines.html)
+- [Load data](/Guides/loading-data/loading-data.html)
+- [Query data](/Guides/query-data/)
+- [Configure security](/Guides/security/)
+- [Develop with Firebolt](/Guides/developing-with-firebolt/)
+- [Integrate with Firebolt](/Guides/integrations/integrations.html)
+- [Export data](/Guides/exporting-data.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt.md b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt.md
new file mode 100644
index 0000000..ae6fa95
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt.md
@@ -0,0 +1,23 @@
+# [](#developing-with-firebolt)Developing with Firebolt
+
+Firebolt provides multiple SDKs, drivers, and libraries to integrate with various programming environments, enabling developers to run queries, manage databases, and build data-driven applications efficiently.
+
+This guide covers how to develop with Firebolt using different languages and frameworks, including:
+
+- [Node.js](/Guides/developing-with-firebolt/connecting-with-nodejs.html) – Use the Firebolt Node.js SDK to interact with Firebolt databases.
+- [Python](/Guides/developing-with-firebolt/connecting-with-Python.html) – Leverage the Firebolt Python SDK for data analysis and automation.
+- [JDBC](/Guides/developing-with-firebolt/connecting-with-jdbc.html) – Connect Firebolt to Java-based applications with the JDBC driver.
+- [SQLAlchemy](/Guides/developing-with-firebolt/connecting-with-sqlalchemy.html) – Integrate Firebolt with SQLAlchemy for ORM-based workflows.
+- [.NET SDK](/Guides/developing-with-firebolt/connecting-with-net-sdk.html) – Work with Firebolt databases using .NET applications.
+- [Go](/Guides/developing-with-firebolt/connecting-with-go.html) – Access Firebolt from Go applications with the Firebolt Go client.
+
+Each section provides installation instructions, authentication methods, and query examples tailored to the respective language or framework.
+
+* * *
+
+- [Node.js](/Guides/developing-with-firebolt/connecting-with-nodejs.html)
+- [Python](/Guides/developing-with-firebolt/connecting-with-Python.html)
+- [JDBC](/Guides/developing-with-firebolt/connecting-with-jdbc.html)
+- [SQLAlchemy](/Guides/developing-with-firebolt/connecting-with-sqlalchemy.html)
+- [.NET SDK](/Guides/developing-with-firebolt/connecting-with-net-sdk.html)
+- [Go](/Guides/developing-with-firebolt/connecting-with-go.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_go.md b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_go.md
new file mode 100644
index 0000000..370c32b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_go.md
@@ -0,0 +1,195 @@
+# [](#firebolt-go-sdk-documentation)Firebolt Go SDK Documentation
+
+## [](#overview)Overview
+
+The Firebolt Go SDK is an implementation of Go’s `database/sql/driver` interface, enabling Go developers to connect to and interact with Firebolt databases seamlessly.
+
+## [](#prerequisites)Prerequisites
+
+You must have the following prerequisites before you can connect your Firebolt account to Go:
+
+- **Go installed and configured** on your system. The minimum supported version is 1.18 or higher. If you do not have Go installed, you can download the [latest version](https://go.dev/dl/). After installing, if you don’t have a Go module yet, you’ll need to initialize one. See the [Go documentation on modules](https://go.dev/doc/tutorial/create-module) for detailed instructions on how to create and initialize a Go module.
+- **Firebolt account** – You need an active Firebolt account. If you do not have one, you can [sign up](https://go.firebolt.io/signup) for one.
+- **Firebolt service account** – You must have access to an active Firebolt [service account](/Guides/managing-your-organization/service-accounts.html), which facilitates programmatic access to Firebolt, its ID and secret.
+- **Firebolt user** – You must have a user that is [associated](/Guides/managing-your-organization/service-accounts.html#create-a-user) with your service account. The user should have [USAGE](/Overview/Security/Role-Based%20Access%20Control/database-permissions/) permission to query your database, and [OPERATE](/Overview/Security/Role-Based%20Access%20Control/engine-permissions.html) permission to start and stop an engine if it is not already started.
+- **Firebolt database and engine (optional)** – You can optionally connect to a Firebolt database and/or engine. If you do not have one yet, you can [create a database](/Guides/getting-started/get-started-sql.html#create-a-database) and also [create an engine](/Guides/getting-started/get-started-sql.html#create-an-engine). You would need a database if want to access stored data in Firebolt and an engine if you want to load and query stored data.
+
+## [](#installation)Installation
+
+To install the Firebolt Go SDK, run the following `go get` command from inside your Go module:
+
+```
+go get github.com/firebolt-db/firebolt-go-sdk
+```
+
+## [](#dsn-parameters)DSN Parameters
+
+Go passes a data source name (DSN) to Firebolt’s Go SDK to connect to Firebolt. The SDK parses the DSN string for parameters to authenticate and connect to a Firebolt account, database, and engine.
+
+The DSN string supports the following parameters:
+
+- `client_id`: client ID of your [service account](/Guides/managing-your-organization/service-accounts.html).
+- `client_secret`: client secret of your [service account](/Guides/managing-your-organization/service-accounts.html).
+- `account_name`: The name of your Firebolt [account](/Guides/managing-your-organization/managing-accounts.html).
+- `database`: (Optional) The name of the [database](/Overview/Security/Role-Based%20Access%20Control/database-permissions/) to connect to.
+- `engine`: (Optional) The name of the [engine](/Overview/Security/Role-Based%20Access%20Control/engine-permissions.html) to run SQL queries on.
+
+The following is an example DSN string:
+
+```
+firebolt://[/<database>]?account_name=<account_name>&client_id=<client_id>&client_secret=<client_secret>&engine=<engine>
+```
+
+## [](#connect-to-firebolt)Connect to Firebolt
+
+To establish a connection to a Firebolt database, construct a DSN string with your credentials and database details. The following example contains a script to connect to Firebolt that you can place in a file (e.g `main.go`) and run using `go run main.go` inside your Go module:
+
+```
+package main
+
+import (
+    "database/sql"
+    "fmt"
+    // Import the Firebolt Go SDK
+    _ "github.com/firebolt-db/firebolt-go-sdk"
+)
+
+func main() {
+    // Replace with your Firebolt credentials and database details
+    clientId := "your_client_id"
+    clientSecret := "your_client_secret"
+    accountName := "your_account_name"
+    databaseName := "your_database_name" // Optional parameter
+    engineName := "your_engine_name" // Optional parameter
+    dsn := fmt.Sprintf("firebolt:///%s?account_name=%s&client_id=%s&client_secret=%s&engine=%s", databaseName, accountName, clientId, clientSecret, engineName)
+
+    // Open a connection to the Firebolt database
+    db, err := sql.Open("firebolt", dsn)
+    if err != nil {
+        log.Fatalf("Error opening database connection: %v\n", err)
+        return
+    }
+    defer db.Close()
+
+    // Your database operations go here
+}
+```
+
+## [](#run-queries)Run queries
+
+Once connected, you can run SQL queries. The following examples show you how to create a table, insert data, and retrieve data. You can place them inside the previous script under `// Your database operations go here`\`:
+
+```
+// Create a table
+_, err = db.Exec("CREATE TABLE IF NOT EXISTS test_table (id INT, value TEXT)")
+if err != nil {
+    log.Fatalf("Error creating table: %v\n", err)
+    return
+}
+
+// Insert data into the table
+_, err = db.Exec("INSERT INTO test_table (id, value) VALUES (?, ?)", 1, "sample value")
+if err != nil {
+    log.Fatalf("Error inserting data: %v\n", err)
+    return
+}
+
+// Query data from the table
+rows, err := db.Query("SELECT id, value FROM test_table")
+if err != nil {
+    log.Fatalf("Error querying data: %v\n", err)
+    return
+}
+defer rows.Close()
+
+// Iterate over the result set
+for rows.Next() {
+    var id int
+    var value string
+    if err := rows.Scan(&id, &value); err != nil {
+        log.Fatalf("Error scanning row: %v\n", err)
+        return
+    }
+    log.Print("Row: id=%d, value=%s\n", id, value)
+}
+```
+
+## [](#streaming-queries)Streaming Queries
+
+Firebolt supports streaming large query results using `rows.Next()`, allowing efficient processing of large datasets.
+
+If you enable result streaming, the query execution might finish successfully, but the actual error might be returned while iterating the rows.
+
+To enable streaming, use the `firebolt-go-sdk/context` package to create a context with streaming enabled:
+
+```
+package main
+
+import (
+    "context"
+    "database/sql"
+    "fmt"
+    "log"
+    
+    "github.com/firebolt-db/firebolt-go-sdk"
+    fireboltContext "github.com/firebolt-db/firebolt-go-sdk/context"
+    
+)
+
+func main() {
+    dsn := "firebolt:///your_database_name?account_name=your_account_name&client_id=your_client_id&client_secret=your_client_secret"
+    db, err := sql.Open("firebolt", dsn)
+    if err != nil {
+        log.Fatalf("Failed to open database: %v", err)
+    }
+    defer db.Close()
+    
+    streamingCtx := fireboltContext.WithStreaming(context.Background())
+    
+    // Execute a query with streaming enabled. Imitate large query result
+    rows, err := db.QueryContext(ctx, "SELECT 123, 'data' FROM generate_series(1, 100000000)")
+    if err != nil {
+        log.Fatalf("Query execution failed: %v", err)
+    }
+    defer rows.Close()
+
+    for rows.Next() {
+        var col1 string
+        var col2 int
+        if err := rows.Scan(&col1, &col2); err != nil {
+            log.Fatalf("Error scanning row: %v", err)
+        }
+        log.Print("Row: col1=%s, col2=%d\n", col1, col2)
+    }
+    if err := rows.Err(); err != nil {
+        log.Fatalf("Row iteration error: %v", err)
+    }
+}
+```
+
+Streaming queries are particularly useful when dealing with large datasets, as they avoid loading the entire result set into memory at once.
+
+## [](#troubleshooting)Troubleshooting
+
+When building a DSN to connect with Firebolt using the Go SDK, follow these best practices to ensure correct connection string formatting and avoid parsing errors. The DSN must follow this structure:
+
+```
+firebolt:///<database_name>?account_name=<account_name>&client_id=<client_id>&client_secret=<client_secret>&engine=<engine_name>
+```
+
+**Guidelines**
+
+- Place the database name in the URI path after `firebolt:///`.
+- Use only letters, numbers, and underscores (\_) in the database name. Avoid hyphens (-), as they may cause parsing errors.
+- Ensure the `account_name` matches the name shown in the Firebolt Console URL, which is usually lowercase with no special characters.
+- Use the exact engine name as shown in the Firebolt Workspace.
+- Do not pass the database name as a query parameter. The SDK does not support `&database=` in the DSN.
+
+### [](#common-errors-and-solutions)Common errors and solutions
+
+Error message Likely cause Solution `invalid connection string format` URI format is invalid or it contains illegal characters (like `-`) Double check the URI format and remove illegal characters. `unknown parameter name database` Attempted to pass `database` as a query parameter. Move the database name into the URI path. `error opening database connection` Incorrect connection credentials. Verify connection parameters values in the Firebolt UI and use exact values.
+
+## [](#additional-resources)Additional Resources
+
+- [Firebolt Go SDK GitHub Repository](https://github.com/firebolt-db/firebolt-go-sdk)
+- [Firebolt Documentation: Connecting with Go](/Guides/developing-with-firebolt/connecting-with-go.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_jdbc.md b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_jdbc.md
new file mode 100644
index 0000000..9a54077
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_jdbc.md
@@ -0,0 +1,183 @@
+# [](#jdbc-driver)JDBC driver
+
+Firebolt’s [type 4](https://en.wikipedia.org/wiki/JDBC_driver#Type_4_driver_%E2%80%93_Database-Protocol_driver/Thin_Driver%28Pure_Java_driver%29) JDBC driver lets Java applications connect to Firebolt. The JDBC driver is open-source software released under an Apache 2 license. You can browse, fork, download, and contribute to its development on [GitHub](https://github.com/firebolt-db/jdbc).
+
+- [Download the JAR file](#download-the-jar-file)
+- [Adding the Firebolt JDBC driver as a Maven dependency](#adding-the-firebolt-jdbc-driver-as-a-maven-dependency)
+- [Adding the Firebolt JDBC driver as a Gradle dependency](#adding-the-firebolt-jdbc-driver-as-a-gradle-dependency)
+- [Connecting to Firebolt with the JDBC driver](#connecting-to-firebolt-with-the-jdbc-driver)
+- [Authentication](#authentication)
+  
+  - [Available connection parameters](#available-connection-parameters)
+  - [System settings as connection parameters](#system-settings-as-connection-parameters)
+- [Applying system settings using SET](#applying-system-settings-using-set)
+- [Connection validation](#connection-validation)
+- [Full reference documentation](#full-reference-documentation)
+
+## [](#download-the-jar-file)Download the JAR file
+
+The Firebolt JDBC driver is provided as a JAR file and requires [Java 11](https://java.com/en/download/manual.jsp) or later.
+
+Download the driver from [GitHub JDBC releases](https://github.com/firebolt-db/jdbc/releases).
+
+## [](#adding-the-firebolt-jdbc-driver-as-a-maven-dependency)Adding the Firebolt JDBC driver as a Maven dependency
+
+To connect your project to Firebolt using [Apache Maven](https://maven.apache.org/), add the Firebolt JDBC driver as a dependency in your **pom.xml** configuration file. Link to the [Firebolt Maven repository](https://central.sonatype.com/artifact/io.firebolt/firebolt-jdbc), so that Maven can download and include the JDBC driver in your project, as shown in the following code example:
+
+```
+<!-- pom.xml  -->
+
+<project ...>
+       <dependency>
+            	<groupId>io.firebolt</groupId>
+            	<artifactId>firebolt-jdbc</artifactId>
+            	<version>3.3.0</version>
+       </dependency>
+</project>
+```
+
+In the previous code example, replace `<version>3.3.0</version>` with the latest version available in the [Firebolt Maven Central repository](https://central.sonatype.com/artifact/io.firebolt/firebolt-jdbc).
+
+## [](#adding-the-firebolt-jdbc-driver-as-a-gradle-dependency)Adding the Firebolt JDBC driver as a Gradle dependency
+
+If you are using the [Gradle Build Tool](https://gradle.org/), you can configure your Gradle project to use the Firebolt JDBC driver by specifying Apache’s [Maven Central](https://maven.apache.org/repository/index.html) as a repository and adding the Firebolt JDBC driver as a dependency as follows:
+
+```
+/* build.gradle */
+
+repositories {
+    mavenCentral()
+}
+
+dependencies {
+    implementation 'io.firebolt:firebolt-jdbc:3.3.0'
+}
+```
+
+In the previous code example, replace `3.3.0` with the latest version available in the [Firebolt Maven Central repository](https://central.sonatype.com/artifact/io.firebolt/firebolt-jdbc).
+
+## [](#connecting-to-firebolt-with-the-jdbc-driver)Connecting to Firebolt with the JDBC driver
+
+Provide connection details to the Firebolt JDBC driver using a connection string in the following format:
+
+```
+jdbc:firebolt:<database>?<connection_params>
+```
+
+In the previous connection example, the following apply:
+
+- `<database>` - Specifies the name of the Firebolt database to connect to.
+- `<connection_params>` - A list of connection parameters formatted as a standard [URL query string](https://en.wikipedia.org/wiki/Query_string#Structure).
+
+## [](#authentication)Authentication
+
+To authenticate, use a [service account ID and secret](/Guides/managing-your-organization/service-accounts.html). A service account, which is used for programmatic access to Firebolt, uses a `client_id` and a `client_secret` for identification. To ensure compatibility with tools external to Firebolt, you can specify the service account’s `client_id` as `user` and `client_secret` as `password`.
+
+The following are examples of how to specify connection strings for authentication and configuration:
+
+**Example**
+
+The following example connection string configures the Firebolt JDBC driver to connect to `my_database` using a specified `client_id` and `secret_id` for authentication:
+
+```
+  jdbc:firebolt:my_database?client_id=<client_id>&client_secret=<client_secret>&account=my_account&engine=my_engine&buffer_size=1000000&connection_timeout_millis=10000
+```
+
+The previous example string also specifies an account name `my_account`, an engine name `my_engine`, a buffer size of `1000000` bytes, and a connection timeout of `10000` milliseconds, or `10` seconds.
+
+**Example**
+
+The following example provides `client_id` and `client_secret` as separate properties, rather than embedding them directly in the connection string, as shown in the previous example.
+
+Connection string:
+
+```
+  jdbc:firebolt:my_database?account=my_account&engine=my_engine&buffer_size=1000000&connection_timeout_millis=10000`
+```
+
+Connection properties:
+
+```
+  client_id=<client_id>
+  client_secret=<client_secret>
+```
+
+**Example**
+
+The following example connects to `my_database` using only connection properties for authentication and parameters, without including any parameters directly in the string.
+
+Connection string:
+
+```
+  jdbc:firebolt:my_database
+```
+
+Connection properties:
+
+```
+  client_id=<client_id>
+  client_secret=<client_secret>
+  account=my_account
+  engine=my_engine
+  buffer_size=1000000
+  connection_timeout_millis=10000
+```
+
+**Example**
+
+The following example is a minimal URL that connects to `my_database` using `client_id` and `client_secret` as connection properties for authentication, omitting the engine name and therefore connects to default engine and relying on default values for all other parameters:
+
+Connection string:
+
+```
+  jdbc:firebolt:my_database
+```
+
+Connection properties:
+
+```
+  client_id=<client_id>
+  client_secret=<client_secret>
+  account=my_account
+```
+
+Because the previous configuration example omits specifying the engine name, `my_database` connects to the default engine.
+
+Since the connection string is a URI, make sure to [percent-encode](https://en.wikipedia.org/wiki/Percent-encoding) any reserved characters or special characters used in parameter keys or parameter values.
+
+### [](#available-connection-parameters)Available connection parameters
+
+The following table lists the available parameters that can be added to a Firebolt JDBC connection string. All parameter keys are case-sensitive.
+
+Parameter key Data type Default value Range Description client\_id TEXT No default value.   (**Required**) The Firebolt service account ID. client\_secret TEXT No default value.   (**Required**) The secret generated for the Firebolt service account. account TEXT No default value.   (**Required**) Your Firebolt account name. database TEXT No default value.   The name of the database to connect to. Takes precedence over the database name provided as a path parameter. engine TEXT The default engine attached to the specified database.   The name of the engine to connect to. buffer\_size INTEGER `65536` `1` to `2147483647` The buffer size, in bytes, that the driver uses to read the responses from the Firebolt API. connection\_timeout\_millis INTEGER `60000` `0` to `2147483647` The wait time in milliseconds before a connection to the server is considered failed. A timeout value of zero means that the connection will wait indefinitely. max\_connections\_total INTEGER `300` `1` to `2147483647` The maximum total number of connections. socket\_timeout\_millis INTEGER `0` `0` to `2147483647` The socket timeout, in milliseconds, which specifies the maximum wait time for data, defining the longest allowed inactivity between consecutive data packets. A value of zero means that there is no timeout limit. connection\_keep\_alive\_timeout\_millis INTEGER `300000` `1` to `2147483647` Defines the duration to keep a server connection open in the connection pool before it is closed. ssl\_mode TEXT `strict` `strict` or `none` When set to `strict`, the SSL or TLS certificate is validated for accuracy and authenticity. If set to `none`, certificate verification is omitted. ssl\_certificate\_path TEXT No default value.   The absolute file path for the SSL root certificate. validate\_on\_system\_engine BOOLEAN `FALSE` `TRUE` or `FALSE` When set to `TRUE`, the connection is always validated against a system engine, even if it’s connected to a regular engine. For more information, see [Connection validation](#connection-validation).
+
+### [](#system-settings-as-connection-parameters)System settings as connection parameters
+
+In addition to the parameters specified in the previous table, any [system setting](/Reference/system-settings.html) can be passed as a connection string parameter. For example, to set a custom time zone, use the following format:
+
+```
+jdbc:firebolt:my_database?time_zone=UTC&<other_connection_params>
+```
+
+## [](#applying-system-settings-using-set)Applying system settings using SET
+
+In addition to passing system settings as connection string parameters, any [system setting](/Reference/system-settings.html) can be passed using the SQL `SET` command. Multiple `SET` statements can be run consecutively, separated by semicolons, as shown below:
+
+```
+SET time_zone = 'UTC';
+SET standard_conforming_strings = false;
+```
+
+## [](#connection-validation)Connection validation
+
+The Firebolt JDBC driver validates the connection by sending a `SELECT 1` query to the system engine. If this query fails, the driver throws an exception. You can use the `validate_on_system_engine` parameter to customize validation. When it is set to `true`, the validation query is sent to the system engine, even if the connection is established with a regular engine. This feature can be useful if you want to stop the regular engine but still need to validate the connection.
+
+The following example configures the Firebolt JDBC driver to connect to `my_database` and validate the connection using the system engine with additional connection parameters specified in `other_connection_parameters`:
+
+```
+jdbc:firebolt:my_database?validate_on_system_engine=true&<other_connection_params>
+```
+
+## [](#full-reference-documentation)Full reference documentation
+
+The complete documentation for classes and methods in the Firebolt JDBC driver is available in the [Firebolt JDBC API reference guide](https://jdbc.docs.firebolt.io/javadoc/).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_net_sdk.md b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_net_sdk.md
new file mode 100644
index 0000000..f02ea9d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_net_sdk.md
@@ -0,0 +1,96 @@
+# [](#firebolt-net-sdk)Firebolt .NET SDK
+
+## [](#overview)Overview
+
+The Firebolt .NET SDK is a software development kit designed to facilitate the integration of Firebolt’s high-performance database capabilities into .NET applications. This SDK provides developers with the tools and interfaces needed to interact with Firebolt databases efficiently, enabling effective data manipulation and query execution.
+
+## [](#installation)Installation
+
+Install the Firebolt .NET SDK by adding the NuGet package to your project. You can do this in several ways:
+
+### [](#via-package-manager-console)Via Package Manager Console
+
+```
+Install-Package FireboltNetSdk
+```
+
+### [](#via-net-cli)Via .NET CLI
+
+```
+dotnet add package FireboltNetSdk
+```
+
+### [](#via-packagereference)Via PackageReference
+
+Add the following line to your project file:
+
+```
+<PackageReference Include="FireboltNetSdk" Version="x.x.x" />
+```
+
+Make sure to replace `x.x.x` with the specific version you want to use.
+
+### [](#via-visual-studio-ui)Via **Visual Studio UI**
+
+`Tools` &gt; `NuGet Package Manager` &gt; `Manage NuGet Packages for Solution` and search for `Firebolt`
+
+For more details and versioning information, please visit the [NuGet Gallery](https://www.nuget.org/packages/FireboltNetSdk/).
+
+## [](#quick-start)Quick Start
+
+Here’s a simple example to get started with the Firebolt .NET SDK:
+
+```
+using System.Data.Common;
+using FireboltDotNetSdk.Client;
+
+public class Program
+{
+    public static async Task Main(string[] args)
+    {
+        // Name of your Firebolt account
+        string account = "my_firebolt_account";
+        // Client credentials, that you want to use to connect
+        string clientId = "my_client_id";
+        string clientSecret = "my_client_secret";
+        // Name of database and engine to connect to (Optional)
+        string database = "my_database_name";
+        string engine = "my_engine_name";
+        
+        // Construct a connection string using defined parameter
+        string conn_string = $"account={account};clientid={clientId};clientsecret={clientSecret};database={database};engine={engine}";
+        
+        // Create a new connection using generated connection string
+        using var conn = new FireboltConnection(conn_string);
+        // Open a connection
+        conn.Open();
+
+        // First you would need to create a command
+        var command = conn.CreateCommand();
+        
+        // ... and set the SQL query
+        command.CommandText = "SELECT * FROM my_table";
+        
+        // Execute a SQL query and get a DB reader
+        DbDataReader reader = command.ExecuteReader();
+        
+        // Optionally you can check whether the result set has rows
+        Console.WriteLine($"Has rows: {reader.HasRows}");
+        
+        // Close the connection after all operations are done
+        conn.Close();
+    }
+}
+```
+
+## [](#documentation)Documentation
+
+For more detailed documentation, including API references and advanced usage, please refer to the [README](https://github.com/firebolt-db/firebolt-net-sdk/blob/main/README.md) file in the repository.
+
+## [](#support)Support
+
+For support, issues, or contributions, please refer to the repository’s issue tracker and contributing guidelines.
+
+## [](#license)License
+
+This SDK is released under **Apache License 2.0**. Please see the [LICENSE](https://github.com/firebolt-db/firebolt-net-sdk/blob/main/LICENSE) file for more details.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_nodejs.md b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_nodejs.md
new file mode 100644
index 0000000..de5322c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_nodejs.md
@@ -0,0 +1,132 @@
+# [](#nodejs)Node.js
+
+- [Overview](#overview)
+- [Installation](#installation)
+- [Authentication](#authentication)
+- [Quick start](#quick-start)
+- [Contribution](#contribution)
+- [License](#license)
+
+## [](#overview)Overview
+
+The Firebolt Node SDK is a software development kit designed to facilitate the integration of Firebolt’s high-performance database capabilities into Node.js applications. This SDK provides a set of tools and interfaces for developers to interact with Firebolt databases, enabling efficient data manipulation and query execution. For more detailed documentation, including API references and advanced usage, refer to the [README](https://github.com/firebolt-db/firebolt-node-sdk/blob/main/README.md) file in the Firebolt Node SDK repository.
+
+## [](#installation)Installation
+
+To install the Firebolt Node SDK, run the following command in your project directory:
+
+```
+npm install firebolt-sdk
+```
+
+## [](#authentication)Authentication
+
+After installation, you must authenticate before you can use the SDK to establish connections, run queries, and manage database resources. The following code example sets up a connection using your Firebolt [service account](/Guides/managing-your-organization/service-accounts.html) credentials:
+
+```
+const connection = await firebolt.connect({
+  auth: {
+    client_id: '12345678-90123-4567-8901-234567890123',
+    client_secret: 'secret',
+  },
+  engineName: 'engine_name',
+  account: 'account_name',
+  database: 'database',
+});
+```
+
+In the previous code example, the following details apply:
+
+- `client_id` and `client_secret`: These are your service account credentials. Refer to Firebolt’s guide to learn how to [create a service account](/Guides/managing-your-organization/service-accounts.html#create-a-service-account) and obtain its [ID](/Guides/managing-your-organization/service-accounts.html#get-a-service-account-id) and [secret](/Guides/managing-your-organization/service-accounts.html#generate-a-secret).
+- `engineName`: The name of the engine used to run your queries on.
+- `database`: The target database where your tables will be stored.
+- `account`: The object within your organization that encapsulates resources for storing, querying, and managing data. In the Node.js SDK, the [account](/Overview/organizations-accounts.html#accounts) parameter specifies which organizational environment the connection will use.
+
+## [](#quick-start)Quick start
+
+In the following code example, credentials are stored in environment variables.
+
+```
+import { Firebolt } from 'firebolt-sdk'
+
+// Initialize client
+const firebolt = Firebolt();
+
+// Establish connection to Firebolt using environment variables for credentials and configuration
+const connection = await firebolt.connect({
+  auth: {
+    client_id: process.env.FIREBOLT_CLIENT_ID,
+    client_secret: process.env.FIREBOLT_CLIENT_SECRET,
+  },
+  account: process.env.FIREBOLT_ACCOUNT,
+  database: process.env.FIREBOLT_DATABASE,
+  engineName: process.env.FIREBOLT_ENGINE_NAME
+});
+
+// Create a "users" table
+await connection.execute(`
+  CREATE TABLE IF NOT EXISTS users (
+    id INT,
+    name STRING,
+    age INT
+  )
+`);
+
+// Insert sample data
+await connection.execute(`
+  INSERT INTO users (id, name, age) VALUES
+  (1, 'Alice', 30),
+  (2, 'Bob', 25)
+`);
+
+// Update rows
+await connection.execute(`
+  UPDATE users SET age = 31 WHERE id = 1
+`);
+
+// Fetch data with a query
+const statement = await connection.execute("SELECT * FROM users");
+
+// Fetch the complete result set
+const { data, meta } = await statement.fetchResult();
+
+// Log metadata describing the columns of the result set
+console.log(meta)
+// Outputs:
+// [
+//   Meta { type: 'int null', name: 'id' },
+//   Meta { type: 'text null', name: 'name' },
+//   Meta { type: 'int null', name: 'age' }
+// ]
+
+// Alternatively, stream the result set row by row
+const { data } = await statement.streamResult();
+
+data.on("metadata", metadata => {
+  console.log(metadata);
+});
+
+// Handle metadata event
+data.on("error", error => {
+  console.log(error);
+});
+
+const rows = []
+
+for await (const row of data) {
+  rows.push(row);
+}
+
+// Log the collected rows
+console.log(rows)
+// Outputs:
+// [ [ 1, 'Alice', 31 ], [ 2, 'Bob', 25 ] ]
+```
+
+## [](#contribution)Contribution
+
+To receive support, report issues, or contribute, please refer to the Firebolt Node SDK repository [issue tracker](https://github.com/firebolt-db/firebolt-node-sdk/issues).
+
+## [](#license)License
+
+This SDK is released under **Apache License 2.0**. See the [LICENSE](https://github.com/firebolt-db/firebolt-node-sdk/blob/main/LICENSE) file for more details.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_python.md b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_python.md
new file mode 100644
index 0000000..873bfcb
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_python.md
@@ -0,0 +1,7 @@
+# [](#python)Python
+
+You can use the Python SDK to work with Firebolt. See the resources below for more information.
+
+- [Firebolt Python SDK documentation](https://python.docs.firebolt.io/sdk_documenation/latest/)
+- The [firebolt-python-sdk repository on GitHub](https://github.com/firebolt-db/firebolt-python-sdk/)
+- Code examples (in Jupyter notebooks) in the SDK repository that demonstrate common [data tasks](https://github.com/firebolt-db/firebolt-python-sdk/blob/main/examples/dbapi.ipynb) and [management tasks](https://github.com/firebolt-db/firebolt-python-sdk/blob/main/examples/management.ipynb)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_sqlalchemy.md b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_sqlalchemy.md
new file mode 100644
index 0000000..71ccf26
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_developing_with_firebolt_connecting_with_sqlalchemy.md
@@ -0,0 +1,11 @@
+# [](#connect-with-sqlalchemy)Connect with SQLAlchemy
+
+SQLAlchemy is an open-source SQL toolkit and object-relational mapper for the Python programming language.
+
+Firebolt’s adapter for SQLAlchemy acts as an interface for other supported third-party applications including Superset and Preset. When the SQLAlchemy adapter is successfully connected, these applications are able to communicate with Firebolt databases through the REST API.
+
+The adapter is written in Python using the SQLAlchemy toolkit.
+
+### [](#get-started)Get started
+
+Follow the guidelines for SQLAlchemy integration in the Firebolt-SQLAlchemy [Github repository](https://github.com/firebolt-db/firebolt-sqlalchemy/).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_exporting_data.md b/cmd/docs-scrapper/fireboltdocs/guides_exporting_data.md
new file mode 100644
index 0000000..3a065f3
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_exporting_data.md
@@ -0,0 +1,90 @@
+# [](#export-data)Export data
+
+You can export data from a `SELECT` query directly to an Amazon S3 location using [COPY TO](/sql_reference/commands/data-management/copy-to.html). This method is more flexible and efficient than downloading query results manually from the **Firebolt Workspace**, making it ideal for data sharing, integration, and archival.
+
+## [](#how-to-export-data)How to export data
+
+The following code example uses `COPY TO` to export the result of a `SELECT` query from `my_table` to a specified Amazon S3 bucket in CSV format using the provided [AWS credentials](/sql_reference/commands/data-management/copy-to.html#credentials):
+
+```
+COPY (
+    SELECT column1, column2 FROM my_table WHERE condition
+) 
+TO 's3://your-bucket/path/'
+WITH (FORMAT = 'CSV')
+CREDENTIALS = ('aws_key_id'='your-key' 'aws_secret_key'='your-secret');
+```
+
+## [](#choose-the-right-export-format)Choose the right export format
+
+Format Best For Characteristics Recommended Use **CSV (Comma-Separated)** General data exchange, spreadsheets, SQL. Simple, widely supported, and easy to read. Best for spreadsheets, databases, or general data exchange. **TSV (Tab-Separated)** Structured text data. Like CSV, but uses tabs instead of commas. Best for Excel, databases, or general data exchange. **JSON** APIs, web applications, NoSQL databases. Flexible, human-readable, and supports nested data. Best for web apps, APIs, or NoSQL integrations. **PARQUET** Big data processing, analytics workloads. Compressed, columnar, and optimized for querying. Ideal for analytics, performance-sensitive workloads, and large datasets.
+
+## [](#examples)Examples
+
+**Export data in CSV format**
+
+Use CSV when you need a simple, widely supported format for spreadsheets, relational databases, or data exchange.
+
+The following code example exports `user_id`, `event_type`, and `timestamp` data and headers from the `user_events` table to a CSV file in an Amazon S3 bucket:
+
+```
+COPY (SELECT user_id, event_type, timestamp FROM user_events) 
+TO 's3://my-export-bucket/user_events.csv'
+WITH (FORMAT = 'CSV', HEADER = TRUE)
+CREDENTIALS = ('aws_key_id'='your-key' 'aws_secret_key'='your-secret');
+```
+
+**Export data in Parquet format**
+
+Parquet is best for big data workloads, as it offers compressed, columnar storage optimized for analytics and query performance.
+
+The following code example exports all data from the `sales_data` table to an Amazon S3 bucket in Parquet format using the provided AWS credentials:
+
+```
+COPY (SELECT * FROM sales_data) 
+TO 's3://my-export-bucket/sales_data.parquet'
+WITH (FORMAT = 'PARQUET')
+CREDENTIALS = ('aws_key_id'='your-key' 'aws_secret_key'='your-secret');
+```
+
+**Export data in JSON format**
+
+JSON is ideal for APIs, web applications, and NoSQL databases, as it supports nested and flexible data structures.
+
+The following code example exports `order_id` and `order_details` from the `orders` table to an Amazon S3 bucket in JSON format using the provided AWS credentials:
+
+```
+COPY (SELECT order_id, order_details FROM orders) 
+TO 's3://my-export-bucket/orders.json'
+WITH (FORMAT = 'JSON')
+CREDENTIALS = ('aws_key_id'='your-key' 'aws_secret_key'='your-secret');
+```
+
+**Export data in TSV format**
+
+TSV is similar to CSV but uses tab delimiters, making it useful for structured text data that may contain commas.
+
+The following code example exports `name`, `age`, and `city` from the `customers` table to an Amazon S3 bucket in TSV format using the provided AWS credentials:
+
+```
+COPY (SELECT name, age, city FROM customers) 
+TO 's3://my-export-bucket/customers.tsv'
+WITH (FORMAT = 'TSV')
+CREDENTIALS = ('aws_key_id'='your-key' 'aws_secret_key'='your-secret');
+```
+
+## [](#additional-considerations)Additional Considerations
+
+**Performance tips**
+
+- Export only required columns and use filters to reduce data volume
+- Ensure proper permissions are set on your S3 bucket
+
+**Security and credentials**
+
+- Always use **secure AWS credentials**.
+- Use **IAM roles** instead setting credentials directly in the code for better security.
+
+## [](#next-steps)Next Steps
+
+For more information about advanced options including **compression**, **partitioning**, and **null handling**, see [COPY TO](/sql_reference/commands/data-management/copy-to.html).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_getting_started.md b/cmd/docs-scrapper/fireboltdocs/guides_getting_started.md
new file mode 100644
index 0000000..202b86e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_getting_started.md
@@ -0,0 +1,16 @@
+# [](#get-started-with-firebolt)Get started with Firebolt
+
+Welcome to the beginning of your journey with Firebolt! This tutorial guides you through all of the steps you need to run a basic workflow which includes setting up your Firebolt account, creating a database and engine, importing a sample dataset, creating indexes, and running a query. If you encounter any issues, reach out to [support@firebolt.io](mailto:support@firebolt.io) for help.
+
+To get started, you must [register](https://go.firebolt.io/signup) and create a Firebolt account. Then, you can either use the **Develop Space** inside the **Firebolt Workspace**, or use the **Load data** wizard to create a database and engine, and load data. Then, you can run your first query to obtain baseline performance statistics. Next, you can tune your workflow using Firebolt’s optimization strategies to reduce query run times. You can set a primary index and use aggregating indexes to speed up your query times significantly. Lastly, you can export your data to an external table. These steps are illustrated in the following workflow:
+
+![Get Started](../assets/images/../../../assets/images/architecture-workflow.png)
+
+After you register, you can either use the [Load data wizard](/Guides/getting-started/get-started-load-data-wizard.html) or the [use SQL](/Guides/getting-started/get-started-sql.html). Use the Load data wizard if your data is in either CSV or Parquet format, and you want to use a graphical user interface to guide you through the first three steps of the workflow. Use the Firebolt **Develop Space** or an API if you prefer to enter SQL, or need a more customized workflow.
+
+## [](#next-steps)Next steps
+
+Choose either of the following:
+
+- [Get started using a wizard](/Guides/getting-started/get-started-load-data-wizard.html)
+- [Get started using SQL](/Guides/getting-started/get-started-sql.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_load_data_wizard.md b/cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_load_data_wizard.md
new file mode 100644
index 0000000..0a0cf68
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_load_data_wizard.md
@@ -0,0 +1,48 @@
+# [](#get-started-using-a-wizard)Get started using a wizard
+
+The **Load data** wizard guides you through creating a database and engine, and loading data from an Amazon S3 bucket. You can specify basic configurations, including what character to use as a file delimiter, which columns to import and their schema. After loading your data, continue working in the **Develop Space** to run and optimize a query, and export to an external table, as shown in the following diagram:
+
+![A simple workflow using the load data wizard starts with registering, using the wizard, running a query, optimizing your workflow, and cleaning up. ](../../assets/images/get_started_wizard_workflow.png)
+
+## [](#register-with-firebolt)Register with Firebolt
+
+![The first step in getting started is to register with Firebolt.](../../assets/images/get_started_wizard_register.png)
+
+Use the following steps to register with Firebolt:
+
+1. [Sign up](https://go.firebolt.io/signup) on Firebolt’s registration page. Fill in your email, name, choose a password, and select **Get Started**.
+2. Firebolt will send a confirmation to the address that you provided. To complete your registration, select **Verify** in the email to take you to Firebolt’s [login page](https://go.firebolt.io/login).
+3. Type in your email and password and select **Log In**.
+
+New accounts receive credits ($200) to get started exploring Firebolt’s capabilities. Credits must be used within 30 days of account creation.
+
+Firebolt’s billing is based on engine runtime, measured in seconds. AWS S3 storage costs are passed through at the rate of $23 per TB per month. Your cost depends primarily on which engines you use and how long those engines are running.
+
+You can view your total cost in FBU up to the latest second and in $USD up to the latest day. For more information, see the following **Create a Database** section. For more information about costs, see [Data Warehouse Pricing](https://www.firebolt.io/pricing). If you need to buy additional credits, connect Firebolt with your AWS Marketplace account. For more information about AWS Marketplace, see the following section: [Registering through AWS Marketplace section](/Guides/getting-started/get-started-next.html#register-through-the-aws-marketplace).
+
+## [](#use-the-load-data-wizard)Use the Load data wizard
+
+![After registering, use the load data wizard to create a database, engine, and load data.](../../assets/images/get_started_wizard_wizard.png)
+
+You can use the **Load data** wizard to load data in either CSV or Parquet form.
+
+To start the **Load data** wizard, select the plus (+) icon in the **Develop Space** next to **Databases** in the left navigation pane and select **Load data**. The wizard will guide you through creating a database, an engine, and loading data. See [Load data using a wizard](/Guides/loading-data/loading-data-wizard.html#load-data-using-a-wizard) for detailed information about the workflow and the available options in the wizard.
+
+Even though the **Load data** wizard creates a database and engine for you, the [**Create a Database**](/Guides/getting-started/get-started-sql.html#create-a-database) and [**Create an Engine**](/Guides/getting-started/get-started-sql.html#create-an-engine) sections in the [Use SQL to load data](/Guides/getting-started/get-started-sql.html) guide contain useful information about billing for engine runtime and schema.
+
+To use the **Load data** wizard, select the plus (+) icon. For detailed information about how to use the **Load data** wizard, see the [Load data](/Guides/loading-data/loading-data.html) guide.
+
+## [](#run-query-optimize-clean-up-and-export)Run query, optimize, clean up, and export
+
+![After using the load data wizard, a simple workflow continues with running a query, optimization, cleaning up, and optionally exporting a dataset.](../../assets/images/get_started_wizard_next.png)
+
+After you have loaded your data in the wizard, the rest of the steps in getting started are the same as if you ran your workflow in SQL. You can use either the **Develop Space** in the **Firebolt Workspace** to enter SQL, or use the [Firebolt API](/Guides/query-data/using-the-api.html).
+
+- For information about how to get started running a query, see [Run query](/Guides/getting-started/get-started-sql.html#run-query).
+- For information about how to get started optimizing your workflow, see [Optimize your workflow](get-started-sql#optimize-your-workflow).
+- For information about how to get started cleaning up resources and data, see [Clean up resources](./get-started-sql#clean-up).
+- For information on how to export your data, see [Export data](/Guides/getting-started/get-started-sql.html#export-data).
+
+## [](#next-steps)Next steps
+
+To continue learning about Firebolt’s architecture, capabilities, using Firebolt after your trial period, and setting up your organization, see [Resources beyond getting started](/Guides/getting-started/get-started-next.html).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_next.md b/cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_next.md
new file mode 100644
index 0000000..aad1d86
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_next.md
@@ -0,0 +1,28 @@
+# [](#resources-beyond-getting-started)Resources beyond getting started
+
+Now that you have successfully created your first engine and database, run your first query, created indexes, copied data into Firebolt and exported data out, you can continue exploring Firebolt’s capabilities.
+
+## [](#register-through-the-aws-marketplace)Register through the AWS Marketplace
+
+If you have exhausted your initial $200 credit, you can continue to use Firebolt after registering through the [AWS Marketplace](https://aws.amazon.com/marketplace). You must set up an account for billing in order to continue using Firebolt’s engines to run queries.
+
+**To register**
+
+1. On the [Firebolt Workspace page](https://go.firebolt.io/), select the **Configure**(![AggIndex](../../assets/images/configure-icon.png)) icon from the left navigation pane.
+2. Under **Organization settings**, select **Billing**.
+3. Click **Connect to AWS Marketplace** to take you to the Firebolt page on AWS Marketplace.
+4. On the AWS Marketplace page, click the **View Purchase Options** in the top right hand corner of the screen.
+5. Click **Setup Your Account**.
+
+Your account should now be associated with AWS Marketplace.
+
+## [](#learn-more-about-firebolt)Learn more about Firebolt
+
+- Learn about Firebolt’s unique [architecture](/Overview/architecture-overview.html).
+- Learn more about creating tables and [managing your data](/Overview/data-management.html) in order to let Firebolt provide the fastest query times.
+- Learn about the [engines](/Overview/engine-fundamentals.html) that Firebolt uses to process queries and how to select the right size.
+- Learn how to [load](/Guides/loading-data/loading-data.html) different kinds of data.
+- Learn more about [querying data](/Guides/query-data/).
+- Learn more about using [indexes](/Overview/indexes/using-indexes.html) to optimize your query times.
+- Learn how to [set up your organization](/Guides/managing-your-organization/) to use Firebolt.
+- Learn how to [integrate Firebolt](/Guides/integrations/integrations.html) with third party tools and applications.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_sql.md b/cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_sql.md
new file mode 100644
index 0000000..da70cb4
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_getting_started_get_started_sql.md
@@ -0,0 +1,373 @@
+# [](#get-started-using-sql)Get started using SQL
+
+You can also use SQL to create a database and engine, and load data. If you use the **Develop Space** inside the **Firebolt Workspace**, you can customize your workflow to handle more unique workflows than with the **Load data** wizard, including loading data in TSV, Avro, JSON Lines, or ORC formats.
+
+The following sections will guide you through a simple workflow to register, create a database and engine, load and query data, learn how to optimize your workflow, and clean up resources as shown in the following diagram:  
+![A simple workflow using SQL includes registering, creating a database and engine, loading data, querying data, optimizing your workflow, cleaning up, and optionally exporting data.](../../assets/images/get_started_sql_workflow.png)
+
+## [](#register-with-firebolt)Register with Firebolt
+
+![The first step in the workflow is to register with Firebolt.](../../assets/images/get_started_sql_register.png)  
+To get started using Firebolt, begin by registering using the following steps:
+
+1. [Register](https://go.firebolt.io/signup) with Firebolt. Fill in your email, name, choose a password, and select ‘Get Started’.
+2. Firebolt will send a confirmation to the address that you provided. To complete your registration, select **Verify** in the email to take you to Firebolt’s [login page](https://go.firebolt.io/login).
+3. Type in your email and password and select **Log In**.
+
+New accounts receive credits ($200) to get started exploring Firebolt’s capabilities. These credits must be used within 30 days of account creation.
+
+Firebolt’s billing is based on engine runtime, measured in seconds. We also pass through AWS S3 storage costs at the rate of $23 per TB per month. The amount that you spend is dependent primarily on which engines you use and how long those engines are running.
+
+You can view your total cost in FBU up to the latest second and in $USD up to the latest day. For more information, see the following **Create a Database** section. For more information about costs, see [Data Warehouse Pricing](https://www.firebolt.io/pricing). If you need to buy additional credits, connect Firebolt with your AWS Marketplace account. For more information about AWS Marketplace, see the following section: [Registering through AWS Marketplace section](/Guides/getting-started/get-started-next.html#register-through-the-aws-marketplace).
+
+## [](#create-a-database)Create a Database
+
+![After registering, create a database.](../../assets/images/get_started_sql_database.png)  
+Firebolt decouples storage and compute resources so that multiple engines can run computations on the same database. You can also configure different engine sizes for different workloads. These workloads can run in parallel or separately. Because storage is decoupled from compute, you must first create both a database and an engine before you can run your first query.
+
+Firebolt’s structure is organized as follows:
+
+- A database holds the elements that you need to run queries such as tables, views and information schema.
+- An [engine](/Overview/engine-fundamentals.html) provides the compute resources for ingesting data and running queries. For more information on using Firebolt engines and how to select the correct size for your workload, see [Operate engines](/Guides/operate-engines/operate-engines.html).
+
+If you used the **Load data** wizard, Firebolt has already created a database for you, and you can skip creating a database.
+
+The following instructions show you how to create a database and then an engine. Note that you can also create the engine first.
+
+1. In the left navigation pane, select the **+** to the right **Databases**.
+2. Select **Create new database**.
+3. Enter the name for your database in the **Database Name** field. For this example, use “tutorial\_database” as your database name. In Firebolt, the names of engines and databases are **case-sensitive**. If you are using uppercase characters in their names, enclose their name inside double quotes (“) when you refer to them in SQL.
+
+Firebolt creates a new database with the following two default schemas:
+
+- **Public** - A namespace where you can create and manage your database objects including tables, engines and queries. The default schema includes **tables**, **external tables**, and **views**.
+- **Information\_schema** - A standardized set of read-only views that provide metadata about database objects including tables, engines, cost information, and queries.
+
+You can find these schema by selecting your database under **Databases** in the left navigation pane. Next to the name of your database, select the drop-down arrow to expand and view the schemas and their contents. You can view your total cost in FBU up to the latest second and in $USD up to the latest day in **Information\_schema**.
+
+If you’re using the **Develop Space**, expand **Information\_schema**, and then **Views** to show the following:
+
+- **engine\_metering\_history** - contains information about billing cost in FBU up to the latest second in **consumed\_fbu**.
+- **engine\_billing** - contains information about billing cost in US dollars up to the latest day in **billed\_cost**.
+
+To see values for the previous costs, select the **More options** icon (![More options icon](../../assets/images/more_options_icon.png)) next to either **consumed\_fbu** or **billed\_cost**, Then select **Preview data**. You can also run a query in the script tab as shown in the following code example:
+
+```
+SELECT * 
+FROM information_schema.engine_metering_history 
+```
+
+## [](#create-an-engine)Create an Engine
+
+![After creating a database, create an engine.](../../assets/images/get_started_sql_engine.png)  
+To process a query, you must use an engine. You can either create an engine based on the following recommendations, or use the system engine. You can only use the system engine to run metadata-related queries, but it is always running, so you don’t have to wait for it to start. You can use the system engine to process data in any database. If you create your own engine, there is a small start up time associated with it.
+
+Firebolt recommends the following initial engine configurations based on where you are in your exploration of Firebolt’s capabilities. An FBU stands for a Firebolt Unit, and is equivalent to 35 US cents.
+
+Each FBU is related to the amount of time as follows:
+
+Task Expected Usage Ingest initial data 4-16 FBU Run test queries 8-32 FBU Find optimal query performance 32-240 FBU Find optimal test integrations 32-240 FBU
+
+Each engine node can cache data locally to improve performance.
+
+Small and medium engines are available for use right away. If you want to use a large or extra-large engine, reach out to support@firebolt.io. The default engine configuration uses a small node, which is sufficient for this tutorial. To learn more about how to select the correct engine size for your workload, see [Sizing Engines](/Guides/operate-engines/sizing-engines.html).
+
+By default, when you login to **Firebolt’s Workspace** for the first time, Firebolt creates a tab in the **Develop Space** called **Script 1**. The following apply:
+
+- The database that **Script 1** will run using is located directly below the tab name. If you want to change the database, select another database from the drop-down list.
+- An engine must be running to process the script in a selected tab. The name and status of the engine that **Script 1** uses for computation is located to the right of the current selected database. To change either the engine or the status, select the drop-down arrow next to the engine name. You can select a new engine and change its status from **Stopped** to **Running** by selecting **Start engine**. If you select **Run** at the bottom of the workspace, the selected engine starts automatically. Select **Stop engine** to change the status to **Stopped**. Firebolt automatically stops your engine if it is inactive for 20 minutes.
+
+Because an engine is a dedicated compute node that nobody else can use, you are charged for each second that your engine is **Running**, even if it’s not processing a query.
+
+If you used the **Load data** wizard, Firebolt has already created an engine for you, and you can skip the following step.
+
+1. Select the **(+)** icon next to **Databases**.
+2. Select **Create new engine** from the drop-down list.
+3. Enter the name of your engine in the **New engine name** text box. For this example, enter “tutorial\_engine” as your engine name.
+
+## [](#load-data)Load Data
+
+![After creating an engine, you can load your data.](../../assets/images/get_started_sql_load.png)
+
+After creating an engine, you can load your data. This tutorial uses Firebolt’s publicly available Firebolt’s sample dataset, from the fictional [“Ultra Fast Gaming Inc.”](https://help.firebolt.io/t/ultra-fast-gaming-firebolt-sample-dataset/250) company. This dataset does not require access credentials. If your personal dataset requires access credentials, you will need to provide them. For examples of how to provide access credentials and more complex loading workflows, see [Loading data](/Guides/loading-data/loading-data.html). For more information about AWS access credentials, see [Creating Access key and Secret ID](/Guides/loading-data/creating-access-keys-aws.html)
+
+If you used the **Load data** wizard, skip ahead to the following **Run query** section.
+
+Use [COPY FROM](/sql_reference/commands/data-management/copy-from.html) in the **Develop Space** to copy data directly from a source into a Firebolt managed table.
+
+1. Enter the following into the **Script 1** tab to load data using the following steps:
+   
+   ```
+     COPY INTO tutorial FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv' WITH HEADER=TRUE;
+   ```
+   
+   For examples of more complex loading workflows, see [Load data](/Guides/loading-data/loading-data.html).
+2. Select **Run**.
+3. In the left navigation pane under the **Tutorial\_Database**, **Tables** now contains the **tutorial** table.
+4. Expand the drop down menu next to **Columns** to view the name and data format of each column.
+5. Select the **More options** icon (![More options icon](../../assets/images/more_options_icon.png)) next to the data type of each column name to open a pop-up that allows you to insert the name of the column into your SQL script. You can also select **Preview data**.
+6. To view the contents of the **tutorial** table, run a SELECT query as shown in the following code example. To run this in a new tab, select the (**+**) icon next to the **Script 1** tab.
+   
+   ```
+     SELECT
+    *
+     FROM
+    tutorial
+   ```
+7. Select **Run**. The bottom of your workspace includes information about your processing job in the following tabs:
+   
+   - The **Results** tab at the bottom of your **Develop Space** shows the contents returned by your query. After running the previous SELECT statement, the **Results** tab should display column names and values for the data in the tutorial.
+   
+   <!--THE END-->
+   
+   - Select the filter icon (![Filter icon](../../assets/images/filter-icon.png)) to change which columns are shown.
+   - Select the **More options** icon (![More options icon](../../assets/images/more_options_icon.png)) to export the contents of the **Results** tab to a JSON or CSV file.
+   - The Statistics tab shows information about running your query including how long it took to run and its status. After running the previous SELECT statement, the **Statistics** tab shows the status of the statement, its STATUS as having succeeded or failed, how long it took to run the query, the number of rows processed, and the amount of data scanned.
+   - Select the **More options** icon (![More options icon](../../assets/images/more_options_icon.png)) to export the contents of the **Statistics** tab to a JSON or CSV file.
+   - The **Query Profile** tab contains metrics for each operator used in your query and a **Query id**. Select an operation to view its metrics. These metrics include the following:
+     
+     - The output cardinality - the number of rows that each operator produced.
+     - The thread time - the sum of the wall clock time that threads spent to run the selected operation across all nodes.
+     - The CPU time - the sum of the time that threads that ran the operator were scheduled on a CPU core.
+     - The output types - the data types of the result of the operator.
+
+You can use these metrics to analyze and measure the efficiency and performance of your query. For example, If the CPU time is much smaller than thread time, the input-output (IO) latency may be high or the engine that you are using may be running multiple queries at the same time. For more information, see [Example with ANALYZE](/sql_reference/commands/queries/explain.html).
+
+- The **Engine monitoring** tab shows monitoring information including the percent CPU, memory, disk use and cache read. Information is shown from the last 5 minutes by default. Select a different time interval from the drop-down menu next to **Last 5 minutes**. You can also select the **Refresh** icon next to the drop-down menu to update the graphical information.
+- The **Query history** tab shows detailed information associated with each query, listed by its **Query id**. This information includes the query status, start time, number of rows and bytes scanned during the load, user and account information. You can choose the following options at the top of the bottom panel:
+  
+  - Select the **Refresh** icon to update the query history and ID.
+  - Select the filter icon (![Filter data icon](../../assets/images/filter-icon.png)) to remove or add columns to display.
+  - Select the **More options** icon (![More options icon](../../assets/images/more_options_icon.png)) to export the contents of the **Query history** tab to a JSON or CSV file.
+
+For more information about Firebolt’s **Develop Space**, see [Using the develop workspace](/Guides/query-data/using-the-develop-workspace.html).
+
+## [](#run-query)Run Query
+
+![After loading your data, you can run a query.](../../assets/images/get_started_sql_query.png)
+
+To run a query on your data, do the following:
+
+1. Select the (**+**) icon next to the **Script 2** tab to open a new tab.
+2. Enter the following simple query, which fetches a list of databases associated with your account:
+   
+   ```
+     SHOW CATALOGS;
+   ```
+3. Select **Run** to process the query. Firebolt uses the engine listed to the right of your database to run your query and its status of **Running** or **Stopped**. You can select a different engine from the dropdown menu next to the engine (![Engine icon](../../assets/images/engine-icon.png)) icon.
+   
+   If your engine is **Stopped**, Firebolt may prompt you to start your engine. Select **Start Engine**. Engine startup typically requires a few moments to complete, as Firebolt prepares your environment for data analysis.
+
+For more information about Firebolt’s **Develop Space**, see [Use the Develop Space](/Guides/query-data/using-the-develop-workspace.html).
+
+## [](#optimize-your-workflow)Optimize your workflow
+
+![After running a baseline query, you can optimize your workflow for better performance.](../../assets/images/get_started_sql_optimize.png)
+
+Firebolt uses a number of optimization strategies to reduce query times. Over small datasets like those specified in this guide, the uplift may not be noticeable. However, these strategies can **dramatically improve** query performance for larger datasets. The following sections discuss how [primary indexes](#primary-indexes) and [aggregating indexes](#aggregating-indexes) to do the following:
+
+- Reduce the amount of data that the query scans.
+- Pre-calculate values that are used repeatedly during computations.
+
+### [](#primary-indexes)Primary Indexes
+
+One of Firebolt’s key optimization strategies is to select a primary index for columns that are used frequently in `WHERE`, `JOIN`, `GROUP_BY`, and clauses used for sorting. In Firebolt, a primary index is a type of **sparse index**. Thus, selecting the best primary index can reduce query run times significantly by reducing the data set that the query searches over. Selecting primary indexes also allows Firebolt to manage updates, deletions and insertions to tables and provide optimal query performance.
+
+If you have a composite primary index, the order that the columns are listed is important. Specify the column that has a large number of unique values, or high cardinality, first, followed by columns with lower cardinality. A sort order with the previous characteristics allows Firebolt to prune, or eliminate irrelevant data, so that it doesn’t have to scan it in query processing. Pruning significantly enhances query performance.
+
+You can create a primary index **only** when you create a table. If you want to change the primary index, you must create a new table. The following example shows how to use [CREATE TABLE](/sql_reference/commands/data-definition/create-fact-dimension-table.html) to create a new `levels` table, define the schema, and set two primary indexes:
+
+```
+CREATE TABLE IF NOT EXISTS levels (
+    "LevelID" INT,
+    "Name" TEXT,
+    "GameID" INT,
+    "LevelType" TEXT,
+    "MaxPoints" INT,
+    "PointsPerLap" DOUBLE,
+    "SceneDetails" TEXT
+)
+PRIMARY INDEX "LevelID", "Name";
+```
+
+In the previous code example, the primary index contains two values. The first value, `LevelID`, is required in order to create a primary index. The second value, `Name`, and any following values are optional. Firebolt will use all listed primary indexes to optimize query scans. If Name has lower cardinality than `LevelID`, then Firebolt can optimize these indexes to eliminate scanning over irrelevant data. For more information about primary indexes and sort order, see [Primary index](/Overview/indexes/primary-index.html).
+
+To read data into the `levels` table, enter the following into a new script tab:
+
+```
+COPY INTO levels
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH TYPE = CSV
+HEADER = TRUE;
+```
+
+### [](#aggregating-indexes)Aggregating Indexes
+
+Another key optimization strategy includes pre-calculating aggregate values for columns that are frequently used in functions that combine data such as `COUNT`, `SUM`, `MAX`, `MIN`, `AVG`, `JOIN`, and `GROUP BY`. Rather than computing aggregate values each time they are used in a calculation, the results are accessed from storage, which helps run queries quickly and saves compute resources.
+
+An aggregating index combines columns into a statistical result. You can calculate an aggregate index on an entire table, or more efficiently, calculate them over a subset of table columns. You can also use your knowledge of which dimensions and aggregate functions are used most often for your use case to predefine what table dimensions and which aggregate functions to use.
+
+Once you create aggregate indexes, Firebolt maintains them automatically for you. If you load new data into your table or alter it, your aggregate indexes are automatically updated. You can also have multiple aggregate indexes for a single table. When you query a table with multiple aggregate indexes, Firebolt will automatically select the best index to use to optimize performance.
+
+From the **tutorial** table that you created in the previous step, assume you want to run a query to look at the AVG(NumberOfLaps), grouped by LevelType. The following example code shows you how to create an aggregating index **levels\_agg\_idx** on the **LevelType** column to pre-calculate the average number of laps for each level.
+
+```
+CREATE AGGREGATING INDEX
+  levels_agg_idx
+ON tutorial (
+  "LevelType" 
+  , AVG("NumberOfLaps")
+  );
+```
+
+After you run the script, the `levels_agg_idx` aggregate index listed in the left navigation pane under **Indexes** in the **tutorial** table. Any queries that run over the tutorial table that use an average of the **NumberOfLaps** column grouped by **LevelType** will now use the `levels_agg_idx` index instead of reading the entire table to calculate it.
+
+For more information, see [Aggregating index](/Overview/indexes/aggregating-index.html).
+
+### [](#warm-data-and-cache-eviction)Warm data and cache eviction
+
+Another key optimization strategy is to read warm data, or data accessed from cache, rather than reading in “cold” data from an Amazon S3 bucket. Querying cold data can be significantly slower than querying warm data, particularly for large datasets that contain millions of rows or more. If you reach about 80% of your available cache, the least recently used data will be moved out of cache into an Amazon S3 bucket.
+
+#### [](#warm-data)Warm data
+
+When data is warm, Firebolt transfers data from remote storage in Amazon (S3) to a local (cache). Data is automatically warmed when you access it during a query, and stored in a solid state drive (SSD) cache. However, when you query data to warm it, you use an engine, and incur [engine consumption](/Overview/engine-consumption.html) costs. Therefore, you should use filters to warm only the data that you need to access frequently in your queries.
+
+The following guidance applies:
+
+- If you need access to all the data in a table, use `CHECKSUM` to warm the entire table as follows:
+  
+  ```
+  SELECT CHECKSUM(*) FROM levels;
+  ```
+- If you only need a few columns that meet a certain criteria, filter them before warming the data as shown in the following code example:
+  
+  ```
+  SELECT CHECKSUM("Name", "MaxPoints") FROM levels WHERE "MaxPoints" BETWEEN 100 AND 250;
+  ```
+- If you have a large dataset, you can divide the data into smaller segments, and execute the queries in parallel, as shown in the following code example:
+  
+  ```
+  SELECT CHECKSUM("Name", "MaxPoints") FROM levels WHERE "MaxPoints" BETWEEN 0 AND 100;
+  SELECT CHECKSUM("Name", "MaxPoints") FROM levels WHERE "MaxPoints" BETWEEN 101 AND 200;
+  SELECT CHECKSUM("Name", "MaxPoints") FROM levels WHERE "MaxPoints" > 200;
+  ```
+
+#### [](#cache-eviction)Cache eviction
+
+When your cache usage exceeds approximately 80% of its capacity, Firebolt automatically evicts the some data from the cache. If you query this data later, Firebolt reloads it into the cache before processing the query. The total available cache size depends on your engine’s size and family. Larger engine sizes provide more cache space, and the storage-optimized family offers more cache than the compute-optimized family. Small and medium sized engines are available for use right away. If you want to use a large or extra-large engine, reach out to [support@firebolt.io](mailto:support@firebolt.io).
+
+You can check the size of your cache using the following example code:
+
+```
+SHOW CACHE;
+```
+
+The previous code example shows your cache usage in GB per total cache available.
+
+When data is loaded into Firebolt, it is stored in units of data storage called tablets. A tablet contains a subset of a table’s rows and columns. If you reach your cache’s 80% capacity, the entire tablet that contains the least recently used data, is evicted.
+
+The following code example shows how to view information about the tablets that are used to store your table including the number of uncompressed and compressed bytes on disk:
+
+```
+SELECT * FROM information_schema.engine_tablets  where table_name = 'levels';
+```
+
+## [](#clean-up)Clean up
+
+![To avoid incurring costs, clean up data and resources when you're finished with your workflow.](../../assets/images/get_started_sql_clean.png)
+
+After you’ve completed the steps in this guide, avoid incurring costs associated with the getting started exercises by doing the following:
+
+- Stop any running engines.
+- Remove data from storage.
+
+### [](#stop-any-running-engines)Stop any running engines
+
+Firebolt shows you the status of your current engine next to the engines icon (![Engine icon](../../assets/images/engine-icon.png)) under your script tab as either **Stopped** or **Running**. To shut down your engine, select your engine from the drop-down list next to the name of the engine, and then select one of the following:
+
+- Stop engine - Allow all of the currently running queries to finish running and then shut down the engine. Selecting this option will allow the engine to run for as long as it takes to complete all queries running on the selected engine.
+- Terminate all queries and stop - Stop the engine and stop running any queries. Selecting this option stops the engine in about 20-30 seconds.
+
+### [](#remove-data-from-storage)Remove data from storage
+
+To remove a table and all of its data, enter [DROP TABLE](/sql_reference/commands/data-definition/drop-table.html) into a script tab, as shown in the following code example:
+
+```
+DROP TABLE levels
+```
+
+To remove a database and all of its associated data, do the following in the Firebolt **Develop Space**:
+
+- Select the database from the left navigation bar.
+- Select the **More options** (![More options icon](../../assets/images/more_options_icon.png)) icon.
+- Select **Delete database**. Deleting your database will permanently remove your database from Firebolt. You cannot undo this action. Select **Delete**.
+
+## [](#export-data)Export data
+
+![The following section shows how to optionally export data after cleaning up.](../../assets/images/get_started_sql_export.png)
+
+If you want to save your data outside of Firebolt, you can use [COPY TO](/sql_reference/commands/data-management/copy-to.html) to export data to an external table. This section shows how to set the minimal AWS permissions and use `COPY TO` to export data to an [AWS S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html). You may have to reach out to your administrator to obtain or change AWS permissions.
+
+### [](#set-permissions-to-write-to-an-aws-bucket)Set permissions to write to an AWS bucket
+
+Firebolt must have the following permissions to write to an AWS S3 bucket:
+
+1. AWS access key credentials. The credentials must be associated with a user with permissions to write objects to the bucket. Specify access key credentials using the following syntax:
+
+```
+    CREDENTIALS = (AWS_ACCESS_KEY_ID = '<aws_access_key_id>' AWS_SECRET_ACCESS_KEY = '<aws_secret_access_key>')
+```
+
+In the previous credentials example, `<aws_access_key_id>` is the AWS access key ID associated with an AWS user or an IAM role. An access key ID has the following form: `AKIAIOSFODNN7EXAMPLE`. The value `<aws_secret_access_key>` is the AWS secret access key. A secret access key has the following form: `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`.
+
+1. An AWS IAM policy statement attached to a user role. Firebolt requires the following minimum permissions in the IAM policy:
+   
+   ```
+    {
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "s3:Get*",
+                "s3:List*",
+                "s3:PutObject",
+                "s3:DeleteObject"
+            ],									
+            "Resource": [
+                "arn:aws:s3:::my_s3_bucket",
+                "arn:aws:s3:::my_s3_bucket/*"
+            ]
+        }
+     ]
+    }
+   ```
+   
+   For more information about AWS access keys and roles, see [Creating Access Key and Secret ID in AWS](/Guides/loading-data/creating-access-keys-aws.html).
+
+### [](#export-to-an-aws-bucket)Export to an AWS bucket
+
+Use [COPY TO](/sql_reference/commands/data-management/copy-to.html) select all the columns from a table and export to an AWS S3 bucket as shown in the following code example:
+
+```
+COPY (SELECT * FROM test_table)
+  TO 's3://my-bucket/path/to/data'
+  CREDENTIALS = 
+  (AWS_ROLE_ARN= 'arn:aws:iam::123456789012:role/my-firebolt-role');
+```
+
+In the previous code example, the role ARN ([Amazon Resource Name](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html)) identifies the AWS IAM role that specifies the access for users or services. An ARN follows the following structure: arn:aws:iam::account-id:role/role-name. Because TYPE is omitted from `COPY TO`, the file or files will be written in the default CSV format. Because `COMPRESSION` is also omitted, the output data is compressed using GZIP (\*.csv.gz) format.
+
+Firebolt assigns a query ID, that has the following example format `16B903C4206098FD`, to the query at runtime. If the size of the compressed output exceeds the default of `16` MB, Firebolt writes multiple GZIP files. In the following example, the size of the output is `40` MB, so Firebolt writes `4` files.
+
+```
+s3://my_bucket/my_fb_queries/
+16B903C4206098FD_0.csv.gz
+16B903C4206098FD_1.csv.gz
+16B903C4206098FD_2.csv.gz
+16B903C4206098FD_3.csv.gz
+```
+
+## [](#next-steps)Next steps
+
+To continue learning about Firebolt’s architecture, capabilities, using Firebolt after your trial period, and setting up your organization, see [Resources beyond getting started](/Guides/getting-started/get-started-next.html).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_airbyte.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_airbyte.md
new file mode 100644
index 0000000..5af6bdc
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_airbyte.md
@@ -0,0 +1,94 @@
+# [](#overview)Overview
+
+![Airbyte](/assets/images/airbyte.png)
+
+Airbyte is an open-source data integration platform that significantly simplifies the ETL (Extract, Transform, Load) process, making it easier for users to manage and migrate their data across various sources. By providing a user-friendly interface and robust functionality, Airbyte enables seamless data movement and transformation, catering to a wide range of data integration needs. One of the key features of Airbyte is its extensive range of connectors, which allow it to integrate with numerous data sources and destinations.
+
+Using Airbyte’s Firebolt connector, users can efficiently and effortlessly load large amounts of data to and from Firebolt. This capability extends to integration with a wide array of data sources, thanks to Airbyte’s extensive library of connectors. Whether your data resides in cloud storage, on-premises databases, SaaS applications, or other data warehouses, Airbyte facilitates smooth and reliable data transfer between these sources and Firebolt.
+
+# [](#quickstart)Quickstart
+
+There are several [ways](https://docs.airbyte.com/deploying-airbyte) to deploy Airbyte. In this tutorial we will the easiest way to start prototyping by using a [Docker Compose](https://docs.docker.com/compose/) deployment locally.
+
+If you already have an airbyte deployment skip to the [configuration section](#step-2-configure-firebolt-connection-via-ui).
+
+#### [](#prerequisites)Prerequisites
+
+1. **Docker**: Ensure you have Docker installed. You can download it from [here](https://www.docker.com/products/docker-desktop).
+2. **Firebolt Account**: You need an active Firebolt account. Sign up [here](https://www.firebolt.io/) if you don’t have one.
+3. **Firebolt Database and Table**: Make sure you have a Firebolt database and table with data ready for querying.
+4. **Firebolt Service Account**: Create a [service account](/Guides/managing-your-organization/service-accounts.html) in Firebolt and note its id and secret.
+
+#### [](#step-1-deploy-airbyte-locally-with-docker)Step 1: Deploy Airbyte Locally with Docker
+
+1. Create a new directory for your Airbyte setup:
+   
+   ```
+   git clone --depth=1 https://github.com/airbytehq/airbyte.git
+   ```
+2. Switch to the Airbyte directory:
+   
+   ```
+   cd airbyte
+   ```
+3. Start Airbyte by running the following command in the terminal:
+   
+   ```
+    ./run-ab-platform.sh
+   ```
+4. Open your browser and navigate to `http://localhost:8000` to access the Airbyte UI.
+5. You will be asked for a username and password. By default the username is `airbyte` and the password is `password`. Before you deploy Airbyte in production make sure to change the password.
+
+#### [](#step-2-configure-firebolt-connection-via-ui)Step 2: Configure Firebolt Connection via UI
+
+1. In the Airbyte UI, click on the **“Connections”** tab and select **“Create your first connection”**.
+2. Click on **“New Destination”** and select **“Firebolt”** as the destination type.
+3. Enter your Firebolt connection details:
+   
+   - Client ID: Your service account id.
+   - Client Secret: Your service account secret.
+   - Database: Your database name.
+   - Account: Your firebolt [account](/Guides/managing-your-organization/managing-accounts.html).
+   - Engine: Firebolt engine which will run the ingestion.
+   - Host (Optional): For non-standard use cases. Should be left blank.
+4. Select replication strategy. SQL is easier to setup but S3 is more performant on production loads. See the [Airbyte doc](https://docs.airbyte.com/integrations/destinations/firebolt) for more information.
+5. Save.
+   
+   ![Connection parameters](../../assets/images/airbyte-connection-parameters.png)
+
+#### [](#step-3-create-a-connection-in-airbyte)Step 3: Create a Connection in Airbyte
+
+1. In the Airbyte UI, click on the **“Connections”** tab and select **“Create your first connection”** (**“New Connection”** if you already have a connection defined).
+2. Choose a source from which you want to extract data. We’ll be using **Faker** to generate some sample data.
+3. Leave fields as is and click **“Set up source”**.
+4. Next in the destination screen select the Firebolt destination you configured earlier.
+5. Select the streams you want to replicate and sync mode (Full refresh or Incremental). To save time select only “products” stream.
+6. Finally specify the frequency of your data repication or manual if you want to trigger the job in UI or via an API call.
+7. Click **“Set up connection”** to start syncing data from your source to Firebolt!
+   
+   ![Streams](/assets/images/airbyte-sample-streams.png)
+
+#### [](#step-4-monitor-and-manage-data-syncs)Step 4: Monitor and Manage Data Syncs
+
+1. Use the Airbyte UI to monitor your data syncs and ensure that data is being transferred accurately and efficiently.
+2. Adjust sync settings and transformations as needed to optimize your ETL process. You can leverage DBT to
+   
+   ![Sync monitoring](/assets/images/airbyte-sync-monitoring.png)
+
+### [](#output-schema)Output schema
+
+The Firebolt Destination connector is a V1 connector, meaning it works with raw data. Refer to Airbyte’s [Destination V2 document](https://docs.airbyte.com/using-airbyte/core-concepts/typing-deduping#what-is-destinations-v2) to learn about the differences. Each stream is written into its own [Fact table](/Overview/indexes/using-indexes.html#firebolt-managed-tables) in Firebolt, containing three columns:
+
+\*`_airbyte_ab_id`: a UUID assigned by Airbyte to each processed event. The column type is TEXT.
+
+- `_airbyte_emitted_at`: a TIMESTAMP indicating when the event was pulled from the source.
+- `_airbyte_data`: a JSON blob representing event data, stored as TEXT, but can be parsed using [JSON functions](/sql_reference/functions-reference/JSON/).
+
+### [](#further-reading)Further Reading
+
+After setting up Airbyte with Firebolt, explore these resources to leverage additional features and enhance your data integration capabilities:
+
+1. Learn how to use [Firebolt Source](https://docs.airbyte.com/integrations/sources/firebolt).
+2. Ensure you’re following [security guidelines](https://docs.airbyte.com/operating-airbyte/security).
+3. Explore other [deployment options](https://docs.airbyte.com/deploying-airbyte).
+4. Configure your [connections](https://docs.airbyte.com/cloud/managing-airbyte-cloud/configuring-connections).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_airflow.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_airflow.md
new file mode 100644
index 0000000..e17c7e3
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_airflow.md
@@ -0,0 +1,413 @@
+# [](#connecting-to-airflow)Connecting to Airflow
+
+[Apache Airflow](https://airflow.apache.org/) is a data orchestration tool that allows you to programmatically create, schedule, and monitor workflows. You can connect a Firebolt database into your data pipeline using the Airflow provider package for Firebolt. For example, you can schedule automatic incremental data ingestion into Firebolt.
+
+This guide explains how to install the [Airflow provider package](https://pypi.org/project/airflow-provider-firebolt/) for Firebolt, set up a connection to Firebolt resources using the Airflow user interface (UI), and create an example Directed Acyclic Graph (DAG) for common Firebolt tasks. The source code for the Airflow provider package for Firebolt is available in the [airflow-provider-firebolt](https://github.com/firebolt-db/airflow-provider-firebolt) repository on GitHub.
+
+## [](#prerequisites)Prerequisites
+
+Make sure that you have:
+
+- A Firebolt account. [Create a new account](/Guides/managing-your-organization/managing-accounts.html#create-a-new-account).
+- A Firebolt database and engine.
+- [Python](https://www.python.org/downloads/) version 3.8 or later.
+- An installation of Airflow. See the [Airflow installation guide](https://airflow.apache.org/docs/apache-airflow/stable/installation/index.html).
+
+## [](#install-the-airflow-provider-package-for-firebolt)Install the Airflow provider package for Firebolt
+
+You need to install the Airflow provider package for Firebolt. This package enables Firebolt as a **Connection type** in the Airflow UI.
+
+1. Install the package.
+   
+   Run the following command to install the package:
+   
+   ```
+   pip install airflow-provider-firebolt
+   ```
+2. Upgrade to the latest version.
+   
+   Run the latest version of the provider package. [Release history](https://pypi.org/project/airflow-provider-firebolt/#history) is available on PyPI.
+   
+   Use the following command to upgrade:
+   
+   ```
+   pip install airflow-provider-firebolt --upgrade
+   ```
+   
+   Restart Airflow after upgrading to apply the new changes.
+3. Install a specific version.
+   
+   If a specific version is required, replace `1.0.0` with the desired version:
+   
+   ```
+   pip install airflow-provider-firebolt==1.0.0
+   ```
+4. Install the provider for AWS Managed Airflow (MWAA).
+   
+   Ensure you are using version 2 of AWS Managed Airflow (MWAA) when working with the Firebolt Airflow provider. Add `airflow-provider-firebolt` to the `requirements.txt` file following the instructions in the [MWAA Documentation.](https://docs.aws.amazon.com/mwaa/latest/userguide/working-dags-dependencies.html)
+
+## [](#connect-airflow-to-firebolt)Connect Airflow to Firebolt
+
+Create a connection object in the Airflow UI to integrate Firebolt with Airflow.
+
+### [](#steps-to-configure-a-connection)Steps to configure a connection
+
+1. Open the Airflow UI and log in.
+2. Select the **Admin** menu.
+3. Choose **Connections**.
+4. Select the **+** button to add a new connection.
+5. Choose Firebolt from the **Connection Type** list
+6. Provide the details in the following table. These connection parameters correspond to built-in Airflow variables.
+   
+   Parameter Description Example value Connection id The name of the connection for the UI. `My_Firebolt_Connection` Description Information about the connection. `Connection to Firebolt database MyDatabase using engine MyFireboltDatabase_general_purpose.` Database The name of the Firebolt database to connect to. `MyFireboltDatabase` Engine The name of the engine to run queries `MyFireboltEngine` Client ID The ID of your service account. `XyZ83JSuhsua82hs` Client Secret The [secret](/Guides/loading-data/creating-access-keys-aws.html) for your service account authentication. `yy7h&993))29&%j` Account The name of your account. `developer` Extra The additional properties that you may need to set (optional). `{"property1": "value1", "property2": "value2"}`
+   
+   Client ID and secret credentials can be obtained by registering a [service account](/Guides/managing-your-organization/service-accounts.html).
+7. Choose **Test** to verify the connection.
+8. Once the test succeeds, select **Save**.
+
+## [](#create-a-dag-for-data-processing-with-firebolt)Create a DAG for data processing with Firebolt
+
+A DAG file in Airflow is a Python script that defines tasks and their execution order for a data workflow. The following example is an example DAG for performing the following tasks:
+
+- Start a Firebolt [engine](/Overview/engine-fundamentals.html).
+- Create an [external table](/Guides/loading-data/working-with-external-tables.html) linked to an Amazon S3 data source.
+- Create a fact table for ingested data. For more information, see [Firebolt-managed tables](/Overview/indexes/using-indexes.html#firebolt-managed-tables).
+- Insert data into the fact table.
+- Stop the Firebolt engine. This task is not required if your engine has `AUTO_STOP` configured
+
+### [](#dag-script-example)DAG script example
+
+The following DAG script creates a DAG named `firebolt_provider_trip_data`. It uses an Airflow connection to Firebolt named `my_firebolt_connection`. For the contents of the SQL scripts that the DAG runs, see the following [SQL script examples](#sql-script-examples). You can run this example with your own database and engine by updating the connector values in Airfow, setting the `FIREBOLT_CONN_ID` to match your connector, and creating the necessary custom variables in Airflow.
+
+```
+import time
+import airflow
+from airflow.models import DAG, Variable
+from firebolt_provider.operators.firebolt \
+    import FireboltOperator, FireboltStartEngineOperator, FireboltStopEngineOperator
+
+# Define function to get Firebolt connection parameters
+def connection_params(conn_opp, field):
+    connector = FireboltOperator(
+        firebolt_conn_id=conn_opp, sql="", task_id="CONNECT")
+    conn_parameters = connector.get_db_hook()._get_conn_params()
+    return getattr(conn_parameters, field)
+
+# Set up the Firebolt connection ID
+firebolt_conn_id = 'firebolt'
+firebolt_engine_name = connection_params(firebolt_conn_id, 'engine_name')
+tmpl_search_path = Variable.get("firebolt_sql_path")
+default_args = {
+    'owner': 'airflow',
+    'start_date': airflow.utils.dates.days_ago(1)
+}
+
+# Function to open query files saved locally.
+def get_query(query_file):
+    return open(query_file, "r").read()
+
+# Define a variable based on an Airflow DAG class.
+# For class parameters, see https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/models/dag/index.html#airflow.models.dag.DAG.
+with DAG('firebolt_provider_startstop_trip_data',
+          default_args=default_args,
+          template_searchpath=tmpl_search_path,
+          schedule_interval=None,
+          catchup=False,
+          tags=["firebolt"]) as dag:
+
+    # Define DAG tasks and task sequence.
+    # Where necessary, read local sql files using the Airflow variable.
+    task_start_engine = FireboltStartEngineOperator(
+        dag=dag,
+        task_id="START_ENGINE",
+        firebolt_conn_id=firebolt_conn_id,
+        engine_name=firebolt_engine_name)
+
+    task_trip_data__external_table = FireboltOperator(
+        dag=dag,
+        task_id="task_trip_data__external_table",
+        sql=get_query(f'{tmpl_search_path}/trip_data__create_external_table.sql'),
+        firebolt_conn_id=firebolt_conn_id
+    )
+
+    task_trip_data__create_table = FireboltOperator(
+        dag=dag,
+        task_id="task_trip_data__create_table",
+        sql=get_query(f'{tmpl_search_path}/trip_data__create_table.sql'),
+        firebolt_conn_id=firebolt_conn_id
+    )
+    task_trip_data__create_table.post_execute = lambda **x: time.sleep(10)
+
+    task_trip_data__process_data = FireboltOperator(
+        dag=dag,
+        task_id="task_trip_data__process_data",
+        sql=get_query(f'{tmpl_search_path}/trip_data__process.sql'),
+        firebolt_conn_id=firebolt_conn_id
+    )
+
+    task_stop_engine = FireboltStopEngineOperator(
+        dag=dag,
+        task_id="STOP_ENGINE",
+        firebolt_conn_id=firebolt_conn_id,
+        engine_name=firebolt_engine_name)
+
+    (task_start_engine >> task_trip_data__external_table >>
+     task_trip_data__create_table >> task_trip_data__process_data >> task_stop_engine)
+```
+
+This DAG showcases various Firebolt tasks as an example and is not intended to represent a typical real-world workflow or pipeline.
+
+### [](#define-airflow-variables)Define Airflow variables
+
+Airflow variables store-key value pairs that DAGs can use during execution. You can create and manage variables through the Airflow user interface (UI) or JSON documents. For detailed instructions, check out Airflow’s [Variables](https://airflow.apache.org/docs/apache-airflow/stable/concepts/variables.html) and [Managing Variables](https://airflow.apache.org/docs/apache-airflow/stable/howto/variable.html) documentation pages.
+
+**Example variable for SQL files**  
+The DAG example uses the custom variable `firebolt_sql_path` to define the directory within your Airflow home directory where SQL files are stored. The DAG reads these files to execute tasks in Firebolt.
+
+- **Key**: `firebolt_sql_path`
+- **Value**: Path to the directory containing SQL scripts. For example, `~/airflow/sql_store`.
+
+**Using the variable in the DAG**  
+A python function in the DAG reads the SQL scripts stored in the directory defined by `firebolt_sql_path`. This allows the DAG to dynamically execute the SQL files as tasks in Firebolt.
+
+The following example demonstrates how the variable is accessed in the DAG script:
+
+```
+tmpl_search_path = Variable.get("firebolt_sql_path")
+
+def get_query(query_file):
+    with open(query_file, "r") as file:
+        return file.read()
+```
+
+### [](#sql-script-examples)SQL script examples
+
+Save the following SQL scripts to your `tmpl_search_path`.
+
+#### [](#trip_data__create_external_tablesql)trip\_data\_\_create\_external\_table.sql
+
+This example creates the `ex_trip_data` fact table to connect to a public Amazon S3 data store.
+
+```
+CREATE EXTERNAL TABLE IF NOT EXISTS ex_trip_data(
+   vendorid INTEGER,
+   lpep_pickup_datetime TIMESTAMP,
+   lpep_dropoff_datetime TIMESTAMP,
+   passenger_count INTEGER,
+   trip_distance REAL,
+   ratecodeid INTEGER,
+   store_and_fwd_flag TEXT,
+   pu_location_id INTEGER,
+   do_location_id INTEGER,
+   payment_type INTEGER,
+   fare_amount REAL,
+   extra REAL,
+   mta_tax REAL,
+   tip_amount REAL,
+   tolls_amount REAL,
+   improvement_surcharge REAL,
+   total_amount REAL,
+   congestion_surcharge REAL
+)
+url = 's3://firebolt-publishing-public/samples/taxi/'
+object_pattern = '*yellow*2020*.csv'
+type = (CSV SKIP_HEADER_ROWS = true);
+```
+
+#### [](#trip_data__create_tablesql)trip\_data\_\_create\_table.sql
+
+This example creates the `my_taxi_trip_data` fact table, to receive ingested data.
+
+```
+DROP TABLE IF EXISTS my_taxi_trip_data;
+CREATE FACT TABLE IF NOT EXISTS my_taxi_trip_data(
+   vendorid INTEGER,
+   lpep_pickup_datetime TIMESTAMP,
+   lpep_dropoff_datetime TIMESTAMP,
+   passenger_count INTEGER,
+   trip_distance REAL,
+   ratecodeid INTEGER,
+   store_and_fwd_flag TEXT,
+   pu_location_id INTEGER,
+   do_location_id INTEGER,
+   payment_type INTEGER,
+   fare_amount REAL,
+   extra REAL,
+   mta_tax REAL,
+   tip_amount REAL,
+   tolls_amount REAL,
+   improvement_surcharge REAL,
+   total_amount REAL,
+   congestion_surcharge REAL,
+   SOURCE_FILE_NAME TEXT,
+   SOURCE_FILE_TIMESTAMP TIMESTAMP
+) PRIMARY INDEX vendorid;
+```
+
+#### [](#trip_data__processsql)trip\_data\_\_process.sql
+
+An `INSERT INTO` operation ingests data into the `my_taxi_trip_data` fact table using the `ex_trip_data` external table. This example uses the external table metadata column, `$source_file_timestamp`, to retrieve records exclusively from the latest file.
+
+```
+INSERT INTO my_taxi_trip_data
+SELECT
+   vendorid,
+   lpep_pickup_datetime,
+   lpep_dropoff_datetime,
+   passenger_count,
+   trip_distance,
+   ratecodeid,
+   store_and_fwd_flag,
+   pu_location_id,
+   do_location_id,
+   payment_type,
+   fare_amount,
+   extra,
+   mta_tax,
+   tip_amount,
+   tolls_amount,
+   improvement_surcharge,
+   total_amount,
+   congestion_surcharge,
+   $source_file_name,
+   $source_file_timestamp
+FROM ex_trip_data
+WHERE coalesce($source_file_timestamp > (SELECT MAX(source_file_timestamp) FROM my_taxi_trip_data), true);
+```
+
+## [](#example-working-with-query-results)Example: Working with query results
+
+The `FireboltOperator` is designed to execute SQL queries but does not return query results. To retrieve query results, use the `FireboltHook` class. The following example demonstrates how to use `FireboltHook` to execute a query and log the row count in the `my_taxi_trip_data` table.
+
+### [](#python-code-example-retrieiving-query-results)Python code example: Retrieiving query results
+
+```
+import logging
+
+import airflow
+from airflow import DAG
+from airflow.operators.python import PythonOperator
+from firebolt_provider.hooks.firebolt import FireboltHook
+from airflow.providers.common.sql.hooks.sql import fetch_one_handler
+
+# Set up the Firebolt connection ID
+firebolt_conn_id = 'firebolt'
+default_args = {
+    'owner': 'airflow',
+    'start_date': airflow.utils.dates.days_ago(1)
+}
+
+
+# Function to notify the team about the data
+def notify(message: str):
+    logging.info(message)
+
+
+# Function to fetch data from Firebolt and notify the team
+def fetch_firebolt_data():
+    hook = FireboltHook(firebolt_conn_id=firebolt_conn_id)
+    results = hook.run(
+        "SELECT count(*) FROM my_taxi_trip_data",
+        handler=fetch_one_handler
+    )
+    count = results[0]
+    notify("Amount of data in Firebolt: " + str(count))
+
+
+with DAG(
+    'return_result_dag',
+    default_args=default_args,
+    schedule_interval=None,  # Run manually
+    catchup=False
+) as dag:
+    # Define a Python operator to fetch data from Firebolt and notify the team
+    monitor_firebolt_data = PythonOperator(
+        task_id='monitor_firebolt_data',
+        python_callable=fetch_firebolt_data
+    )
+
+    monitor_firebolt_data
+```
+
+## [](#example-controlling-query-execution-timeout)Example: Controlling query execution timeout
+
+The Firebolt provider includes parameters to control query execution time and behavior when a timeout occurs:
+
+- `query_timeout`: Sets the maximum duration (in seconds) that a query can run
+- `fail_on_query_timeout` - If `True`, a timeout raises a `QueryTimeoutError`. If `False`, the task terminates quietly, and the task proceeds without raising an error.
+
+### [](#python-code-example-using-timeout-settings)Python code example: Using timeout settings
+
+In this example, the `FireboltOperator` task stops execution after one second and proceeds without error. The `PythonOperator` task fetches data from Firebolt with a timeout of 0.5 seconds and raises an error if the query times out.
+
+```
+import airflow
+from airflow.models import DAG, Variable
+from airflow.operators.python import PythonOperator
+from firebolt_provider.hooks.firebolt import FireboltHook
+from airflow.providers.common.sql.hooks.sql import fetch_one_handler
+from firebolt_provider.operators.firebolt import FireboltOperator
+
+# Set up the Firebolt connection ID
+firebolt_conn_id = 'firebolt'
+default_args = {
+    'owner': 'airflow',
+    'start_date': airflow.utils.dates.days_ago(1)
+}
+tmpl_search_path = Variable.get("firebolt_sql_path")
+
+
+def get_query(query_file):
+    return open(query_file, "r").read()
+
+# Function to fetch data with a timeout
+def fetch_with_timeout():
+    hook = FireboltHook(
+        firebolt_conn_id=firebolt_conn_id,
+        query_timeout=0.5, 
+        fail_on_query_timeout=True, 
+    )
+    results = hook.run(
+        "SELECT count(*) FROM my_taxi_trip_data",
+        handler=fetch_one_handler,
+    )
+    print(f"Results: {results}")
+
+# Define the DAG
+with DAG(
+    'timeout_dag',
+    default_args=default_args,
+    schedule_interval=None,  # Run manually
+    catchup=False
+) as dag:
+
+    # Firebolt operator with a timeout
+
+    firebolt_operator_with_timeout = FireboltOperator(
+        dag=dag,
+        task_id="insert_with_timeout",
+        sql=get_query(f'{tmpl_search_path}/trip_data__process.sql'),
+        firebolt_conn_id=firebolt_conn_id,
+        query_timeout=1,
+        # Task will not fail if query times out, and will proceed to the next task
+        fail_on_query_timeout=False,
+    )
+
+    # Python operator to fetch data with a timeout
+    operator_with_hook_timeout = PythonOperator(
+        dag=dag,
+        task_id='select_with_hook_timeout',
+        python_callable=fetch_with_timeout,
+    )
+
+    firebolt_operator_with_timeout >> operator_with_hook_timeout
+```
+
+## [](#additional-resources)Additional resources
+
+For more information about connecting to Airflow, refer to the following resources:
+
+- [Managing Connections in Airflow](https://airflow.apache.org/docs/apache-airflow/stable/howto/connection.html)
+- [Firebolt Airflow provider on Pypi](https://pypi.org/project/airflow-provider-firebolt/)
+- [DAGs](https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/dags.html)
+- [airflow.models.dag](https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/models/dag/index.html#module-airflow.models.dag)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_apache_superset.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_apache_superset.md
new file mode 100644
index 0000000..1866423
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_apache_superset.md
@@ -0,0 +1,105 @@
+# [](#apache-superset)Apache Superset
+
+[Apache Superset](https://superset.apache.org) is an open-source data exploration and visualization platform that empowers users to create interactive, shareable dashboards and charts for analyzing and presenting data. It supports a wide range of data sources and provides an intuitive, web-based interface for data exploration, slicing, and dicing, with features like dynamic filtering, pivot tables, and drag-and-drop functionality. Superset also offers a rich set of visualization options and can be extended through custom plugins, making it a versatile tool for data analysts and business users to gain insights from their data and collaborate effectively.
+
+With its exceptional speed and scalability, Firebolt allows users to handle vast amounts of data with minimal query latency, ensuring that Superset dashboards and visualizations load quickly, even when dealing with massive datasets. This integration between Firebolt and Superset creates a powerful combination for data professionals, offering them a streamlined and efficient workflow for extracting maximum value from their data.
+
+Firebolt is also supported in [Preset](/Guides/integrations/connecting-to-preset.html), a fully managed cloud Superset solution.
+
+# [](#prerequisites)Prerequisites
+
+Superset can be installed in several ways, including using a pre-built [Docker container](https://superset.apache.org/docs/installation/installing-superset-using-docker-compose), building it from [source](https://superset.apache.org/docs/installation/installing-superset-from-scratch) or deploying via [Kubernetes Helm chart](https://superset.apache.org/docs/installation/running-on-kubernetes).
+
+The easiest way to get started is to run Superset via Docker.
+
+You will need:
+
+- [Docker](https://www.docker.com/) and [Docker Compose](https://docs.docker.com/compose/).
+- [VirtualBox](https://www.virtualbox.org/) (Windows only).
+- [Git](https://git-scm.com/).
+
+# [](#quickstart)Quickstart
+
+Follow this guide to setup Superset and get your first chart ready.
+
+### [](#setup-superset)Setup Superset
+
+1. Clone Superset’s GitHub [repository](https://github.com/apache/superset)
+   
+   ```
+   git clone https://github.com/apache/superset.git
+   ```
+2. Change directory to the root of the newly cloned repository and add the Firebolt driver
+   
+   ```
+   cd superset
+   touch ./docker/requirements-local.txt
+   echo "firebolt-sqlalchemy" >> ./docker/requirements-local.txt
+   ```
+3. Run Superset via Docker Compose
+   
+   ```
+   docker compose -f docker-compose-non-dev.yml up
+   ```
+4. (Optional) Verify firebolt driver is present in Superset container
+   
+   ```
+   docker exec -it <container_name> bash
+   pip freeze | grep firebolt
+   ```
+   
+   You should see `firebolt-sqlalchemy` in the output.
+
+Once your Superset is booted up you should be able to access it in http://localhost:8088/
+
+> **Note:** For more installation details, refer to [Adding New Database Drivers in Docker](https://superset.apache.org/docs/databases/docker-add-drivers) in the Superset documentation.
+
+### [](#setup-firebolt-connection)Setup Firebolt connection
+
+After the initial setup in Superset User Inteface head to the `Settings -> Database connections` in the top right corner.
+
+![Database Connections](../../assets/images/superset-settings.png)
+
+On the next screen, press the `+ Database` button and select Firebolt from the dropdown. If you don’t see Firebolt in the list, please refer to the [Setup Superset](#setup-superset) section for instructions on how to install the Firebolt driver and verify that the driver is present.
+
+![Connect database](../../assets/images/superset-connect-a-database.png)
+
+The connection expects a SQLAlchemy connection string of the form:
+
+```
+firebolt://{client_id}:{client_secret}@{database}/{engine_name}?account_name={account_name}
+```
+
+To authenticate, use a service account ID and secret. A service account is identified by a `client_id` and a `client_secret`. Learn how to generate an ID and secret [here](/Guides/managing-your-organization/service-accounts.html).
+
+Account name must be provided, you can learn about accounts in [Manage accounts](/Guides/managing-your-organization/managing-accounts.html) section.
+
+![Credentials](../../assets/images/superset-firebolt-uri.png)
+
+Click the Test Connection button to confirm things work end to end. If the connection looks good, save the configuration by clicking the Connect button in the bottom right corner of the modal window. Now you’re ready to start using Superset!
+
+### [](#build-your-first-chart)Build your first chart
+
+> **Note:** This section assumes you have followed Firebolt [tutorial](/Guides/getting-started/) and loaded a sample data set into your database.
+
+Now that you’ve configured Firebolt as a data source, you can select specific tables (Datasets) that you want to see in Superset.
+
+Go to Data -&gt; Datasets and select `+ Dataset`. There you can select your sample table by specifying Firebolt as your Database, your schema and the table name you chose.
+
+![Dataset](/assets/images/superset-dataset-config.png)
+
+Press “Create Dataset and Create Chart”. On the next screen you can select your desired chart type. For this tutorial we will go with a simple Bar Chart.
+
+![Chart type](/assets/images/superset-char-type-select.png)
+
+In the next screen you can drag and drop your table columns into Metrics and Dimensions, specify filters or sorting orders. We will plot max play time per level grouping it by level type and sorting the x-axis in ascending order.
+
+![Chart](/assets/images/superset-sample-chart.png)
+
+Your first chart is ready! You can now save it, add more data to it or change its type. You can also start building a dashboard with different charts telling a story. Learn more about this functionality and more by following the links below.
+
+# [](#further-reading)Further reading
+
+- [Creating your first Dashboard](https://superset.apache.org/docs/creating-charts-dashboards/creating-your-first-dashboard).
+- [Exploring data](https://superset.apache.org/docs/creating-charts-dashboards/exploring-data).
+- [Preset](https://preset.io/) - managed Superset.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_paradime.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_paradime.md
new file mode 100644
index 0000000..2162cde
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_paradime.md
@@ -0,0 +1,82 @@
+# [](#integrate-paradime-with-firebolt)Integrate Paradime with Firebolt
+
+![Paradime logo](../../assets/images/paradime_logo.png)
+
+[Paradime](https://www.paradime.io/) is a unified platform for data science and analytics that streamlines workflows for data teams. It offers a collaborative workspace where data scientists and analysts can explore, analyze, and visualize data across multiple tools and environments. Paradime integrates with tools including Jupyter notebooks, SQL editors, and Tableau. You can use the Paradime connector to link the Paradime platform directly to Firebolt’s cloud data warehouse. This connection allows you to run SQL queries, visualize results, and collaborate with team members all within the Paradime workspace.
+
+This guide shows you how to connect Paradime to Firebolt using the Paradime user interface (UI). You must have a Firebolt account, a Firebolt service account, access to a Firebolt database, and an account with Paradime. These instructions build on the steps in Paradime’s [Getting Started with your Paradime Workspace](https://docs.paradime.io/app-help/guides/paradime-101/getting-started-with-your-paradime-workspace) guide, providing Firebolt-specific configuration details.
+
+Topics:
+
+- [Prerequisites](#prerequisites)
+- [Create a Paradime workspace](#create-a-paradime-workspace).
+- (Optional) [Create a schedule](#create-a-schedule-optional).
+
+## [](#prerequisites)Prerequisites
+
+Before you can connect Paradime to Firebolt, you must have the following:
+
+1. **Firebolt Account**: Ensure that you have access to an active Firebolt account. If you don’t have access, you can [sign up for an account](https://www.firebolt.io/sign-up). For more information about how to register with Firebolt, see [Get started with Firebolt](/Guides/getting-started/).
+2. **Service Account**: You must have access to an active Firebolt [service account](/Guides/managing-your-organization/service-accounts.html), which facilitates programmatic access to Firebolt.
+3. **Firebolt Database**: You must have access to a Firebolt database. If you don’t have access, you can [create a database](/Guides/getting-started/get-started-sql.html#create-a-database).
+4. **Paradime Account**: You must have access to an active Paradime account. If you don’t have access, you can [sign up](https://app.paradime.io) for one.
+
+## [](#create-a-paradime-workspace)Create a Paradime workspace
+
+Create a Paradime workspace to connect to Firebolt as follows:
+
+01. In the Paradime UI, navigate to your account profile in the upper-right corner of the page.
+02. Select **Profile Settings**.
+03. In the **Workspaces** window, select the **New Workspace** button.
+04. Enter a descriptive name for your workspace in the text box under **Name**.
+05. Select **Create Workspace**.
+06. Select **Continue**.
+07. Select the most recent dbt-core version from the drop-down list.
+08. Select **Continue**.
+09. Select a dbt repository. You can either use an existing data build tool ([dbt](https://www.getdbt.com/blog/what-exactly-is-dbt)) repository or fork Firebolt’s sample [Jaffle Shop](https://github.com/firebolt-db/jaffle_shop_firebolt) repository from GitHub. Paradime supports the following providers: Azure DevOps, Bitbucket, GitHub, and GitLab.
+10. Select **Next**.
+11. Enter the SSH URI for your repository in the text box under **Repository URI**. Copy the key that appears under the **Deploy Key**.
+12. Add the new deploy key to your dbt repository and allow write access. The following are resources for providers supported by Paradime:
+    
+    - [Add the deploy key](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys#set-up-deploy-keys) in **github**.
+    - [Add a deployment key](https://www.atlassian.com/blog/bitbucket/deployment-keys) in **Bitbucket**.
+    - Use [deploy keys](https://docs.gitlab.com/ee/user/project/deploy_keys/) in **gitlab**.
+    - [Use SSH key authentication](https://learn.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops) to connect with **Azure DevOps**.
+13. Select **Continue**.
+14. If your repository connected successfully, select **Continue**.
+15. Select **Firebolt** from the choices under **Warehouse connection**.
+16. Under **Connection Settings**, enter the following:
+    
+    1. **Profile Name** – The name of a [connection profile](https://docs.getdbt.com/docs/core/connect-data-platform/connection-profiles) that is defined in `dbt_project.yaml` by a workspace administrator, and contains configurations including credentials to connect to a data warehouse. For more information, see Paradime’s [Setting up your profile](https://docs.getdbt.com/docs/core/connect-data-platform/connection-profiles#setting-up-your-profile) guide.
+    2. **Target** – Specify the [target variable](https://docs.getdbt.com/reference/dbt-jinja-functions/target) that contains information about your data warehouse connection including its name, schema, and type.
+    3. **Host Name** – Enter `api.app.firebolt.io`.
+17. Under **Development Credentials**, enter the following:
+    
+    1. **Client Id** – Enter your Firebolt [service account ID](/Guides/managing-your-organization/service-accounts.html#get-a-service-account-id). Do not enter your Firebolt login email.
+    2. **Client Secret** – Enter your Firebolt [service account secret](/Guides/managing-your-organization/service-accounts.html#generate-a-secret). Do not enter your Firebolt password.
+    3. **Account Name** – Enter your Firebolt [account name](/Guides/managing-your-organization/managing-accounts.html).
+    4. **Engine Name** – Enter the name of the engine where you want to run your queries.
+    5. **Database Name** – Specify the Firebolt database name.
+    6. Select **Test Connection** to connect to Firebolt and authenticate.
+    7. Select **Next**.
+
+For more information about the previous connection settings, see Paradime’s documentation to [add a development connection](https://docs.paradime.io/app-help/documentation/settings/connections/development-environment/firebolt).
+
+## [](#create-a-schedule-optional)Create a schedule (Optional)
+
+Paradime offers a scheduling feature using a [Bolt user interface](https://docs.paradime.io/app-help/documentation/bolt) to automatically run dbt commands on a specified interval or event. You can use Bolt to run a dbt job in a production environment, in a test environment prior to merging changes to production, or in an environment that runs jobs only on changed models.
+
+To create a new schedule:
+
+1. Login to your [Paradime account](https://app.paradime.io/?target=main-app).
+2. Select **Bolt** from the left navigation bar.
+3. Select **+ New Schedule**.
+4. Select a pre-configured template from a list of popular Bolt templates or create a new schedule using a blank template. For information about how to configure settings in a Paradime schedule, see [Schedule Fields](https://docs.paradime.io/app-help/guides/paradime-101/running-dbt-in-production-with-bolt/creating-bolt-schedules#ui-based-schedule-fields).
+5. Select **Publish**.
+6. To view the new schedule, select **Bolt** from the left navigation pane.
+
+# [](#additional-resources)Additional resources
+
+- Learn about the [Paradime integrated development Environment](https://docs.paradime.io/app-help/guides/paradime-101/getting-started-with-the-paradime-ide).
+- Learn to use the [Bolt scheduler](https://docs.paradime.io/app-help/bolt-scheduler/running-dbt-tm-in-production/creating-bolt-schedules) to run your dbt jobs.
+- Learn how to [manage your Bolt schedule](https://docs.paradime.io/app-help/documentation/bolt/managing-schedules).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_preset.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_preset.md
new file mode 100644
index 0000000..a36abbe
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_to_preset.md
@@ -0,0 +1,66 @@
+# [](#preset)Preset
+
+[Preset](https://preset.io/) is a cloud-hosted data exploration and visualization platform built on top of the popular open-source project, [Apache Superset](https://superset.apache.org/). This fully managed service makes it easy to run Superset at scale with enterprise-ready security, reliability, and governance.
+
+Boasting exceptional speed and scalability, Firebolt enables users to adeptly manage substantial data volumes with minimal query latency. The integration with Preset establishes a strong partnership for data professionals, presenting them with a streamlined and efficient workflow. This collaboration ensures prompt loading of Preset dashboards and visualizations, even when confronted with extensive datasets, thereby facilitating the extraction of maximum value from their data.
+
+# [](#prerequisites)Prerequisites
+
+Preset is a managed service so most of the deployment requirements are handled by them.
+
+You will only need:
+
+- To [register](https://manage.app.preset.io/starter-registration/) a Preset account.
+- To have a Firebolt account and service account [credentials](/Guides/managing-your-organization/service-accounts.html).
+- [Load data](/Guides/loading-data/loading-data.html) you want to visualise.
+
+Make sure that your [service account’s network policy](https://docs.firebolt.io/Guides/managing-your-organization/service-accounts.html#edit-your-service-account-using-the-ui) allows connections from [Preset IPs](https://docs.preset.io/docs/connecting-your-data).
+
+# [](#quickstart)Quickstart
+
+### [](#create-a-workspace)Create a workspace
+
+A workspace is an organizational unit, accessible by team members, that is created for a specific purpose. You can read Preset’s [guidance](https://docs.preset.io/docs/about-workspaces) on workspaces to learn more.
+
+1. To Create a Workspace, navigate to the empty card and select + Workspace.
+   
+   ![Create Workspace](../../assets/images/preset-create-workspace-click.png)
+2. Define Workspace name and settings
+   
+   ![Add new Workspace](../../assets/images/preset-add-new-workspace.png)
+3. Save the workspace and enter it by clicking the card.
+
+### [](#setup-firebolt-connection)Setup Firebolt connection
+
+After the initial setup in Preset User Inteface head to the `Settings -> Database connections` in the top right corner.
+
+![Database Connections](../../assets/images/preset-settings.png)
+
+On the next screen, press the `+ Database` button and select Firebolt from the dropdown.
+
+![Connect database](../../assets/images/superset-connect-a-database.png)
+
+The connection expects a SQLAlchemy connection string of the form:
+
+```
+firebolt://{client_id}:{client_secret}@{database}/{engine_name}?account_name={account_name}
+```
+
+To authenticate, use a service account ID and secret. A service account is identified by a `client_id` and a `client_secret`. Learn how to generate an ID and secret [here](/Guides/managing-your-organization/service-accounts.html).
+
+Account name must be provided, you can learn about accounts in [Manage accounts](/Guides/managing-your-organization/managing-accounts.html) section.
+
+![Credentials](../../assets/images/superset-firebolt-uri.png)
+
+Click the Test Connection button to confirm things work end to end. If the connection looks good, save the configuration by clicking the Connect button in the bottom right corner of the modal window. Now you’re ready to start using Preset!
+
+### [](#build-your-first-chart)Build your first chart
+
+To build a chart you can follow our guide in the [Superset section](/Guides/integrations/connecting-to-apache-superset.html#build-your-first-chart), as the Preset works identically.
+
+# [](#further-reading)Further reading
+
+- [Creating a chart](https://docs.preset.io/docs/creating-a-chart) walkthrough.
+- [Creating a Dashboard](https://docs.preset.io/docs/creating-a-dashboard).
+- [Collaboration features of Preset](https://docs.preset.io/docs/sharing-and-collaboration).
+- [Storytelling in charts](https://docs.preset.io/docs/storytelling-with-charts-and-dashboards-mini-guide).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_with_dbt.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_with_dbt.md
new file mode 100644
index 0000000..422e2a0
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_connecting_with_dbt.md
@@ -0,0 +1,213 @@
+# [](#overview)Overview
+
+![DBT](/assets/images/dbt-logo.png)
+
+[DBT](https://www.getdbt.com), or Data Build Tool, is a framework designed for managing and executing data transformations within modern data warehousing architectures. It facilitates the development and deployment of SQL-based transformations in a version-controlled environment, enabling collaboration and ensuring reproducibility of data pipelines. DBT streamlines the process of transforming raw data into analytics-ready datasets, accelerating the delivery of insights.
+
+The Firebolt adapter for dbt brings together dbt’s state-of-the-art development tools and Firebolt’s next-generation analytics performance. On top of dbt’s core features, the adapter offers native support for all of Firebolt’s index types and has been specifically enhanced to support ingestion from S3 using Firebolt’s external tables mechanics.
+
+# [](#prerequisites)Prerequisites
+
+There are two ways to deploy DBT: self-hosted [DBT Core](https://docs.getdbt.com/docs/introduction#dbt-core) and managed [DBT Cloud](https://docs.getdbt.com/docs/cloud/about-cloud/dbt-cloud-features).
+
+This guide shows how to set up a local installation of [DBT Core](https://docs.getdbt.com/docs/introduction#dbt-core). This guide uses Python’s `pip` package manager, but you can use the following ways to install DBT: [Homebrew](https://docs.getdbt.com/docs/core/homebrew-install), [Docker](https://docs.getdbt.com/docs/core/docker-install), and from [source](https://docs.getdbt.com/docs/core/source-install).
+
+You will need the following:
+
+- A GitHub account.
+- Python 3.8+.
+
+# [](#quickstart)Quickstart
+
+This guide shows you how to set up DBT with Firebolt and run your first DBT [model](https://docs.getdbt.com/docs/build/models).
+
+### [](#setup-dbt-core)Setup DBT Core
+
+1. Create a new Python [virtual environment](https://docs.python.org/3/library/venv.html), as shown in the following script example:
+   
+   ```
+    python3 -m venv dbt-env
+   ```
+2. Activate your `venv`, as shown in the following script example:
+   
+   ```
+    source dbt-env/bin/activate
+   ```
+3. Install Firebolt’s [adapter](https://github.com/firebolt-db/dbt-firebolt) for DBT, as shown in the following script example:
+   
+   ```
+    python -m pip install dbt-firebolt
+   ```
+4. (Optional) Check that both dbt packages are installed:
+   
+   ```
+    python -m pip list | grep dbt
+   ```
+   
+   This command should return `dbt-core` and `dbt-firebolt` and their respective versions.
+
+### [](#setup-connection-to-firebolt)Setup connection to Firebolt
+
+DBT uses a `profiles.yml` file to store the connection information. This file generally lives outside of your dbt project to avoid checking in sensitive information in to version control.
+
+The usual place to create this file on Mac and Linux is `~/.dbt/profiles.yml`.
+
+1. Open `~/.dbt/profiles.yml` with your preferred text editor.
+2. Paste the following sample configuration:
+   
+   ```
+    jaffle-shop:
+    target: dev
+    outputs:
+        dev:
+          type: firebolt
+          client_id: "<client-id>"
+          client_secret: "<client-secret>"
+          database: "<database-name>"
+          engine_name: "<engine-name>"
+          account_name: "<account-name>"
+          schema: "<table-prefix>"
+   ```
+3. Replace the placeholders with your account’s information.
+   
+   `<client-id>` and `<client-secret>` are key and secret of your service account. If you don’t have one, follow the steps in the [Manage service accounts](/Guides/managing-your-organization/service-accounts.html) page to learn how to set one up.
+   
+   `<database-name>` and `<engine-name>` are the Firebolt’s database and engine that you want your queries to run.
+   
+   `<account-name>` is a Firebolt account that you’re connected to. Learn more [here](/Guides/managing-your-organization/managing-accounts.html).
+   
+   `<table-prefix>` is a prefix prepended to your table names. Since Firebolt does not support custom schemas, this prefix serves as a [workaround](https://docs.getdbt.com/docs/core/connect-data-platform/firebolt-setup#supporting-concurrent-development) to prevent table name conflicts during concurrent development.
+
+### [](#setup-jaffle-shop-a-sample-dbt-project)Setup Jaffle Shop, a sample dbt project
+
+`jaffle_shop` is a fictional ecommerce store. This dbt project transforms raw data from an app database into a customers and orders model ready for analytics. [This version](https://github.com/firebolt-db/jaffle_shop_firebolt) is designed to showcase Firebolt’s integration with DBT.
+
+1. Clone `jaffle-shop-firebolt` repository and change to the newly created directory, as follows:
+   
+   ```
+    git clone https://github.com/firebolt-db/jaffle_shop_firebolt.git
+    cd jaffle_shop_firebolt
+   ```
+2. Ensure your profile is setup correctly:
+   
+   ```
+    dbt debug
+   ```
+   
+   If you’re seeing an error here, check that your `profiles.yml` is [set up correctly](#setup-connection-to-firebolt), is in the right directory on your system, and that the [engine](/Guides/operate-engines/operate-engines.html). is running. Also check that you’re still in `dbt-env` virtual Python environment that we’ve [setup earlier](#setup-dbt-core) and that both packages are present.
+3. Install dependent packages:
+   
+   ```
+    dbt deps
+   ```
+4. Run the external table model. If your database is not in `us-east-1` AWS region then refer to the [Readme](https://github.com/firebolt-db/jaffle_shop_firebolt) on how to copy the files.
+   
+   ```
+    dbt run-operation stage_external_sources
+   ```
+5. Load sample CSV in your database:
+   
+   ```
+    dbt seed
+   ```
+6. Run the models:
+   
+   ```
+    dbt run
+   ```
+
+You should now see the `customers` and `orders` tables in your database, created using dbt models. From here you can explore more of DBT’s capabilities, including incremental models, documentation generation, and more, by following the official guides in the section below.
+
+# [](#limitations)Limitations
+
+Not every feature of DBT is supported in Firebolt. You can find an up-to-date list of features in the [adapter documentation](https://github.com/firebolt-db/dbt-firebolt?tab=readme-ov-file#feature-support).
+
+# [](#external-table-loading-strategy)External table loading strategy
+
+In the previous Jaffle Shop example we used a public Amazon S3 bucket to load data. If your bucket contains sensitive data, you will want to restrict access. Follow our [guide](/Guides/loading-data/creating-access-keys-aws.html) to set up AWS authentication using an ID and secret key.
+
+In your `dbt_project.yml`, you can specify the credentials for your external table in fields `aws_key_id` and `aws_secret_key`, as shown in the following code example:
+
+```
+sources:
+  - name: firebolt_external
+    schema: ""
+    loader: S3
+
+    tables:
+      - name: <table-name>
+        external:
+          url: 's3://<bucket_name>/'
+          object_pattern: '<regex>'
+          type: '<type>'
+          credentials:
+            aws_key_id: <aws-id>
+            aws_secret_key: <aws-secret-key>
+          object_pattern: '<regex>'
+          compression: '<compression-type>'
+          partitions:
+            - name: <partition-name>
+              data_type: <partition-type>
+              regex: '<partition-definition-regex>'
+          columns:
+            - name: <column-name>
+              data_type: <type>
+```
+
+To use external tables, you must define a table as external in your `dbt_project.yml` file. Every external table must contain the fields: `url`, `type`, and `object_pattern`. The Firebolt external table [specification](/sql_reference/commands/data-definition/create-external-table.html) requires fewer fields than those specified in the dbt documentation.
+
+# [](#copy-loading-strategy)“Copy” loading strategy
+
+You can also use [COPY FROM](/sql_reference/commands/data-management/copy-from.html) to load data from Amazon S3 into Firebolt. It has a simple syntax and doesn’t require an exact match with your source data. `COPY_FROM` does not create an intermediate table and writes your data straight into Firebolt so you can start working with it right away.
+
+The copy syntax in dbt closely adheres to the [syntax](/sql_reference/commands/data-management/copy-from.html#syntax) in Firebolt’s `COPY_FROM`.
+
+To use `COPY FROM` instead of creating an external table, set `strategy: copy` in your external source definition. For backwards compatibility, if no strategy is specified, the external table strategy is used by default.
+
+```
+
+sources:
+  - name: s3
+    tables:
+      - name: <table-name>
+        external:
+          strategy: copy
+          url: 's3://<bucket_name>/'
+          credentials:
+            aws_key_id: <aws-id>
+            aws_secret_key: <aws-secret-key>
+          options:
+            object_pattern: '<regex>'
+            type: 'CSV'
+            auto_create: true
+```
+
+You can also include the following options:
+
+```
+options:
+    object_pattern: '<regex>'
+    type: 'CSV'
+    auto_create: true
+    allow_column_mismatch: false
+    max_errors_per_file: 10
+    csv_options:
+        header: true
+        delimiter: ','
+        quote: DOUBLE_QUOTE
+        escape: '\'
+        null_string: '\\N'
+        empty_field_as_null: true
+        skip_blank_lines: true
+        date_format: 'YYYY-MM-DD'
+        timestamp_format: 'YYYY-MM-DD HH24:MI:SS'
+```
+
+In the previous code example, `csv_options` are indented. For detailed descriptions of these options and their allowed values, refer to the [parameter specification](/sql_reference/commands/data-management/copy-from.html#parameters).
+
+# [](#further-reading)Further reading
+
+- [Configuring Firebolt-specific features](https://docs.getdbt.com/reference/resource-configs/firebolt-configs).
+- [Incremental models](https://docs.getdbt.com/docs/build/incremental-models).
+- [Data tests](https://docs.getdbt.com/docs/build/data-tests).
+- [Documenting your models](https://docs.getdbt.com/docs/collaborate/documentation).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_cube_js.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_cube_js.md
new file mode 100644
index 0000000..7ff4d34
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_cube_js.md
@@ -0,0 +1,98 @@
+# [](#overview)Overview
+
+![Cube](/assets/images/cube-js-logo.png)
+
+Cube.js is an open-source analytical API platform that empowers developers to build custom and scalable analytics solutions. By acting as an intermediary between your data sources and front-end applications, Cube.js simplifies the process of querying large datasets and ensures efficient data management and visualization.
+
+Integrating Cube.js with Firebolt significantly enhances the data processing capabilities of your analytics stack. Firebolt’s ability to execute complex queries with minimal latency aligns perfectly with Cube.js’s goal of delivering fast and responsive analytics. As a result, users benefit from a seamless and highly performant analytics experience, making it an ideal solution for businesses looking to scale their data operations without compromising on speed or efficiency.
+
+# [](#quickstart-connecting-cubejs-to-firebolt)Quickstart: Connecting Cube.js to Firebolt
+
+Follow these steps to quickly connect Cube.js to Firebolt and start building powerful analytics solutions using Docker. For this demo we’ll be using [Cube Core](https://cube.dev/docs/product/getting-started/core). For other deployment options follow the Cube [documentation](https://cube.dev/docs/product/deployment).
+
+#### [](#prerequisites)Prerequisites
+
+1. **Docker**: Ensure you have Docker installed. You can download it from [here](https://www.docker.com/products/docker-desktop).
+2. **Firebolt Account**: You need an active Firebolt account. Sign up [here](https://www.firebolt.io/) if you don’t have one.
+3. **Firebolt Database and Table**: Make sure you have a Firebolt database and table with data ready for querying. Follow our [Getting started tutorial](/Guides/getting-started/) to set up some sample data.
+4. **Firebolt Service Account**: Create a [service account](/Guides/managing-your-organization/service-accounts.html) in Firebolt and note its id and secret.
+
+#### [](#step-1-create-a-cubejs-project-with-docker)Step 1: Create a Cube.js Project with Docker
+
+1. Create a new directory for your Cube.js project:
+   
+   ```
+   mkdir cubejs-firebolt
+   cd cubejs-firebolt
+   touch docker-compose.yml
+   ```
+2. Create a `docker-compose.yml` file with the following content:
+   
+   ```
+   version: "2.2"
+   
+   services:
+     cube:
+       image: cubejs/cube:latest
+       ports:
+        - 4000:4000
+        - 15432:15432
+       environment:
+         CUBEJS_DEV_MODE: "true"
+       volumes:
+         - .:/cube/conf
+   ```
+
+#### [](#step-2-start-cubejs)Step 2: Start Cube.js
+
+1. Run the Cube.js development server using Docker Compose:
+   
+   ```
+   docker compose up -d
+   ```
+2. Open your browser and navigate to `http://localhost:4000`. You should see the Cube.js [playground](https://cube.dev/docs/product/workspace/playground).
+
+#### [](#step-3-configure-firebolt-connection-via-ui)Step 3: Configure Firebolt Connection via UI
+
+The Playground has a database connection wizard that loads when Cube is first started up and no .env file is found. After database credentials have been set up, an .env file will automatically be created and populated with credentials.
+
+1. Select **Firebolt** as the database type.
+2. Enter your Firebolt credentials:
+   
+   - **Client ID**: Your service account ID
+   - **Client Secret**: Your service account secret
+   - **Database**: Your Firebolt database name
+   - **Account**: Your [account](/Guides/managing-your-organization/managing-accounts.html) name
+   - **Engine Name**: Your Firebolt engine name
+3. Click “Apply” to set up the connection
+
+#### [](#step-4-generate-schema-using-ui)Step 4: Generate Schema Using UI
+
+You should see tables available to you from the configured database
+
+1. Select the `levels` table.
+2. After selecting the table, click Generate Data Model and pick either YAML (recommended) or JavaScript format.
+3. Click build.
+   
+   ![Data Model](/assets/images/cube-data-model-generation.png)
+
+You can start exploring your data!
+
+#### [](#step-5-query-data-in-playground)Step 5: Query data in Playground
+
+Select measures, dimensions and filters to explore your data!
+
+![Playground](../../assets/images/cube-playground-example.png)
+
+Congratulations! You have successfully connected Cube.js to Firebolt and can now start building high-performance analytics solutions. For more detailed configuration and advanced features, refer to the [Cube.js documentation](https://cube.dev/docs) and [Firebolt documentation](https://docs.firebolt.io/).
+
+### [](#further-reading)Further Reading
+
+After setting up Cube.js with Firebolt, you can explore and leverage several powerful features to enhance your analytics capabilities. Here are some resources to help you get started:
+
+1. **Cube.js Data Blending**: Understand how to combine data from different sources for more comprehensive analysis. [Cube.js Data Blending Documentation](https://cube.dev/docs/product/data-modeling/concepts/data-blending)
+2. **Cube.js Security**: Implement row-level security to ensure your data is accessed appropriately. [Cube.js Security Documentation](https://cube.dev/docs/security)
+3. **Cube.js API**: Explore the Cube.js REST API to programmatically access your data and build custom integrations. [Cube.js API Reference](https://cube.dev/docs/rest-api)
+4. **Cube.js Dashboard App**: Build and deploy powerful dashboards using Cube.js and your favorite front-end frameworks. [Cube.js Dashboard App Documentation](https://cube.dev/docs/dashboard-app)
+
+These resources will help you unlock the full potential of Cube.js and create robust, high-performance analytics solutions.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_dbeaver.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_dbeaver.md
new file mode 100644
index 0000000..f82189f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_dbeaver.md
@@ -0,0 +1,59 @@
+# [](#integrate-with-dbeaver)Integrate with DBeaver
+
+![DBeaver logo](../../assets/images/DBeaver-logo.png)
+
+DBeaver is a free, open-source database administration tool that supports multiple database types. It provides a graphical interface for managing databases, running queries, and analyzing data. DBeaver is widely used for database development, troubleshooting, and administration, making it a versatile choice for both developers and database administrators. You can connect DBeaver to Firebolt using the [Firebolt JDBC driver](/Guides/developing-with-firebolt/connecting-with-jdbc.html).
+
+- [Prerequisites](#prerequisites)
+- [Add the Firebolt JDBC Driver in DBeaver](#add-the-firebolt-jdbc-driver-in-dbeaver)
+- [Connect to Firebolt in DBeaver](#connect-to-firebolt-in-dbeaver)
+- [Query Firebolt in DBeaver](#query-firebolt-in-dbeaver)
+- [Additional Resources](#additional-resources)
+
+## [](#prerequisites)Prerequisites
+
+You must have the following prerequisites before you can connect your Firebolt account to DBeaver:
+
+- **Firebolt account** – You need an active Firebolt account. If you do not have one, you can [sign up](https://go.firebolt.io/signup) for one.
+- **Firebolt database and engine** – You must have access to a Firebolt database. If you do not have access, you can [create a database](/Guides/getting-started/get-started-sql.html#create-a-database) and then [create an engine](/Guides/getting-started/get-started-sql.html#create-an-engine).
+- **Firebolt service account** – You must have an active Firebolt [service account](/Guides/managing-your-organization/service-accounts.html) for programmatic access, along with its ID and secret.
+- **Sufficient permissions** – Your service account must be [associated](/Guides/managing-your-organization/service-accounts.html#create-a-user) with a user. The user should have [USAGE](/Overview/Security/Role-Based%20Access%20Control/database-permissions/) permission to query your database, and [OPERATE](/Overview/Security/Role-Based%20Access%20Control/engine-permissions.html) permission to start and stop an engine if it is not already started. It should also have at least USAGE and SELECT [permissions](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html) on the schema you are planning to query.
+- **DBeaver installed** – You must have downloaded and installed [DBeaver](https://dbeaver.io/download/).
+
+## [](#add-the-firebolt-jdbc-driver-in-dbeaver)Add the Firebolt JDBC Driver in DBeaver
+
+To connect to Firebolt, you must add the Firebolt JDBC driver to DBeaver as follows:
+
+1. Download the [Firebolt JDBC driver](/Guides/developing-with-firebolt/connecting-with-jdbc.html#download-the-jar-file).
+2. In the DBeaver user interface (UI), under **Database**, select **Driver Manager**.
+3. In **Driver Manager**, select **New** and enter the following parameters:
+   
+   - **Driver Name**: `Firebolt`
+   - **Class Name**: `com.firebolt.FireboltDriver`
+4. Select the **Libraries** tab.
+5. Select **Add File**, and then select the JDBC driver you downloaded in the first step.
+6. Select **Close**.
+
+## [](#connect-to-firebolt-in-dbeaver)Connect to Firebolt in DBeaver
+
+To connect to Firebolt, you must configure a new database connection in DBeaver as follows:
+
+1. In DBeaver, select **Database**, then **New Database Connection**.
+2. Enter `Firebolt` in the search box, then select it from the list.
+3. Select **Next&gt;**.
+4. Enter the connection parameters in the **Main** tab as follows:
+   
+   Parameter Description **JDBC URL** Use `jdbc:firebolt:<db_name>?engine=<engine_name>&account=<account_name>` replacing `<db_name>` with your Firebolt [database name](/Overview/indexes/using-indexes.html#databases), `<engine_name>` with your [engine name](/Guides/getting-started/get-started-sql.html#create-an-engine) and `<account_name>` with your [account name](/Guides/managing-your-organization/managing-accounts.html). **Username** Your Firebolt [service account](/Guides/managing-your-organization/service-accounts.html#get-a-service-account-id) ID. **Password** Your Firebolt [service account](/Guides/managing-your-organization/service-accounts.html#generate-a-secret) secret.
+5. Select **Test Connection** to verify the connection. Ensure your Firebolt database is running before testing.
+6. If the connection is successful, select **Finish**.
+
+## [](#query-firebolt-in-dbeaver)Query Firebolt in DBeaver
+
+1. In the database navigator, right-click or open the context menu of your Firebolt connection, select **SQL Editor**, then select **New SQL Script**.
+2. Enter SQL queries into the SQL editor to interact with your Firebolt database.
+
+## [](#additional-resources)Additional Resources
+
+- Learn more about the [Firebolt JDBC driver](/Guides/developing-with-firebolt/connecting-with-jdbc.html).
+- Explore [DBeaver’s documentation](https://dbeaver.io/documentation/) for details on its UI, integrations, tools, and features.
+- Discover other tools that [Firebolt integrates](/Guides/integrations/integrations.html) with.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_estuary.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_estuary.md
new file mode 100644
index 0000000..18b1551
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_estuary.md
@@ -0,0 +1,127 @@
+# [](#integrate-estuary-flow-with-firebolt)Integrate Estuary Flow with Firebolt
+
+![Estuary logo](../../assets/images/estuary.png)
+
+Estuary Flow is a real-time data integration platform designed to streamline the movement and transformation of data between diverse sources and destinations. It provides an event-driven architecture and a user-friendly interface for building pipelines with minimal effort. You can use Flow to set up pipelines to load data from various sources, such as cloud storage and databases, into Firebolt’s cloud data warehouse for low-latency analytics.
+
+This guide shows you how to set up a Flow pipeline that automatically moves data from your Amazon S3 bucket to your Firebolt database using the Estuary Flow user interface (UI). You must have access to an Estuary Flow account, an Amazon S3 bucket, and a Firebolt service account.
+
+Topics:
+
+- [Integrate Estuary Flow with Firebolt](#integrate-estuary-flow-with-firebolt)
+  
+  - [Prerequisites](#prerequisites)
+  - [Configure your Estuary Flow source](#configure-your-estuary-flow-source)
+  - [Configure your Estuary Flow destination](#configure-your-estuary-flow-destination)
+  - [Monitor your materialization](#monitor-your-materialization)
+  - [Validate your materialization](#validate-your-materialization)
+  - [Additional resources](#additional-resources)
+
+## [](#prerequisites)Prerequisites
+
+1. **Estuary Flow account** – You must have access to an active Estuary Flow account. If you do not have access, you can [sign up](https://www.estuary.dev) with Estuary.
+2. **Amazon S3 bucket** – you must have access to the following:
+   
+   - An [AWS Access Key ID and AWS Secret Access Key](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html) for an Amazon S3 bucket.
+   - The name and path to an [Amazon S3 bucket](https://aws.amazon.com/s3/) that contains your data.
+3. **Firebolt service account** –
+   
+   - Access to an organization in Firebolt. If you don’t have access, you can [create an organization](/Guides/managing-your-organization/creating-an-organization.html).
+   - Access to a Firebolt database and engine. If you don’t have access, you can [create a database](/Guides/getting-started/get-started-sql.html#create-a-database) and [create an engine](/Guides/getting-started/get-started-sql.html#create-an-engine).
+   - Access to a Firebolt service account, which is used for programmatic access, its [service account ID](/Guides/managing-your-organization/service-accounts.html#get-a-service-account-id) and [secret](/Guides/managing-your-organization/service-accounts.html#generate-a-secret-using-the-ui). If you don’t have access, you can [create a service account](/Guides/managing-your-organization/service-accounts.html#create-a-service-account).
+
+## [](#configure-your-estuary-flow-source)Configure your Estuary Flow source
+
+To set up an Estuary Flow pipeline that automatically moves data from your Amazon S3 bucket, you must create a capture that defines how and where data should be collected. Create a capture for the Estuary Flow source as follows:
+
+1. Sign in to your [Estuary Flow Dashboard](https://dashboard.estuary.dev).
+2. Select **Sources** from the left navigation pane.
+3. In the **Sources** window, select **+ NEW CAPTURE**.
+4. From the list of available connectors, navigate to **Amazon S3**, and select **Capture**.
+5. Under **Capture Details**, enter a descriptive name for your capture in the text box under **Name**.
+6. Under **Endpoint Config**, enter the following:
+   
+   1. **AWS Access Key ID** – The AWS account ID associated with the Amazon S3 bucket containing your data.
+   2. **AWS Secret Access Key** – The AWS secret access key associated with the Amazon S3 bucket containing your data.
+   3. **AWS Region** – The [AWS region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) that contains your Amazon S3 bucket. For example: `us-east-1`.
+   4. **Bucket** – The name of your Amazon S3 bucket. For example, `firebolt-publishing-public`.
+   5. **Prefix** (Optional) – A folder or key prefix to restrict the data to a specific path within the bucket. An example prefix structure follows: `/help_center_assets/firebolt_sample_dataset/levels.csv`.
+   6. **Match Keys** (Optional) – Use a filter to include only specific object keys under the prefix, narrowing the capture’s scope.
+7. Select the **NEXT** button in the upper-right corner of the page.
+8. Test and save your connection as follows:
+   
+   1. Select **TEST** in the upper-right corner of the page. Estuary will run a test for your capture and display **Success** if it completes successfully.
+   2. Select **CLOSE** in the bottom-right corner of the page.
+   3. Select the **SAVE AND PUBLISH** button in the upper-right corner of the page. Estuary will test, save, and publish your capture and display **Success** if it completes successfully.
+   4. Select **CLOSE** in the bottom-right corner of the page.
+
+## [](#configure-your-estuary-flow-destination)Configure your Estuary Flow destination
+
+To set up an Estuary Flow pipeline that automatically moves data from your Amazon S3 bucket, you must create a materialization that defines how the data should appear in the destination system, including any schema or transformation logic. Create a materialization for the Estuary Flow destination as follows:
+
+1. Select **Destinations** from the left navigation pane.
+2. Select the **+ NEW MATERIALIZATION** button in the upper-left corner of the page.
+3. Navigate to the **Firebolt** connector and select **Materialization**.
+4. Under **Materialization Details**, enter a descriptive name for your materialization in the text box under **Name**.
+5. Under **Endpoint Config**, enter the following:
+   
+   01. **Client ID** – The service account ID for your Firebolt service account.
+   02. **Client Secret** – The secret for your Firebolt service account.
+   03. **Account Name** – The name of your service account.
+   04. **Database** – The name of the Firebolt database where you want to put your data. For example, `my-database`.
+   05. **Engine Name** – The name of the Firebolt engine to run the queries. For example: `my-engine-name`.
+   06. **S3 Bucket** – The name of the Amazon S3 bucket to store temporary intermediate files related to the operation of the external table. For example, `my-bucket`.
+   07. **S3 Prefix** – (Optional) A folder or key prefix to restrict the data to a specific path within the bucket. An example prefix structure follows the format in: `temp_files/`.
+   08. **AWS Key ID** – The access key ID for the AWS account linked to the Amazon S3 bucket for temporary file storage.
+   09. **AWS Secret Key** – The AWS secret key associated with the Amazon S3 bucket to store temporary files.
+   10. **AWS Region** – The [AWS region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) of your Amazon S3 bucket. For example: `us-east-1`.
+6. Select the **NEXT** button in the upper-right corner of the page.
+7. Under **Source Collections**, do the following:
+   
+   1. Select **Source From Capture**.
+   2. In the **Captures** window, select the checkbox next to the Amazon S3 source you specified when you configured your Estuary Flow source.
+   3. Select the **CONTINUE** button in the bottom-right corner of the page.
+   4. Verify that the **Table** name and type in the **CONFIG** tab under **Resource Configuration** are correct, and update if necessary.
+   5. (Optional) Choose **Refresh** next to **Field Selection** to preview the fields, their types, and actions that will be written to Firebolt.
+8. Test and save your materialization as follows:
+   
+   1. Select the **TEST** button in the upper-right corner of the page. Estuary will run a test for your materialization and display **Success** if it completes successfully.
+   2. Select **CLOSE** in the bottom-right corner of the page.
+   3. Select the **SAVE AND PUBLISH** button in the upper-right corner of the page. Estuary will test, save, and publish your materialization and display **Success** if it completes successfully.
+   4. Select **CLOSE** in the bottom-right corner of the page.
+
+## [](#monitor-your-materialization)Monitor your materialization
+
+You can monitor your new data pipeline in Estuary Flow’s dashboard as follows:
+
+1. Select **Destinations** from the left navigation pane.
+2. Select your newly created materialization to view a dashboard with the following tabs:
+   
+   1. **OVERVIEW** – Provides a high-level summary of the materialization that includes throughput over time.
+   2. **SPEC** – Displays the configurations and specifications of the materialization that includes schema mapping from the source to destination, the configuration of the destination, and any filters or constrains on the materialized data.
+   3. **LOGS** – Provides records of materialization activity including success and failure events, messages, and errors.
+
+Ensure that your data is being ingested and transferred as expected.
+
+## [](#validate-your-materialization)Validate your materialization
+
+You can validate that your data has arrived at Firebolt as follows:
+
+1. Log in to the [Firebolt Workspace](https://firebolt.go.firebolt.io/signup).
+2. Select the **Develop** icon (![The Firebolt Develop Space icon.](../../assets/images/develop-icon.png)) from the left navigation pane.
+3. In the **Script Editor**, run a query on the table that you specified as an Estuary Flow destination to confirm the transfer of data as follows:
+   
+   1. Select the name of the database that you specified as your Estuary Flow destination from the drop-down list next to **Databases**.
+   2. Enter a script in the script editor to query the table that you specified as an Estuary Flow destination. The following code example returns the contents of all rows and all columns from the `games` table:
+   
+   ```
+    SELECT * FROM games
+   ```
+   
+   You’ve successfully set up an Estuary Flow pipeline to move data from an Amazon S3 source to a Firebolt destination. Next, explore the following resources to continue expanding your knowledge base.
+
+## [](#additional-resources)Additional resources
+
+- Explore the [core concepts](https://docs.estuary.dev/concepts/) of Estuary Flow.
+- Access [tutorials](https://docs.estuary.dev/getting-started/tutorials/) for Estuary Flow including a tutorial on [data transformation](https://docs.estuary.dev/guides/derivation_tutorial_sql/).
+- Learn more about Estuary Flow’s [command line interface](https://docs.estuary.dev/concepts/flowctl/).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_integrations.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_integrations.md
new file mode 100644
index 0000000..c2e5e03
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_integrations.md
@@ -0,0 +1,16 @@
+# [](#integrate-with-firebolt)Integrate with Firebolt
+
+* * *
+
+- [Airflow](/Guides/integrations/airflow.html)
+- [dbt](/Guides/integrations/connecting-with-dbt.html)
+- [Apache Superset](/Guides/integrations/connecting-to-apache-superset.html)
+- [Preset](/Guides/integrations/connecting-to-preset.html)
+- [Cube.js](/Guides/integrations/cube-js.html)
+- [Airbyte](/Guides/integrations/airbyte.html)
+- [OpenTelemetry Exporter](/Guides/integrations/otel-exporter.html)
+- [Tableau](/Guides/integrations/tableau.html)
+- [Paradime](/Guides/integrations/connecting-to-paradime.html)
+- [Metabase](/Guides/integrations/metabase.html)
+- [Estuary](/Guides/integrations/estuary.html)
+- [DBeaver](/Guides/integrations/dbeaver.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_metabase.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_metabase.md
new file mode 100644
index 0000000..0ca8720
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_metabase.md
@@ -0,0 +1,56 @@
+![Metabase](/assets/images/metabase.png)
+
+# [](#connecting-to-metabase)Connecting to Metabase
+
+[Metabase](https://www.metabase.com/) is an open-source business intelligence platform. You can use Metabase’s user interface to explore, analyze, and visualize data, query databases, generate reports, and create dashboards.
+
+This guide shows you how to [set up a Firebolt connector](#set-up-a-connector-to-metabase) for a self-hosted Metabase instance and how to [create a connection](#create-a-connection-to-metabase). If you are using either the managed or cloud-hosted version of [**Metabase Cloud**](https://www.metabase.com/docs/latest/cloud/start), you can skip directly to the [Create a Connection](#create-a-connection-to-metabase).
+
+You can also watch a short video on how to connect Metabase to Firebolt:
+
+**Topics:**
+
+1. [Set up a connector to metabase](#set-up-a-connector-to-metabase)
+2. [Create a connection to metabase](#create-a-connection-to-metabase)
+3. [Additional Resources](#additional-resources)
+
+### [](#set-up-a-connector-to-metabase)Set up a connector to metabase
+
+Metabase can be deployed as a **self-hosted instance**, which is a version that you install and manage on your own server infrastructure. If you are using either the managed or cloud-hosted version of [**Metabase Cloud**](https://www.metabase.com/docs/latest/cloud/start), you can skip directly to the [Create a Connection](#create-a-connection-to-metabase).
+
+For self-hosted deployments on-premises, the Firebolt connector must be installed manually using the following steps:
+
+1. **Download the Firebolt Metabase driver**
+   
+   - Go to the [GitHub Releases page for Firebolt](https://github.com/firebolt-db/metabase-firebolt-driver/releases).
+   - Locate the most recent version of the Firebolt driver, and download it.
+2. **Move the driver file to the plugins directory**
+   
+   - Save the downloaded driver file in the `/plugins` directory on your Metabase host system.
+   - By default, the `/plugins` directory is located in the same folder where the `metabase.jar` file runs. After completing these steps, the Firebolt connector will be available for configuration within Metabase.
+
+### [](#create-a-connection-to-metabase)Create a connection to metabase
+
+After setting up the Firebolt connector, use the following steps to create a connection between Metabase and your Firebolt database:
+
+1. Open your Metabase instance’s home page in a web browser.
+2. Select **Settings** from the top-right menu of the Metabase interface.
+3. Select **Admin** from the dropdown menu.
+4. On the **Admin** page, select **Databases** in the top navigation bar.
+5. Select the **Add Database** button.
+6. From the **Database Type** dropdown list, select **Firebolt**.
+   
+   Fill out the required connection details using the descriptions provided in the following table:
+   
+   Field Description **Display Name** A name to identify your database in Metabase. Use the same name as your Firebolt database for simplicity. **Client ID** The [service account ID](/Guides/managing-your-organization/service-accounts.html#get-a-service-account-id) associated with your Firebolt database. **Client Secret** The [secret for the service account](/Guides/managing-your-organization/service-accounts.html#generate-a-secret) associated with your Firebolt database. **Database name** Specify the name of the Firebolt database you want to connect to. **Account name** The name of your Firebolt account, which is required to log in and authenticate your database connection. **Engine name** Provide the name of the Firebolt engine that will be used to run queries against the database. **Additional JDBC options** Add any extra parameters needed for the connection, such as `connection_timeout_millis=10000`. For more options, access the [JDBC connection parameters guide](/Guides/developing-with-firebolt/connecting-with-jdbc.html#available-connection-parameters).
+7. Select **Save** to store your database configuration.
+
+Verify the connection by confirming that Metabase displays a success message indicating that your Firebolt database has been added successfully. If the connection fails, double-check your settings and ensure all required fields are correct.
+
+### [](#additional-resources)Additional Resources
+
+For more information about Metabase configuration and troubleshooting, refer to the following resources:
+
+- [**Adding and Managing Databases**](https://www.metabase.com/docs/latest/databases/connecting) — Official Metabase documentation on connecting to data sources and managing database connections.
+- [**Troubleshooting Database Connections**](https://www.metabase.com/docs/latest/troubleshooting-guide/db-connection) — Guidance on resolving issues when connecting [Metabase](https://www.metabase.com/docs/latest/databases/connecting) to your databases.
+- [**Troubleshooting Database Performance**](https://www.metabase.com/docs/latest/troubleshooting-guide/db-performance) — Tips for identifying and addressing performance issues with connected databases.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_otel_exporter.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_otel_exporter.md
new file mode 100644
index 0000000..5a8d7cb
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_otel_exporter.md
@@ -0,0 +1,9 @@
+# [](#overview)Overview
+
+[OpenTelemetry](https://opentelemetry.io/) is a [CNCF](https://www.cncf.io/) project that provides a collection of APIs, SDKs, and tools to instrument, generate, collect, and export telemetry data (metrics, logs, and traces). In the past few years, this project become the accepted standard for telemetry, with native support by all major vendors. As such, Firebolt provides an OpenTelemetry exporter which gives and compatibility with minimal effort.
+
+Firebolt OpenTelemetry Exporter is provided as a docker image, which allows exporting engine metrics to any [OTLP](https://opentelemetry.io/docs/specs/otel/protocol/) compatible collector. This makes possible to integrate Firebolt runtime metrics into customer’s monitoring and alerting systems and be able to use homogeneous infrastructure for observability of the entire data stack.
+
+# [](#enabling-firebolt-opentelemetry-exporter)Enabling Firebolt OpenTelemetry Exporter
+
+For installation and usage instructions, see the [otel-exporter](https://github.com/firebolt-db/otel-exporter) repository on GitHub.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_integrations_tableau.md b/cmd/docs-scrapper/fireboltdocs/guides_integrations_tableau.md
new file mode 100644
index 0000000..6beef0d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_integrations_tableau.md
@@ -0,0 +1,79 @@
+# [](#integrate-with-tableau)Integrate with Tableau
+
+![Tableau icon](../../assets/images/Tableau.png)
+
+[Tableau](https://www.tableau.com/) is a visual analytics platform that empowers users to explore, analyze, and present data through interactive visualizations. It supports diverse use cases such as data exploration, reporting, and collaboration, and helps users gain insights and make informed decisions. This guide shows you how to set up your Firebolt account to integrate with [Tableau Desktop](https://www.tableau.com/products/desktop) and [Tableau Exchange](https://exchange.tableau.com).
+
+The latest Firebolt version is not compatible with Tableau Online, and you will not be able to connect it to your Firebolt account. You can only use the connector from Tableau Exchange with an older version of Firebolt. If you want to use the latest version, use Tableau Desktop or Tableau Server and follow the instructions below.
+
+## [](#prerequisites)Prerequisites
+
+You must have the following prerequisites before you can connect your Firebolt account to Tableau:
+
+- **Tableau account** – You must have access to an active Tableau account. If you do not have access, you can [sign up](https://www.tableau.com/products/trial) for one.
+- **Firebolt account** – You need an active Firebolt account. If you do not have one, you can [sign up](https://go.firebolt.io/signup) for one.
+- **Firebolt database and table** – You must have access to a Firebolt database that contains a table with data ready for visualization. If you don’t have access, you can [create a database](/Guides/getting-started/get-started-sql.html#create-a-database) and then [load data](/Guides/loading-data/loading-data.html) into it.
+- **Firebolt service account** – You must have access to an active Firebolt [service account](/Guides/managing-your-organization/service-accounts.html), which facilitates programmatic access to Firebolt, its ID and secret.
+- **Firebolt user** – You must have a user that is [associated](/Guides/managing-your-organization/service-accounts.html#create-a-user) with your service account. The user should have [USAGE](/Overview/Security/Role-Based%20Access%20Control/database-permissions/) permission to query your database, and [OPERATE](/Overview/Security/Role-Based%20Access%20Control/engine-permissions.html) permission to start and stop an engine if it is not already started.
+
+## [](#connect-to-tableau)Connect to Tableau
+
+To connect to Tableau, you must download a Firebolt connector, a [JDBC driver](/Guides/developing-with-firebolt/connecting-with-jdbc.html#jdbc-driver), connect to Firebolt, and select a database and schema to query. You can either install [Tableau Desktop](https://www.tableau.com/products/desktop) for individual use or [Tableau Server](https://www.tableau.com/products/server) for centralized access to dashboards on a shared server.
+
+1. **Download and install Tableau**
+   
+   1. To download Tableau’s Desktop, navigate to Tableau’s Desktop [download page](https://www.tableau.com/en-gb/products/desktop/download), and follow the prompts to install the program. To use Tableau Server, follow Tableau’s instructions for [installation and configuration](https://help.tableau.com/current/server/en-us/install_config_top.htm).
+   2. Follow the prompts to install Tableau.
+2. **Download the latest Firebolt connector**
+   
+   Download the latest version of Firebolt’s Tableau connector from Firebolt’s GitHub [repository](https://github.com/firebolt-db/tableau-connector/releases). The earliest version of the driver that is compatible with the latest version of Firebolt is [v1.1.0](https://github.com/firebolt-db/tableau-connector/releases/tag/v1.1.0). The name of the file has the following format: `firebolt_connector-<version>.taco`, and should be saved in a specific directory that depends on the operating system used as follows:
+   
+   For Tableau Desktop, save the file connector to:
+   
+   - Windows - `C:\Users\[Windows User]\Documents\My Tableau Repository\Connectors`
+   - MacOS - `/Users/[user]/Documents/My Tableau Repository/Connectors`
+   
+   For any other installations including Tableau Server and older versions of Tableau, follow the steps in the Tableau [guide](https://help.tableau.com/current/pro/desktop/en-us/examples_connector_sdk.htm#use-a-connector-built-with-tableau-connector-sdk).
+3. **Download the latest JDBC driver**
+   
+   Download a JDBC driver, which will allow Tableau to interact with a Firebolt databases using Java, from Firebolt’s GitHub [repository](https://github.com/firebolt-db/jdbc/releases). The name of the file has the following format: `firebolt-jdbc-<version>.jar`, and should be saved in a specific directory that depends on the operating system as follows:
+   
+   - Windows: `C:\Program Files\Tableau\Drivers`
+   - Mac: `/Users/<username>/Library/Tableau/Drivers`
+   - Linux: `/opt/tableau/tableau_driver/jdbc`
+4. **Start Tableau and verify Firebolt connector availability**
+   
+   1. Start your Tableau Desktop or Server. If you already started Tableau prior to downloading the drivers, restart Tableau.
+   2. In the left navigation panel, under **To a Server**, select the `>` to the right of **More…**.
+   3. Search for and select the **Firebolt by Firebolt Analytics Inc** connector in the search bar.
+   4. In the left navigation panel, under **To a Server**, select the `>` to the right of **More…**.
+   5. Select **Firebolt Connector by Firebolt**.
+   6. Enter the following parameters in the **General** tab:
+      
+      **Field** **Required** **Description** **Host** No Most users should not enter a value in the text box under `Host`. **Account** Yes The name of your Firebolt account within your organization. **Engine Name** Yes The name of the [engine](/Overview/engine-fundamentals.html) to run queries. **Database** Yes The name of the Firebolt [database](/Overview/indexes/using-indexes.html#databases) to connect to. **Client ID** Yes The [ID of your service account](/Guides/managing-your-organization/service-accounts.html#get-a-service-account-id). **Client Secret** Yes The [secret](/Guides/managing-your-organization/service-accounts.html#generate-a-secret) for your service account authentication.
+   7. Select **Sign in**.
+5. **Choose the database and the schema to query**
+   
+   After successful authentication, **Database** and **Schema** drop-down lists appear in the left navigation pane under **Connections**. The database name from the previous step appears in the database drop-down list. To change the database, you must repeat the previous step and set up a new connector.
+   
+   Choose the schema and tables as follows:
+   
+   1. Select the drop-down list under **Schema** to select a [schema](/Overview/indexes/using-indexes.html#schema). Most users should choose `public`. For more information about schema permissions and privileges, see [Schema permissions](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html).
+   2. Drag and drop tables from the list of available tables in your schema to use them in Tableau.
+6. **Visualize your data**
+   
+   Once your data source is selected you can begin visualizing the data by creating graphs and charts as follows:
+   
+   1. Select `Sheet 1` tab from the bottom-left corner of your Tableau window next to **Data Source**.
+   2. In the left navigation panel under **Sheets**, drag and drop any available columns or pre-defined aggregation from your table into the Tableau workspace to start building charts. See Tableau’s [Build a view from scratch](https://help.tableau.com/current/pro/desktop/en-us/getstarted_buildmanual_ex1basic.htm) documentation for more information.
+
+## [](#limitations)Limitations
+
+- Firebolt does not support [Tableau Cloud](https://www.tableau.com/products/cloud-bi).
+- Once you have set up a connection to Firebolt, you cannot change the database that you specified during setup. In order to change the database, you must repeat step 4 to **Start Tableau and verify Firebolt connector availability** in [Connect to Tableau](#connect-to-tableau) to set up a new connection.
+
+## [](#additional-resources)Additional resources
+
+- Watch Tableau’s [free training videos](https://www.tableau.com/en-gb/learn/training) on getting started, preparing data, and geographical analysis.
+- Read Tableau’s data visualization [articles](https://www.tableau.com/en-gb/learn/articles) about creating effective, engaging, and interactive examples.
+- Follow Tableau’s [blog](https://www.tableau.com/en-gb/blog) for new features and tips.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_configuring_aws_role_to_access_amazon_s3.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_configuring_aws_role_to_access_amazon_s3.md
new file mode 100644
index 0000000..8b9e010
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_configuring_aws_role_to_access_amazon_s3.md
@@ -0,0 +1,163 @@
+# [](#use-aws-iam-roles-to-access-amazon-s3)Use AWS IAM roles to access Amazon S3
+
+Firebolt uses AWS Identity and Access Management (IAM) permissions to load data from an Amazon S3 bucket into Firebolt. This requires you to set up permissions using the AWS Management Console. Specify credentials when you create an external table using one of the following options:
+
+- You can provide **Access Keys** associated with an IAM principal that has the required permissions.
+- You can specify an **IAM role** that Firebolt assumes for the appropriate permissions.
+
+This guide explains how to create an AWS IAM permissions policy and an IAM role to grant Firebolt the necessary permissions to access and read data from an Amazon S3 bucket.
+
+1. [Create an IAM permissions policy in AWS](#create-an-iam-permissions-policy-in-aws)
+2. [Create the IAM role in AWS](#create-the-iam-role-in-aws)
+3. [How to specify the IAM role](#how-to-specify-the-iam-role)
+   
+   1. [Specify the IAM role for data loading](#specify-the-iam-role-for-data-loading)
+   2. [Specify the IAM role in `COPY FROM`](#specify-the-iam-role-in-copy-from)
+   3. [Using IAM role in the Firebolt load data wizard](#using-iam-role-in-the-firebolt-load-data-wizard)
+   4. [Using IAM role in external table definitions](#using-iam-role-in-external-table-definitions)
+
+## [](#create-an-iam-permissions-policy-in-aws)Create an IAM permissions policy in AWS
+
+01. Log in to the [AWS Identity and Access Management (IAM) Console](https://console.aws.amazon.com/iam/home#/home).
+02. From the left navigation panel, under **Access management**, choose **Account settings**.
+03. Under **Security Token Service (STS),** in the **Endpoints** list, find the **Region name** where your account is located. If the status is **Inactive**, choose **Activate**.
+04. Choose **Policies** from the left navigation panel.
+05. Select **Create Policy**.
+06. Select the **JSON** tab.
+07. Add a policy document that grants Firebolt access to the Amazon S3 bucket and folder.
+    
+    The following policy in JSON format provides Firebolt with the required permissions to unload data using a single bucket and folder path. Copy and paste the text into the policy editor. Replace `<bucket>` and `<prefix>` with the actual bucket name and path prefix.
+    
+    ```
+    {
+       "Version": "2012-10-17",
+       "Statement": [
+           {
+               "Effect": "Allow",
+               "Action": [
+                   "s3:GetObject",
+                   "s3:GetObjectVersion"
+               ],
+               "Resource": "arn:aws:s3:::<bucket>/<prefix>/*"
+           },
+           {
+               "Effect": "Allow",
+               "Action": "s3:GetBucketLocation",
+               "Resource": "arn:aws:s3:::<bucket>"
+           },
+           {
+               "Effect": "Allow",
+               "Action": "s3:ListBucket",
+               "Resource": "arn:aws:s3:::<bucket>",
+               "Condition": {
+                   "StringLike": {
+                       "s3:prefix": [
+                           "<prefix>/*"
+                       ]
+                   }
+               }
+           }
+       ]
+    }
+    ```
+    
+    - If you encounter the following error: `Access Denied (Status Code: 403; Error Code: AccessDenied)`, one possible fix may be to remove the following condition from the IAM policy:
+    
+    ```
+               "Condition": {
+                   "StringLike": {
+                       "s3:prefix": [
+                           "<prefix>/*"
+                       ]
+                   }
+               }
+    ```
+08. Select **Next** in the bottom-right corner of the workspace.
+09. In the **Review and create** pane, under **Policy details**, enter the **Policy name**. For example, `_firebolt-s3-access_`.
+10. Enter an optional **Description**.
+11. Select the **Create policy** button in the bottom-right corner of the workspace.
+
+Setting the s3:prefix condition key to * grants access to **all** prefixes in the specified bucket for the associated action.
+
+## [](#create-the-iam-role-in-aws)Create the IAM role in AWS
+
+To integrate Firebolt with AWS, you must create an IAM role and associate it with the permission policy that you created in the previous [Create an IAM permissions policy in AWS](#create-an-iam-permissions-policy-in-aws) section. The following steps guide you through creating an IAM role, configuring the required trust policy from the Firebolt Workspace, and associating it with your IAM permissions policy. Once completed, you can use the role’s Amazon Resource Name (ARN) in Firebolt’s `CREDENTIALS` clause to enable secure data ingestion.
+
+01. Log in to the [AWS Identity and Access Management (IAM) Console](https://console.aws.amazon.com/iam/home#/home).
+02. Select **Roles** from the left navigation panel.
+03. Select the **Create role** button in the top right part of the main window.
+04. In the **Select trusted entity** window, select the radio button next to **Custom trust policy**.
+05. A **Custom trust policy** window opens. Leave this window open until you obtain a custom trust policy from the Firebolt **Workspace** as follows:
+    
+    1. Log in to the [Firebolt Workspace](https://go.firebolt.io/login).
+    2. Select the plus (**+**) sign in Firebolt’s **Develop Space**.
+    3. Select **Load data** from the drop-down list.
+    4. Select an engine from the drop-down list next to **Select engine for ingestion**. If you do not have an engine, select **Create new engine** to create one.
+    5. Select the **Next step** button.
+    6. Select the radio button next to **IAM Role** in the **Authentication method** row.
+    7. Select the **Create an IAM role** button.
+    8. In the **Create new IAM role** window that pops up, select the copy icon under **Trust policy** to copy the entire trust policy to your clipboard.
+    9. Return to the AWS **Custom trust policy** window from step 5.
+06. Replace the entire contents of the **Custom trust policy** with the contents of your clipboard from the Firebolt **Workspace**.
+07. Select the **Next** button in the bottom right part of the main window.
+08. Under **Permissions policies** enter the name of and select the checkbox next to the policy you created in step 9 of the previous section [create an IAM permissions policy in AWS](#create-an-iam-permissions-policy-in-aws).
+09. Select the **Next** button in the bottom right part of the main window.
+10. Under **Role name**, enter a name that you can use to identify it.
+11. Select the **Create role** button in the bottom right part of the main window.
+12. Under **Role name**, select the name of the role you created in step 10.
+13. Copy the value under **ARN**. This value has the following format: `arn:aws:iam::123456789012:role/your_role_name`. Use the ARN value in the Firebolt `CREDENTIALS` clause as the `AWS_ROLE_ARN`, as shown in the following sections.
+
+Once you’ve created your IAM policy and associated it with your IAM role, you’re ready to load data into Firebolt using IAM roles. Firebolt assumes the IAM role to securely access and read data from your Amazon S3 bucket.
+
+## [](#how-to-specify-the-iam-role)How to specify the IAM role
+
+Firebolt supports AWS IAM roles for secure access to Amazon S3 when loading data. You can specify an IAM role in different ways, including in the `COPY FROM` statement, the Firebolt **Load Data** wizard, or an external table definition. The following sections explain how to configure IAM roles for each method.
+
+### [](#specify-the-iam-role-for-data-loading)Specify the IAM role for data loading
+
+When loading data into Firebolt, specify the IAM role ARN from the previous step to grant the necessary permissions. If you configured an external ID, ensure it is included along with the role ARN. The following sections show you how to load data into Firebolt using AWS IAM roles to access your storage bucket.
+
+### [](#specify-the-iam-role-in-copy-from)Specify the IAM role in `COPY FROM`
+
+Use the IAM role ARN from the previous step in the [CREDENTIALS](/sql_reference/commands/data-management/copy-from.html) of the `COPY FROM` statement. If you specified an external ID, make sure to specify it in addition to the role ARN. When you use the `COPY FROM` statement to load data from your source, Firebolt assumes the IAM role to obtain permissions to read from the location specified in the `COPY FROM` statement.
+
+For a step-by-step guide, see [The simplest COPY FROM workflow](/Guides/loading-data/loading-data-sql.html#the-simplest-copy-from-workflow).
+
+**Example**
+
+The following code example loads data from a CSV file in an Amazon S3 bucket into the `tutorial` table in Firebolt, using an AWS IAM role for authentication, treating the first row as a header, and automatically creating the table if it does not exist:
+
+```
+COPY INTO tutorial 
+FROM 's3://your_s3_bucket/your_file.csv'
+WITH
+CREDENTIALS = (
+    AWS_ROLE_ARN='arn:aws:iam::123456789012:role/my-firebolt-role'
+    AWS_EXTERNAL_ID='ca4f5690-4fdf-4684-9d1c-2d5f9fabc4c9'
+)
+HEADER=TRUE AUTO_CREATE=TRUE;
+```
+
+### [](#using-iam-role-in-the-firebolt-load-data-wizard)Using IAM role in the Firebolt load data wizard
+
+You can use the role ARN from the previous step when loading data using the **Load data** wizard in the **Firebolt Workspace**. For a step-by-step guide, see [Load data using a wizard](/Guides/loading-data/loading-data-wizard.html).
+
+### [](#using-iam-role-in-external-table-definitions)Using IAM role in external table definitions
+
+Specify the IAM role ARN and the optional `external_id` in the [`CREDENTIALS`](/sql_reference/commands/data-definition/create-external-table.html) of the `CREATE EXTERNAL TABLE` statement. Firebolt assumes this IAM role when using an `INSERT INTO` statement to load data into a fact or dimension table.
+
+**Example**
+
+The following code example creates an external table which maps to Parquet files stored in an Amazon S3 bucket, using an AWS IAM role for access, and extracts partition values for `c_type` from the file path based on a specified regex pattern:
+
+```
+CREATE EXTERNAL TABLE my_ext_table (
+  c_id    INTEGER,
+  c_name  TEXT,
+  c_type  TEXT PARTITION('[^/]+/c_type=([^/]+)/[^/]+/[^/]+')
+)
+CREDENTIALS = (AWS_ROLE_ARN='arn:aws:iam::123456789012:role/my-firebolt-role' AWS_ROLE_EXTERNAL_ID='ca4f5690-4fdf-4684-9d1c-2d5f9fabc4c9')
+URL = 's3://my_bucket/'
+OBJECT_PATTERN= '*.parquet'
+TYPE = (PARQUET)
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_creating_access_keys_aws.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_creating_access_keys_aws.md
new file mode 100644
index 0000000..df8d12d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_creating_access_keys_aws.md
@@ -0,0 +1,107 @@
+# [](#creating-an-access-key-and-secret-id-in-aws)Creating an access key and secret ID in AWS
+
+This section will walk you through the steps to create security credentials in AWS. These credentials will be used to load data from AWS S3 into Firebolt.
+
+In order to enable Firebolt to load data from your S3 buckets, you must:
+
+1. Create a user.
+2. Create appropriate permissions for this user.
+3. Create access credentials to authenticate this user.
+
+## [](#create-a-user)Create a user
+
+1. Log into your AWS Management console and go to the IAM section. You can do this by typing “IAM” in the search bar.
+2. Once you are in the IAM section, select the **Create User** button.
+   
+   ![Create IAM User](/assets/images/Create_User_Dialog.png)
+3. Enter a name for the user and select **Next**.
+   
+   ![Specify User Name](/assets/images/Specify_User_Name.png)
+4. You can have the default permission option set to **Add user to group** and select **Next**.
+   
+   ![Set Permissions](/assets/images/Set_Permissions.png)
+5. Select **Create User**.
+   
+   ![Review and Create User](/assets/images/Review_Create_User.png)
+6. You will see a message **User created successfully**.
+   
+   ![User created successfully](/assets/images/User_Created_Successfully.png)
+
+## [](#create-s3-access-permissions)Create S3 access permissions
+
+Now that you have created the user, you will now assign this user appropriate permissions for S3.
+
+1. Select on the user name as shown below.
+   
+   ![Click User](/assets/images/Click_User.png)
+2. In the Permissions tab, select the **Add Permissions** drop-down and choose **Create inline policy**.
+   
+   ![Choose Inline Policy](/assets/images/Choose_Iniline_Permissions.png)
+3. In **Specify Permissions** choose S3 as the service.
+   
+   ![Choose S3](/assets/images/Choose_S3.png)
+4. Choose **JSON**, paste the following JSON code in the policy editor, and select **Next**.
+   
+   ![Set Permissions](/assets/images/Specify_Permissions.png)
+   
+   ```
+   {
+      "Version": "2012-10-17",
+      "Statement": [
+          {
+              "Effect": "Allow",
+              "Action": [
+                  "s3:GetObject",
+                  "s3:GetObjectVersion"
+              ],
+              "Resource": "arn:aws:s3:::<bucket>/<prefix>/*"
+          },
+          {
+              "Effect": "Allow",
+              "Action": "s3:GetBucketLocation",
+              "Resource": "arn:aws:s3:::<bucket>"
+          },
+          {
+              "Effect": "Allow",
+              "Action": "s3:PutObject",
+              "Resource": "arn:aws:s3:::<bucket>/*"
+          },
+          {
+              "Effect": "Allow",
+              "Action": "s3:ListBucket",
+              "Resource": "arn:aws:s3:::<bucket>",
+              "Condition": {
+                  "StringLike": {
+                      "s3:prefix": [
+                          "<prefix>/*"
+                      ]
+                  }
+              }
+          }
+      ]
+   }
+   ```
+   
+   **IMPORTANT:** Replace “&lt;bucket&gt;” with the S3 bucket that you want to provide access to.
+5. Enter a description for the policy and select **Create Policy**.
+   
+   ![Create policy](/assets/images/Create_Policy.png)
+6. You will see a message that the policy has been successfully created.
+
+## [](#create-access-key-and-secret-id)Create access key and secret ID
+
+Now that you have created a user, authorized the user with the appropriate S3 permissions, you will create access credentials for this user. These credentials will be used to authenticate the user.
+
+1. Select the **Security Credentials** tab, as shown in the following image:
+   
+   ![Security Credentials](/assets/images/Choose_Security_Credentials.png)
+2. In the **Access Keys** section, select the **Create Access Key** button.
+   
+   ![Create Access Key](/assets/images/Create_Access_Keys.png)
+3. For the use case, choose the **Application running on AWS compute service**. You will see an alternative recommendation. You can check the box that says “I understand the above recommendation and want to proceed to create an access key” and select **Next**.
+   
+   ![Use case warning](/assets/images/Access_Key_Use_Case.png)
+4. Set a description tag for the access key and select \*\*C, ![Set Desc tag Access Key](/assets/images/Description_Tag_Access_Key.png)
+5. You will see a message indicating that the access key was created. Make sure to download the access key. You will need these credentials when you load S3 data into Firebolt.
+   
+   ![Access Key created successfully](/assets/images/Download_CSV_Access_Key.png)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data.md
new file mode 100644
index 0000000..c88334b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data.md
@@ -0,0 +1,48 @@
+# [](#load-data)Load data
+
+You can load data into Firebolt from an Amazon S3 bucket using two different workflows.
+
+If you want to get started quickly, load data using a **wizard** in the **Firebolt Workspace**. If you want a more customized experience, you can write **SQL scripts** to handle each part of your workflow. This guide shows you how to load data using both the wizard and SQL, and some common data loading workflows and errors.
+
+![You can use either the load data wizard or SQL to create a database, engine, and then load data.](../../assets/images/load_data_workflow.png)
+
+Before you can load data, you must first register with Firebolt, then create a database and an engine. For information about how to register, see [Get Started](../../Guides/getting-started/). See the following sections for information about how to create a database and engine.
+
+## [](#load-data-using-a-wizard)Load data using a wizard
+
+You can use the **Load data** wizard in the **Firebolt Workspace** to load data in either CSV or Parquet format, and choose from a variety of different loading parameters which include the following:
+
+- Specifying a custom delimiter, quote character, escape character, and other options.
+- How to handle errors during data load.
+- Specifying a primary index.
+
+The **Load data** wizard guides you through the process of creating an engine and database as part of the loading process.
+
+See [Load data using a wizard](/Guides/loading-data/loading-data-wizard.html) for information about the options available in the **Load data** wizard.
+
+## [](#load-data-using-sql)Load data using SQL
+
+You can use SQL to load data in CSV, Parquet, TSV, AVRO, JSON Lines or ORC formats. Prior to loading data, you must also create a database and engine using either of the following options:
+
+- Use buttons in the **Firebolt Workspace** to create a database and engine. For more information, see the [Create a Database](/Guides/getting-started/get-started-sql.html#create-a-database) and [Create an Engine](/Guides/getting-started/get-started-sql.html#create-an-engine) sections in the [Get Started using SQL](/Guides/getting-started/get-started-sql.html) guide.
+- Use the SQL commands [CREATE DATABASE](/sql_reference/commands/data-definition/create-database.html) and [CREATE ENGINE](/sql_reference/commands/engines/create-engine.html).
+
+See [SQL to load data](/Guides/loading-data/loading-data-sql.html) for information and code examples to load data using SQL.
+
+## [](#optimizing-during-data-loading)Optimizing during data loading
+
+Optimizing your workflow for Firebolt starts when you load your data. Use the following guidance:
+
+1. A primary index is a sparse index that uniquely identifies rows in a table. Having a primary index is critical to query performance at Firebolt because it allows a query to locate data without scanning an entire dataset. If you are familiar with your data and query history well enough to select an optimal primary index, you can define it when creating a table. If you don’t, you can still load your data without a primary index. Then, once you know your query history patterns, you must create a new table in order to define a primary index.
+   
+   You can specify primary indexes in either the **Load data** wizard or inside SQL commands. The [Load data using a wizard](/Guides/loading-data/loading-data-wizard.html) guide discusses considerations for selecting and how to select primary indexes. The [Load data using SQL](/Guides/loading-data/loading-data-sql.html) discusses considerations for selecting and shows code examples that select primary indexes. For more advanced information, see [Primary indexes](/Overview/indexes/primary-index.html).
+2. If you intend to use [aggregate functions](/sql_reference/functions-reference/aggregation/) in queries, you can calculate an aggregating index when loading your data. Then queries use these pre-calculated values to access information quickly. For an example of calculating an aggregating index during load, see [Load data using SQL](/Guides/loading-data/loading-data-sql.html). For an introduction to aggregating indexes, see the [Aggregating indexes](/Guides/getting-started/get-started-sql.html#aggregating-indexes) section of the **Get Started** guide. For more information, see [Aggregating indexes](/Overview/indexes/aggregating-index.html).
+
+## [](#next-steps)Next steps
+
+After you load your data, you can start running and optimizing your queries. A typical workflow has the previous steps followed by data and resource cleanup as shown in the following diagram:
+
+![The load data workflow includes using the load data wizard or SQL to create a database, engine, and then load data.](../../assets/images/get_started_workflow.png)
+
+- [Load data using a wizard](/Guides/loading-data/loading-data-wizard.html)
+- [Load data using SQL](/Guides/loading-data/loading-data-sql.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data_sql.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data_sql.md
new file mode 100644
index 0000000..04c1dde
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data_sql.md
@@ -0,0 +1,497 @@
+# [](#load-data-using-sql)Load data using SQL
+
+If the **Load data** wizard does not meet your needs, or you prefer to write directly in SQL, you can enter SQL and run it in the **Firebolt Workspace**, or use an API.
+
+Before you can load data using a SQL script, you must register with Firebolt, and create a database and an engine.
+
+A general workflow to load data using SQL is shown in the following diagram, with the highlighted path representing the SQL workflow and the muted path representing using the **Load data** wizard:
+
+![You can use either the load data wizard or SQL to create a database, engine, and then load data.](../../assets/images/load_data_sql_workflow.png)
+
+For more information on how to register, create a database and engine using the **Firebolt Workspace**, see the [Get Started](/Guides/getting-started/) guide. To create an engine using SQL, use [CREATE ENGINE](/sql_reference/commands/engines/create-engine.html). You can check how many engines are defined in your current account using [SHOW ENGINES](/sql_reference/commands/metadata/show-engines.html). For more information and examples of how to create engines, see [Work with engines using DDL](/Guides/operate-engines/working-with-engines-using-ddl.html). To create a database, use [CREATE DATABASE](/sql_reference/commands/data-definition/create-database.html). You can check how many databases (i.e., catalogs) are defined in your current account using [SHOW CATALOGS](/sql_reference/commands/metadata/show-catalogs.html). Next, log into the **Firebolt Workspace** and enter SQL into the script tab in the **SQL Editor**.
+
+The following code examples show different workflows based on need and complexity:
+
+- [The simplest COPY FROM workflow](#the-simplest-copy-from-workflow)
+- [Define a schema, create a table, and load data](#define-a-schema-create-a-table-and-load-data)
+- [Load multiple files into a table](#load-multiple-files-into-a-table)
+- [Filter data before loading using OFFSET and LIMIT](#filter-data-before-loading-using-offset-and-limit)
+- [Aggregating data during data load](#aggregating-data-during-data-load)
+- [Update an existing table from an external table](#update-an-existing-table-from-an-external-table)
+- [Load source file metadata into a table](#load-source-file-metadata-into-a-table)
+- [Continue loading even with errors](#continue-loading-even-with-errors)
+- [Log errors during data load](#log-errors-during-data-load)
+
+## [](#the-simplest-copy-from-workflow)The simplest COPY FROM workflow
+
+Although there are many options to handle different data loading workflows, `COPY FROM` requires only two parameters:
+
+1. The name of the table that you are loading data into.
+2. A location to load the data from.
+
+An example of the **simplest** way to invoke `COPY FROM` is:
+
+```
+COPY INTO tutorial FROM 
+'s3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv' WITH HEADER=TRUE;
+```
+
+The previous code creates a table named `tutorial`, reads a CSV file with headers from a public Amazon S3 bucket, automatically generates a schema, and loads the data.
+
+If the data is contained in an Amazon S3 bucket with restricted access, you will need to provide credentials. The following example shows how to provide credentials and read a file with headers, and automatically generate a schema:
+
+```
+COPY INTO tutorial 
+FROM 's3://your_s3_bucket/your_file.csv'
+WITH
+CREDENTIALS = (
+    AWS_ROLE_ARN='arn:aws:iam::123456789012:role/my-firebolt-role'
+)
+HEADER=TRUE AUTO_CREATE=TRUE;
+```
+
+Firebolt supports authentication using both permanent AWS access keys and temporary security credentials obtained through Amazon’s [AssumeRole](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html) feature. To provide your credentials for the previous example, follow these steps:
+
+#### [](#static-credentials)Static Credentials
+
+Replace `<aws_access_key_id>` with an AWS access key ID associated with an AWS user or IAM role. The access key ID is a 20-character string (e.g., AKIAIOSFODNN7EXAMPLE). Replace `<aws_secret_access_key>` with the AWS secret access key associated with the AWS user or IAM role. The secret access key is a 40-character string (e.g., wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY). You can also specify an `AWS_SESSION_TOKEN`.
+
+**Example:**
+
+```
+COPY INTO tutorial 
+FROM 's3://test-bucket/data.csv'
+WITH
+CREDENTIALS = (
+    AWS_ACCESS_KEY_ID = 'AKIAIOSFODNN7EXAMPLE' AWS_SECRET_ACCESS_KEY = 'wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY'
+)
+```
+
+#### [](#assume-role-authentication)Assume Role Authentication
+
+Replace with your role's Amazon Resource Name (ARN) of the IAM role that you want Firebolt to assume. This method gives Firebolt temporary credentials to authenticate and access your Amazon S3 bucket.
+
+**Example:**
+
+```
+COPY INTO tutorial 
+FROM 's3://test-bucket/data.csv'
+WITH
+CREDENTIALS = (
+    AWS_ROLE_ARN='arn:aws:iam::746669185839:role/example'
+)
+```
+
+## [](#define-a-schema-create-a-table-and-load-data)Define a schema, create a table, and load data
+
+You can also load data into an existing table using your own schema definition. Manually defining your own schema, can give you finer control over data ingestion. This example contains the following two steps:
+
+1. Create the target table.
+   
+   Create a table to load the data into, as shown in the following code example:
+   
+   ```
+    CREATE TABLE IF NOT EXISTS levels (
+    LevelID INT,
+    Name TEXT,
+    GameID INT,
+    LevelType TEXT,
+    MaxPoints INT,
+    PointsPerLap DOUBLE,
+    SceneDetails TEXT
+   );
+   ```
+   
+   The previous code example creates a table named `levels`, and defines each of the columns with a name and data type. For more information about the data types that Firebolt supports, see [Data types](/sql_reference/data-types.html).
+2. Run COPY FROM.
+   
+   Use COPY FROM to load the data from an Amazon S3 bucket into the levels table, as shown in the following code example:
+   
+   ```
+    COPY INTO levels
+    FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+    WITH TYPE = CSV
+    HEADER = TRUE;
+   ```
+   
+   The previous code example reads data from a Firebolt test data set from the fictional [Ultra Fast Gaming Inc.](https://help.firebolt.io/t/ultra-fast-gaming-firebolt-sample-dataset/250) company. The `levels` data set is in CSV format, but you can also use `COPY FROM` to read files in `Parquet` format. If you are reading in a `CSV` file and specify `HEADER = TRUE`, then Firebolt expects the first line of your file to contain column names.
+
+## [](#load-multiple-files-into-a-table)Load multiple files into a table
+
+You can use the `PATTERN` option in `COPY FROM` to load several files at the same time from an Amazon S3 bucket. The `PATTERN` option uses standard regular expressions. For more information about regular expressions, see the Wikipedia [glob programming](https://en.wikipedia.org/wiki/Glob_%60%28programming%60%29) article.
+
+```
+COPY INTO nyc_restaurant_inspections FROM 
+'s3://firebolt-sample-datasets-public-us-east-1/nyc_sample_datasets/nyc_restaurant_inspections/parquet/'
+WITH PATTERN="*.parquet" AUTO_CREATE=TRUE TYPE=PARQUET;
+```
+
+In the previous code example, the following apply:
+
+- **COPY INTO**: Specifies the target table to load the data into.
+- **FROM**: Specifies the S3 bucket location of the data.
+- **WITH PATTERN**= “\*.parquet”: Uses a regular expressions pattern with wildcards (\*) to include all Parquet files in the directory.
+- **AUTO\_CREATE=TRUE**: Automatically creates the table and the schema if the table does not already exist. Parquet files include rich data, and typically have schema information for simple and high-fidelity schema creation. Specifying AUTO\_CREATE to TRUE ensures the schema in the Parquet file is preserved after loading.
+- **TYPE = PARQUET**: Specifies the data format as Parquet.
+
+## [](#filter-data-before-loading-using-offset-and-limit)Filter data before loading using OFFSET and LIMIT
+
+You can use `COPY FROM` with the `LIMIT` and `OFFSET` clauses to filter out data before you load it into Firebolt. The following example demonstrates how to filter the source data by skipping the first five rows of data and inserting only the next three rows.
+
+```
+COPY offset_limit
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+OFFSET 5 LIMIT 3
+WITH TYPE = CSV HEADER = TRUE;
+```
+
+In the previous code example, the following apply:
+
+- **OFFSET**: Specifies a non-negative number of rows that are skipped before returning results from the query.
+- **LIMIT**: Restricts the number of rows that are included in the result set.
+- **TYPE = CSV**: Specifies the data format as CSV.
+- **HEADER**: Specifies that the first row of the source file contains column headers.
+
+For more information about `OFFSET` and `LIMIT`, see [SELECT Query Syntax](/sql_reference/commands/queries/select.html).
+
+## [](#aggregating-data-during-data-load)Aggregating data during data load
+
+If you frequently use [aggregation functions](/sql_reference/functions-reference/aggregation/) such as `COUNT`, `MAX`, or `SUM`, you can perform these aggregations on top of an external table without loading the raw data into Firebolt. This approach allows you to avoid costs associated with importing and storing the dataset, particularly if you don’t need to store the originating data set.
+
+The following example shows how to aggregate data using an [external table](/Guides/loading-data/working-with-external-tables.html). Then, define a table in the Firebolt database with the desired aggregations. Finally, insert data from the external table into the internal table. This example contains the following three steps:
+
+1. Create an external table linked to files in an Amazon S3 bucket.
+   
+   The following code creates an external table that links to files in Amazon S3 bucket. The table has a defined schema that matches the type and names of the originating data:
+   
+   ```
+    CREATE EXTERNAL TABLE IF NOT EXISTS ex_playstats (
+      GameID INTEGER,
+      PlayerID INTEGER,
+      StatTime TIMESTAMPNTZ,
+      SelectedCar TEXT,
+      CurrentLevel INTEGER,
+      CurrentSpeed REAL,
+      CurrentPlayTime BIGINT,
+      CurrentScore BIGINT,
+      Event TEXT,
+      ErrorCode TEXT,
+      TournamentID INTEGER) 
+    URL = 's3://firebolt-sample-datasets-public-us-east-1/gaming/parquet/playstats/'
+    OBJECT_PATTERN = '*'
+    TYPE = (PARQUET);
+   ```
+   
+   The previous code uses `OBJECT_PATTERN` to link all (\*) files inside the specified directory contained in `URL`, and `TYPE` to specify the file format.
+2. Define a table in the Firebolt database with the desired aggregations, as shown in the following code example:
+   
+   ```
+    CREATE TABLE IF NOT EXISTS playstats_max_scores (
+      PlayerID INTEGER,
+      TournamentID INTEGER,
+      MaxCurrentLevel INTEGER,
+      MaxCurrentSpeed REAL,
+      MaxCurrentScore BIGINT
+    ) PRIMARY INDEX TournamentID, PlayerID;
+   ```
+   
+   The previous code creates a table with the aggregate values `MaxCurrentLevel`, `MaxCurrentSpeed`, and `MaxCurrentScore`.
+3. Insert data from the external table into the internal table using the aggregate functions, as shown in the following code example:
+
+```
+    INSERT INTO playstats_max_scores 
+    SELECT PlayerID,  
+      TournamentID,
+      MAX(CurrentLevel),
+      MAX(CurrentSpeed),
+      MAX(CurrentScore)
+    FROM ex_playstats
+    GROUP BY ALL
+```
+
+The previous code calculates the aggregate function `MAX` before loading the data into the `playstats_max_scores` table.
+
+## [](#update-an-existing-table-from-an-external-table)Update an existing table from an external table
+
+Firebolt saves metadata including virtual columns, and the source file’s name, size and timestamp when mapping data from an Amazon S3 bucket to a Firebolt database. You can query this metadata directly for troubleshooting and analysis, or use it to find new data, as shown in this example.
+
+To load only new and updated data from an Amazon S3 bucket into an existing table, use an external table and two temporary tables. This section guides you through creating a new table, which will serve as the existing table in a complete example. If you already have an existing table, its schema definition must include the file timestamp and file name metadata. For more information about these metadata columns, see **Using metadata virtual columns** in [Work with external tables](/Guides/loading-data/working-with-external-tables.html).
+
+The full workflow involves creating an internal source data table, an external table linked to the source data, and two temporary tables for the latest timestamp and updated data. The `updates_table` selects new data and uses an inner join to insert these records into your existing table, as illustrated in the diagram below:
+
+![Use an external table and two temporary tables to update a main internal table by timestamp.](../../assets/images/workflow_update_from_external_table.png)
+
+This example contains the following nine steps:
+
+1. Create a table
+   
+   The following code example shows you how to create a `players` table from a sample players dataset, and then copy data from a parquet file in an Amazon S3 bucket into it:
+   
+   ```
+    CREATE TABLE IF NOT EXISTS
+    players (
+      PlayerID INTEGER,
+      Nickname TEXT,
+      Email TEXT,
+      AgeCategory TEXT,
+      Platforms ARRAY (TEXT NULL),
+      RegisteredOn DATE,
+      IsSubscribedToNewsletter BOOLEAN,
+      InternalProbabilityToWin DOUBLE PRECISION,
+      SOURCE_FILE_NAME TEXT,
+      SOURCE_FILE_TIMESTAMP TIMESTAMPNTZ)
+      PRIMARY INDEX agecategory, registeredon;
+   ```
+   
+   The previous code example defines the schema for the players table, which includes the [metadata columns](/Guides/loading-data/working-with-external-tables.html) `SOURCE_FILE_NAME` and `SOURCE_FILE_TIMESTAMP`.
+2. Create an external table
+   
+   Use an external table to query the source data directly to compare it to data in your existing table. The advantages of using an external table to check for new data are as follows:
+   
+   - An external table links to the data source without loading it into a database, which avoids costs associated with importing and storing it.
+   - Using an external table isolates data operations to reduce the risk of corrupting data contained in the main `players` table.
+   
+   The following code example creates an external players\_ext table linked to the source data:
+   
+   ```
+    CREATE EXTERNAL TABLE IF NOT EXISTS
+    players_ext (
+      PlayerID INTEGER,
+      Nickname TEXT,
+      Email TEXT,
+      AgeCategory TEXT,
+      Platforms ARRAY (TEXT NULL),
+      RegisteredOn PGDATE,
+      IsSubscribedToNewsletter BOOLEAN,
+      InternalProbabilityToWin DOUBLE PRECISION)
+    URL = 's3://firebolt-sample-datasets-public-us-east-1/gaming/parquet/players/'
+    OBJECT_PATTERN = '*'
+    TYPE = (PARQUET);
+   ```
+   
+   The previous code example defines the schema for parquet data and links to all parquet files in the Amazon S3 bucket that contains the source data.
+   
+   If you are using an external table to link to data in parquet format, the order of the columns in the external table does not have to match the order of the columns in the source data. If you are reading data in csv format, the order must match the order in the source data.
+3. Copy data from the `players_ext` external table into an internal `players` table, as shown in the following code example:
+   
+   ```
+    INSERT INTO players
+    SELECT *,
+      $SOURCE_FILE_NAME,
+      $SOURCE_FILE_TIMESTAMP
+    FROM players_ext
+   ```
+4. Create a temporary table that contains the most recent timestamp from your existing table, as shown in the following code example:
+   
+   ```
+    CREATE TABLE IF NOT EXISTS control_maxdate AS (
+    SELECT MAX(source_file_timestamp) AS max_time
+    FROM players
+    );
+   ```
+   
+   The previous code example uses an aggregate function `MAX` to select the most recent timestamp from the existing `players` table.
+5. Create a temporary table to select and store data that has a newer timestamp than that contained in the control\_maxdate table, as shown in the following code example:
+   
+   ```
+    CREATE TABLE IF NOT EXISTS updates_table AS (
+    WITH external_table AS (
+    SELECT *,
+      $SOURCE_FILE_NAME AS source_file_name_new,
+      $SOURCE_FILE_TIMESTAMP AS source_file_timestamp_new,
+    FROM players_ext
+    WHERE $source_file_timestamp > (SELECT max_time FROM control_maxdate)
+    AND playerid IN (SELECT DISTINCT playerid FROM players)
+    )
+    SELECT
+    e.*
+    FROM players f
+    INNER JOIN external_table e
+    ON f.playerid = e.playerid
+    );
+   ```
+   
+   The previous code example creates an `updates_table` using a `SELECT` statement to filter out data that is older than the previously recorded timestamp. The code includes a table alias `e`, which refers to `external_table`, and the table alias `f`, which refers to the `players` table. The `INNER JOIN` uses `playerid` to match rows in the external table to those in the `player` table, and then updates the `players` table.
+6. Delete records from the original players table that have been updated, based on matching player IDs in the `updates_table`, as shown in the following code example:
+   
+   ```
+    DELETE FROM players
+    WHERE playerid IN (SELECT playerid FROM updates_table);
+   ```
+7. Insert updated records from the `updates_table`, including a new timestamp, into the `players` table to replace the deleted records from the previous step, as shown in the following example:
+   
+   ```
+    INSERT INTO players
+    SELECT
+      playerid,
+      nickname,
+      email,
+      agecategory,
+      platforms,
+      registeredon,
+      issubscribedtonewsletter,
+      internalprobabilitytowin,
+      source_file_name_new,
+      source_file_timestamp_new
+    FROM updates_table;
+   ```
+8. Insert any entirely new, rather than updated, records into the `players` table, as shown in the following code example:
+   
+   ```
+    INSERT INTO players
+    SELECT *,
+      $SOURCE_FILE_NAME,
+      $SOURCE_FILE_TIMESTAMP
+    FROM players_ext
+    WHERE $SOURCE_FILE_TIMESTAMP > (SELECT max_time FROM control_maxdate)
+    AND playerid NOT IN (SELECT playerid FROM players);
+   ```
+9. Clean up resources. Remove the temporary tables used in the update process as shown in the following code example:
+   
+   ```
+    DROP TABLE IF EXISTS control_maxdate;
+    DROP TABLE IF EXISTS updates_table;
+   ```
+
+## [](#load-source-file-metadata-into-a-table)Load source file metadata into a table
+
+When you load data from an Amazon S3 bucket, Firebolt uses an external table which holds metadata about your source file to map into a Firebolt database. You can load metadata from the virtual columns contained in the external file into a table. You can use the name, timestamp and file size to determine the source of a row of data in a table. When adding data to an existing table, you can use this information to check whether new data is available, or to determine the vintage of the data. The external table associated with your source file contains the following fields:
+
+- `source_file_name` - the name of your source file.
+- `source_file_timestamp` - the date that your source file was modified in the Amazon S3 bucket that it was read from.
+- `source_file_size` - the size of your source file in bytes.
+
+The following code example shows you how to create and load metadata into a `levels_meta` table, which contains only the metadata:
+
+```
+    CREATE TABLE levels_meta (
+      day_of_creation date, 
+      name_of_file text, 
+      size_of_file int);
+    COPY levels_meta(
+      day_of_creation $source_file_timestamp, 
+      name_of_file $source_file_name, 
+      size_of_file $source_file_size) 
+    FROM  's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+    WITH AUTO_CREATE = TRUE
+    HEADER = TRUE
+    TYPE = CSV;
+```
+
+The following code shows you how to read in the source data from the Amazon S3 bucket and add the metadata as new columns in that table:
+
+```
+CREATE TABLE IF NOT EXISTS levels_meta_plus (
+	"LevelID" INT,
+	"Name" TEXT,
+	"GameID" INT,
+	"LevelType" TEXT,
+	"MaxPoints" INT,
+	"PointsPerLap" DOUBLE,
+	"SceneDetails" TEXT,
+	day_of_creation date,
+	name_of_file text,
+	size_of_file int
+);
+
+COPY INTO levels_meta_plus (
+  "LevelID",    
+   "GameID",
+   "Name",
+  "LevelType",
+  "MaxPoints",
+  "PointsPerLap",
+  "SceneDetails",
+  day_of_creation $source_file_timestamp,  
+  name_of_file $source_file_name,      	
+  size_of_file $source_file_size
+)
+FROM  's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH
+HEADER = TRUE
+TYPE = CSV;
+```
+
+For more information about metadata, see **Using metadata virtual columns** in [Work with external tables](/Guides/loading-data/working-with-external-tables.html).
+
+## [](#continue-loading-even-with-errors)Continue loading even with errors
+
+By default, if Firebolt runs into an error when loading your data, the job will stop loading and end in error. If you want to continue loading your data even in the presence of errors, set `MAX_ERRORS_PER_FILE` to a percentage or integer larger than `0`. `COPY FROM` will then continue to load data until it exceeds the specified percent based on the total number of rows in your data. If you enter an integer between `0` and `100`, `COPY FROM` will interpret the integer as a percentage of rows. You can specify only `0%` or `100%`.
+
+For example, if `MAX_ERRORS_PER_FILE` is set to `0` or `0%`, `COPY FROM` will load data until one row has an error, and then return an error. Setting `MAX_ERRORS_PER_FILE` to either `100` or `100%` allows the loading process to continue even if every row has an error. If all rows have errors, no data will load into the target table.
+
+The following code example loads a sample CSV data set with headers, and will finish the loading job even if every row contains an error.
+
+```
+COPY INTO new_levels_auto
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH AUTO_CREATE = TRUE
+HEADER = TRUE
+TYPE = CSV
+MAX_ERRORS_PER_FILE = '100%';
+```
+
+In the previous code example, the following apply:
+
+- `COPY INTO new_levels_auto`: Creates a new table named `new_levels_auto`. The `INTO` clause is optional. If the table already exists, `COPY FROM` will add the rows to the existing table.
+- `FROM`: Specifies the S3 bucket location of the data. In this example, the dataset is located in a publicly accessible bucket, so you do not need to provide credentials.
+- `AUTO_CREATE=TRUE`: Creates a target table and automatically infers the schema.
+- `HEADER=TRUE`: Specifies that the first row of the source file contains column headers.
+- `TYPE`: Specifies the data format of the incoming data.
+- `MAX_ERRORS_PER_FILE`: Specified as an integer or literal text. In the previous example, `MAX_ERRORS_PER_FILE` uses text.
+
+## [](#log-errors-during-data-load)Log errors during data load
+
+`COPY FROM` supports an option to generate error files that describe the errors encountered and note the rows with errors. To store these files in an Amazon S3 bucket, you must provide credentials to allow Firebolt to write to the bucket.
+
+The following example sets an error handling threshold and specifies an Amazon S3 bucket as the source data and another to write the error file:
+
+```
+COPY INTO my_table
+FROM 's3://my-bucket/data.csv'
+WITH
+CREDENTIALS = (
+  AWS_ROLE_ARN='arn:aws:iam::123456789012:role/my-firebolt-role'
+)
+MAX_ERRORS_PER_FILE = '100%'
+ERROR_FILE = 's3://my-bucket/error_logs/'
+ERROR_FILE_CREDENTIALS = (
+  AWS_ROLE_ARN='arn:aws:iam::123456789012:role/my-firebolt-role'
+)
+HEADER = TRUE
+```
+
+In the previous code example, the following apply:
+
+- `COPY INTO`: Specifies the target table to load the data into.
+- `FROM`: Specifies the S3 bucket location of the data.
+- `CREDENTIALS`: Specifies AWS credentials to access information in the Amazon S3 bucket that contains the source data. AWS [AssumeRole](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html) authentication is used for dynamic, temporary credentials. For more Information about credentials and how to set them up, see [The simplest COPY FROM workflow](/Guides/loading-data/loading-data-sql.html#the-simplest-copy-from-workflow).
+- Error Handling:
+  
+  - `MAX_ERRORS_PER_FILE = ‘100%’`: Allows errors in up to `100%` of the rows per file before the load data job fails.
+  - `ERROR_FILE`: Specifies the Amazon S3 bucket location to write the error file.
+- `HEADER = TRUE`: Indicates that the first row of the CSV file contains column headers.
+
+**How to examine the error files**
+
+If you specify an S3 path with the necessary permissions for an error file and the `COPY FROM` process encounters errors, two different files will be generated in your bucket. The following queries show you how to load these error files into new tables so that you can query and examine the error details and the corresponding rows.
+
+The following query loads the `error_reasons` csv file, which contains a header with column names:
+
+```
+COPY error_reasons FROM 's3://my-bucket/error_logs/' 
+WITH PATTERN='*error_reasons*.csv' HEADER=TRUE;
+
+SELECT * from error_reasons;
+```
+
+The following query loads a file containing all rows that encountered errors. Although this file has no header, the table schema should match that of the source file where the errors occurred.
+
+```
+COPY rejected_rows FROM 's3://my-bucket/error_logs/'
+WITH PATTERN='*rejected_rows*.csv' HEADER=FALSE;
+
+SELECT * FROM rejected_rows;
+```
+
+Configure error handling parameters such as `MAX_ERRORS_PER_FILE`, `ERROR_FILE`, and `ERROR_FILE_CREDENTIALS` to manage how errors are handled, ensure data integrity, and record errors for future review. For more information about `ERROR_FILE` or `ERROR_FILE_CREDENTIALS`, see the **Parameters** section of [COPY FROM](/sql_reference/commands/data-management/copy-from.html).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data_wizard.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data_wizard.md
new file mode 100644
index 0000000..61090f2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_loading_data_wizard.md
@@ -0,0 +1,185 @@
+# [](#load-data-using-a-wizard)Load data using a wizard
+
+The **Load data** wizard can help you get started loading data from an Amazon S3 bucket using a simple workflow. You can use the wizard to both create an engine and load your data.
+
+A general workflow to load data using the **Load data** wizard is shown in the following diagram as the highlighted decision path compared to using SQL shown in the muted path:
+
+![You can use either the Load data wizard or SQL to create a database, engine, and then load data.](../../assets/images/load_data_wizard_workflow.png)
+
+The wizard also guides you through setting up an AWS connection. To use the wizard, you will need the uniform resource locator (URL) of an Amazon S3 bucket. If credentials are required to access the data that you want to load, you will also need an AWS Key ID and your AWS Secret Key. In most steps in the wizard, you can view the SQL commands associated with your selections in the **Load data** main window by selecting **Show SQL script** in the left navigation pane at the bottom of the window.
+
+To use the wizard, use the following steps:
+
+1. Register and/or log in to the [Firebolt Workspace](https://firebolt.go.firebolt.io/signup).
+2. Select the (+) icon from the left navigation pane next to **Databases**.
+3. Select **Load data** from the drop-down menu, as shown in the following image:
+
+![To launch the wizard, select the plus icon in the left navigation pane of the Firebolt Workspace.](../../assets/images/load_data_wizard_launch.png)
+
+## [](#select-an-engine)Select an engine
+
+![The next step in the wizard is to create an engine.](../../assets/images/load_data_wizard_engine.png)
+
+Select an engine to load data. If the engine that you want to use already exists, select it from the dropdown list next to **Select engine for ingestion**. Otherwise, select **Create new engine** from the dropdown list, and do the following:
+
+1. Enter a name in the **New engine name** text box.
+2. Select an engine size from the drop-down list next to **Node type**. Consider the following when creating a new engine:
+   
+   1. If you are loading data and using Firebolt for the first time, use the smallest engine size (S) and a small dataset to try out Firebolt’s capabilities. Refer to the [Get Started](/Guides/getting-started/) guide for more information.
+   2. If you want to load larger datasets, and a S engine provides insufficient performance, Firebolt recommends **scaling out**, or adding more nodes, first, as shown in the following diagram.
+   
+   ![First try adding more nodes, or scaling out if you need to load a large dataset.](../../assets/images/load_data_scale_out.png)  
+   Scaling out can enhance performance for workloads with many similarly sized files, but it also increases billing costs.
+   
+   Small and medium engines are available for use right away. If you want to use a large or extra-large engine, reach out to support@firebolt.io. For more information, see [Sizing Engines](/Guides/operate-engines/sizing-engines.html).
+3. Select the number of compute nodes to use to load your data next to **Number of nodes**. A node is an individual compute unit within a compute cluster.
+
+<!--THE END-->
+
+- Using more than one node allows Firebolt to load your data and perform operations on your data in parallel on multiple nodes within a single cluster, which can speed up the data loading process.
+- A higher number of nodes also means increased costs for compute resources. You can see the total cost per hour for your selection under Advanced settings, given in Firebolt Units (FBU). Each FBU is equivalent to $0.35 US dollars per hour. Find the right balance between cost and speed for your workload. You must use at least one node.
+
+<!--THE END-->
+
+1. Select the number of clusters next to **Number of clusters**. A cluster is a group of nodes that work together. The following apply:
+   
+   - If you increase the number of clusters, you will add the number of compute nodes that you selected for each added cluster.
+     
+     You can see the total cost per hour for your selection under **Advanced settings**, given in Firebolt Units (FBU). Find the right balance between cost and speed for your workload. You must use at least one cluster.
+2. Select the down arrow next to **Advanced settings** for more options for your engine including setting a time to stop the engine after a period of inactivity.
+
+## [](#set-up-aws-connection)Set up AWS connection
+
+![The first step in the wizard is to connect to AWS and specify an Amazon S3 bucket.](../../assets/images/load_data_wizard_connect.png)
+
+### [](#a-using-public-data-that-do-not-require-access-credentials)A. Using public data that do not require access credentials
+
+- If the data is public and no credentials are needed, simply provide the URL of your Amazon S3 bucket and select **Next Step**.
+
+### [](#b-using-private-data-credentials-required)B. Using Private Data (Credentials Required)
+
+If the data requires credentials for access, you must provide them so that Firebolt can retrieve it from AWS on your behalf. You can choose either **Static Credentials** or **Assume Role Authentication**.
+
+- Use static credentials for simplicity and persistent access when security risks are low, and if your environment requires minimal configuration.
+- Use [AssumeRole](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html) Authentication\** for enhanced security, temporary access, and dynamic role management, particularly in environments requiring fine-grained permissions or cross-account access.
+
+#### [](#1-static-credentials)1. Static Credentials
+
+1. Provide the **URL** for your Amazon S3 bucket.
+2. Enter your **AWS Key ID** and **AWS Secret Key**.
+3. For authentication:
+   
+   - Select **Access Key ID &amp; Secret Key** as your authentication method.
+   - The **AWS Key ID** is a 20-character string associated with an AWS user or IAM role (e.g., `AKIAIOSFODNN7EXAMPLE`).
+   - The **AWS Secret Key** is a 40-character string linked to the AWS Key ID (e.g., `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`).
+   - Optionally, you can also specify an **AWS Session Token**.
+   - For more information about these credentials, see [Create Access Key and Secret ID in AWS](/Guides/loading-data/creating-access-keys-aws.html).
+4. Select **Next Step**.
+
+#### [](#2-assume-role-authentication)2. Assume Role Authentication
+
+1. Select **IAM Role** as your authentication method.
+2. Select **Create an IAM role**. To allow Firebolt to read and write to your Amazon S3 bucket using dynamic credentials, you must do the following:
+   
+   - Create an IAM Role.
+   - Define an **AssumeRole** Policy.
+3. After the role is created in your AWS account and the trust policy is attached, copy the **Amazon Resource Name (ARN)** of the role to your clipboard.
+4. Paste the ARN into the **Amazon Resource Name** field in Firebolt.
+5. Select **Next Step**.
+
+#### [](#3-using-firebolts-test-dataset-if-youre-not-ready-with-your-own-data)3. Using Firebolt’s Test Dataset (If You’re Not Ready with Your Own Data)
+
+If you don’t have your own data ready, you can use Firebolt’s sample dataset from the fictional company [Ultra Fast Gaming Inc](https://help.firebolt.io/t/ultra-fast-gaming-firebolt-sample-dataset/250):
+
+- Use the following Amazon S3 bucket URL: `s3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/`.
+
+Alternatively, you can click the toggle button next to **Use Firebolt Playground Bucket to load sample data**.
+
+1. Select **Next step**.
+
+## [](#select-data-to-ingest)Select data to ingest
+
+![The next step in the wizard is to specify a data source.](../../assets/images/load_data_wizard_source.png)
+
+1. Select the data file that you want to load. Firebolt’s **Load data** wizard currently supports files in both CSV and Parquet formats. The contents of your S3 bucket are shown automatically along with their object type, size, and when the object was last modified.
+2. Enter text or a [prefix](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-prefixes.html) into the search field above **FILE NAME** to filter the list of objects. You can enter either part of the object’s name or the full prefix that it starts with.
+3. Select one file. Firebolt does not support selecting multiple files, or selecting folders.
+4. If you are using Firebolt’s test data, select box next to `levels.csv`.
+5. Select **Next step**.
+
+## [](#set-up-destination)Set up destination
+
+![The next step in the wizard is to specify a data target.](../../assets/images/load_data_wizard_target.png)  
+Specify the table inside a database that you want to load your data into.
+
+1. You can either select an existing database from the drop-down list next to **Select database** or **Create new database**.
+   
+   1. If you created a new database, enter a new database name and a new table to load your data into. Select **Next step**.
+   2. If you selected an existing database, select the table in the database from the drop-down list next to **Select table**, or **Create new table** and provide a new table name.
+2. Select **Next step**.
+
+## [](#format-data)Format data
+
+![The next step in the wizard is to configure your data format.](../../assets/images/load_data_wizard_format.png)  
+A default formatting and error handling scheme shows a preview of your data. You can change the default configuration using the following options:
+
+1. Toggle off **Use default formatting** to show custom formatting options. You can specify options including different file delimiter, quote character, and escape character.
+   
+   - Enter a new value in the text box or select an option from the drop-down arrow next to the option that you want to change.
+   - After each change, the data preview changes to reflect your selection.
+2. Toggle off **Use default error handling** to show the following additional error handling options:
+   
+   - You can specify a file to write errors to. Enter the name of the file that you want to write including the URL address for an Amazon S3 bucket that contains that file, and your AWS credentials. Firebolt will use these credentials to write an error file on your behalf. The output file should be in the following format:
+     
+     ```
+     s3://<your_bucket_name>/<your_error_file.ext>>
+     ```
+   - **Max errors per file** - Specify the percentage of errors you want to allow during data loading. By default, the maximum is set to `0%`, meaning any error will stop the loading process. If you wish to continue loading despite errors, set **Max errors per file** to a non-zero value. For example, entering `10%` or `10` allows the process to continue until errors affect `10%` of the rows.
+3. Select **Next step**.
+
+## [](#map-data)Map data
+
+![The next step in the wizard is to map your data to your table.](../../assets/images/load_data_wizard_map.png)
+
+Map the values in your data to columns into the target table. Firebolt automatically detects the schema of your data and displays information including the detected column names, type, and a preview of the data in the next window. By default, each column has a checkbox next to its name. Deselect the box if you don’t want to load the column. You can adjust the schema for the following items:
+
+1. **Type** - you can change the [data type](/sql_reference/data-types.html) of the column.
+2. **Nullable** - toggle this switch to `ON` if the columns in your data can contain `NULL` values. If this value is toggled off for a column, and that column contains `NULL` values, then the wizard will generate an error and stop loading.
+3. **Primary index** - toggle this switch to `ON` for the columns you want to include in your primary index.
+   
+   - One of Firebolt’s key optimization strategies is to use a primary index that ties to columns that are used frequently in `WHERE`, `JOIN`, `GROUP_BY`, and other clauses used for sorting. Selecting the best primary index, which is a sparse index, can reduce query run times significantly by reducing the data set that the query scans. A primary index also allows Firebolt to manage updates, deletions and insertions to tables and provide optimal query performance.
+   - It’s best if you choose a primary index based on knowledge about your data and query history. If you don’t know which column(s) to select, you can use Firebolt’s suggested primary indexes by keeping **Automatically assign primary indexes** checked, as shown in the following image:
+     
+     ![The next step in the wizard is to map your data to your table.](../../assets/images/load_data_wizard_autopi.png)
+     
+     Using Firebolt’s suggested primary index is preferable to having none. In the absence of a query history, Firebolt prioritizes choosing a column for the primary index in the following order: a datetime or timestamp column, a column with low cardinality, or the first column.
+   - If you include multiple columns as a composite primary index, they will be added in sort order. For example, if you select `column_1` first, then select `column_3`, then `column_3` will be added as a primary index after `column_1`. This means `column_1` will be used first as a sparse index, followed by `column_3`. If you choose more than one primary index, the order of sorting appears next to the toggle switch under the **Primary Index** column. In the previous example, the number `1` appears next to `column_1` and a number `2` appears next to `column_3`. To achieve optimal results, choose indexes in the order of their cardinality, or the number of unique values. Start with the column that has the highest number of unique values as your first primary index, followed by the column with the next highest cardinality. For more information about how to choose a primary index, see [Primary index](/Overview/indexes/primary-index.html).
+4. Select **Next step**.
+
+## [](#review-configuration)Review configuration
+
+The **Review configuration** window displays your selections in SQL code. If you want to change the configuration, you must go back through the **Load data** wizard workflow to the section that you want to change and amend your selection. You cannot edit the SQL code in the **Review configuration** window.
+
+1. Select **Run ingestion** to load your data. The **Load data** wizard completes and your configuration will run in the **Develop Space** inside the **Firebolt Workspace**. The main window in the **SQL editor** contains the SQL script that configures your load data selections, and may contain several queries.
+
+## [](#view-results-and-query-statistics)View results and query statistics
+
+![The next step in the wizard is to specify a data source.](../../assets/images/load_data_wizard_results.png)
+
+After your load data job completes, you can view the results of each query that was configured by the **Load data** wizard in Firebolt user interface under **Results** in the bottom window. If you need to edit the queries, you can enter the change into the **SQL Editor** directly and select **Run**.
+
+1. View information about your query in the **Statistics** tab. This information contains the status of the query, how long it took to run, and the number of rows processed during the data loading job.
+2. View metrics in the **Query Profile** tab for each operator used in your query. Select an operation to view metrics. These metrics include the following:
+   
+   1. The output cardinality - the number of rows each operator produced.
+   2. The thread time - the sum of the wall clock time that threads spent to run the selected operation across all nodes.
+   3. The CPU time - the sum of the time that threads that ran the operator were scheduled on a CPU core.
+   4. The output types - the data types of the result of the query.
+   
+   You can use metrics in the **Query Profile** tab to analyze and measure the efficiency and performance of your query. For example, If the CPU time is much smaller than thread time, the input-output (IO) latency may be high or the engine that you are using may be running multiple queries at the same time. For more information, see [Example with ANALYZE](/sql_reference/commands/queries/explain.html).
+3. View monitoring information including the percent CPU, memory, disk use and cache read in the **Engine monitoring** tab. Information is shown from the last 5 minutes by default. Select a different time interval from the drop-down menu next to **Last 5 minutes**. You can also select the **Refresh** icon next to the drop-down menu to update the graphical information.
+4. View detailed information associated with each query in the **Query history** tab. This information includes the query status, start time, number of rows and bytes scanned during the load, user and account information. You can do the following:
+   
+   1. Select the **Refresh** icon to update the query history and ID.
+   2. Select the filter icon (![filter icon](../../assets/images/filter-icon.png)) to remove or add columns to display.
+   3. Select the **More options** icon (![more options icon](../../assets/images/more_options_icon.png)) to export the contents of the Query history tab to a JSON or CSV file.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_external_tables.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_external_tables.md
new file mode 100644
index 0000000..36e5d08
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_external_tables.md
@@ -0,0 +1,87 @@
+# [](#work-with-external-tables)Work with external tables
+
+Firebolt supports loading data using *external tables*, which are different from [fact and dimension tables](/Overview/indexes/using-indexes.html#firebolt-managed-tables). External tables store metadata objects that reference files stored in an Amazon S3 bucket, rather than actual data.
+
+To create an external table, run the [CREATE EXTERNAL TABLE](/sql_reference/commands/data-definition/create-external-table.html) command. After you create an external table, use the [INSERT](/sql_reference/commands/data-management/insert.html) command to load the data from the external table into a fact or dimension table. Data that you ingest must be in the same AWS Region as the target Firebolt database.
+
+Although you can run a query over an external table to return query results, we don’t recommend it. Such a query will be significantly slower than the same query run over the same data in a fact or dimension table because of the data transfer between Firebolt and your data store. We strongly recommend that you use external tables only for ingestion, specifying the table and its columns only in the `FROM` clause of an `INSERT` statement.
+
+## [](#workflows)Workflows
+
+For a simple end-to-end workflow that demonstrates loading data into Firebolt, see the [Getting started tutorial](/Guides/getting-started/).
+
+## [](#supported-file-formats)Supported file formats
+
+Firebolt supports loading the following source file formats from S3: `PARQUET`, `CSV`, `TSV`, `AVRO`, `JSON` ([JSON Lines](https://jsonlines.org/)), and `ORC`. We are quick to add support for more types, so make sure to let us know if you need it.
+
+## [](#using-metadata-virtual-columns)Using metadata virtual columns
+
+Firebolt external tables include metadata virtual columns that Firebolt populates with useful system data during ingestion. Firebolt includes these columns automatically. You don’t need to specify them in the `CREATE EXTERNAL TABLE` statement.
+
+When you use an external table to ingest data, you can explicitly reference these columns to ingest the metadata. First, you define the columns in a `CREATE FACT|DIMENSION TABLE` statement. Next, you specify the virtual column names to select in the `INSERT INTO` statement, with the fact or dimension table as the target. You can then query the columns in the fact or dimension table for analysis, troubleshooting, and to implement logic. For more information, see the example below.
+
+The metadata virtual columns listed below are available in external tables.
+
+Metadata column name Description Data type `$source_file_name` The full path of the row data’s source file in Amazon S3, without the bucket. For example, with a source file of `s3://my_bucket/xyz/year=2018/month=01/part-00001.parquet`, the `$source_file_name` is `xyz/year=2018/month=01/part-00001.parquet`. TEXT `$source_file_timestamp` The UTC creation timestamp in second resolution of the row’s source file in Amazon S3. (S3 objects are immutable. In cases where files are overwritten with new data - this will be Last Modified time.) TIMESTAMPTZ `$source_file_size` Size in bytes of the row’s source file in Amazon S3. BIGINT
+
+### [](#examplequerying-metadata-virtual-column-values)Example–querying metadata virtual column values
+
+The query example below creates an external table that references an AWS S3 bucket that contains Parquet files from which Firebolt will ingest values for `c_id` and `c_name`.
+
+```
+CREATE EXTERNAL TABLE my_external_table
+  (
+    c_id    INTEGER,
+    c_name  TEXT
+  )
+  CREDENTIALS = ( 
+    AWS_ACCESS_KEY_ID = 'AKIAIOSFODNN7EXAMPLE' AWS_SECRET_ACCESS_KEY = 'wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY'
+  )
+  URL = 's3://my_bucket/'
+  OBJECT_PATTERN= '*.parquet'
+  TYPE = (PARQUET);
+```
+
+The query example below creates a dimension table, which will be the target for the data to be ingested. The statement defines two additional columns, `$source_file_name` and `$source_file_timestamp`, to contain metadata values that Firebolt creates automatically for the external table.
+
+```
+CREATE DIMENSION TABLE my_dim_table_with_metadata
+(
+   c_id INTEGER,
+   c_name TEXT,
+   source_file_name TEXT,
+   source_file_timestamp TIMESTAMPTZ,
+);
+```
+
+Finally, the `INSERT` query below ingests the data from `my_external_table` into `my_dim_table_with_metadata`. The `SELECT` clause explicitly specifies the metadata virtual columns, which is a requirement.
+
+```
+INSERT INTO
+    my_dim_table_with_metadata
+SELECT
+    *,
+    $source_file_name,
+    $source_file_timestamp
+FROM
+    my_external_table;
+```
+
+An example `SELECT` query over `my_dim_table_with_metadata` shows that the source data file (minus the `s3://my_bucket` portion of the file path) and file timestamp are included in the dimension table for each row.
+
+```
+SELECT * FROM my_dim_table_with_metadata;
+```
+
+```
++-----------+---------------------+------------------------ +------------------------+
+| c_id      | c_name              | source_file_name        | source_file_timestamp  |
++-----------+---------------------+-------------------------+------------------------+
+| 11385     | ClevelandDC8933     | central/cle.parquet     | 2021-09-10 10:32:03+00 |
+| 12386     | PortlandXfer9483    | west/pdx.parquet        | 2021-09-10 10:32:04+00 |
+| 12387     | PortlandXfer9449    | west/pdx.parquet        | 2021-09-10 10:32:04+00 |
+| 12388     | PortlandXfer9462    | west/pdx.parquet        | 2021-09-10 10:32:04+00 |
+| 12387     | NashvilleXfer9987   | south/bna.parquet       | 2021-09-10 10:33:01+00 |
+| 12499     | ClevelandXfer8998   | central/cle.parquet     | 2021-09-10 10:32:03+00 |
+[...]
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_load_json_data.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_load_json_data.md
new file mode 100644
index 0000000..bb95ebc
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_load_json_data.md
@@ -0,0 +1,193 @@
+# [](#load-semi-structured-json-data)Load semi-structured JSON data
+
+Semi-structured data does not follow a strict table format but contains structured tags or key-value pairs. JSON is an example of semi-structured data. Firebolt supports the following three ways to ingest JSON based on how your data changes and how you query it:
+
+- [Load JSON into a fixed schema](#load-json-into-a-fixed-schema) if your JSON data has a stable set of fields with shallow nesting.
+- [Transform the input during load](#transform-the-input-during-load) if your table must always contain certain fields.
+- [Store JSON as text](#store-json-as-text) if you need only specific fields on demand or if the table structure changes frequently.
+
+This document shows you how to load data using each of the previous methods and the sample JSON dataset in the following section.
+
+### [](#sample-json-dataset)Sample JSON dataset
+
+The following JSON data shows two session records for a website, where each line represents a single JSON object. This sample data is used in each of the examples in this document.
+
+```
+[
+  {
+    "id": 1,
+    "StartTime": "2020-01-06 17:00:00",
+    "Duration": 450,
+    "tags": ["summer-sale", "sports"],
+    "user_agent": {
+      "agent": "Mozilla/5.0",
+      "platform": "Windows NT 6.1",
+      "resolution": "1024x4069"
+    }
+  },
+  {
+    "id": 2,
+    "StartTime": "2020-01-05 12:00:00",
+    "Duration": 959,
+    "tags": ["gadgets", "audio"],
+    "user_agent": {
+      "agent": "Safari",
+      "platform": "iOS 14"
+    }
+  }
+]
+```
+
+The following code example creates a staging table that stores the raw JSON data, allowing you to run the subsequent examples:
+
+```
+-- Create a staging table for raw JSON data with one JSON object per row
+DROP TABLE IF EXISTS doc_visits_source;
+CREATE TABLE doc_visits_source (
+  raw_json TEXT
+);
+
+-- Insert raw JSON data as individual rows
+INSERT INTO doc_visits_source (raw_json)
+VALUES
+('{"id": 1, "StartTime": "2020-01-06 17:00:00", "Duration": 450, "tags": ["summer-sale", "sports"], "user_agent": {"agent": "Mozilla/5.0", "platform": "Windows NT 6.1", "resolution": "1024x4069"}}'),
+('{"id": 2, "StartTime": "2020-01-05 12:00:00", "Duration": 959, "tags": ["gadgets", "audio"], "user_agent": {"agent": "Safari", "platform": "iOS 14"}}');
+```
+
+If you want to load JSON data from an Amazon S3 bucket, you can create an external table that references the file as follows:
+
+```
+CREATE EXTERNAL TABLE visits_external (
+  raw_json TEXT
+)
+LOCATION = 's3://your-bucket-name/path/to/json-file/'
+FILE_FORMAT = (TYPE = 'JSON');
+```
+
+## [](#load-json-into-a-fixed-schema)Load JSON into a fixed schema
+
+If your JSON data has a stable set of fields with shallow nesting, you can load it into a table with a fixed schema to simplify queries. Missing keys are assigned default values. This method allows you to query columns directly without additional parsing, making queries faster and easier to write. Extra keys that are not explicitly mapped are excluded from structured tables, making this approach less flexible for changing data. If stored separately in a `TEXT` column, they remain accessible for later extraction.
+
+The following code example uses the previously created `doc_visits_source` table to define columns that map directly to known keys:
+
+```
+-- Create the target table 'visits_fixed' with a fixed schema
+DROP TABLE IF EXISTS visits_fixed;
+CREATE FACT TABLE visits_fixed (
+  id INT DEFAULT 0,
+  start_time TIMESTAMP DEFAULT '1970-01-01 00:00:00',
+  duration INT DEFAULT 0,
+  tags ARRAY(TEXT) DEFAULT []
+)
+PRIMARY INDEX start_time;
+
+-- Insert data into 'visits_fixed' by extracting values from the raw JSON
+INSERT INTO visits_fixed
+SELECT
+  JSON_POINTER_EXTRACT(raw_json, '/id')::INT AS id,
+  TO_TIMESTAMP(TRIM(BOTH '"' FROM JSON_POINTER_EXTRACT(raw_json, '/StartTime')), 'YYYY-MM-DD HH24:MI:SS') AS start_time,
+  JSON_POINTER_EXTRACT(raw_json, '/Duration')::INT AS duration,
+  JSON_POINTER_EXTRACT(raw_json, '/tags')::ARRAY(TEXT) AS tags
+FROM doc_visits_source;
+```
+
+The following table shows the expected results:
+
+id start\_time duration tags 1 1/6/2020 17:00 450 \[“summer-sale”, “sports”] 2 1/5/2020 12:00 959 \[“gadgets”, “audio”]
+
+Important characteristics of the table:
+
+- The mandatory scalar fields, `id`, `start_time`, and `duration`, are stored in separate columns, which makes it easier to filter, sort, or join by these fields.
+- Each column maps directly to a known JSON key, allowing for simpler queries without the need for JSON functions.
+- Default values ensure that the table loads even if some fields are missing or additional keys appear. Extra JSON fields such as `user_agent` with `agent`, `platform`, and `resolution` are ignored and not stored in the table.
+- Array columns are used to store `tags`, which supports arbitrary numbers of values without schema changes.
+
+## [](#transform-the-input-during-load)Transform the input during load
+
+Parsing JSON data during ingestion eliminates the need for subsequent query-time parsing, simplifying and accelerating queries. However, transforming data during load also requires well-defined JSON paths that remain consistent. If the JSON paths change, the load might fail.
+
+The following code example uses the previously created `doc_visits_source` table to parse JSON data as it loads and inserts extracted fields into a Firebolt table named `visits_transformed`. It shows how to use [JSON\_POINTER\_EXTRACT\_KEYS](/sql_reference/functions-reference/JSON/json-pointer-extract-keys.html) and [JSON\_POINTER\_EXTRACT\_VALUES](/sql_reference/functions-reference/JSON/json-pointer-extract-values.html) to store a dynamic key-value pair – `agent_props_keys` and `agent_props_vals` – from a nested object:
+
+```
+DROP TABLE IF EXISTS visits_transformed;
+CREATE FACT TABLE visits_transformed (
+  id INT,
+  start_time TIMESTAMP,
+  duration INT,
+  tags ARRAY(TEXT),
+  agent_props_keys ARRAY(TEXT),
+  agent_props_vals ARRAY(TEXT)
+)
+PRIMARY INDEX start_time;
+
+INSERT INTO visits_transformed
+SELECT
+  JSON_POINTER_EXTRACT(raw_json, '/id')::INT,
+  TO_TIMESTAMP(TRIM(BOTH '"' FROM JSON_POINTER_EXTRACT(raw_json, '/StartTime')), 'YYYY-MM-DD HH24:MI:SS'),
+  JSON_POINTER_EXTRACT(raw_json, '/Duration')::INT,
+  JSON_POINTER_EXTRACT(raw_json, '/tags')::ARRAY(TEXT),
+  JSON_POINTER_EXTRACT_KEYS(raw_json, '/user_agent')::ARRAY(TEXT),
+  JSON_POINTER_EXTRACT_VALUES(raw_json, '/user_agent')::ARRAY(TEXT)
+FROM doc_visits_source;
+```
+
+The following table shows the expected results:
+
+id start\_time duration tags agent\_props\_keys agent\_props\_vals 1 1/6/2020 17:00 450 \[“summer-sale”,”sports”] \[“agent”, “platform”, “resolution”] \[“Mozilla/5.0”, “Windows NT 6.1”, “1024x4069”] 2 1/5/2020 12:00 959 \[“gadgets”,”audio”] \[“agent”, “platform”] \[“Safari”, “iOS 14”]
+
+Important characteristics of the previous table:
+
+- The `user_agent` object is stored in two arrays: `agent_props_keys` and `agent_props_vals`. The [`JSON_POINTER_EXTRACT_KEYS`](/sql_reference/functions-reference/JSON/json-pointer-extract-keys.html) function extracts the keys from the `user_agent` object into the `agent_props_keys` array. The [`JSON_POINTER_EXTRACT_VALUES`](/sql_reference/functions-reference/JSON/json-pointer-extract-values.html) function extracts the corresponding values into the `agent_props_vals` array. Storing keys and values in parallel arrays offers flexibility when the `user_agent` map changes and avoids schema updates for new or removed fields.
+
+A common error may occur if a field path does not exist in the JSON document. Firebolt returns an error because `NULL` values cannot be cast to `INT`. For example, the following query attempts to extract a non-existent field `/unknown_field` and cast it to `INT`, which results in an error:
+
+```
+SELECT JSON_POINTER_EXTRACT(raw_json, '/unknown_field')::INT 
+FROM doc_visits_source;
+```
+
+To avoid this error, use a default value or conditional expression as shown in the following code example:
+
+```
+INSERT INTO visits_transformed
+SELECT
+  CASE 
+    WHEN JSON_POINTER_EXTRACT(raw_json, '/unknown_field') IS NOT NULL 
+    THEN JSON_POINTER_EXTRACT(raw_json, '/unknown_field')::INT 
+    ELSE NULL
+  END AS id
+FROM doc_visits_source;
+```
+
+The following table shows the expected results:
+
+id start\_time duration tags 0 NULL NULL NULL 0 NULL NULL NULL 1 1/6/2020 17:00 450 \[“summer-sale”, “sports”] 2 1/5/2020 12:00 959 \[“gadgets”, “audio”]
+
+## [](#store-json-as-text)Store JSON as text
+
+You can store JSON as a single text column if the data structure changes frequently or if you only need certain fields in some queries. This approach simplifies ingestion since no parsing occurs during loading, but it requires parsing fields at query time, which can make queries more complex if you need to extract many fields regularly.
+
+The following code example uses the previously created intermediary `doc_visits_source` table to create a permanent table that stores raw JSON, allowing you to parse only what you need on demand:
+
+```
+DROP TABLE IF EXISTS visits_raw;
+CREATE FACT TABLE visits_raw (
+  raw_json TEXT
+);
+
+-- Insert data into the 'visits_raw' table from the staging table
+INSERT INTO visits_raw
+SELECT raw_json
+FROM doc_visits_source;
+```
+
+The following table shows the expected results:
+
+raw\_json {“id”: 1, “StartTime”: “2020-01-06 17:00:00”, “Duration”: 450, “tags”: \[“summer-sale”, “sports”], “user\_agent”: {“agent”: “Mozilla/5.0”, “platform”: “Windows NT 6.1”, “resolution”: “1024x4069”}} {“id”: 2, “StartTime”: “2020-01-05 12:00:00”, “Duration”: 959, “tags”: \[“gadgets”, “audio”], “user\_agent”: {“agent”: “Safari”, “platform”: “iOS 14”}}
+
+Important characteristics of the table:
+
+- The `id`, `start_time`, `durations`, and `tags` columns follow the same purpose as in the [previous table example](#transform-the-input-during-load).
+- Each row in the previous table contains a complete JSON object stored in a single `TEXT` column, rather than being parsed into separate fields. This approach is beneficial when the required fields are unknown at ingestion or the JSON structure changes frequently, allowing for flexible data storage without modifying the schema. Fields can be extracted dynamically at query time using Firebolt’s JSON functions, though frequent parsing may increase query complexity and cost.
+- Parsing occurs at query time, which can save upfront processing when data is loaded, but it might increase query complexity and cost if you need to parse many fields frequently.
+- Subsequent queries need to extract fields manually with JSON functions as needed.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_load_parquet_data.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_load_parquet_data.md
new file mode 100644
index 0000000..9594460
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_load_parquet_data.md
@@ -0,0 +1,179 @@
+# [](#load-semi-structured-parquet-data)Load semi-structured Parquet data
+
+Apache Parquet is a binary file format that supports both structured columns and semi-structured data, including arrays, structs, and maps. If these nested structures do not align to a strictly relational schema, they are described as semi-structured. Firebolt’s external tables support extracting these semi-structured fields from Parquet files, treating them similarly as other semi-structured data such as JSON. This document shows how to load and query Parquet data that is stored as structs in arrays or as maps of key-value pairs.
+
+- [Defining external table columns for Parquet arrays and maps](#defining-external-table-columns-for-parquet-arrays-and-maps)
+- [Syntax for defining a Parquet nested structure](#syntax-for-defining-a-parquet-nested-structure)
+- [Example–ingest and work with structs inside Parquet arrays](#exampleingest-and-work-with-structs-inside-parquet-arrays)
+  
+  - [Step 1–create an external table](#step-1create-an-external-table)
+  - [Step 2–create a fact or dimension table](#step-2create-a-fact-or-dimension-table)
+  - [Step 3–insert into the fact table from the external table](#step-3insert-into-the-fact-table-from-the-external-table)
+  - [Step 4–query array values](#step-4query-array-values)
+- [Example–ingest and work with maps](#exampleingest-and-work-with-maps)
+  
+  - [Step 1–create an external table](#step-1create-an-external-table-1)
+  - [Step 2–create a fact or dimension table](#step-2create-a-fact-or-dimension-table-1)
+  - [Step 3–insert into the fact table from the external table](#step-3insert-into-the-fact-table-from-the-external-table-1)
+  - [Step 4–query map values](#step-4query-map-values)
+
+## [](#defining-external-table-columns-for-parquet-arrays-and-maps)Defining external table columns for Parquet arrays and maps
+
+When you set up an external table to ingest Parquet data files, you use a hierarchical dotted notation syntax to define table columns. Firebolt uses this notation to identify the field to ingest.
+
+## [](#syntax-for-defining-a-parquet-nested-structure)Syntax for defining a Parquet nested structure
+
+You specify the top grouping element of a nested structure in Parquet followed by the field in that structure that contains the data to ingest. You then declare the column type using the `ARRAY(<data_type>)` notation, where `<data type>` is the [Firebolt data type](/sql_reference/data-types.html) corresponding to the data type of the field in Parquet.
+
+```
+"<grouping1>.<datafield>" ARRAY(<data_type>)
+```
+
+Examples of this syntax in `CREATE EXTERNAL TABLE` queries are demonstrated below.
+
+## [](#exampleingest-and-work-with-structs-inside-parquet-arrays)Example–ingest and work with structs inside Parquet arrays
+
+Consider the Parquet schema example below. The following elements define an array of structs:
+
+- A single, optional group field, `hashtags`, contains any number of another group, `bag`. This is the top grouping element.
+- The `bag` groups each contain a single, optional group, `array_element`.
+- The`array_element` group contains a single, optional field, `s`.
+- The field `some_value` contains a value that is a `TEXT` type (in binary primitive format).
+
+```
+optional group hashtags (LIST) {
+  repeated group bag {
+    optional group array_element {
+      optional binary some_value (TEXT);
+    }
+  }
+}
+```
+
+The steps below demonstrate the process to ingest the array values into Firebolt. You create an external table, create a fact table, and insert data into the fact table from the external table, which is connected to the Parquet data store.
+
+### [](#step-1create-an-external-table)Step 1–create an external table
+
+The `CREATE EXTERNAL TABLE` example below creates a column in an external table from the Parquet schema shown in the example above. The column definition uses the top level grouping `hashtags` followed by the field `some_value`. Intermediate nesting levels are omitted.
+
+```
+CREATE EXTERNAL TABLE IF NOT EXISTS my_parquet_array_ext_tbl
+(
+  [...,] --additional columns possible, not shown
+  "hashtags.some_value" ARRAY(TEXT)
+  [,...]
+)
+CREDENTIALS = (AWS_KEY_ID = '****' AWS_SECRET_KEY = '*****')
+URL = 's3://my_bucket_of_parquet_goodies/'
+OBJECT_PATTERN = '*.parquet'
+TYPE = (PARQUET);
+```
+
+### [](#step-2create-a-fact-or-dimension-table)Step 2–create a fact or dimension table
+
+Create a fact or dimension table that defines a column of the same `ARRAY(TEXT)` type that you defined in the external table in step 1. The example below demonstrates this for a fact table.
+
+```
+CREATE FACT TABLE IF NOT EXISTS my_parquet_array_fact_tbl
+(
+  [...,] --additional columns possible, not shown
+  some_value ARRAY(TEXT)
+  [,...]
+)
+[...]
+--required primary index for fact table not shown
+--optional partitions not shown
+;
+```
+
+### [](#step-3insert-into-the-fact-table-from-the-external-table)Step 3–insert into the fact table from the external table
+
+The example below demonstrates an `INSERT` statement that selects the array values from Parquet data files using the external table column definition in step 1, and then inserts them into the specified fact table column, `some_value`.
+
+```
+INSERT INTO my_parquet_array_fact_tbl
+  SELECT "hashtags.some_value" AS some_value
+  FROM my_parquet_array_ext_tbl;
+```
+
+### [](#step-4query-array-values)Step 4–query array values
+
+After you ingest array values into the fact table, you can query and manipulate the array using array functions and Lambda functions. For more information, see [Working with arrays](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html).
+
+Use multipart Parquet column names to extract data from nested structures. For simple `ARRAY(TEXT)`, use a single top-level field name.
+
+## [](#exampleingest-and-work-with-maps)Example–ingest and work with maps
+
+External tables connected to AWS Glue currently do not support reading maps from Parquet files.
+
+Parquet stores maps as arrays of key-value pairs, where each key\_value group contains a key and its corresponding value. Consider the Parquet schema example below. The following define the key-value elements of the map:
+
+- A single, optional group, `context`, is a group of mappings that contains any number of the group `key_value`.
+- The `key_value` groups each contain a required field, `key`, which contains the key name as a `TEXT`. Each group also contains an optional field `value`, which contains the value as a `TEXT` corresponding to the key name in the same `key_value` group.
+
+```
+optional group context (MAP) {
+    repeated group key_value {
+      required binary key (TEXT);
+      optional binary value (TEXT);
+    }
+  }
+```
+
+The steps below demonstrate the process of creating an external table, creating a fact table, and inserting data into the fact table from the Parquet file using the external table.
+
+### [](#step-1create-an-external-table-1)Step 1–create an external table
+
+When you create an external table for a Parquet map, you use the same syntax that you use in the example for arrays above. You create one column for keys and another column for values. The `CREATE EXTERNAL TABLE` example below demonstrates this.
+
+```
+CREATE EXTERNAL TABLE IF NOT EXISTS my_parquet_map_ext_tbl
+(
+  "context.keys" ARRAY(TEXT),
+  "context.values" ARRAY(TEXT)
+)
+CREDENTIALS = (AWS_KEY_ID = '****' AWS_SECRET_KEY = '*****')
+URL = 's3://my_bucket_of_parquet/'
+OBJECT_PATTERN = '*.parquet'
+TYPE = (PARQUET);
+```
+
+### [](#step-2create-a-fact-or-dimension-table-1)Step 2–create a fact or dimension table
+
+Create a Firebolt fact or dimension table that defines columns of the same `ARRAY(TEXT)` types that you defined in the external table in step 1. The example below demonstrates this for a fact table.
+
+```
+CREATE FACT TABLE IF NOT EXISTS my_parquet_map_fact_tbl
+(
+  [...,] --additional columns possible, not shown
+  my_parquet_array_keys ARRAY(TEXT),
+  my_parquet_array_values ARRAY(TEXT)
+  [,...]
+)
+[...] --required primary index for fact table not shown
+      --optional partitions not shown
+```
+
+### [](#step-3insert-into-the-fact-table-from-the-external-table-1)Step 3–insert into the fact table from the external table
+
+The example below demonstrates an `INSERT INTO` statement that selects the array values from Parquet data files using the external table column definition in step 1, and inserts them into the specified fact table columns, `my_parquet_array_keys` and `my_parquet_array_values`.
+
+```
+INSERT INTO my_parquet_map_fact_tbl
+  SELECT "context.keys" AS my_parquet_array_keys,
+         "context.values" AS my_parquet_array_values
+  FROM my_parquet_map_ext_tbl;
+```
+
+### [](#step-4query-map-values)Step 4–query map values
+
+After you ingest array values into the fact table, you can query and manipulate the array using array functions and Lambda functions. For more information, see [Working with arrays](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html).
+
+A query that uses a Lambda function to return a specific value by specifying the corresponding key value is shown below. For more information, see [Manipulating arrays using Lambda functions](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html#manipulating-arrays-with-lambda-functions).
+
+```
+SELECT
+  ARRAY_FIRST(v, k -> k = 'key_name_of_interest', my_parquet_array_keys, my_parquet_array_values) AS returned_corresponding_key_value
+FROM
+  my_parquet_map_ext_tbl;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_working_with_arrays.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_working_with_arrays.md
new file mode 100644
index 0000000..50554b1
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_working_with_arrays.md
@@ -0,0 +1,387 @@
+# [](#work-with-arrays)Work with arrays
+
+This section covers querying and manipulating arrays in Firebolt.
+
+- [Declaring ARRAY data types in table definitions](#declaring-array-data-types-in-table-definitions)
+- [Simple array functions](#simple-array-functions)
+- [Manipulating arrays with Lambda functions](#manipulating-arrays-with-lambda-functions)
+  
+  - [Lambda function general syntax](#lambda-function-general-syntax)
+  - [Lambda function example–single array](#lambda-function-examplesingle-array)
+  - [Lambda function example–multiple arrays](#lambda-function-examplemultiple-arrays)
+- [UNNEST](#unnest)
+  
+  - [Example–single UNNEST with single ARRAY-typed column](#examplesingle-unnest-with-single-array-typed-column)
+  - [Example–single UNNEST using multiple ARRAY-typed columns](#examplesingle-unnest-using-multiple-array-typed-columns)
+  - [Example–multiple UNNEST clauses resulting in a Cartesian product](#examplemultiple-unnest-clauses-resulting-in-a-cartesian-product)
+  - [Example–error on UNNEST of multiple arrays with different lengths](#exampleerror-on-unnest-of-multiple-arrays-with-different-lengths)
+- [ARRAY input and output syntax](#array-input-and-output-syntax)
+  
+  - [Converting ARRAY to TEXT](#converting-array-to-text)
+  - [Converting TEXT to ARRAY](#converting-text-to-array)
+  - [Nested ARRAYs](#nested-arrays)
+
+## [](#declaring-array-data-types-in-table-definitions)Declaring ARRAY data types in table definitions
+
+Array types are declared using `ARRAY(<type>)` where `<type>` can be any data type that Firebolt supports. This includes the `ARRAY` data type, so arrays can be arbitrarily nested.
+
+If you load an array from a CSV file, the arrays in the CSV file must be enclosed in double quotes (`""`).
+
+For example, if a CSV file contains a row containing `value1 , value2 , "[array_value3 , array_value4]"` , you can create a table using the following code to read `array_value3` and `array_value4` into `array_values`.
+
+```
+CREATE TABLE IF NOT EXISTS array_example
+    (  
+      value1 STRING,  
+      value2 STRING,  
+      array_values ARRAY(TEXT)
+    )
+    URL = 's3://path_to_your_data/'
+    TYPE = (csv);
+```
+
+Array literals are also supported. For example, the `SELECT` statement shown below is valid.
+
+```
+SELECT [1,2,3,4]
+```
+
+### [](#basis-for-examples)Basis for examples
+
+All examples in this topic are based on the table below, named `visits`. The column `id` is of type `INTEGER`. All other columns are of type `ARRAY(TEXT)`.
+
+![](/assets/images/array_example_table.png)
+
+## [](#simple-array-functions)Simple array functions
+
+There are several fundamental functions that you can use to work with arrays, including [ARRAY\_LENGTH](/sql_reference/functions-reference/array/array-length.html), [ARRAY\_CONCAT](/sql_reference/functions-reference/array/array-concat.html), and [ARRAY\_FLATTEN](/sql_reference/functions-reference/array/flatten.html). See the respective reference for a full description. Brief examples are shown below.
+
+### [](#length-example)LENGTH example
+
+`LENGTH` returns the number of elements in an array.
+
+```
+SELECT 
+  id,
+  LENGTH(agent_props_keys) as key_array_length
+FROM visits;
+```
+
+**Returns**:
+
+```
++-----------------------+
+| id | key_array_length |
++-----------------------+
+| 1  | 3                |
+| 2  | 2                |
+| 3  | 3                |
++-----------------------+
+```
+
+### [](#array_concat-example)ARRAY\_CONCAT example
+
+`ARRAY_CONCAT` combines multiple arrays into a single array.
+
+```
+SELECT 
+  id, 
+  ARRAY_CONCAT(agent_props_keys, agent_props_vals) as concat_keys_and_vals
+FROM visits;
+```
+
+**Returns**:
+
+```
++----+------------------------------------------------------------------------------+
+| id | concat_keys_and_vals                                                         |
++----+------------------------------------------------------------------------------+
+| 1  | ["agent","platform","resolution","Mozilla/5.0","Windows NT 6.1","1024X4069"] |
+| 2  | ["agent","platform","Safari","iOS 14"]                                       |
+| 3  | ["agent","platform","platform","Safari","iOS 14","Windows 11"]               |
++----+------------------------------------------------------------------------------+
+```
+
+### [](#array_flatten-example)ARRAY\_FLATTEN example
+
+`ARRAY_FLATTEN` converts an ARRAY of ARRAYs into a single flattened ARRAY. Note that this operation flattens only one level of the array hierarchy.
+
+```
+SELECT ARRAY_FLATTEN([ [[1,2,3],[4,5]], [[2]] ]) as flattened_array;
+```
+
+**Returns**:
+
+```
++---------------------+
+| flattened_array     |
++---------------------+
+| [[1,2,3],[4,5],[2]] |
++---------------------+
+```
+
+## [](#manipulating-arrays-with-lambda-functions)Manipulating arrays with Lambda functions
+
+Firebolt *Lambda functions* are a powerful tool that you can use on arrays to extract results. Lambda functions iteratively perform an operation on each element of one or more arrays. Arrays and the operation to perform are specified as arguments to the Lambda function.
+
+### [](#lambda-function-general-syntax)Lambda function general syntax
+
+The general syntax pattern of a Lambda function is shown below. For detailed syntax and examples see the reference topics for [Lambda functions](/sql_reference/functions-reference/Lambda/).
+
+```
+<LAMBDA_FUNC>(<arr1_var>[, <arr2_var>][, ...<arrN_var>]) -> <operation>, <array1>[, <array2>][, ...<arrayN>])
+```
+
+Parameter Description `<LAMBDA_FUNC>` Any array function that accepts a Lambda expression as an argument. For a list, see [Lambda functions](/sql_reference/functions-reference/Lambda/). `<arr1_var>[, <arr2_var>][, ...<arrN_var>]` A list of one or more variables that you specify. The list is specified in the same order and must be the same length as the list of array expressions (`<array1>[, <array2>][, ...<arrayN>]`). At runtime, each variable contains an element of the corresponding array. The specified `<operation>` is performed for each variable. The operation that is performed for each element of the array. This is typically a function or Boolean expression. \[, ]\[, ...] A comma-separated list of expressions, each of which evaluates to an `ARRAY` data type.
+
+### [](#lambda-function-examplesingle-array)Lambda function example–single array
+
+Consider the following [TRANSFORM](/sql_reference/functions-reference/Lambda/transform.html) array function that uses a single array variable and reference in the Lambda expression. This example applies the `UPPER` function to each element `t` in the `ARRAY`-typed column `tags`. This converts each element in each `tags` array to upper-case.
+
+```
+SELECT 
+  id, 
+  TRANSFORM(t -> UPPER(t), tags) AS up_tags
+FROM visits;
+```
+
+**Returns:**
+
+```
++----+--------------------------+
+| id | up_tags                  |
++----+--------------------------+
+| 1  | ["SUMMER-SALE","SPORTS"] |
+| 2  | ["GADGETS","AUDIO"]      |
+| 3  | ["SUMMER-SALE","AUDIO"]  |
++----+--------------------------+
+```
+
+### [](#lambda-function-examplemultiple-arrays)Lambda function example–multiple arrays
+
+[ARRAY\_FIRST](/sql_reference/functions-reference/Lambda/array-first.html) is an example of a function that takes multiple arrays as arguments in a map of key-value pairs. One array represents the keys and the other represents the values.
+
+`ARRAY_FIRST` uses a Boolean expression that you specify to find the key in the key array. If the Boolean expression resolves to true, the function returns the first value in the value array that corresponds to the key’s element position. If there are duplicate keys, only the first corresponding value is returned.
+
+The example below returns the first value in the `agent_props_vals` array where the corresponding position in the `agent_props_keys` array contains the key `platform`.
+
+```
+SELECT 
+  id, 
+  ARRAY_FIRST(v, k -> k = 'platform', agent_props_vals, agent_props_keys) AS platform
+FROM visits;
+```
+
+**Returns**:
+
+```
++----+----------------+
+| id | platform       |
++----+----------------+
+| 1  | Windows NT 6.1 |
+| 2  | iOS 14         |
+| 3  | iOS 14         |
++----+----------------+
+```
+
+[ARRAY\_SORT](/sql_reference/functions-reference/array/array-sort.html) sorts one array by another. One array represents the values and the other represents the sort order.
+
+The example below sorts the first array by the positions defined in the second array
+
+```
+SELECT 
+  ARRAY_SORT(x,y -> y, [ 'A','B','C'],[3,2,1]) AS res;
+```
+
+**Returns**:
+
+```
++-----------------+
+| res             |
++-----------------+
+| ["C", "B", "A"] |
++-----------------+
+```
+
+## [](#unnest)UNNEST
+
+You might want to transform a nested array structure to a standard tabular format. `UNNEST` serves this purpose.
+
+[UNNEST](/sql_reference/commands/queries/select.html#unnest) is a table-valued function (TVF) that transforms an input row containing an array into a set of rows. `UNNEST` unfolds the elements of the array and duplicates all other columns found in the `SELECT` clause for each array element. If the input array is empty, the corresponding row is eliminated.
+
+You can use a single `UNNEST` command to unnest several arrays if the arrays are the same length.
+
+Multiple `UNNEST` statements in a single `FROM` clause result in a Cartesian product. Each element in the first array has a record in the result set corresponding to each element in the second array.
+
+### [](#examplesingle-unnest-with-single-array-typed-column)Example–single UNNEST with single ARRAY-typed column
+
+The following example unnests the `tags` column from the `visits` table.
+
+```
+SELECT 
+    id, 
+    tag
+FROM 
+    visits,
+    UNNEST(tags) as r(tag);
+```
+
+**Returns**:
+
+```
++----+---------------+
+| id |     tag       |
++----+---------------+
+|  1 | "summer-sale" |
+|  1 | "sports"      |
+|  2 | "gadgets"     |
+|  2 | "audio"       |
++----+---------------+
+```
+
+### [](#examplesingle-unnest-using-multiple-array-typed-columns)Example–single UNNEST using multiple ARRAY-typed columns
+
+The following query specifies both the `agent_props_keys` and `agent_props_vals` columns to unnest.
+
+```
+SELECT
+    id,
+    a_key,
+    a_val
+FROM
+    visits,
+    UNNEST(agent_props_keys, agent_props_vals) as r(a_key, a_val);
+```
+
+**Returns**:
+
+```
++----+------------+------------------+
+| id | a_key      | a_val            |
++----+------------+------------------+
+| 1  | agent      | “Mozilla/5.0”    |
+| 1  | platform   | “Windows NT 6.1” |
+| 1  | resolution | “1024x4069”      |
+| 2  | agent      | “Safari”         |
+| 2  | platform   | “iOS 14”         |
++----+------------+------------------+
+```
+
+### [](#examplemultiple-unnest-clauses-resulting-in-a-cartesian-product)Example–multiple UNNEST clauses resulting in a Cartesian product
+
+The following query, while valid, creates a Cartesian product.
+
+```
+SELECT
+    id,
+    a_key,
+    a_val
+FROM
+    visits,
+    UNNEST(agent_props_keys as a_keys) as r1(a_key),
+    UNNEST(agent_props_vals as a_vals) as r2(a_val);
+```
+
+**Returns**:
+
+```
++-----+------------+------------------+
+| id  | a_key      |   a_val          |
++-----+------------+------------------+
+|   1 | agent      | "Mozilla/5.0"    |
+|   1 | agent      | "Windows NT 6.1" |
+|   1 | agent      | "1024x4069"      |
+|   1 | platform   | "Mozilla/5.0"    |
+|   1 | platform   | "Windows NT 6.1" |
+|   1 | platform   | "1024x4069"      |
+|   1 | resolution | "Mozilla/5.0"    |
+|   1 | resolution | "Windows NT 6.1" |
+|   1 | resolution | "1024x4069"      |
+|   2 | agent      | "Safari"         |
+|   2 | agent      | "iOS 14"         |
+|   2 | platform   | "Safari"         |
+|   2 | platform   | "iOS 14"         |
++-----+------------+------------------+
+```
+
+### [](#exampleerror-on-unnest-of-multiple-arrays-with-different-lengths)Example–error on UNNEST of multiple arrays with different lengths
+
+The following query is **invalid** and will result in an error as the `tags` and `agent_props_keys` arrays have different lengths for row 1.
+
+```
+SELECT
+    id,
+    tag,
+    a_key
+FROM
+    visits,
+    UNNEST(tags, agent_props_keys) as r(tag, a_key);
+```
+
+## [](#array-input-and-output-syntax)ARRAY input and output syntax
+
+`ARRAY` values can be converted from and to `TEXT`. This happens, for example, when an explicit `CAST` is added to a query, or when `ARRAY` values are (de-)serialized in a `COPY` statement.
+
+### [](#converting-array-to-text)Converting ARRAY to TEXT
+
+Broadly, the `TEXT` representation of an `ARRAY` value starts with an opening curly brace (`{`). This is followed by the `TEXT` representations of the individual array elements separated by commas (`,`). It ends with a closing curly brace (`}`). `NULL` array elements are represented by the literal string `NULL`. For example, the query
+
+```
+SELECT
+    CAST([1,2,3,4,NULL] AS TEXT)
+```
+
+returns the `TEXT` value `'{1,2,3,4,NULL}'`.
+
+When converting `ARRAY` values containing `TEXT` elements to `TEXT`, some additional rules apply. Specifically, array elements are enclosed by double quotes (`"`) in the following cases:
+
+- The array element is an empty string.
+- The array element contains curly or square braces (`{`,`[`,`]`,`}`), commas (`,`), double quotes (`"`), backslashes (`\`), or white space.
+- The array element matches the word `NULL` (case-insensitively).
+
+Additionally, double quotes and backslashes embedded in array elements will be backslash-escaped. For example, the query
+
+```
+SELECT
+    CAST(['1','2','3','4',NULL,'','{impostor,array}','["impostor","array","back\slash"]',' padded and spaced ', 'only spaced', 'null'] AS TEXT)
+```
+
+returns the `TEXT` value `'{1,2,3,4,NULL,"","{impostor,array}","[\"impostor\",\"array\",\"back\\slash\"]"," padded and spaced ","only spaced","null"}'`.
+
+### [](#converting-text-to-array)Converting TEXT to ARRAY
+
+When converting the `TEXT` representation of an array back to `ARRAY`, the same quoting and escaping rules as above apply. Unquoted whitespace surrounding array elements is trimmed, but whitespace contained within array elements is preserved. The array elements themselves are converted according to the conversion rules for the requested array element type. For example, the query
+
+```
+SELECT
+    CAST('{1, 2, 3, 4, null, "", "{impostor,array}", "[\"impostor\",\"array\",\"back\\slash\"]", " padded and spaced ", "null",   unquoted padded and spaced   }' AS ARRAY(TEXT))
+```
+
+returns the `ARRAY(TEXT)` value `[1,2,3,4,NULL,'','{impostor,array}','["impostor","array","back\slash"]',' padded and spaced ','null','unquoted padded and spaced']`.
+
+It is also possible to enclose arrays with square braces (`[` and `]`) instead of curly braces (`{` and `}`) when converting from `TEXT` to `ARRAY`. For example, the query
+
+```
+SELECT
+    CAST('[1, 2, 3, 4, NULL]' AS ARRAY(INTEGER))
+```
+
+returns the `ARRAY(INTEGER)` value `[1,2,3,4,NULL]`.
+
+### [](#nested-arrays)Nested ARRAYs
+
+Finally, the same prodedure applies when converting nested `ARRAY` values from and to `TEXT`. For example, the query
+
+```
+SELECT
+    CAST([NULL,[],[NULL],[1,2],[3,4]] AS TEXT)
+```
+
+returns the `TEXT` value `{NULL,{},{1,2},{3,4}}`, and the query
+
+```
+SELECT
+    CAST('{NULL,{},{1,2},{3,4}}' AS ARRAY(ARRAY(INTEGER)))
+```
+
+returns the `ARRAY(ARRAY(INTEGER))` value `[NULL,[],[NULL],[1,2],[3,4]]`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_working_with_semi_structured_data.md b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_working_with_semi_structured_data.md
new file mode 100644
index 0000000..f553233
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_loading_data_working_with_semi_structured_data_working_with_semi_structured_data.md
@@ -0,0 +1,21 @@
+# [](#work-with-semi-structured-data)Work with semi-structured data
+
+Semi-structured data is any data that does not follow a strict tabular schema and often includes fields that are not standard SQL data types. This data typically has a nested structure and supports complex types such as arrays, maps, and structs.
+
+Common formats of semi-structured data include:
+
+- **JSON**— A widely used format for semi-structured data. For information on loading JSON data with Firebolt, see [Load semi-structured JSON data](/Guides/loading-data/working-with-semi-structured-data/load-json-data.html).
+- **Parquet and ORC**— Serialization formats that support nested structures and complex data types. For information on loading Parquet data with Firebolt, see [Load semi-structured Parquet data](/Guides/loading-data/working-with-semi-structured-data/load-parquet-data.html).
+
+## [](#firebolts-approach-to-semi-structured-data)Firebolt’s approach to semi-structured data
+
+Firebolt transforms semi-structured data using arrays, enabling efficient querying. Arrays in Firebolt represent the following data constructs:
+
+- **Variable-length arrays**— Arrays with unpredictable lengths in the source data are supported by Firebolt. These arrays can have arbitrary nesting levels, provided the nesting level is consistent within a column and known during table creation.
+- **Maps**— Maps, also known as dictionaries, are represented using two coordinated arrays—one for keys and one for values. This approach is particularly useful for JSON-like data where objects have varying keys.
+
+* * *
+
+- [Load semi-structured JSON data](/Guides/loading-data/working-with-semi-structured-data/load-json-data.html)
+- [Load semi-structured Parquet data](/Guides/loading-data/working-with-semi-structured-data/load-parquet-data.html)
+- [Work with arrays](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization.md b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization.md
new file mode 100644
index 0000000..8d69785
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization.md
@@ -0,0 +1,20 @@
+# [](#register-and-set-up-your-organization)Register and set up your organization
+
+Learn how to register your organization, create accounts, and create logins and/or service accounts.
+
+- [Register your organization](/Guides/managing-your-organization/creating-an-organization.html)
+- [Create an account](/Guides/managing-your-organization/managing-accounts.html)
+- [Manage logins](/Guides/managing-your-organization/managing-logins.html)
+- [Create service accounts](/Guides/managing-your-organization/service-accounts.html)
+
+# [](#manage-user-permissions)Manage user permissions
+
+Learn how to create users, and link logins and/or service accounts.
+
+- [Manage users](/Guides/managing-your-organization/managing-users.html)
+
+# [](#manage-billing)Manage billing
+
+Learn how to manage billing with observability at both organization and account levels.
+
+- [Manage billing](/Guides/managing-your-organization/billing.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_billing.md b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_billing.md
new file mode 100644
index 0000000..3968304
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_billing.md
@@ -0,0 +1,33 @@
+# [](#billing)Billing
+
+Firebolt bills are based on the consumption of resources within each account in your organization. This includes the total amount of data stored and engine usage.
+
+- **Data storage** usage is calculated on the daily average amount of data (in bytes) stored under your Firebolt account name for indexes and raw compressed data.
+- **Engine resources** usage is calculated with **one-second granularity** between the time Firebolt makes the engine available for queries and when the the engine moves to the stopped state.
+
+## [](#set-up-account-billing-through-aws-marketplace)Set-up account billing through AWS Marketplace
+
+To continue using Firebolt’s engines for query execution after your initial $200 credit, valid for 30 days, you’ll need to set-up a billing account by connecting your account to the [AWS Marketplace](https://aws.amazon.com/marketplace).
+
+**Steps for registration:**
+
+1. On the [Firebolt Workspace page](https://go.firebolt.io/), select the **Configure**(![AggIndex](../../assets/images/configure-icon.png)) icon from the left navigation pane.
+2. Under **Organization settings**, select **Billing**.
+3. Click **Connect to AWS Marketplace** to take you to the Firebolt page on AWS Marketplace.
+4. On the AWS Marketplace page, click the **View Purchase Options** in the top right hand corner of the screen.
+5. Click **Setup Your Account**.
+
+Your account should now be associated with AWS Marketplace.
+
+## [](#invoices)Invoices
+
+Invoices for Firebolt engines and data are submitted through the AWS Marketplace. The final monthly invoice is available on the third day of each month through the AWS Marketplace. A billing cycle starts on the first day of the month and finishes on the last day of the same month.
+
+## [](#viewing-billing-information)Viewing billing information
+
+Users with the **Org Admin** role can monitor the cost history of each account in the organization.
+
+**To view cost information for your organization** Organization cost details are captured in two information\_schema tables. Query those two tables and retrieve any information about the organization’s cost  
+1\) [Engines billing](/sql_reference/information-schema/engines-billing.html) 2) [Storage billing](/sql_reference/information-schema/storage-billing.html)
+
+Firebolt billing is reported to the AWS Marketplace at the beginning of the next day. By default, the **Accounts &amp; Billing** page displays the engine usage breakdown based on billing time. If you prefer to see the engine usage by actual usage day, you can click the **Engines breakdown** selector under the **Usage cost by engine** table and click **Actual running time**.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_creating_an_organization.md b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_creating_an_organization.md
new file mode 100644
index 0000000..7e87995
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_creating_an_organization.md
@@ -0,0 +1,36 @@
+# [](#register-to-firebolt)Register to Firebolt
+
+To start working with Firebolt, you first need to register your organization and create your first account. An organization provides a logical structure for managing accounts, billing, and authentication. [Read more about organizations and accounts and their benefits.](/Overview/organizations-accounts.html)
+
+When registering to Firebolt, the domain name used in your registration email will determine the organization name. Organization names are globally unique — no two organizations can have the same name. If you need two organizations under the same domain, contact the Firebolt Support team for further assistance.
+
+## [](#create-an-organization)Create an organization
+
+To register to Firebolt and create an organization:
+
+1. Go to Firebolt’s registration page: [go.firebolt.io/signup](https://go.firebolt.io/signup)
+2. Enter the following information in the form:
+   
+   - First name
+   - Last name
+   - Email - make sure you use a business email address, such as `you@anycorp.com`. Based on that address, Firebolt infers the name of your company and organization. Firebolt does not support usernames with personal email addresses, such as `me@gmail.com` or `you@outlook.com`.
+   - Region in which to create your first account. You will be able to create additional accounts in other regions later on, if needed.
+3. Click **Register**.
+4. An email will be sent to the address provided to verify the organization. When this email is received, click on **Activate**. To move on to the next step, Firebolt will approve your registration request and validate your information - this step might take a couple of minutes to complete.
+5. Once approved, you will get a welcome email. Click **Go to Firebolt** in this email.
+6. Enter a password as instructed and choose **Set password**.
+7. Choose **Log in**. Enter your login information (email address and password) and click **Log in**.
+
+Congratulations - you have successfully set up your organization. Welcome to Firebolt!
+
+![Enter Firebolt](../../assets/images/enter_firebolt.png)
+
+Your organization comes prepared with one account for your convenience - choose your own name or keep the default.
+
+## [](#next-steps)Next steps:
+
+- [Manage accounts](/Guides/managing-your-organization/managing-accounts.html)
+- [Create logins](/Guides/managing-your-organization/managing-logins.html) or [set up SSO authentication](/Guides/security/sso/)
+- [Add users](/Guides/managing-your-organization/managing-users.html) to your account
+- [Manage roles](/Guides/security/rbac.html)
+- Create databases, engines, and load your data. Follow our [getting started tutorial](/Guides/getting-started/) to try this out with sample data.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_accounts.md b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_accounts.md
new file mode 100644
index 0000000..a1114ae
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_accounts.md
@@ -0,0 +1,89 @@
+# [](#manage-accounts)Manage accounts
+
+Your organization comes prepared with one account for your convenience. You can add more accounts, edit existing accounts, or delete accounts using SQL or in the UI.
+
+To view all accounts, click **Configure** to open the configure space, then choose **Accounts** from the menu, or query the [information\_schema.accounts](/sql_reference/information-schema/accounts.html) view.
+
+## [](#create-a-new-account)Create a new account
+
+Creating an account requires the org\_admin role.
+
+### [](#sql)SQL
+
+To create an account using SQL, use the [CREATE ACCOUNT](/sql_reference/commands/data-definition/create-account.html) statement. For example:
+
+```
+CREATE ACCOUNT dev WITH REGION = 'us-east-1';
+```
+
+### [](#ui)UI
+
+To create an account via the UI:
+
+![Configure > Accounts](/assets/images/accountspage.png)
+
+1. Click **Configure** to open the configure space, then choose **Accounts** from the menu.
+2. From the Accounts management page, choose **Create Account**. Type a name for the account and choose a region. You won’t be able to change the region for this account later, so choose carefully.
+3. Choose **Create**.
+
+![Create account](../../assets/images/createaccount.png)
+
+Then you will see your new account on the **Accounts management** page.
+
+There can be up to 20 accounts per organization and you can use `CREATE ACCOUNT` 25 times. If you have a need for additional account creations beyond this limit, contact [Firebolt Support](https://docs.firebolt.io/godocs/Reference/help-menu.html) for assistance. Our team can provide guidance and, if appropriate, adjust your account settings to accommodate your needs.
+
+## [](#edit-an-existing-account)Edit an existing account
+
+Editing an account requires the account\_admin or org\_admin role.
+
+### [](#sql-1)SQL
+
+To edit an existing account using SQL, use the [ALTER ACCOUNT](/sql_reference/commands/data-definition/alter-account.html) statement. For example:
+
+```
+ALTER ACCOUNT dev RENAME TO staging;
+```
+
+### [](#ui-1)UI
+
+To edit an account via the UI:
+
+1. Click **Configure** to open the configure space, then choose **Accounts** from the menu.
+2. Search for the relevant account using the top search filters or by scrolling through the accounts list. Hover over the right-most column to make the account menu appear then choose **Edit account**. Edit the name of the account.
+3. Choose **Save**.
+
+![Edit account](../../assets/images/editaccount.png)
+
+## [](#delete-an-existing-account)Delete an existing account
+
+Deleting an account requires the account\_admin or org\_admin role.
+
+### [](#sql-2)SQL
+
+To delete an existing account using SQL, use the [DROP ACCOUNT](/sql_reference/commands/data-definition/drop-account.html) statement. For example:
+
+```
+DROP ACCOUNT dev;
+```
+
+### [](#ui-2)UI
+
+To delete an account via the UI:
+
+1. Click **Configure** to open the configure space, then choose **Accounts** from the menu.
+2. Search for the relevant account using the top search filters or by scrolling through the accounts list. Hover over the right-most column to make the account menu appear then choose **Delete account**. If your account is not empty (for example, if it contains other objects such as users/databases/engines/etc.), you will need to confirm that you will also delete the sub-objects by selecting **Delete account sub-objects permanently**.
+3. Choose **Confirm**.
+
+![Delete account](../../assets/images/deleteaccount.png)
+
+The account will be removed from the **Accounts management** page.
+
+## [](#switch-accounts)Switch accounts
+
+To switch the account you are using:
+
+### [](#ui-3)UI
+
+Click on your login button - the current account will be marked. Choose an account you would like to switch to.
+
+![Switch account](../../assets/images/switch_account.png)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_logins.md b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_logins.md
new file mode 100644
index 0000000..a8eccfc
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_logins.md
@@ -0,0 +1,80 @@
+# [](#manage-logins)Manage logins
+
+Logins are managed at the organization level and are used for authentication. Logins are a combination of a login name (email), first name, last name, and password, unless you’ve configured [Single Sign-On (SSO)](../security/sso/). Moreover, logins can be configured with advanced authentication properties such as [MFA](/Guides/security/enabling-mfa.html) and [network policies](/Guides/security/network-policies.html). Logins are linked to users at the account level, so that roles may be managed separately per account. A user must be linked to either a login or a service account for programmatic use to gain access to Firebolt. You can add, edit or delete logins using SQL or in the UI.
+
+To view all logins, click **Configure** to open the configure space, then choose **Logins** from the menu, or query the [information\_schema.logins](/sql_reference/information-schema/logins.html) view.
+
+Managing logins requires the org\_admin role.
+
+## [](#create-a-new-login)Create a new login
+
+### [](#sql)SQL
+
+To create a login using SQL, use the [CREATE LOGIN](/sql_reference/commands/access-control/create-login.html) statement. For example:
+
+```
+CREATE LOGIN "alexs@acme.com" WITH FIRST_NAME = 'Alex' LAST_NAME = 'Summers';
+```
+
+### [](#ui)UI
+
+To create a login via the UI:
+
+1. Click **Configure** to open the configure space, then choose **Logins** from the menu:
+
+<!--THE END-->
+
+![Configure > Logins](/assets/images/loginspage.png)
+
+1. From the Logins management page, choose **Create Login**.
+2. Enter the following details:
+   
+   - First name: specifies the first name of the user for the login.
+   - Last name: specifies the last name of the user for the login.
+   - Login name: specifies the login in the form of an email address. This must be unique within your organization.
+3. Optionally, you can:
+   
+   - Associate a [network policy](/Guides/security/network-policies.html) with the login by choosing a network policy name under the **Network policy attached** field.
+   - Enable password login, which specifies if the login can authenticate Firebolt using a password.
+   - Enable multi-factor authentication (MFA). Read more about how to configure MFA [here](/Guides/security/enabling-mfa.html).
+   - Set the login as **organisation admin**, which enables fully managing the organization.
+
+## [](#edit-an-existing-login)Edit an existing login
+
+### [](#sql-1)SQL
+
+To edit an existing login using SQL, use the [ALTER LOGIN](/sql_reference/commands/access-control/alter-login.html) statement. For example:
+
+```
+ALTER LOGIN "alexs@acme.com" SET NETWORK_POLICY = my_network_policy
+```
+
+### [](#ui-1)UI
+
+To edit a login via the UI:
+
+1. Click **Configure** to open the configure space, then choose **Logins** from the menu.
+2. Search for the relevant login using the top search filters, or by scrolling through the list of logins. Hover over the right-most column to make the login menu appear, then choose **Edit login details**. Edit the desired fields and choose **Save**.
+
+Login name can not be changed for logins that were provisioned via SSO.
+
+![Edit login](../../assets/images/editlogin.png)
+
+## [](#deleting-an-existing-login)Deleting an existing login
+
+### [](#sql-2)SQL
+
+To delete an existing login using SQL, use the [DROP LOGIN](/sql_reference/commands/access-control/drop-login.html) statement. For example:
+
+```
+DROP LOGIN "alexs@acme.com";
+```
+
+### [](#ui-2)UI
+
+To delete a login via the UI:
+
+1. Click **Configure** to open the configure space, then choose **Logins** from the menu.
+2. Search for the relevant login using the top search filters, or by scrolling through the logins list. Hover over the right-most column to make the login menu appear, then choose **Delete login**.
+
+If the login is linked to any users, deletion will not be permitted. The login must be unlinked from all users before deletion.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_users.md b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_users.md
new file mode 100644
index 0000000..1c26d19
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_managing_users.md
@@ -0,0 +1,355 @@
+# [](#manage-users-and-roles)Manage users and roles
+
+In Firebolt, an **organization** can have multiple **accounts**, each serving as a separate workspace for managing resources and data. Within each account, users are created to control access, with their identities defined through logins or service accounts. **Logins** are associated with individual human users, each authenticated by unique credentials, allowing them to interact directly with Firebolt’s resources according to assigned roles. **Service accounts** provide programmatic access for applications and automated processes within the account, such as data pipelines or monitoring tools. Each login and service account is linked to specific **roles**, which define their permissions, ensuring that access is managed efficiently and securely across the organization.
+
+## [](#-logins)![Icon for a Firebolt login for human access.](../../assets/images/icon-login.png) Logins
+
+A **login** in Firebolt represents a **human user** and is associated with an individual’s credentials, identified by an **email address**. Logins are tied to user roles, which define what the individual can access or modify. A login is primarily used for human authentication and allows a user to access the platform, run queries, and interact with databases and other resources. For instance, a login object might be created for a specific person such as `kate@acme.com`, and this login is linked to roles that control permissions.
+
+## [](#-service-accounts)![Icon for a Firebolt service account for programmatic access.](../../assets/images/icon-service-account.png) Service accounts
+
+A **service account** represents a **machine or application** rather than a human user. It allows automated processes to authenticate and interact with Firebolt resources. A service account is used for programmatic access, such as in pipelines, monitoring systems, application data access, and scheduled queries. Service accounts are associated with roles just like logins but are designed to operate without human intervention. For example, a service account might be used for a data pipeline that regularly ingests data into Firebolt. Each service account must be associated with a user. For more information about how to create and manage service accounts, see [Manage programmatic access to Firebolt](/Guides/managing-your-organization/service-accounts.html).
+
+## [](#-users)![Icon for a Firebolt user.](../../assets/images/icon-user-bangs.png) Users
+
+A **user** is a distinct identity that interacts with the Firebolt platform. Each user is assigned specific **roles**, which determine what actions they can perform and which resources they can access. Users are essential for controlling access in Firebolt and are managed through **role-based access control (RBAC)**. Users authenticate via **logins** or **service accounts**, depending on whether they are human users or machine-based processes.
+
+A user must be associated with **either** a login or a service account, as follows:
+
+![A user must be associated with either a login or a service account.](../../assets/images/user_login_service-account.png)
+
+There can be multiple users per login or service account. Users are managed at the account level, as shown in the following diagram:
+
+![There can be multiple users per login, for human access, or per service account, for programmatic access](../../assets/images/multiple-users-per-login-or-sa.png)
+
+You can [add](#set-up-a-new-user), [edit](#edit-an-existing-user) or [delete](#deleting-an-existing-user) users using SQL in the **Develop Space** or using the user interface (UI) in the **Configure Space**.
+
+Managing roles requires the account\_admin role. For more information about roles, see the [Roles](/Overview/organizations-accounts.html#roles) section in [Organizations and accounts](/Overview/organizations-accounts.html), and the [Account permissions](/Overview/Security/Role-Based%20Access%20Control/account-permissions.html) section of [Role-based access control](/Overview/Security/Role-Based%20Access%20Control/) that specifies permissions for **CREATE USER**.
+
+**Topics**
+
+- [Manage users and roles](#manage-users-and-roles)
+  
+  - [Logins](#-logins)
+  - [Service accounts](#-service-accounts)
+  - [Users](#-users)
+  - [Set up a new user](#set-up-a-new-user)
+    
+    - [Set up a new user for programmatic access](#set-up-a-new-user-for-programmatic-access)
+    - [Set up a new user for human access](#set-up-a-new-user-for-human-access)
+      
+      - [Create a login](#create-a-login)
+        
+        - [Create a login using the UI](#create-a-login-using-the-ui)
+        - [Create a login using SQL](#create-a-login-using-sql)
+      - [Create a user](#create-a-user)
+        
+        - [Create a user using the UI](#create-a-user-using-the-ui)
+        - [Create a user using SQL](#create-a-user-using-sql)
+      - [Link the user to the login or service account](#link-the-user-to-the-login-or-service-account)
+        
+        - [Link a user using the UI](#link-a-user-using-the-ui)
+        - [Link a user using SQL](#link-a-user-using-sql)
+      - [Create a role](#create-a-role)
+        
+        - [Create a role using the UI](#create-a-role-using-the-ui)
+        - [Create a role using SQL](#create-a-role-using-sql)
+      - [Assign a role to a user](#assign-a-role-to-a-user)
+        
+        - [Assign a role using the UI](#assign-a-role-using-the-ui)
+        - [Assign a role using SQL](#assign-a-role-using-sql)
+  - [Edit an existing user](#edit-an-existing-user)
+    
+    - [Edit a user using the UI](#edit-a-user-using-the-ui)
+    - [Edit a user using SQL](#edit-a-user-using-sql)
+  - [Deleting an existing user](#deleting-an-existing-user)
+    
+    - [Delete a user using the UI](#delete-a-user-using-the-ui)
+    - [Delete a user using SQL](#delete-a-user-using-sql)
+
+## [](#set-up-a-new-user)Set up a new user
+
+To set up a new user, complete the following steps:
+
+1. Create a new login or service account. The following section provides information about creating a new login, for human access to Firebolt. If you want to set up a new user for programmatic access, see [Create a service account](/Guides/managing-your-organization/service-accounts.html#create-a-service-account).
+2. Create a new user.
+3. Link the user with a login or a service account.
+4. Create a role.
+5. Assign the role to the user.
+
+The following sections guide you through the previous steps.
+
+### [](#set-up-a-new-user-for-programmatic-access)Set up a new user for programmatic access
+
+![To set up a new user for programmatic access, first set up a service account.](../../assets/images/workflow-new-user-sa.png)
+
+To set up a user for programmatic access, [create a service account](/Guides/managing-your-organization/service-accounts.html#create-a-service-account), and then complete the steps in the following sections to [create a user](#create-a-user), [link the user](#link-the-user-to-the-login-or-service-account) to a service account, [create a role](#create-a-role), and [assign the role](#assign-a-role-to-a-user) to the user.
+
+### [](#set-up-a-new-user-for-human-access)Set up a new user for human access
+
+#### [](#create-a-login)Create a login
+
+![To set up a user for human access, first create a login.](../../assets/images/workflow-new-user-create-login.png)
+
+A login is an **email** that is used for authentication. A login can be associated with multiple accounts. When you set up a new user, you must create either a login or service account for them. Create a login if you want to associate a user with human access to Firebolt. [Create a service account](/Guides/managing-your-organization/service-accounts.html#create-a-service-account) for programmatic access. You will link the user to **either** a login or a service account.
+
+##### [](#create-a-login-using-the-ui)Create a login using the UI
+
+Login to [Firebolt’s Workspace](https://go.firebolt.io/login). If you haven’t yet registered with Firebolt, see the [Get Started](/Guides/getting-started/) guide. If you encounter any issues, reach out to [support@firebolt.io](mailto:support@firebolt.io) for help. Then, do the following:
+
+1. Select the Configure icon (![The Firebolt Configure Space icon.](../../assets/images/configure-icon.png)) in the left navigation pane to open the **Configure Space**.
+2. Select **Logins**.
+3. Select **Create Login**.
+4. In the **Create login** window that pops up, enter the following:
+   
+   1. First Name - The first name of the user.
+   2. Last Name - The last name of the user.
+   3. Login Name - The email address of the user.
+5. Select a network policy from the drop-down list. You can choose **Default** or create your own. The default network policy accepts traffic from any IP address. For more about network policies, including how to create a new policy, see [Manage network policies](/Guides/security/network-policies.html).
+6. Toggle the following options on or off to select the following:
+   
+   1. Is password enabled - Toggle **on** to require authentication using a password.
+   2. Is MFA enabled - Toggle **on** to require authentication using multi-factor authentication (MFA).
+   3. Is organization admin - Toggle **on** to grant that login permissions associated with an **Organization Admin**. A user must have organization administrative privileges to manage logins and service accounts. For more information about organization administrative privileges and other roles, see the [Roles](/Overview/organizations-accounts.html#roles) section in [Organizations and accounts](/Overview/organizations-accounts.html).
+7. Select **Create**.
+
+##### [](#create-a-login-using-sql)Create a login using SQL
+
+Login to [Firebolt’s Workspace](https://go.firebolt.io/login). If you haven’t yet registered with Firebolt, see the [Get Started](/Guides/getting-started/) guide. If you encounter any issues, reach out to [support@firebolt.io](mailto:support@firebolt.io) for help. Then, do the following:
+
+1. Select the **Develop** icon (![The Firebolt Develop Space icon](../../assets/images/develop-icon.png)).
+   
+   By default, when you login to **Firebolt’s Workspace** for the first time, Firebolt creates a tab in the **Develop Space** called **Script 1**. The following apply:
+   
+   - The database that **Script 1** will use is located directly below the tab name. If you want to change the database, select another database from the drop-down list.
+   - An engine must be running to process the script in a selected tab. The name and status of the engine that **Script 1** uses for computation is located to the right of the current selected database. If the engine has auto-start set to `TRUE`, it will start from a stopped state. For more information about auto-start, see [Immediately Starting or Automatically Stopping an Engine](/Guides/operate-engines/working-with-engines-using-ddl.html#automatically-start-or-stop-an-engine).
+2. Select **system** from the drop-down arrow next to the engine name. The system engine is always running, and you can use it to create a login. You can also use an engine that you create.
+3. Use the syntax in the following example code to create a login in the SQL Script Editor:
+   
+   ```
+    CREATE LOGIN "<login_name>"
+    WITH FIRST_NAME = <first_name> 
+    LAST_NAME = <last_name>;
+   ```
+
+#### [](#create-a-user)Create a user
+
+![To set up a new user, after you create a login, create a user.](../../assets/images/workflow-new-user-create-user.png)
+
+After you create a login, the next step is to create a user.
+
+##### [](#create-a-user-using-the-ui)Create a user using the UI
+
+1. Select the **Govern** icon (![The Firebolt Govern Space icon.](../../assets/images/govern-icon.png)) in the left navigation pane to open the **Govern Space**.
+2. Select **Users** from the left sub-menu bar.
+3. Select the **+ Create User** button at the top right of the **Govern Space**.
+4. In the **Create User** window, enter the following:
+   
+   1. **User name** - The name of the user to associate with the login. This name can be any string, excluding spaces, and special characters such as exclamation points (!), percent signs (%), at sign(@), dot sign (.), underscore sign (\_), minus sign (-), and asterisks (\*).
+   2. **Assign to** - Use the dropdown to assign the user to one of the following:  
+      i. **Unassigned** - No specific assignment.
+      
+      ii. **Login** - Associates the user with a login name or email address. After selecting this option, you will be prompted to choose the login name or email address.
+      
+      iii. **Service Account** - Associates the user with a service account. After selecting this option, you will be prompted to choose a service account name.
+   3. **Role** - Select the role you want to assign to the user. If no role is specified, the user is automatically granted a [public role](/Overview/organizations-accounts.html#public-role). For more information about roles, see the [Roles](/Overview/organizations-accounts.html#roles) section in [Organization and accounts](/Overview/organizations-accounts.html).
+   4. **Default Database** - Choose a database to associate with the user, setting it as their default for access.
+   5. **Default Engine** - Choose a default processing engine to associate with the user.
+5. Select **Create new user** to save the configuration.
+
+##### [](#create-a-user-using-sql)Create a user using SQL
+
+Use the syntax in the following example code and the [CREATE USER](/sql_reference/commands/access-control/create-user.html) statement to create a user in the **SQL Script Editor** in the **Develop Space**:
+
+```
+CREATE USER <my_user>;
+```
+
+You can also create a user and link it to a login simultaneously as shown in the following code example:
+
+```
+CREATE USER <my_user> WITH LOGIN = "<my_login>";
+```
+
+Create a user and link it to a service account at the same time as shown in the following code example:
+
+```
+CREATE USER <my_user> WITH SERVICE_ACCOUNT=<my_service_account>
+```
+
+#### [](#link-the-user-to-the-login-or-service-account)Link the user to the login or service account
+
+![To set up a new user, after you create a user, link it to the login or service account.](../../assets/images/workflow-new-user-link-login.png)
+
+If the user wasn’t associated with a login or service account when they were created, you must link them.
+
+##### [](#link-a-user-using-the-ui)Link a user using the UI
+
+1. Select the Govern icon (![The Firebolt Govern Space icon](../../assets/images/govern-icon.png)) in the left navigation pane to open the **Govern Space**.
+2. Select **Users** from the left sub-menu bar.
+3. Select the three horizontal dots (…) to the right of the user that you need to link to a login.
+4. Select **Edit user details**.
+5. If you want to link the user to a login for human access, select **Login** from the drop-down list next to **Assign to**. If you want to link the user to a service account for programmatic access, select **Service Account** from the drop-down list next to **Assign to**.
+6. If you want to link the user to a login for human access, select the name of the login to associate with the user from the drop-down list under **Login name**. If you want to link the user to a service account for programmatic access, select a name from the drop-down list next to **Service account name**. This drop-down list contains only login accounts that are not already assigned to a user in the current account.
+7. Select **Save**.
+
+##### [](#link-a-user-using-sql)Link a user using SQL
+
+Use the syntax in the following example code and the [ALTER\_USER](/sql_reference/commands/access-control/alter-user.html) statement to link a user to a login in the **SQL Script Editor** in the **Develop Space**:
+
+```
+ALTER USER <my_user> SET LOGIN = "<login_name>";
+```
+
+The following code links a user to a service account:
+
+```
+ALTER USER <user_name> SET SERVICE_ACCOUNT = <service_account_name>
+```
+
+#### [](#create-a-role)Create a role
+
+![To set up a new user, after you link the user, create a role.](../../assets/images/workflow-new-user-create-role.png)
+
+If you don’t already have a role that you want to assign to a user, you can create a role to define what actions users can perform. For more information, see [Roles](/Overview/organizations-accounts.html#roles).
+
+##### [](#create-a-role-using-the-ui)Create a role using the UI
+
+1. Select the Govern icon (![The Firebolt Govern Space icon.](../../assets/images/govern-icon.png)) in the left navigation pane to open the **Govern Space**.
+2. Select **Roles** from the left sub-menu bar.
+3. Select the **+ New Role** button at the top right of the **Govern Space**.
+4. In the left sub-menu bar, enter the following:
+   
+   1. Role name - The name of the role that you want to create. You can use this role to grant privileges for more than one user.
+5. Select **Databases** in the left sub-menu bar, and select the following in **Database privileges**:
+   
+   1. **Create database** - Toggle **on** to allow the user to create any database in the account.
+   2. **Modify any database** - Toggle **on** to allow the user to modify any database in the account, or keep the option **off** to select the specific database the user can modify.
+   3. **Usage any database** - Toggle **on** to allow the user to use any database in the account, or keep the option **off** to select the specific database the user can use.
+   4. If you didn’t specify using or modifying all databases, select the checkbox next to the specific database that you want to grant the user access to modify or use.
+6. Select **Engines** in the left sub-menu bar, and select the following in **Engine privileges**:
+   
+   1. **Create engine** - Toggle **on** to allow the user to create any engine in the account.
+   2. **Modify any engine** - Toggle **on** to allow the user to modify any engine in the account, or keep the option **off** to select the specific engine the user can modify.
+   3. **Operate any engine** - Toggle **on** to allow the user to stop or start any engine in the account, or keep the option **off** to select the specific engine the user can start or stop. Any running engine that is not the system engine accumulates usage costs.
+   4. **Usage any engine** - Toggle **on** to allow the user to use any engine in the account, or keep the option **off** to select the specific engine the user can use.
+7. Select **Create**.
+
+##### [](#create-a-role-using-sql)Create a role using SQL
+
+Use the syntax in the following example code and the [CREATE ROLE](/sql_reference/commands/access-control/create-role.html) and [GRANT](/sql_reference/commands/access-control/grant.html) statements to create a role in the **SQL Script Editor** in the **Develop Space**:
+
+```
+CREATE ROLE <my_role>;
+```
+
+Use the following code to grant engine **access to a role**:
+
+```
+GRANT USAGE ON ENGINE <engine_name> TO <role_name>
+```
+
+Use the following code example to grant a role permission to **modify a database**:
+
+```
+GRANT MODIFY ON DATABASE <database_name> TO <role_name>
+```
+
+Use the following code example to grant a role permission to **create objects inside the public schema**:
+
+```
+GRANT CREATE ON SCHEMA public TO <role_name>
+```
+
+Use the following code to grant a role permission to **access the public schema** in a database:
+
+```
+GRANT USAGE ON SCHEMA public TO <role_name>
+```
+
+Use the following code example to grant a role permission to **read data from a specified table**:
+
+```
+GRANT SELECT ON TABLE <table_name> TO <role_name>
+```
+
+For more information about role-based access, see [Manage role-based access control](/Guides/security/rbac.html).
+
+#### [](#assign-a-role-to-a-user)Assign a role to a user
+
+![To set up a new user, after creating a role, assign it to a user.](../../assets/images/workflow-new-user-assign.png)
+
+You can assign a new role to the user or change the role assigned to the user from the default **public** role to grant them specific permissions. A user can have multiple roles.
+
+##### [](#assign-a-role-using-the-ui)Assign a role using the UI
+
+1. Select the Govern icon (![The Firebolt Govern Space icon.](../../assets/images/govern-icon.png)) in the left navigation pane to open the **Govern Space**.
+2. Select **Users** from the left sub-menu bar.
+3. Select the three horizontal dots (…) to the right of the user that you need to link to a login.
+4. Select **Edit user details**.
+5. Select the checkbox next to the role that you want to assign to the user from the list under **Assign Roles**.
+6. Select **Save**.
+
+##### [](#assign-a-role-using-sql)Assign a role using SQL
+
+Use the syntax in the following example code and the [GRANT](/sql_reference/commands/access-control/grant.html) statement to assign a role in the **SQL Script Editor** in the **Develop Space**:
+
+```
+GRANT <my_role> TO USER <my_user>;
+```
+
+You can use `GRANT` to assign a role to another role as follows:
+
+```
+GRANT <some_role> TO ROLE <another_role>
+```
+
+## [](#edit-an-existing-user)Edit an existing user
+
+You can alter a user’s name, login or service account that they are associated with, their default database, and engine.
+
+### [](#edit-a-user-using-the-ui)Edit a user using the UI
+
+1. Select the Govern icon (![The Firebolt Govern Space icon.](../../assets/images/govern-icon.png)) in the left navigation pane to open the **Govern Space**.
+2. Select **Users** from the left sub-menu bar.
+3. Select the three horizontal dots (…) to the right of the user that you need to edit.
+4. Select **Edit user details**.
+5. Edit the desired fields.
+6. Select **Save**.
+
+### [](#edit-a-user-using-sql)Edit a user using SQL
+
+Use the [ALTER USER](/sql_reference/commands/access-control/alter-user.html) statement to change a user’s information in the **SQL Script Editor** in the **Develop Space**.
+
+The following code example changes a user’s name:
+
+```
+ALTER USER "alex" RENAME TO "alexs";
+```
+
+The following code example changes a user’s login:
+
+```
+ALTER USER alex SET LOGIN="alexs@acme.com";
+```
+
+Users can modify most of their own account settings without requiring [RBAC](/Overview/Security/Role-Based%20Access%20Control/#role-based-access-control-rbac) permissions, except when altering [LOGIN](/Guides/managing-your-organization/managing-logins.html) configurations or a [SERVICE ACCOUNT](/Guides/managing-your-organization/service-accounts.html).
+
+## [](#deleting-an-existing-user)Deleting an existing user
+
+You can delete a user using either the UI or with SQL. The delete operation is irreversible.
+
+### [](#delete-a-user-using-the-ui)Delete a user using the UI
+
+1. Select **Users** from the left sub-menu bar.
+2. Select the three horizontal dots (…) to the right of the user that you need to delete.
+3. Select **Delete user**.
+4. Select **Confirm** to delete the user. This operation is irreversible.
+
+### [](#delete-a-user-using-sql)Delete a user using SQL
+
+Use the syntax in the following example code and the the [DROP USER](/sql_reference/commands/access-control/drop-user.html) statement to delete an existing user in the **SQL Script Editor** in the **Develop Space**:
+
+```
+DROP USER "alex";
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_service_accounts.md b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_service_accounts.md
new file mode 100644
index 0000000..d28a1b1
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_managing_your_organization_service_accounts.md
@@ -0,0 +1,219 @@
+# [](#manage-programmatic-access-to-firebolt)Manage programmatic access to Firebolt
+
+Service accounts in Firebolt are used exclusively for **programmatic access**, allowing applications, scripts, or automated systems to securely interact with Firebolt resources. Unlike regular logins for individuals, each service account has an ID and a secret for authentication.
+
+To manage service accounts, you must have the **organization admin** role, which grants full administrative control over an organization in Firebolt, including managing logins, network policies, and accounts. This role ensures proper access management, security, and compliance with organizational policies.
+
+Administrators use service accounts to control how external tools and applications access Firebolt, ensuring access is limited to necessary resources. Service accounts are associated with specific users within the organization, giving administrators control over what data and permissions they have. This helps enforce security rules, track usage, and audit system access in a clear and controlled way.
+
+You can access a Firebolt database programmatically using either of the following:
+
+- The [Firebolt API](https://docs.firebolt.io/godocs/Guides/query-data/using-the-api.html#firebolt-api) - directly interacts with Firebolt’s data warehouse using HTTP requests.
+- The [Firebolt drivers](https://docs.firebolt.io/godocs/Guides/developing-with-firebolt/) - use a third party tool or programming language to integrate with Firebolt’s data warehouse. Firebolt supports several languages including Python, Node, .Net, and Go.
+
+Service accounts must be manually linked to a [user account](https://docs.firebolt.io/godocs/Guides/managing-your-organization/managing-users.html) after they have been created. The service account provides access to the organization, and the associated user provides access to an account within the organization. To use Firebolt programmatically, you must authenticate with an ID and a secret. These are generated when you create a service account. You can add, delete and generate secrets for service accounts using SQL scripts in the **Develop Space** or through the user interface (UI) in the **Configure Space**.
+
+Follow these steps to **gain programmatic access to Firebolt**:
+
+1. [Create a service account](#create-a-service-account).
+2. [Get a service account ID](#get-a-service-account-id).
+3. [Generate a secret](#generate-a-secret).
+4. [Create a user](#create-a-user).
+
+After completing the previous steps, the following sections show you how to **manage programmatic access through your service account**:
+
+1. [Test your new service account](#test-your-new-service-account).
+2. [Edit your service account](#edit-your-service-account).
+3. [Delete your service account](#delete-your-service-account).
+
+## [](#create-a-service-account)Create a service account
+
+![The first step to obtain programmatic access is to create a service account.](../../assets/images/service_accounts_create.png)
+
+You can create a service account using SQL scripts in the **Develop Space** or through the user interface (UI) in the **Configure Space**.
+
+### [](#create-a-service-account-using-the-ui)Create a service account using the UI
+
+Login to Firebolt’s [Workspace](https://go.firebolt.io/login). If you haven’t yet registered with Firebolt, see the [Get Started](https://docs.firebolt.io/Guides/getting-started/) guide. If you encounter any issues, reach out to support@firebolt.io for help. Then, do the following:
+
+1. Select the **Configure** icon (![The icon to open the Configure Space.](../../assets/images/configure-icon.png)) in the left navigation pane to open the **Configure Space**.
+2. Select Service accounts on the left sub-menu bar.
+3. Select the **+ Create a service account** button at the top right of the **Configure Space**.
+4. In the **Create a service account** window that appears, enter the following:
+   
+   - Name - The name of the service account.
+   - [Network policy](https://docs.firebolt.io/Guides/security/network-policies.html) - A security feature that defines a list of allowed and blocked IP addresses or ranges to manage access at the organization level, login level, or for service accounts.
+   - Description - A description for the service account.
+5. Toggle **Is organization admin** to designate the service account as an account with administrative privileges in your organization. In Firebolt, the organization admin role provides full administrative privileges over the organization, allowing management of users, service accounts, network policies, and other organization-wide settings.
+6. Select **Create** to finish creating the service account.
+
+### [](#create-a-service-account-using-sql)Create a service account using SQL
+
+Login to Firebolt’s [Workspace](https://go.firebolt.io/login). If you haven’t yet registered with Firebolt, see [Get Started](https://docs.firebolt.io/Guides/getting-started/). If you encounter any issues, reach out to support@firebolt.io for help. Then, do the following:
+
+1. Select the **Develop** icon (![The icon to open the Develop Space.](../../assets/images/develop-icon.png)).
+2. By default, when you login to **Firebolt’s Workspace** for the first time, Firebolt creates a tab in the **Develop Space** called **Script 1**. The following apply:
+   
+   - The database that **Script 1** will run using is located directly below the tab name. If you want to change the database, select another database from the drop-down list.
+   - An engine must be running to process the script in a selected tab. The name and status of the engine that **Script 1** uses for computation is located to the right of the current selected database.
+   
+   Select **system** from the drop-down arrow next to the engine name. The system engine is always running, and you can use it to create a service account. You can also use an engine that you create.
+3. Use the syntax in the following example code to create a service account in the **SQL Script Editor**:
+   
+   ```
+    CREATE SERVICE ACCOUNT IF NOT EXISTS "service_account_name" WITH DESCRIPTION = 'service account 1';
+   ```
+   
+   For more information, see the [CREATE SERVICE ACCOUNT](https://docs.firebolt.io/sql_reference/commands/access-control/create-service-account.html) command.
+
+## [](#get-a-service-account-id)Get a service account ID
+
+![The second step to obtain programmatic access is to get a service account ID.](../../assets/images/service_accounts_id.png)
+
+Your new service account is listed in the **Configure Space** in the **Service accounts** on the left sub-menu bar. Note the ID of this service account under the **ID** column in the **Service accounts management** table. You will use this ID for authentication.
+
+## [](#generate-a-secret)Generate a secret
+
+![The third step to obtain programmatic access is to generate a secret.](../../assets/images/service_accounts_secret.png)
+
+Each service account requires a secret to access Firebolt programmatically. You can generate a secret using SQL scripts in the **Develop Space** or through the UI in the **Configure Space**.
+
+If you generate a new secret, the previous secret for your service account will no longer work inside your applications or services.
+
+### [](#generate-a-secret-using-the-ui)Generate a secret using the UI
+
+1. Select the **Configure** icon (![The icon to open the Configure Space.](../../assets/images/configure-icon.png)) in the left navigation pane to open the **Configure Space**.
+2. Select **Service accounts** from the left sub-menu bar.
+3. Select the three horizontal dots (…) to the right of the service account that you want to generate a secret.
+4. Select **Create a new secret**.
+5. Select the copy icon from the pop-up window **New secret for service account** that displays the new secret to copy the secret to your clipboard. This secret is not stored anywhere. Once you close the pop-up window, you will no longer be able to retrieve this secret.
+
+### [](#generate-a-secret-using-sql)Generate a secret using SQL
+
+Use the syntax in the following example code to generate a secret for a service account in the **SQL Script Editor** in the **Develop Space**:
+
+```
+CALL fb_GENERATESERVICEACCOUNTKEY('service_account_name')
+```
+
+The `CALL fb_GENERATESERVICEACCOUNTKEY` command in the previous code example returns both the service account ID and secret. Once you retrieve this secret, you cannot retrieve it again later.
+
+## [](#create-a-user)Create a user
+
+![The last step to obtain programmatic access is to create a user.](../../assets/images/service_accounts_user.png)
+
+Once you create the service account, it must be associated with a user. Your organization may have multiple Firebolt accounts, each with its own set of resources, databases, and users. Each service account can only be linked to one user per Firebolt account, but it can be assigned to different users across multiple accounts. This setup allows the service account to work across multiple accounts, while ensuring it is linked to only one user per account.
+
+You can create a user using SQL scripts in the **Develop Space** or through the UI in the **Govern Space**.
+
+### [](#create-a-user-using-the-ui)Create a user using the UI
+
+1. Select the Govern icon (![The icon to open the Govern Space.](../../assets/images/govern-icon.png)) in the left navigation pane to open the **Govern Space**.
+2. Select Users from the left sub-menu bar.
+3. Select the **+ Create User** button at the top right of the **Govern Space**.
+4. In the **Create User** window, enter the following:
+   
+   - **User Name** - The name of the user to associate with the service account.
+   - **Default Database** - (Optional) The name of the database that is associated with the user.
+   - **Default Engine** - (Optional) The name of the engine that is associated with the user.
+   
+   Toggle the radio button next to **Associate a service account**.
+5. Select the name of the service account to associate with the user from the drop-down list under **Service Account Associated**. This drop-down list contains only service accounts that are not already assigned to a user in the current account.
+
+### [](#create-a-user-using-sql)Create a user using SQL
+
+Use the syntax in the following example code to generate a secret for a service account in the **SQL Script Editor** in the **Develop Space**:
+
+```
+CREATE USER alex WITH SERVICE_ACCOUNT = service_account_name;
+```
+
+The previous code example creates a user with the username `alex`, and associates it with a service account by its `service_account_name`.
+
+For more information, see [Manage users](https://docs.firebolt.io/godocs/Guides/managing-your-organization/managing-users.html#create-a-new-user).
+
+## [](#test-your-new-service-account)Test your new service account
+
+Once you have set up your service account, use the following code example to send a request to Firebolt’s REST API, and receive an authentication token:
+
+```
+curl -X POST --location 'https://id.app.firebolt.io/oauth/token' \
+--header 'Content-Type: application/x-www-form-urlencoded' \
+--data-urlencode 'grant_type=client_credentials' \
+--data-urlencode 'audience=https://api.firebolt.io' \
+--data-urlencode "client_id=${service_account_id}" \
+--data-urlencode "client_secret=${service_account_secret}"
+```
+
+In the previous code example, use the service account ID and secret from the previous **Generate a secret** step for `service_account_id` and `service_account_secret`.
+
+The following is an example response to the REST API request:
+
+**Response:**
+
+```
+{
+  "access_token":"eyJz93a...k4laUWw",
+  "token_type":"Bearer",
+  "expires_in":86400
+}
+```
+
+In the previous example response, the following apply:
+
+- The `access_token` is a unique token that authorizes your API requests that acts as a temporary key to access resources or perform actions. You can use this token to authenticate with Firebolt’s platform until it expires.
+- The `token_type` is `Bearer`, which means that the access token must be included in an authorization header of your API requests using the format: `Authorization: Bearer <access_token>`.
+- The token `expires_in` indicates the number of seconds until the token expires.
+
+Use the returned `access_token` to authenticate with Firebolt.
+
+## [](#edit-your-service-account)Edit your service account
+
+You can edit your service account using SQL scripts in the **Develop Space** or through the UI in the **Configure Space**.
+
+### [](#edit-your-service-account-using-the-ui)Edit your service account using the UI
+
+1. Select **Configure** icon (![The icon to open the Configure Space.](../../assets/images/configure-icon.png)) in the left navigation pane to open the **Configure Space**.
+2. Select **Service accounts** from the left sub-menu bar.
+3. Select the three horizontal dots (…) to the right of the service account that you want to edit.
+4. Select **Edit service account**.
+   
+   In the **Edit service account** pop-up window, you can edit the following:
+   
+   - **Name** - The name of the service account.
+   - **Network policy** - The network policy associated with the service account that defines whether an IP address is allowed or blocked from interacting with Firebolt resources.
+   - **Description** - The description of the service account.
+   - **Is organization admin** - Toggle on or off to identify the service account as an organizational admin.
+   
+   Select **Save** to keep your edits.
+
+### [](#edit-your-service-account-using-sql)Edit your service account using SQL
+
+Use [ALTER SERVICE ACCOUNT](https://docs.firebolt.io/sql_reference/commands/access-control/alter-service-account.html), as shown in the following example to edit a service account in the **SQL Script Editor** in the **Develop Space**:
+
+```
+ALTER SERVICE ACCOUNT service_account_name SET NETWORK_POLICY = my_network_policy
+```
+
+In the previous code example, the service account’s network policy is set to a new value.
+
+## [](#delete-your-service-account)Delete your service account
+
+You can delete your service account using SQL scripts in the **Develop Space** or through the UI in the **Configure Space**.
+
+{: .note} You can’t delete a service account if it is linked to users. You must first unlink the service account from all users. You can view all users linked to a service account by navigating to the **Users** section in the **Govern Space**. In the **Users Management** table, each **User Name** has the name of a **Service Account** if it is associated with one. To unlink a user account, select the three horizontal dots (…) to the right of the **User Name**, and select **Edit user details**. Then, toggle off **Associate a service account**.
+
+### [](#delete-your-service-account-using-the-ui)Delete your service account using the UI
+
+1. Select the **Configure** icon (![The icon to open the Configure Space.](../../assets/images/configure-icon.png)) in the left navigation pane to open the **Configure Space**.
+2. Select **Service accounts** from the left sub-menu bar.
+3. Select the three horizontal dots (…) to the right of the service account that you want to delete.
+4. Select **Delete service account**.
+
+### [](#delete-your-service-account-using-sql)Delete your service account using SQL
+
+Use [DROP SERVICE ACCOUNT](https://docs.firebolt.io/sql_reference/commands/access-control/drop-service-account.html), as shown in the following example to delete a service account in the **SQL Script Editor** in the **Develop Space**:
+
+```
+DROP SERVICE ACCOUNT service_account_name;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_operate_engines.md b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_operate_engines.md
new file mode 100644
index 0000000..352cd8a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_operate_engines.md
@@ -0,0 +1,10 @@
+# [](#operate-engines)Operate engines
+
+Learn how to work with engines using both the UI and SQL, how to size and monitor engines, how to use RBAC to govern engines and how to use the system engine.
+
+* * *
+
+- [Work with engines](/Guides/operate-engines/working-with-engines-using-ddl.html)
+- [Sizing Engines](/Guides/operate-engines/sizing-engines.html)
+- [System Engine](/Guides/operate-engines/system-engine.html)
+- [Governing Engines](/Guides/operate-engines/rbac-for-engines.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_rbac_for_engines.md b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_rbac_for_engines.md
new file mode 100644
index 0000000..a1b20ae
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_rbac_for_engines.md
@@ -0,0 +1,59 @@
+# [](#governing-engines)Governing Engines
+
+Use [Role Based Access Control](/Guides/security/rbac.html) (RBAC) to granularly control which users within an account can create new engines, use, operate, monitor and modify existing engines. Accordingly, Firebolt provides CREATE, USAGE, OPERATE, MONITOR and MODIFY permissions to control these actions. You can use RBAC to control whether a user has permissions to perform these actions for specific engines or for all engines in a given account. Note that permissions for CREATE ENGINE can only be granted at the account level.
+
+Follow the below steps to control what permissions a user has for a given engine or for any engine within an account:
+
+- Create a new role
+- Grant permissions to the role
+- Assign role to a user
+
+**Example 1:** We want to provide a user kate with permissions to create and operate engines
+
+```
+CREATE ROLE prodAdminRole;
+
+GRANT CREATE ENGINE ON ACCOUNT myAccount IN ORGANIZATION myOrg TO prodAminRole; 
+
+GRANT OPERATE ON ENGINE myEngine IN ACCOUNT myAccount TO prodAdminRole; 
+
+GRANT ROLE prodAdminRole TO USER kate;  
+```
+
+**Example 2:** We want to provide a user kate with permissions to only use and operate engines
+
+```
+CREATE ROLE prodAdminRole;
+
+GRANT USAGE ENGINE ON myEngine IN ACCOUNT myAccount TO prodAminRole; 
+
+GRANT OPERATE ON ENGINE myEngine IN ACCOUNT myAccount TO prodAdminRole; 
+
+GRANT ROLE prodAdminRole TO USER kate;  
+```
+
+**Example 3:** We want to provide a user kate with permissions to use, operate and monitor engine metrics
+
+```
+CREATE ROLE prodAdminRole;
+
+GRANT USAGE ENGINE ON myEngine IN ACCOUNT myAccount TO prodAminRole;
+
+GRANT MONITOR USAGE ON ENGINE myEngine IN ACCOUNT myAccount TO prodAminRole; 
+
+GRANT OPERATE ON ENGINE myEngine IN ACCOUNT myAccount TO prodAdminRole; 
+
+GRANT ROLE prodAdminRole TO USER kate;  
+```
+
+**Example 4:** We want to provide a user kate with permissions to create and modify engines
+
+```
+CREATE ROLE prodAdminRole;
+
+GRANT CREATE ENGINE ON ACCOUNT myAccount IN ORGANIZATION myOrg TO prodAminRole; 
+
+GRANT MODIFY ON ENGINE myEngine IN ACCOUNT myAccount TO prodAdminRole; 
+
+GRANT ROLE prodAdminRole TO USER kate;  
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_sizing_engines.md b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_sizing_engines.md
new file mode 100644
index 0000000..6e16f03
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_sizing_engines.md
@@ -0,0 +1,45 @@
+# [](#sizing-engines)Sizing Engines
+
+Selecting an appropriate engine size for your workload depends on multiple factors such as the size of your active dataset, latency and throughput requirements of your workload, your considerations for price-performance and the number of users and queries your workload is expected to handle concurrently. Our guidance is to start small with an engine size that fits your active dataset and monitor the workload using the engine observability metrics (see below). Based on these metrics, you can then dynamically resize your engine to meet the needs of your workload.
+
+If your workload requires high processing power relative to data size, use a compute-optimized node type. These nodes have the approximately same processing power as storage-optimized nodes but have less memory, cache space, and cost.
+
+## [](#dimensions-of-engine-sizing)Dimensions of engine sizing
+
+Firebolt allows you to change:
+
+- The type of nodes in your engine.
+- The compute family of nodes in your engine.
+- The number of nodes in a cluster of your engine.
+- The number of copies of that cluster in your engine.
+
+See the [engine fundamentals](/Overview/engine-fundamentals.html) page for details.
+
+## [](#using-observability-metrics-to-resize-an-engine)Using Observability Metrics to Resize an Engine
+
+Firebolt provides engine observability metrics that give visibility into how the engine resources are being utilized by your workloads. Use the [Information\_Schema.engine\_metrics\_history](/sql_reference/information-schema/engine-metrics-history.html) view to understand how much CPU, RAM, and disk are utilized by your workloads. In addition, this view also provides details on how often your queries hit the local cache and how much of your query data is spilling onto the disk. These metrics can help you decide whether your engine needs a different node type and whether you need to add more nodes to improve the query performance. Use the [Information\_Schema.engine\_running\_queries](/sql_reference/information-schema/engine-running-queries.html) view to understand how many queries are waiting in the queue to be run. If there are a number of queries still waiting to be run, adding another cluster to your engine may help improve the query throughput.
+
+## [](#initial-sizing)Initial Sizing
+
+**ELT Workloads**
+
+For the ELT workloads, the engine size would depend on the number of files and the size of the files used to ingest the data. You can parallelize the ingest process with additional nodes, which can provide improved performance.
+
+**Queries**
+
+To correctly size an engine for querying data, there are several factors to consider:
+
+- The size of frequently accessed data under your query pattern. More data will require a engine with a larger cache size.
+- The relative amount of processing performed within the queries in your query pattern. More complex queries will generally require more CPU cores.
+- The Queries Per Second (QPS) of your workload. At higher QPS you may need to enable auto-scaling or multiple clusters on your engine.
+- The number of requests outstanding or the time submitted queries run. Longer running queries may raise the requirements of the engine to need instance types with more memory or more clusters in the engine.
+
+For query processing, our recommendation is to start with a S or M storage-optimized instance type. Then, run a checksum over the dataset you expect to be queried frequently. Firebolt Engines cache the data locally, which helps serve queries at low latencies. The cache size provided by the engines varies depending on the type of node used in your engines, with each size having twice the cache of the next smallest size. Compute-optimized instances have approximately one quarter of the cache size of storage-optimized instances. After the checksum, you can use [Information\_Schema.engine\_metrics\_history](/sql_reference/information-schema/engine-metrics-history.html) to see the cache utilization percentage. If an acceptable percentage of your active dataset fits, you can then run queries at your expected QPS on the engine.
+
+**TIP:** You can use [Multi-Cluster Engine Warmup](/Reference/system-settings.html#multi-cluster-engine-warmup) to submit your checksum queries to all clusters in a multi-cluster engine.
+
+Small and medium storage-optimized engines are available for use right away. Compute-optimized instance types are available, but may see longer engine start times. If you want to use a large or extra-large engine, reach out to [support@firebolt.io](mailto:support@firebolt.io).
+
+**TIP:** You also have the option to run your workload simultaneously on engines with different configurations and use these metrics to identify which configuration best fits your needs.
+
+You will need to have the appropriate [RBAC](/Guides/operate-engines/rbac-for-engines.html) permissions to use the engine observability metrics.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_system_engine.md b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_system_engine.md
new file mode 100644
index 0000000..92f9b88
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_system_engine.md
@@ -0,0 +1,111 @@
+# [](#system-engine)System Engine
+
+Firebolt’s system engine enables running various metadata-related queries without having to start an engine. The system engine is always available for you in all databases to select and use.
+
+The system engine supports running the following commands:
+
+- All [access control](/sql_reference/commands/access-control/) commands
+- All [engine](/sql_reference/commands/engines/) commands
+- Most [data definition](/sql_reference/commands/data-definition/) commands. The following commands are not supported:
+  
+  - [ALTER TABLE DROP PARTITION](/sql_reference/commands/data-definition/alter-table.html)
+  - [CREATE AGGREGATING INDEX](/sql_reference/commands/data-definition/create-aggregating-index.html)
+  - [CREATE EXTERNAL TABLE](/sql_reference/commands/data-definition/create-external-table.html)
+  - [CREATE TABLE AS SELECT](/sql_reference/commands/data-definition/create-fact-dimension-table-as-select.html)
+- Most [metadata](/sql_reference/commands/metadata/) commands. The following commands are not supported:
+  
+  - [SHOW CACHE](/sql_reference/commands/metadata/show-cache.html)
+- Non-data-accessing [SELECT](/sql_reference/commands/queries/select.html) queries like `SELECT CURRENT_TIMESTAMP()`
+- [SELECT](/sql_reference/commands/queries/select.html) queries on some [information\_schema](/sql_reference/information-schema/) views:
+  
+  - [information\_schema.accounts](/sql_reference/information-schema/accounts.html)
+  - [information\_schema.applicable\_roles](/sql_reference/information-schema/applicable-roles.html)
+  - [information\_schema.transitive\_applicable\_roles](/sql_reference/information-schema/transitive-applicable-roles.html)
+  - [information\_schema.columns](/sql_reference/information-schema/columns.html)
+  - [information\_schema.catalogs](/sql_reference/information-schema/catalogs.html)
+  - [information\_schema.enabled\_roles](/sql_reference/information-schema/enabled-roles.html)
+  - [information\_schema.engines](/sql_reference/information-schema/engines.html)
+  - [information\_schema.indexes](/sql_reference/information-schema/indexes.html)
+  - [information\_schema.logins](/sql_reference/information-schema/logins.html)
+  - [information\_schema.network\_policies](/sql_reference/information-schema/network_policies.html)
+  - [information\_schema.service\_accounts](/sql_reference/information-schema/service-accounts.html)
+  - [information\_schema.tables](/sql_reference/information-schema/tables.html)
+  - [information\_schema.users](/sql_reference/information-schema/users.html)
+  - [information\_schema.views](/sql_reference/information-schema/views.html)
+
+## [](#using-the-system-engine-via-the-firebolt-manager)Using the system engine via the Firebolt manager
+
+1. In the Firebolt manager, choose the Databases icon in the navigation pane.
+2. Click on the SQL Workspace icon for the desired database. In case you have no database in your account - create one first.
+3. From the engine selector in the SQL Workspace, choose System Engine, then run one of the supported queries.
+
+## [](#using-the-system-engine-via-sdks)Using the system engine via SDKs
+
+### [](#python-sdk)Python SDK
+
+Connect via the connector without specifying the engine\_name. Database parameter is optional.
+
+System engine does not need a database defined. If you wish to connect to an existing database and run metadata queries with the system engine, just specify the name of your database.
+
+**Example**
+
+```
+from firebolt.db import connect
+from firebolt.client import DEFAULT_API_URL
+from firebolt.client.auth import ClientCredentials
+
+client_id = "<service_account_id>"
+client_secret = "<service_account_secret>"
+account_name = "<your_account_name>"
+
+with connect(
+   database="<any_db_here>", # Omit this parameter if you don't need db-specific operations
+   auth=ClientCredentials(client_id, client_secret),
+   account_name=account_name,
+   api_endpoint=DEFAULT_API_URL,
+) as connection:
+
+   cursor = connection.cursor()
+
+   cursor.execute("SHOW CATALOGS")
+
+   print(cursor.fetchall())
+```
+
+Guidance on creating service accounts can be found in the [service account](/Guides/managing-your-organization/service-accounts.html) section.
+
+### [](#other-sdks)Other SDKs
+
+Any other Firebolt connector can also be used similarly, as long as the engine name is omitted.
+
+## [](#system-engine-limitations)System Engine Limitations
+
+### [](#supported-queries-for-system-engine)Supported queries for system engine
+
+System engine only supports running the metadata-related queries listed above. Additional queries will be supported in future versions.
+
+### [](#rate-limits-for-system-engines)Rate Limits for System Engines
+
+To ensure fair and consistent access to the System Engine for all users, we have introduced rate limits that govern resource usage per account. These limits are designed to prevent resource contention and ensure optimal performance for everyone.
+
+When the rate limits are exceeded on the system engine, the system will return the following error: `429: Account system engine resources usage limit exceeded`. This error typically occurs when an account submits an excessive number of queries or executes highly complex queries that surpass the allocated resource thresholds.
+
+**What to Do If You Encounter Rate Limits**
+
+If you receive the 429 error, consider these steps to resolve the issue:
+
+- Switch to a User Engine: Offload your workloads to a dedicated User Engine if possible. User Engines do not have the same rate limits, making them better suited for higher workloads or complex operations.
+- Review your query patterns and ensure they are not unnecessarily complex or resource-intensive. Use best practices to write efficient queries that minimize resource consumption.
+- Contact Support: If you believe your account has been rate-limited unfairly or you anticipate requiring higher limits, reach out to our support team to discuss adjusting your account’s thresholds.
+
+**Best Practices to Avoid Rate Limits**
+
+- Avoid running multiple concurrent queries that heavily use system resources.
+- Leverage Firebolt’s indexing and other optimization features to streamline your queries.
+- Regularly audit your workloads and usage patterns to align with the system’s best practices.
+
+**Why This Matters**
+
+These rate limits are critical for maintaining a fair and robust environment where all users can achieve reliable performance without disruption from resource-heavy neighbors. This measure aligns with our commitment to delivering consistent and high-quality service across all accounts.
+
+For additional support or questions, please contact our support team or refer to our documentation on optimizing query performance.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_working_with_engines_using_ddl.md b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_working_with_engines_using_ddl.md
new file mode 100644
index 0000000..ef2ba5c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_operate_engines_working_with_engines_using_ddl.md
@@ -0,0 +1,204 @@
+# [](#work-with-engines)Work with engines
+
+You can create, run, modify, and scale Firebolt engines using either the **Firebolt Workspace** [user interface](/Guides/query-data/using-the-develop-workspace.html) (UI) or the [Firebolt API](/API-reference/). Learn how to perform key engine operations, including starting, stopping, resizing, and configuring auto-start/stop settings, using both the UI and SQL commands. Firebolt also allows the dynamic scaling of engines without stopping them.
+
+All the engine operations in this guide can be performed using a [system engine](/Guides/operate-engines/system-engine.html).
+
+Topics:
+
+- [Create engines](#create-engines) – Learn how to create an engine.
+- [Start or resume an engine](#start-or-resume-an-engine) – Learn how to start or resume an engine.
+- [Stop an engine](#stop-an-engine) – Learn how to stop an engine either gracefully or immediately.
+- [Resize engines](#resize-engines) – Learn how to scale engines up or down by adjusting the node type or number of nodes.
+- [Concurrency auto-scaling](#concurrency-auto-scaling) – Learn how to enable auto-scaling for engines to automatically adjust the number of clusters based on workload.
+- [Automatically start or stop an engine](#automatically-start-or-stop-an-engine) – Learn how to configure engines to start and stop automatically based on specific conditions.
+
+## [](#create-engines)Create engines
+
+You can create an engine using SQL scripts or through the UI in the **Develop Space**.
+
+### [](#create-an-engine-using-the-ui)Create an engine using the UI
+
+1. Login to the [Firebolt Workspace](https://firebolt.go.firebolt.io/signup).
+2. Select the **Develop Space** icon (&lt;/&gt;) from the left navigation bar.
+3. Select the red plus (+) button from the top of the left navigation bar.
+4. Select **Create new engine**.  
+   ![](/assets/images/Engine_Create_Popup.png)
+5. Enter the engine name, type, and number of nodes.  
+   ![](/assets/images/Create_Engine_Dialog.png)
+6. Select **Create new engine**.
+
+### [](#create-an-engine-using-the-api)Create an engine using the API
+
+To create an engine, use [CREATE ENGINE](/sql_reference/commands/engines/create-engine.html).
+
+The following code example creates an engine with one cluster containing two nodes of type `S`:
+
+```
+CREATE ENGINE myengine;
+```
+
+The following code example creates an engine with two nodes of type `M`:
+
+```
+CREATE ENGINE myengine WITH
+TYPE="M" NODES=2 CLUSTERS=1;
+```
+
+When creating an engine using the UI, Firebolt preserves the exact capitalization of the engine name. For example, an engine named **MyEngine** will retain its casing. To reference this engine in SQL commands, enclose the name in quotes: “MyEngine”. For more information, visit the [Object Identifiers](/Reference/object-identifiers.html) page.
+
+## [](#start-or-resume-an-engine)Start or resume an engine
+
+### [](#start-an-engine-using-the-ui-)Start an engine using the UI
+
+1. In the **Engines** list, find the engine you want to start.
+2. Open the dropdown menu next to the engine and select **Start engine**.  
+   ![](/assets/images/Start_Engine.png)
+3. The engine status changes to **Running** once started.
+
+### [](#start-an-engine-using-the-api-)Start an engine using the API
+
+To start your engine, use the [START ENGINE](/sql_reference/commands/engines/start-engine.html) command:
+
+```
+START ENGINE myengine;
+```
+
+## [](#stop-an-engine)Stop an engine
+
+### [](#stop-an-engine-using-the-ui-)Stop an engine using the UI
+
+1. In the **Engines** list, find the engine you want to stop.
+2. Open the dropdown menu and select **Stop engine**.  
+   ![](/assets/images/Stop_Engine.png)
+
+### [](#stop-an-engine-using-the-api-)Stop an engine using the API
+
+To stop an engine, use the [STOP ENGINE](/sql_reference/commands/engines/stop-engine.html) command:
+
+```
+STOP ENGINE myengine;
+```
+
+To stop an engine immediately without waiting for running queries to complete, use:
+
+```
+STOP ENGINE myengine WITH TERMINATE=TRUE;
+```
+
+Stopping an engine clears its cache. Queries run after restarting will experience a cold start, potentially impacting performance until the cache is rebuilt.
+
+## [](#resize-engines)Resize engines
+
+### [](#scale-engines-up-or-down-using-the-ui-)Scale engines up or down using the UI
+
+1. In the **Engines** list, find the engine to modify.
+2. Open the dropdown menu and select the **More options** icon (![More options icon](../../assets/images/more_options_icon.png)).
+3. Choose **Modify engine**.  
+   ![](/assets/images/Alter_Engine_Popup.png)
+4. Choose the new node type and select **Modify engine**.  
+   ![](/assets/images/Modify_Engine_Type.png)
+
+### [](#scale-engines-up-or-down-using-the-api-)Scale engines up or down using the API
+
+Use the [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html) command to change the node type:
+
+```
+ALTER ENGINE my_prod_engine SET TYPE = “M”;
+```
+
+The previous example updates all nodes in the engine to use the ‘M’ type.
+
+### [](#scale-engines-out-or-in-using-the-ui)Scale engines out or in using the UI
+
+1. In the **Engines** list, find the engine to modify.
+2. Open the dropdown menu, select the **More options** icon (![More options icon](../../assets/images/more_options_icon.png)), and choose **Modify engine**.  
+   ![](/assets/images/Alter_Engine_Popup.png)
+3. Adjust the number of nodes using the (-) and (+) buttons.
+
+### [](#scale-engines-out-or-in-using-the-api)Scale engines out or in using the API
+
+Use the [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html) command to change the number of nodes:
+
+```
+ALTER ENGINE my_prod_engine SET NODES = 3;
+```
+
+The previous example updates the engine so that it uses three nodes.
+
+## [](#concurrency-auto-scaling)Concurrency auto-scaling
+
+You can use the `MIN_CLUSTERS` and `MAX_CLUSTERS` parameters to enable auto-scaling and allow the engine to adjust the number of clusters based on workload. Firebolt scales the clusters between the defined minimum and maximum based on engine CPU usage, time in the queue, and other factors that vary with demand. Auto-scaling helps your engine adapt to fluctuating workloads, improving performance, minimizing delays during high demand, avoiding bottlenecks, ensuring consistent query response times, and optimizing resource utilization for a more cost-effective solution.
+
+To use auto-scale, do the following:
+
+1. Create an engine with `MIN_CLUSTERS` set to a value and `MAX_CLUSTERS` set to a value higher than `MIN_CLUSTERS` as shown in the following code example:
+   
+   ```
+    CREATE ENGINE your_engine with MIN_CLUSTERS = 1 MAX_CLUSTERS = 2;
+   ```
+   
+   In the previous code example, If `MIN_CLUSTERS` has the same value as `MAX_CLUSTERS`, auto-scaling is not enabled.
+2. Check the `information_schema.engines` view to check how many clusters are being used by your engine. The following code example returns the number of `CLUSTERS`, `MIN_CLUSTERS`, and `MAX_CLUSTERS` from the specified engine:
+   
+   ```
+    SELECT CLUSTERS, MIN_CLUSTERS, MAX_CLUSTERS 
+    FROM information_schema.engines WHERE engine_name = 'your_engine'
+   ```
+   
+   You can also select the **Engine monitoring** tab at the bottom of the **SQL script editor** in the **Develop Workspace** as shown in the following image:
+   
+   ![Icon showing the engine monitoring tab selected in the Firebolt Develop Workspace.](../../assets/images/icon-engine-monitoring.png)
+   
+   The **Engine monitoring** tab displays CPU, memory, and disk use, cache reads, number of running and suspended queries, and spilled bytes.
+3. Test auto-scaling by running a query that overloads a single cluster, then check `information_schema.engines` to observe the change in the `CLUSTERS` value. You can use any query to test this functionality as long as it can overload the engine. The following example is one such query, but you can use any query that causes the engine to overload.
+   
+   1. In the **Develop Space**, run the following example query **in two separate tabs simultaneously**.  
+      The following code example calculates the maximum product of `a.x` and `b.y` after casting them to `BIGINT`, and the total count of joined rows from two generated series of numbers ranging from 1 to 1,000,000:
+      
+      ```
+      SELECT MAX(a.x::bigint * b.y::bigint), COUNT(*) 
+      FROM GENERATE_SERIES(1, 1000000) AS a(x) 
+      JOIN GENERATE_SERIES(1, 1000000) AS b(y) ON TRUE;
+      ```
+   2. After about a minute, enter the code example in step 1 in a new tab. The query should return the numbers of `CLUSTERS` as `2` as shown in the following table:
+      
+      clusters min\_clusters max\_clusters 2 1 2
+   3. Stop the engine to stop resource consumption. These queries can run for a very long time and prevent the engine from stopping automatically. The following code example stops an engine without waiting for running queries to finish:
+   
+   ```
+    STOP ENGINE your_engine WITH TERMINATE=true
+   ```
+
+If you are using Firebolt in preview mode, you can only use a single cluster for your engines. If you want to try using multi-cluster engines, contact [Firebolt support](mailto:support@firebolt.io). Additionally, when scaling an engine, both the old and new compute resources may be active at the same time for a period. This simultaneous operation can result in higher consumption of Firebolt Units ([FBUs](/Overview/engine-consumption.html)).
+
+## [](#automatically-start-or-stop-an-engine)Automatically start or stop an engine
+
+You can configure an engine to start automatically after creation and to stop after a set idle time.
+
+### [](#configure-automatic-startstop-using-the-ui)Configure automatic start/stop using the UI
+
+1. In the **Create new engine** menu, open **Advanced Settings**.
+2. Disable **Start engine immediately** to prevent the engine from starting upon creation.  
+   ![](/assets/images/Engine_Initially_Stopped.png)
+3. To configure automatic stopping, enable **Automatically stop engine** and set your idle timeout. The default is 20 minutes. Toggle the button off to disable auto-stop.  
+   ![](/assets/images/Engine_Auto_Stop.png)
+
+### [](#configure-automatic-startstop-using-the-api)Configure automatic start/stop using the API
+
+Use the [CREATE ENGINE](/sql_reference/commands/engines/create-engine.html) command to set auto-start and auto-stop options:
+
+```
+CREATE ENGINE my_prod_engine WITH 
+INITIALLY_STOPPED = true AUTO_STOP = 10;
+```
+
+The previous example creates an engine that remains stopped after creation and auto-stops after 10 minutes of inactivity.
+
+To modify the auto-stop feature later, use the [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html) command:
+
+```
+ALTER ENGINE my_prod_engine SET AUTO_STOP = 30;
+```
+
+The `INITIALLY_STOPPED` function can only be set during engine creation and cannot be modified afterward.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_query_data.md b/cmd/docs-scrapper/fireboltdocs/guides_query_data.md
new file mode 100644
index 0000000..c6f0c8f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_query_data.md
@@ -0,0 +1,10 @@
+# [](#query-data)Query data
+
+Querying data in Firebolt is designed to be fast, flexible, and efficient, allowing you to extract insights from large datasets. Firebolt supports interactive querying through the **Develop Workspace** for hands-on exploration and offers an API for programmatic access, making it easy to integrate queries into automated workflows.
+
+Firebolt provides the following approaches for querying data:
+
+- The [Develop Workspace](/Guides/query-data/using-the-develop-workspace.html) – An intuitive, web-based user interface for writing, running, and refining SQL queries. It simplifies the query development process with features like syntax highlighting, instant query results, and result visualization. Designed for interactive exploration and analysis, the **Develop Workspace** can help you work efficiently with large datasets, troubleshoot queries, and fine-tune performance in a single integrated environment.
+- [Drivers](/Guides/developing-with-firebolt/) – Libraries and SDKs that enable you to connect to Firebolt databases from your applications, scripts, and tools. Firebolt provides drivers for popular programming languages like Python, .NET, and Java, allowing you to interact with Firebolt databases programmatically and integrate them into your applications.
+- [Connectors](/Guides/integrations/integrations.html) – Pre-built integrations that enable you to connect Firebolt to third-party tools, data sources, and services. Firebolt offers connectors for popular data tools like Tableau, Looker, and dbt, allowing you to seamlessly query Firebolt databases from your preferred analytics platforms.
+- The [Firebolt API](/Guides/query-data/using-the-api.html) – A REST API that provides access to Firebolt databases. Allows you to create a custom integration with Firebolt, in case none of the available drivers or connectors meet your requirements.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_query_data_using_the_api.md b/cmd/docs-scrapper/fireboltdocs/guides_query_data_using_the_api.md
new file mode 100644
index 0000000..d46ae34
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_query_data_using_the_api.md
@@ -0,0 +1,121 @@
+# [](#firebolt-api)Firebolt API
+
+Use the Firebolt REST API to execute queries on engines programmatically. Learn how to use the API, including authentication, working with engines and executing queries. A service account is required to access the API. Learn about [managing programmatic access to Firebolt](/Guides/managing-your-organization/service-accounts.html).
+
+- [Firebolt API](#firebolt-api)
+  
+  - [Create a service account and associate it with a user](#create-a-service-account-and-associate-it-with-a-user)
+  - [Use tokens for authentication](#use-tokens-for-authentication)
+  - [Get the system engine URL](#get-the-system-engine-url)
+  - [Execute a query on the system engine](#execute-a-query-on-the-system-engine)
+  - [Get a user engine URL](#get-a-user-engine-url)
+  - [Execute a query on a user engine](#execute-a-query-on-a-user-engine)
+
+## [](#create-a-service-account-and-associate-it-with-a-user)Create a service account and associate it with a user
+
+Create a service account with organization administrator privilege, i.e., the service account property\_is\_organization\_admin_ must be *true*. Next, create a user with role privileges you would like to have the service account and associate the service account with the user.
+
+## [](#use-tokens-for-authentication)Use tokens for authentication
+
+To authenticate Firebolt using the service accounts with the properties as described above via Firebolt’s REST API, send the following request to receive an authentication token:
+
+```
+curl -X POST --location 'https://id.app.firebolt.io/oauth/token' \
+--header 'Content-Type: application/x-www-form-urlencoded' \
+--data-urlencode 'grant_type=client_credentials' \
+--data-urlencode 'audience=https://api.firebolt.io' \
+--data-urlencode "client_id=${service_account_id}" \
+--data-urlencode "client_secret=${service_account_secret}"
+```
+
+where:
+
+Property Data type Description client\_id TEXT The service [account ID](/Guides/managing-your-organization/service-accounts.html#get-a-service-account-id). client\_secret TEXT The service [account secret](/Guides/managing-your-organization/service-accounts.html#generate-a-secret).
+
+**Response**
+
+```
+{
+  "access_token":"access_token_value",
+  "token_type":"Bearer",
+  "expires_in":86400
+}
+```
+
+In the previous example response, the following apply:
+
+- The `access_token` is a unique token that authorizes your API requests that acts as a temporary key to access resources or perform actions. You can use this token to authenticate with Firebolt’s platform until it expires.
+- The `token_type` is `Bearer`, which means that the access token must be included in an authorization header of your API requests using the format: `Authorization: Bearer <access_token>`.
+- The token `expires_in` indicates the number of seconds until the token expires.
+
+Use the returned access\_token to authenticate with Firebolt.
+
+To run a query using the API, you must first obtain the url of the engine you want to run on. Queries can be run against any engine in the account, including the system engine.
+
+## [](#get-the-system-engine-url)Get the system engine URL
+
+Use the following endpoint to return the system engine URL for `<account name>`.
+
+```
+curl https://api.app.firebolt.io/web/v3/account/<account name>/engineUrl \
+-H 'Accept: application/json' \
+-H 'Authorization: Bearer <access token>'
+```
+
+**Example:** `https://api.app.firebolt.io/web/v3/account/my-account/engineUrl`
+
+**Response**
+
+```
+{
+  "engineUrl":"<prefix>.api.us-east-1.app.firebolt.io"
+}
+```
+
+## [](#execute-a-query-on-the-system-engine)Execute a query on the system engine
+
+Use the following endpoint to run a query on the system engine:
+
+```
+curl --location 'https://<system engine URL>' \
+--header 'Authorization: Bearer <access token>' \
+--data '<SQL query>'
+```
+
+where:
+
+Property Data type Description system engine URL TEXT The system engine URL ([retrieved here](#get-the-system-engine-url)) SQL query TEXT Any valid SQL query (optional) database name TEXT The database name
+
+## [](#get-a-user-engine-url)Get a user engine URL
+
+Get a user engine url by running the following query against the `information_schema.engines` table:
+
+```
+SELECT url 
+FROM information_schema.engines 
+WHERE engine_name='<engine_name>'
+```
+
+You can run the query on the system engine using the API with the following request:
+
+```
+curl --location 'https://<system engine URL>/query' \
+--header 'Authorization: Bearer <access token>' \
+--data 'SELECT * FROM information_schema.engines WHERE engine_name='\''my_engine'\'''
+```
+
+## [](#execute-a-query-on-a-user-engine)Execute a query on a user engine
+
+Use the following endpoint to run a query on a user engine:
+
+```
+curl --location 'https://<user engine URL>&database=<database name>' \
+--header 'Authorization: Bearer <access token>' \
+--data '<SQL query>'
+```
+
+where:
+
+Property Data type Description user engine URL TEXT The user engine URL ([retrieved here](#get-a-user-engine-url)) database name TEXT The database to run the query SQL query TEXT Any valid SQL query
+
+Queries are per request. To run multiple statement queries, separate queries each into one request.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_query_data_using_the_develop_workspace.md b/cmd/docs-scrapper/fireboltdocs/guides_query_data_using_the_develop_workspace.md
new file mode 100644
index 0000000..a61949a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_query_data_using_the_develop_workspace.md
@@ -0,0 +1,157 @@
+# [](#use-the-develop-space)Use the Develop Space
+
+- [Open the Develop Space](#open-the-develop-space)
+- [A quick tour](#a-quick-tour)
+- [Using the document editor](#using-the-document-editor)
+  
+  - [Using auto-complete](#using-auto-complete)
+  - [Using script templates](#using-script-templates)
+  - [Using the CREATE EXTERNAL TABLE template to import data](#using-the-create-external-table-template-to-import-data)
+- [Managing scripts](#managing-scripts)
+- [Running scripts and working with results](#running-scripts-and-working-with-results)
+  
+  - [Viewing results](#viewing-results)
+  - [Viewing multi-statement script results](#viewing-multi-statement-script-results)
+  - [Exporting results to a local hard drive](#exporting-results-to-a-local-hard-drive)
+- [Switching between light and dark mode](#switching-between-light-and-dark-mode)
+- [Keyboard shortcuts for the Develop Space](#keyboard-shortcuts-for-the-develop-space)
+  
+  - [Query operations](#query-operations)
+  - [Script management](#script-management)
+  - [Search functionality](#search-functionality)
+  - [Editing text](#editing-text)
+
+The **Firebolt Workspace** has a **Develop Space** that you use to edit and run SQL scripts and view query results.
+
+## [](#open-the-develop-space)Open the Develop Space
+
+You can launch the space for a database by clicking the **Develop** icon from the left navigation pane or clicking the “+” icon next to “Script 1”.
+
+![drawing](../../assets/images/develop_workspace_ex0.png)
+
+![drawing](../../assets/images/develop_workspace_ex4.png)
+
+**Starting the Develop Space for the last database you worked with**
+
+1. Choose the **&lt;/&gt;** icon from the left navigation pane.
+   
+   ![drawing](../../assets/images/develop_workspace_ex0.png)
+   
+   The space for the database that you last worked with will open, and the database will be selected from the list.
+2. To switch to different database’s space, choose from the dropdown menu in the Databases panel.
+
+## [](#a-quick-tour)A quick tour
+
+The **Develop Space** is organized into two panels.
+
+- The left panel is the explore panel. You can use it to navigate to different databases and to work with different scripts in your database.
+- The center panel is the document editor. You can use it to edit scripts, save them, and run scripts. When you run a script, the results will be shown in the bottom part of the pane.
+  
+  ![drawing](../../assets/images/develop_workspace_ex5.png)
+
+## [](#using-the-document-editor)Using the document editor
+
+The document editor uses tabs to help you organize your SQL scripts. You can switch tabs to work with different scripts and run them. You can have multiple query statements on the same tab. Each statement must be terminated by a semi-colon (`;`).
+
+### [](#using-auto-complete)Using auto-complete
+
+As you enter your code in a script tab, Firebolt suggests keywords and object names from the chosen database. Press the tab key to add the first suggestion in the list to your script, or use arrow keys to select a different item from the list and then press the tab key.
+
+### [](#using-script-templates)Using script templates
+
+Script templates are available for common tasks, such as creating fact or dimension tables. Place the cursor in the editor where you want to insert code, choose the **&lt;/+** icon, and then select a query template from the list.
+
+### [](#using-the-create-external-table-template-to-import-data)Using the CREATE EXTERNAL TABLE template to import data
+
+To create an external table, which is the first step for ingesting data into Firebolt, choose the **Import Data** button from the object pane or choose the download icon and then choose **Import data** as shown in the example below.
+
+Firebolt creates a new tab with a `CREATE EXTERNAL TABLE` statement.
+
+## [](#managing-scripts)Managing scripts
+
+- [To rename a script](#scriptrename)
+- [To copy a script](#scriptcopy)
+- [To export a script and download it as a .sql file](#scriptexport)
+
+**Renaming a script**[]()
+
+- Choose the vertical ellipses next to the script name in the left pane, choose **Rename script**, type a new name, and then press ENTER.
+
+**Copying a script**[]()
+
+- Choose the vertical ellipses next to the script name in the left pane, choose **Duplicate script**, and then press ENTER. Firebolt saves a new script with the pattern \`\_copy.
+
+**Exporting a script and downloading it as a .sql file**[]()
+
+- Choose the vertical ellipses next to the script name in the left pane, and then choose **Export script**.
+  
+  Firebolt downloads the file to your browser’s default download directory using the file pattern `<your_script_name>.sql`.
+
+## [](#running-scripts-and-working-with-results)Running scripts and working with results
+
+At the bottom of each script tab, you can choose **Run** to execute SQL statements. SQL statements can only run on running engines. If an engine isn’t running, you can select it from the list and then choose the **Start** button for that engine. For more information about engines, see [Operate engines](/Guides/operate-engines/operate-engines.html)
+
+You can run all statements in a script or select snippets of SQL to run.
+
+**Running all SQL statements in a script**
+
+- Position the cursor anywhere in the script editor and then choose **Run**. All SQL statements must be terminated by a semi-colon (`;`) or an error occurs.
+
+**Running a snippet of SQL as a statement**
+
+- Select the SQL code you want to run as a statement and then choose **Run**. Behind the scenes, Firebolt automatically appends a semi-colon to the selected SQL code so it can run as a statement.
+
+### [](#viewing-results)Viewing results
+
+After you run a script or query statement, more results appear below the script editor, along with statistics about query execution. The statistics section will provide further information on your statement such as its status, duration, and more.
+
+![drawing](../../assets/images/develop_workspace_ex1.png)
+
+### [](#viewing-multi-statement-script-results)Viewing multi-statement script results
+
+When you run a script that has multiple SQL statements with result sets (`SELECT` statements), each result is shown on a separate line with statistics about statement execution. The first statement that ran is numbered 1 and at the bottom of the list.
+
+To view the results table for a result set, choose the table icon as shown in the example below.
+
+![drawing](../../assets/images/develop_workspace_ex6.png)
+
+### [](#exporting-results-to-a-local-hard-drive)Exporting results to a local hard drive
+
+You can export up to 10,000 rows of query results to your local hard drive after you run a query.
+
+1. Choose the download icon (see image below).
+2. Choose **Export table as CSV** or **Export table as JSON**.  
+   Firebolt downloads the file type that you chose to the default download location for your browser.
+
+It is possible to export the results of a single query alongside the results summary of all queries run in your script (with the statistics).
+
+## [](#switching-between-light-and-dark-mode)Switching between light and dark mode
+
+Click on the toggle at the bottom of the left navigation pane to switch between light and dark mode.
+
+![drawing](../../assets/images/develop_workspace_ex7.png)
+
+## [](#keyboard-shortcuts-for-the-develop-space)Keyboard shortcuts for the Develop Space
+
+- [Query operations](#query-operations)
+- [Script management](#script-management)
+- [Search functionality](#search-functionality)
+- [Editing text](#editing-text)
+
+**Tip:** Use the **Keyboard shortcuts panel** (`Ctrl + Shift + ?`) to quickly view available shortcuts directly within the Develop Space.
+
+### [](#query-operations)Query operations
+
+Function Windows &amp; Linux Shortcut Mac Shortcut **Run** the **currently selected query**. Ctrl + Enter ⌘ + Enter **Run all** queries in the current script. Ctrl + Shift + Enter ⌘ + Shift + Enter **Toggle** expanding or collapsing **query results**. Ctrl + Alt + E ⌘ + Option + E
+
+### [](#script-management)Script management
+
+Function Windows &amp; Linux Shortcut Mac Shortcut **Create** a new script. Ctrl + Alt + N ⌘ + Option + N **Jump** to a **previous** script. Ctrl + Alt + \[ ⌘ + Option + \[ **Jump** to the **next** script. Ctrl + Alt + ] ⌘ + Option + ] **Close** the **current** script. Ctrl + Alt + X ⌘ + Option + X **Close all** scripts. Ctrl + Alt + G ⌘ + Option + G **Close all but** the **current** script. Ctrl + Alt + O ⌘ + Option + O
+
+### [](#search-functionality)Search functionality
+
+Function Windows &amp; Linux Shortcut Mac Shortcut **Open** a **search** panel. Ctrl + F ⌘ + F **Find** the **next search result**. F3 F3 **Find** the **previous search result**. Shift + F3 Shift + F3
+
+### [](#editing-text)Editing text
+
+Function Windows &amp; Linux Shortcut Mac Shortcut **Toggle** adding or removing a **comment marker** for the current line. Ctrl + / Cmd + / **Toggle** adding or removing a **block comment marker** around a block of code or text. Shift + Alt + A Shift + Option + A **Automatically organize and indent** code for readability. Ctrl + Alt + F ⌘ + Option + F **Copy** the selected lines and paste them directly **above** the original. Alt + Shift + Up arrow Shift + Option + Up arrow **Move** the selected lines and paste them directly **above** the original without creating a duplicate. Alt + Up arrow Option + Up arrow **Copy** the selected lines and paste them directly **below** the original. Alt + Shift + Down arrow Shift + Option + Down arrow **Move** the selected lines and paste them directly **below** the original without creating a duplicate. Alt + Down arrow Option + Down arrow **Select text** to the **left** of the cursor. Alt + Shift + Left arrow Ctrl + Shift + Left arrow **Select text** to the **right** of the cursor. Alt + Shift + Right arrow Ctrl + Shift + Right arrow **Select** the **entire line**. Alt + L Ctrl + L **Decrease** the **indentation level** of the current or selected lines. Ctrl + \[ Cmd + \[ **Increase** the **indentation level** of the current or selected lines. Ctrl + ] Cmd + ] **Delete** the current or selected **lines**. Shift + Ctrl + K Shift + Cmd + K
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security.md b/cmd/docs-scrapper/fireboltdocs/guides_security.md
new file mode 100644
index 0000000..79183de
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security.md
@@ -0,0 +1,12 @@
+# [](#configure-security)Configure security
+
+Learn how to reduce potential attack surface with Firebolt’s security features, including multi-factor authentication and single-sign-on (SSO) integration, role-based access control (RBAC) and network policies to secure data assets in data warehouses.
+
+* * *
+
+- [Configure SSO](/Guides/security/sso/)
+- [Role-based access control (RBAC)](/Guides/security/rbac.html)
+- [Network policies](/Guides/security/network-policies.html)
+- [Multi-factor authentication](/Guides/security/enabling-mfa.html)
+- [Ownership](/Guides/security/ownership.html)
+- [AWS PrivateLink](/Guides/security/privatelink.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_enabling_mfa.md b/cmd/docs-scrapper/fireboltdocs/guides_security_enabling_mfa.md
new file mode 100644
index 0000000..4ce62a0
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_enabling_mfa.md
@@ -0,0 +1,36 @@
+# [](#enable-multi-factor-authentication-mfa)Enable multi-factor authentication (MFA)
+
+Enable multi-factor authentication (MFA) as an additional layer of security to protect data that is accessible through Firebolt. With MFA enabled, users must authenticate with a one-time code generated by their mobile device upon login. MFA can be enabled per login.
+
+Enabling MFA for a login requires the org\_admin role.
+
+## [](#enable-mfa-for-a-login)Enable MFA for a login
+
+### [](#sql)SQL
+
+To enable MFA for a login using SQL, use the [ALTER LOGIN](/sql_reference/commands/access-control/alter-login.html) statement. For example:
+
+```
+ALTER LOGIN "alex@acme.com" SET IS_MFA_ENABLED = TRUE;
+```
+
+Multi-factor authentication can also be set for new logins, with the [CREATE LOGIN](/sql_reference/commands/access-control/create-login.html) command. For example:
+
+```
+CREATE LOGIN "betsy@acme.com" SET IS_MFA_ENABLED = TRUE;
+```
+
+### [](#ui)UI
+
+To enable MFA for a login in the UI:
+
+![Configure > MFA](/assets/images/mfamanagement.png)
+
+1. Click **Configure** to open the configure space, then choose **Logins** from the menu.
+2. Search for the relevant login using the top search filters or by scrolling through the logins list. Toggle on **Is MFA enabled**.
+
+![Is MFA enabled](/assets/images/mfaenabled.png)
+
+MFA can also be enabled when creating a login, by toggling **Is MFA enabled** in the **Create login** window:
+
+![Enable MFA](../../assets/images/mfaloginenabled.png)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_network_policies.md b/cmd/docs-scrapper/fireboltdocs/guides_security_network_policies.md
new file mode 100644
index 0000000..16b0fae
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_network_policies.md
@@ -0,0 +1,101 @@
+# [](#manage-network-policies)Manage network policies
+
+By default, Firebolt accepts traffic from any IP address. As an additional layer of security, you can configure individual Firebolt logins or service accounts so their traffic must originate only from the IP addresses that you specify. For each configuration (network policy), you specify a list of IP addresses from which traffic is allowed (the allow list) and a list of IP addresses from which traffic is denied (the blocked list). A network policy is a collection of allowed and blocked lists of IP addresses.
+
+Network policies can be configured on the organization level and also per login or service account. When evaluating a network policy, Firebolt validates the login/service account IP addresses first by the policy set at organization level. If there is no network policy on the organization level (or the organization-level network policy does not allow access), then the network policy is validated at the login/service account level. If a network policy does not allow access, the user will receive a `401 Unauthorized` response.
+
+The IP allow and blocked lists used to specify a network policy are specified as comma-separated IPv4 addresses and/or IPv4 address ranges in CIDR format. You can apply the same list to one or many users, and each user can have unique lists. You can specify lists manually or import lists of addresses and ranges from a CSV file saved locally. You can add, edit or delete network policies using SQL or in the UI.
+
+To view all network policies, click **Configure** to open the configure space, then choose **Network policies** from the menu, or query the [information\_schema.network\_policies](/sql_reference/information-schema/network_policies.html) view.
+
+Managing network policies requires the org\_admin role.
+
+## [](#create-a-network-policy)Create a network policy
+
+### [](#sql)SQL
+
+To create a network policy using SQL, use the [CREATE NETWORK POLICY](/sql_reference/commands/access-control/create-network-policy.html) statement. For example:
+
+```
+CREATE NETWORK POLICY my_network_policy WITH ALLOWED_IP_LIST = (‘4.5.6.1’, ‘2.4.5.1’) DESCRIPTION = 'my new network policy'
+```
+
+### [](#ui)UI
+
+To create a network policy via the UI:
+
+![Configure > Network policies](/assets/images/networkpoliciespage.png)
+
+1. Click **Configure** to open the configure space, then choose **Network policies** from the menu.
+2. From the Network policies management page, choose **Create a new network policy**.
+3. Enter a network policy name. Optionally, enter a network policy description. To add to the allow list, enter comma-separated IPv4 addresses, or IPv4 address ranges in CIDR format under **Grant access from selected allowed IP addresses**, or choose **import file** to read IP addresses from a CSV file.
+4. Enter addreses for the block list in the **Deny access from selected blocked IP addresses**.
+5. Choose **Save**.
+
+For each user, the Allowed IPs and Blocked IPs are updated to reflect the total number of IP addresses from each list that you specified for that user. Network policies created in UI are automatically attached to the organization to which the policy creator is logged in.
+
+## [](#attach-a-network-policy-to-an-organization)Attach a network policy to an organization
+
+### [](#sql-1)SQL
+
+When a network policy is created in UI, it is automatically attached to an organization the creator is logged in to. However, to attach (or detach) a network policy, you can use the command [ALTER ORGANIZATION](/sql_reference/commands/data-definition/alter-organization.html). For example:
+
+```
+ALTER ORGANIZATION my_organization SET NETWORK_POLICY = my_network_policy
+```
+
+or to detach:
+
+```
+ALTER ORGANIZATION my_organization SET NETWORK_POLICY = DEFAULT
+```
+
+### [](#ui-1)UI
+
+To attach/detach a network policy to an organization via the UI:
+
+![Configure > Network policies](/assets/images/networkpoliciespagetoggle.png)
+
+1. Click **Configure** to open the configure space, then choose **Network policies** from the menu.
+2. Search for the relevant network policy using the top search filters or by scrolling through the list.
+3. Switch the **Is organizational** toggle to on or off.
+
+## [](#edit-a-network-policy)Edit a network policy
+
+### [](#sql-2)SQL
+
+To edit a network policy using SQL, use the [ALTER NETWORK POLICY](/sql_reference/commands/access-control/alter-network-policy.html) statement. For example:
+
+```
+ALTER NETWORK POLICY my_network_policy SET ALLOWED_IP_LIST = (‘4.5.6.7’, ‘2.4.5.7’) BLOCKED_IP_LIST = (‘6.7.8.9’) DESCRIPTION = 'updated network policy'
+```
+
+### [](#ui-2)UI
+
+To edit a network policy via the UI:
+
+1. Click **Configure** to open the configure space, then choose **Network policies** from the menu.
+2. Search for the relevant network policy using the top search filters or by scrolling through the list. Hover over the right-most column to make the network policy menu appear, then choose **Edit network policy**.
+3. From here you can edit description, allowed and blocked IP addresses and choose **Save**.
+
+![Edit network policy](../../assets/images/editnetworkpolicy.png)
+
+## [](#delete-a-network-policy)Delete a network policy
+
+### [](#sql-3)SQL
+
+To delete a network policy using SQL, use the [DROP NETWORK POLICY](/sql_reference/commands/access-control/drop-network-policy.html) statement. For example:
+
+```
+DROP NETWORK POLICY my_network_policy [ RESTRICT | CASCADE ]
+```
+
+### [](#ui-3)UI
+
+To delete a network policy via the UI:
+
+1. Click **Configure** to open the configure space, then choose **Network policies** from the menu.
+2. Search for the relevant network policy using the top search filters or by scrolling through the list. Hover over the right-most column to make the network policy menu appear, then choose **Delete network policy**. You will need to confirm that you will also be removing links to the network policy by choosing **Remove the linkage to logins, service accounts, or to the entire organization**
+3. Choose **Confirm**.
+
+![Delete network policy](../../assets/images/deletenetworkpolicy.png)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_ownership.md b/cmd/docs-scrapper/fireboltdocs/guides_security_ownership.md
new file mode 100644
index 0000000..22bb4c7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_ownership.md
@@ -0,0 +1,77 @@
+# [](#ownership)Ownership
+
+Ownership allows users to perform all operations on any object they created without having to grant privileges for these operations manually. This provides a smoother user experience because objects are immediately available to use as they are created. These operations include granting privileges on owned objects.
+
+## [](#supported-object-types)Supported object types
+
+The object types that support ownership are:
+
+- Role
+- User
+- Engine
+- Database
+- Schema
+- Table
+- View
+
+The current owner of an object can be viewed in the corresponding information\_schema view:
+
+Object View Role N/A User [information\_schema.users](/sql_reference/information-schema/users.html) Database [information\_schema.catalogs](/sql_reference/information-schema/catalogs.html) Engine [information\_schema.engines](/sql_reference/information-schema/engines.html) Schema [information\_schema.schemata](/sql_reference/information-schema/schemata.html) Table [information\_schema.tables](/sql_reference/information-schema/tables.html) View [information\_schema.views](/sql_reference/information-schema/views.html) or [information\_schema.tables](/sql_reference/information-schema/tables.html)
+
+Index ownership, shown in [information\_schema.indexes](/sql_reference/information-schema/indexes.html), will always show the table owner as an index’s owner.
+
+## [](#changing-an-objects-owner)Changing an object’s owner
+
+The owner of an object may alter its ownership using the following syntax:
+
+```
+ALTER <object type>  <object name> OWNER TO <user>
+```
+
+Examples:
+
+```
+ALTER DATABASE db OWNER TO new_owner
+ALTER ENGINE eng OWNER TO new_owner
+ALTER ROLE r OWNER TO new_owner
+ALTER USER u OWNER TO new_owner
+ALTER SCHEMA public OWNER TO new_owner
+ALTER TABLE t OWNER TO new_owner
+ALTER VIEW v OWNER TO new_owner
+```
+
+## [](#dropping-users-that-own-objects)Dropping users that own objects
+
+Any objects owned by a user must first be dropped or have their owner changed before dropping the user.
+
+A table owner can drop the table even if there are views referencing it that are not owned by the table’s owner, using the `CASCADE` parameter to [DROP TABLE](/sql_reference/commands/data-definition/drop-table.html).
+
+## [](#transfer-ownership-using-the-firebolt-workspace)Transfer ownership using the Firebolt Workspace
+
+You can use the user interface in the **Firebolt Workspace** to transfer ownership of objects as follows:
+
+1. Log in to the [Firebolt Workspace](https://firebolt.go.firebolt.io/signup). If you don’t yet have an account with Firebolt, you can sign up for one.
+2. Select the Govern icon (![The icon to open the Govern Space.](../../assets/images/govern-icon.png)) in the left navigation pane to open the **Govern Space**.
+3. Select **Ownership** from the left navigation pane.
+4. Select the three horizontal dots (…) to the right of the object that you want to transfer ownership of.
+5. Select **Transfer ownership** from the drop-down list.
+6. In the **Transfer ownership** window that opens, choose a new owner from the drop-down list.
+7. Select the **Transfer ownership** button to confirm.
+
+##### [](#viewing-all-objects-owned-by-a-user)Viewing all objects owned by a user
+
+1. From the [Firebolt Workspace](https://firebolt.go.firebolt.io/signup), select the Govern icon (![The icon to open the Govern Space.](../../assets/images/govern-icon.png)) in the left navigation pane to open the **Govern Space**.
+2. Select **Users** from the left navigation pane.
+3. Select the user from the **User Name** column.
+4. Select the **Ownership** tab to view a list of objects owned by the selected user.
+
+##### [](#bulk-transferring-or-deleting-objects-owned-by-a-user)Bulk transferring or deleting objects owned by a user
+
+1. From the [Firebolt Workspace](https://firebolt.go.firebolt.io/signup), select the Govern icon (![The icon to open the Govern Space.](../../assets/images/govern-icon.png)) in the left navigation pane to open the **Govern Space**.
+2. Select **Users** from the left navigation pane.
+3. Select the three horizontal dots (…) to the right of the user whose objects you want to transfer ownership of.
+4. Select **Transfer ownership** from the drop-down list.
+5. In the window that opens, select the checkboxes next to objects that you want to delete or transfer ownership of.
+6. Select the **Delete object** or **Transfer ownership** button to apply changes.
+
+Ownership transfer using the **Firebolt Workspace** is not available for `Schema`, `Table`, and `View` objects. These must be modified using SQL commands in the **Develop Workspace** or using the [Firebolt API](/API-reference/).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_privatelink.md b/cmd/docs-scrapper/fireboltdocs/guides_security_privatelink.md
new file mode 100644
index 0000000..f056b6c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_privatelink.md
@@ -0,0 +1,117 @@
+# [](#aws-privatelink)AWS PrivateLink
+
+Firebolt supports AWS PrivateLink to help you securely access the Firebolt API without exposing traffic to the public internet. AWS PrivateLink enhances security, minimizes data exposure, and improves network reliability by keeping traffic within AWS. This guide shows you how to:
+
+- [Request AWS PrivateLink access](#request-aws-privatelink-access)
+- [Configure your VPC endpoint](#configure-your-vpc-endpoint)
+- [Configure your service account](#configure-your-service-account)
+- [Test your AWS PrivateLink connection](#test-your-aws-privatelink-connection)
+
+AWS PrivateLink for Firebolt is in public preview and available in all Firebolt regions.
+
+## [](#prerequisites)Prerequisites
+
+Before setting up AWS PrivateLink, ensure you have the following:
+
+- An **AWS account** with permissions to create a [VPC interface endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html). If you don’t have access, you can [sign up](https://signin.aws.amazon.com/signup) for an AWS account.
+- A **Firebolt Account**: Ensure that you have access to an active Firebolt account. If you don’t have access, you can [sign up for an account](https://www.firebolt.io/sign-up). For more information about how to register with Firebolt, see [Get started with Firebolt](/Guides/getting-started/).
+- **Service Account**: You must have access to an active Firebolt [service account](/Guides/managing-your-organization/service-accounts.html), which facilitates programmatic access to Firebolt. Your service account must be associated with a [user](/Overview/organizations-accounts.html#users) with privileges associated with an [account administrative role](/Overview/organizations-accounts.html#account-administrative-role) or an [organizational administrative role](/Overview/organizations-accounts.html#organizational-administrative-role) to request AWS PrivateLink access.
+
+## [](#request-aws-privatelink-access)Request AWS PrivateLink access
+
+After meeting the previous prerequisites, request AWS PrivateLink access using Firebolt’s user interface as follows:
+
+1. [Log in](https://go.firebolt.io/signup) to the **Firebolt Workspace**.
+2. Select the **Help** icon (?) at the bottom of the left navigation pane.
+3. Select **Request PrivateLink**.
+4. In the pop-up window, enter the following information:
+   
+   1. **Organization Name** – The name of your [organization](/Overview/organizations-accounts.html#organizations) in Firebolt.
+   2. **Account** – The Firebolt [account](/Overview/organizations-accounts.html#accounts) associated with a [role](/Overview/organizations-accounts.html#roles) with sufficient permission to request AWS PrivateLink. These include the [account administrative](/Overview/organizations-accounts.html#account-administrative-role) or [organizational administrative roles](/Overview/organizations-accounts.html#organizational-administrative-role).
+   3. **AWS Account IDs** – The AWS account IDs for which you want to create a PrivateLink integration. For additional information about permissions, see [Manage permissions](https://docs.aws.amazon.com/vpc/latest/privatelink/configure-endpoint-service.html#add-remove-permissions).
+5. After you submit the AWS PrivateLink request, Firebolt’s support team will review it, provision a dedicated VPC endpoint in your Account’s AWS Region, and send an email to the requestor containing the `Endpoint URL` and `endpointServiceId`. Save this information for configuration.
+
+### [](#configure-your-vpc-endpoint)Configure your VPC endpoint
+
+After you have requested AWS PrivateLink on Firebolt’s user interface, login to AWS and configure a VPC endpoint as follows:
+
+01. Sign in to the [AWS Management Console](https://aws.amazon.com/console/).
+02. In the search bar at the top, enter **VPC**.
+03. Select **VPC (Virtual Private Cloud)** from the dropdown list.
+04. In the left navigation pane under **VPC Dashboard**, expand **PrivateLink and Lattice**.
+05. Select **Endpoints**.
+06. In the upper right corner, select **Create endpoint**.
+07. In the **Create endpoint** pane, enter an optional **Name tag** to identify your endpoint.
+08. Select the radio button next to **Endpoint services that use NLBs and GWLBs**.
+09. In the **Service settings** pane, in the text box under **Service name**, enter the `endpointServiceId` provided in the email from Firebolt’s support team in the previous step to [request AWS PrivateLink access](#request-aws-privatelink-access).
+10. Select **Verify service** to confirm that your AWS PrivateLink access is configured correctly. and select Other endpoint services.
+11. In the **Network settings** pane, select the down arrow to select your autopopulated **VPC** from the dropdown list.
+12. Select the checkbox **Enable DNS NAME**.
+13. In the **Subnets** pane select the checkbox next to the subnets that match the **Availability Zone** where your resources reside in your AWS Region.
+14. Select the down arrow under **Subnet ID** and hoose the appropriate Subnet ID for your VPC.
+15. In the **Security groups** pane, select the checkbox next to the **Group ID** of your security group. Your security group should allow inbound traffic on **port 443** in order to interact with the Firebolt API.
+16. Select the **Create endpoint** button in the bottom-right corner of the main workspace.
+17. After the endpoint is created, ensure that your security groups and route tables are correctly configured to allow traffic to the endpoint, so that your intended workloads can access Firebolt over the Private API endpoint. Use the following code example to validate your connection to Firebolt by sending it from an EC2 instance in your VPC:
+
+```
+curl -v https://api.app.firebolt.io --resolve api.app.firebolt.io:443:<PRIVATE_IP_OF_VPC_ENDPOINT>
+```
+
+In the previous code example, replace with the private IP address of your newly created VPC endpoint network interface.
+
+### [](#configure-your-service-account)Configure your service account
+
+Configure your Firebolt [service account](/Guides/managing-your-organization/service-accounts.html) with the `PRIVATE_ONLY` connection preference to ensure it accesses Firebolt only through AWS PrivateLink and uses private APIs. A claim is a setting that defines how a connection behaves. The `PRIVATE_ONLY` claim enforces private networking by restricting access to public endpoints.
+
+Use the following code example inside the **Develop Workspace** in the **Firebolt Workspace**:
+
+```
+CREATE SERVICE ACCOUNT IF NOT EXISTS "test_sa"
+WITH CONNECTION_PREFERENCE = PRIVATE_ONLY;
+```
+
+### [](#test-your-aws-privatelink-connection)Test your AWS PrivateLink connection
+
+After configuring your VPC to use the Firebolt AWS PrivateLink endpoint, test connectivity using the endpoint URL provided by the Firebolt support team.
+
+Use the following curl command to retrieve the private endpoint from your account:
+
+```
+curl https://api.go.firebolt.io/web/v3/account/developer/engineUrl \
+-H 'Accept: application/json' \
+-H "Authorization: Bearer $TOKEN"
+{
+    "engineUrl": "01hnj9r1xrx3a4t3kb1ec7qs2b.api-private.us-east-1.app.firebolt.io"
+}
+```
+
+If your service account has the `PRIVATE_ONLY` claim, requests from that service account to any Firebolt public endpoint will fail.
+
+When using the `PRIVATE_ONLY` claim, requests to the private endpoint complete successfully if the traffic originates from an authorized AWS VPC endpoint with the necessary route tables, security group rules, and network access control lists to enable communication.
+
+The following code example sends a `SELECT 42` query to a Firebolt private API endpoint using `curl`, authenticates with a bearer token, and returns a JSON response containing the query result:
+
+```
+curl --location 'https://01hnj3r1xrx3a4t3kb1ec7qs2b.api-private.us-east-1.app.firebolt.io' \
+--header "Authorization: Bearer $TOKEN" \
+--data 'SELECT 42'
+
+{
+    "meta": [
+        {
+            "name": "?column?",
+            "type": "int"
+        }
+    ],
+    "data": [
+        {
+            "?column?": 42
+        }
+    ],
+    "rows": 1,
+    "statistics": {
+        "elapsed": 0.014256,
+        "rows_read": 1,
+        "bytes_read": 1
+}
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_rbac.md b/cmd/docs-scrapper/fireboltdocs/guides_security_rbac.md
new file mode 100644
index 0000000..17fd2ea
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_rbac.md
@@ -0,0 +1,194 @@
+# [](#manage-role-based-access-control)Manage role-based access control
+
+Role-Based Access Control (RBAC) allows you to manage user permissions by controlling who can access or perform operations on specific objects in Firebolt. This guide provides a step-by-step process for setting RBAC in Firebolt.
+
+## [](#prerequisites)Prerequisites
+
+The following material can help you understand key concepts related to organizations and RBAC in Firebolt:
+
+- [Organizations and accounts](/Overview/organizations-accounts.html) – How Firebolt provides a structure for managing users, resources, and permissions.
+- [Role-Based Access Control](/Overview/Security/Role-Based%20Access%20Control/) – How administrators manage user permissions and control access to resources based on predefined roles.
+
+## [](#view-all-roles)View all roles
+
+To view all roles using the **Firebolt Workspace**, do the following:
+
+1. Login to the [Firebolt Workspace](https://firebolt.go.firebolt.io/signup).
+2. Select the **Govern** icon (![The Firebolt Govern Space icon.](../../assets/images/govern-icon.png))from the left navigation bar to open the **Govern Space**.
+3. Choose **Roles** from the left panel under **Govern**.
+
+To view all roles using SQL, query the [information\_schema.applicable\_roles](/sql_reference/information-schema/applicable-roles.html) view as shown in the following code example:
+
+```
+SELECT
+  *
+FROM
+  information_schema.applicable_roles;
+```
+
+## [](#create-a-role)Create a role
+
+You can create a role using the **Firebolt Workspace** user interface (UI) or using SQL.
+
+### [](#create-a-role-using-sql)Create a role using SQL
+
+The following code example uses [CREATE ROLE](/sql_reference/commands/access-control/create-role.html) to create the role `user_role`:
+
+```
+CREATE ROLE user_role;
+```
+
+### [](#create-a-role-using-the-ui)Create a role using the UI
+
+To create a custom role using the UI:
+
+1. Select the **Govern** icon (![The Firebolt Govern Space icon.](../../assets/images/govern-icon.png)) from the left navigation bar to open the **Govern Space**.
+2. Choose **Roles** from the left panel under **Govern**.
+3. Choose the **+ New Role** button in the upper-right corner of the page.
+4. Under **Create role**, enter a role name.
+5. Under **Role privileges:**, select the object type that you want to grant permissions for. You can choose either **Databases** or **Engines**.
+6. Configure permissions for the role:
+   
+   - Toggle the buttons under **Databases privileges** or **Engine privileges** to grant permissions to **create** or **modify** an objects across all databases or engines. If you want to apply permissions to a specific engine or database, select it from the table under the toggle buttons.
+   - Define permissions more granularly using table views.
+
+## [](#delete-a-role)Delete a role
+
+You can delete a role using either the UI in the **Govern Workspace** or using SQL.
+
+### [](#delete-a-role-using-sql)Delete a role using SQL
+
+To delete a role using SQL, use [DROP ROLE](/sql_reference/commands/access-control/drop-role.html) as shown in the following code example:
+
+```
+DROP ROLE user_role;
+```
+
+### [](#delete-a-role-using-the-ui)Delete a role using the UI
+
+To delete a role via the UI:
+
+1. Select the **Govern** icon (![The Firebolt Govern Space icon.](../../assets/images/govern-icon.png)) from the left navigation bar to open the **Govern Space**.
+2. Choose **Roles** from the left panel under **Govern**.
+3. Search for the relevant role using the top search filters or by scrolling through the list. Hover over the right-most column to make the role menu appear, then choose **Delete role**.
+4. Choose **Confirm**.
+
+## [](#grant-permissions-to-a-role)Grant permissions to a role
+
+### [](#grant-permissions-using-sql)Grant permissions using SQL
+
+To grant a permission to a role using SQL, use [GRANT](/sql_reference/commands/access-control/grant.html) as shown in the following code example:
+
+```
+GRANT USAGE ON DATABASE my_db TO user_role;
+```
+
+### [](#grant-permissions-using-the-ui)Grant permissions using the UI
+
+To grant a permission to a role via the UI:
+
+1. Select **Govern** to open the govern space, then choose **Roles** from the menu:
+2. Search for the relevant role either by using the search filters at the top of the page, or by scrolling through the list of logins. Hover over the right-most column to make the role menu appear, then choose **Edit role**.
+3. Navigate to the permissions tab and select the desired permissions. To grant permissions over all objects of that type, choose the topmost line.
+4. Select **Update**.
+
+## [](#grant-a-role-to-users)Grant a role to users
+
+### [](#grant-a-role-to-users-using-sql)Grant a role to users using SQL
+
+To grant a role to a user or another role using SQL, use [GRANT ROLE](/sql_reference/commands/access-control/grant.html) as shown in the following code example:
+
+```
+GRANT ROLE user_role TO ROLE user2_role;
+```
+
+### [](#grant-a-role-using-the-ui)Grant a role using the UI
+
+To grant a role to a user via the UI:
+
+1. Select **Govern**, then choose **Users** from the menu:
+2. In the user’s row, select the three horizontal dots to the right.
+3. Select **Edit user details**.
+4. Select the drop-down list next to **Role**.
+5. Select the checkbox next to the roles that you want to grant.
+6. Select **Edit user**.
+
+## [](#revoke-permissions)Revoke permissions
+
+You can revoke permissions using the UI in the **Govern Space** or using SQL.
+
+### [](#revoke-permissions-using-sql)Revoke permissions using SQL
+
+To revoke a permission from a role using SQL, use [REVOKE](/sql_reference/commands/access-control/revoke.html) as shown in the following example:
+
+```
+REVOKE USAGE ON DATABASE my_db FROM user_role;
+```
+
+### [](#revoke-permissions-using-the-ui)Revoke permissions using the UI
+
+To revoke permissions, follow the same steps described in [Grant permissions to a role](#grant-permissions-to-a-role).
+
+## [](#revoke-role)Revoke role
+
+You can revoke a role from either a user or another role using either the UI in the **Govern Space** or SQL.
+
+### [](#revoke-a-role-using-sql)Revoke a role using SQL
+
+To revoke a role from a user or another role using SQL, use the [REVOKE ROLE](/sql_reference/commands/access-control/revoke.html) statement. For example:
+
+```
+REVOKE ROLE user_role FROM USER alex;
+```
+
+### [](#revoke-a-role-using-the-ui)Revoke a role using the UI
+
+To revoke a role, follow the steps in [Grant a role to users](#grant-a-role-to-users).
+
+### [](#check-assigned-privileges-using-sql)Check assigned privileges using SQL
+
+To check the effective privileges for the current user, run the following example query:
+
+```
+SELECT
+  AR.grantee,
+  AR.role_name,
+  OP.privilege_type,
+  OP.object_type,
+  OP.object_name
+FROM information_schema.transitive_applicable_roles AS AR
+JOIN information_schema.object_privileges AS OP
+ON (AR.role_name = OP.grantee)
+WHERE
+  AR.grantee = session_user();
+```
+
+**Returns**:
+
+grantee role\_name privilege\_type object\_type object\_name test\_user account\_admin USAGE engine engine1 test\_user account\_admin USAGE database db1
+
+#### [](#owner-rights)Owner rights
+
+When a query is run on a view, the database checks and uses the permissions of the view’s owner to access the underlying objects that view references, rather than the permissions of the user that ran the query on the view. The view’s owner is the user that created the view.
+
+The following code example shows how granting and revoking privileges affects access to a base table and its view, ultimately causing an authorization failure when the view’s owner loses schema usage privileges:
+
+```
+CREATE USER user1 WITH ROLE=role1;
+CREATE USER user2 WITH ROLE=role2;
+
+CREATE TABLE base_table (a int); -- executed by user1
+CREATE VIEW view_over_base_table AS SELECT * FROM base_table; -- executed by user1
+
+GRANT SELECT ON VIEW view_over_base_table TO role2;
+REVOKE SELECT ON TABLE base_table FROM role2;
+
+SELECT * FROM base_table; -- executed by user2, fails with an authorization error
+SELECT * FROM view_over_base_table; -- executed by user2, successfully
+
+REVOKE USAGE ON SCHEMA public FROM role1;
+-- role1 no longer has no access to the table due to missing schema usage privileges
+SELECT * FROM view_over_base_table; -- executed by user2 and fails because the view owner's role1 cannot access table t
+```
+
+If the view owner’s privileges are revoked, the query will fail even if the user has access to the view.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_sso.md b/cmd/docs-scrapper/fireboltdocs/guides_security_sso.md
new file mode 100644
index 0000000..fe7f871
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_sso.md
@@ -0,0 +1,28 @@
+# [](#configure-your-idp)Configure your IdP
+
+An **Identity Provider (IdP)** is a service that handles user authentication and manages user identities. When you set up Single Sign-On (SSO), the IdP verifies your users’ credentials and allows them to access multiple applications, including Firebolt, without needing to login repeatedly.
+
+For your organization, an IdP simplifies user management and strengthens security. You can enforce centralized security policies, like multi-factor authentication (MFA), and quickly revoke access when someone leaves the team.
+
+For your users, using single sign-on gives them access to all the tools they need, including Firebolt.
+
+Single-sign on (SSO) is an authentication process that allows access to multiple applications or services with a single set of credentials. It provides a centralized authentication mechanism for your organization so that it’s easier to manage user access, enforce security policies, and revoke access when necessary.
+
+## [](#pre-requisites)Pre-requisites
+
+Before you can use SSO with Firebolt, you must complete specific configuration steps in your Identity Provider (IdP) system, which is responsible for authenticating users and managing their credentials. Part of these steps include defining an **Audience URI**, which specifies the intended recipient of a SAML assertion about a user’s authentication. The configuration of an Audience URI depends on your IdP. See the following list of supported IdPs for specific instructions.
+
+If your Audience URI is not configured correctly, Security Assertion Markup Language (SAML) assertions used for authentication will fail, preventing users from signing in using SSO.
+
+## [](#supported-idps)Supported IdPs
+
+Firebolt allows you to sign in using federated identities. The SSO implementation supports the following IdPs:
+
+- [Auth0](/Guides/security/sso/auth0.html)
+- [Okta](/Guides/security/sso/okta.html)
+- [OneLogin](/Guides/security/sso/onelogin.html)
+- [Salesforce](/Guides/security/sso/salesforce.html)
+- [PingFederate (Ping Identity)](/Guides/security/sso/pingfederate.html)
+- [Custom Identity provider](/Guides/security/sso/custom-sso.html)
+
+If your IdP is not listed but supports SAML2.0, contact the [Firebolt support team](mailto:support@firebolt.io).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_sso_auth0.md b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_auth0.md
new file mode 100644
index 0000000..7785b24
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_auth0.md
@@ -0,0 +1,99 @@
+# [](#auth0)Auth0
+
+[Auth0](https://auth0.com/) is an identity management platform that provides authentication and authorization services for applications. Auth0 supports implementing secure login systems with authentication methods including single-sign on (SS0).
+
+To integrate Auth0 with Firebolt’s platform, you need to configure both an [Auth0 application for Firebolt](#configure-an-auth0-application) and [Firebolt’s SSO for Auth0](#configure-firebolt-for-auth0). Detailed instructions can be found in the following sections:
+
+## [](#configure-an-auth0-application)Configure an Auth0 application
+
+01. Login to your Auth0 Dashboard. If you don’t yet have an account with Auth0, you can [sign up](https://auth0.com/signup) to access their services.
+02. Select **Applications** from the left navigation panel.
+03. Select **Applications** again.
+04. Select the **+ Create Application** button.
+05. Under **Name**, enter a name for your application.
+06. In the dropdown list under **Application Type**, select **Regular Web Application**.
+07. Select **Create the Application**.
+08. Once your application is created, it will appear under **Applications**. Select the three horizontal dots (…) next to your application’s name, and select **Settings** from the dropdown list.
+09. Navigate to the **Application URIs** section.
+10. In the textbox under **Application Login URI**, enter your Firebolt organization URL address, followed by `/login?`. For example, `https://staging-go.firebolt.io/login?`.
+11. In the textbox under **Allowed Callback URLs** field, provide a callback URL with the following format: `https://id.app.firebolt.io/login/callback?connection=<org_name>-<provider>&organization=<organization_identifier>`. For example, `https://id.app.firebolt.io/login/callback?connection=firebolt-staging-auth0&organization=org_UJhpsQ5ypXVU8JVB`. The following apply:
+    
+    - **`<org_name>`** - the organizational name used to create your Firebolt account referenced in your vanity URL.
+    - **`<provider>`** - the provider, `Auth0`.
+    - **`<organization_identifier>`** - the unique identifier for your organization in Firebolt. To retrieve your **`<organization_identifier>`** , do the following:
+      
+      1. Login to the [Firebolt Workspace](https://go.firebolt.io/signup).
+      2. Select the **Configure** icon (![The Firebolt Configure Space icon.](../../../assets/images/configure-icon.png)).
+      3. Select **SSO** from the left navigation pane.
+      4. Select **Copy organization SSO identifier**.
+12. Save the configuration.
+13. Select the **Addons** tab at the top of the application work area.
+14. Toggle **SAML2 WEB APP**.
+15. In the **Usage** tab, do the following:
+    
+    1. Copy the `Identity Provider Login URL` and save for the following Firebolt configuration step.
+    2. Note the **Issuer** for the following Firebolt configuration step.
+    3. Select **Download Auth0 certificate**. These are needed to configuring Firebolt to work with the Auth0 IdP.
+16. Select the **Settings** tab.
+17. Select **Enable** to enable the SSO using SAML2.0 on the IdP. You are now ready to configure Firebolt to use Auth0 as your IdP.
+
+## [](#configure-firebolt-for-auth0)Configure Firebolt for Auth0
+
+Once your Identity Provider(IdP) is configured, you can now configure Firebolt to integrate with Auth0 either using SQL scripts in the **Develop Space** or through the user interface (UI) in the **Configure Space**.
+
+### [](#configure-firebolt-to-integrate-with-auth0-using-the-ui)Configure Firebolt to integrate with Auth0 using the UI
+
+1. Login to the [Firebolt Workspace](https://go.firebolt.io/signup).
+2. Select the **Configure** icon (![The Firebolt Configure Space icon.](../../../assets/images/configure-icon.png)).
+3. Select **SSO** from the left navigation pane.
+4. Under **Configure SSO for your organization**, enter the following:
+   
+   1. **Sign-on URL** - Enter the sign-on URL, provided by the SAML identity provider, where Firebolt will send SAML requests. The URL is specific to the IdP and is defined during configuration. For Auth0, this value corresponds to the Identity Provider Login URL value copied in **Step 15** of the [Auth0 application configuration](#configure-an-auth0-application).
+   2. **Issuer** - A unique value generated by the SAML identity provider specifying the issuer value. The issuer corresponds to the **Issuer** value noted in **Step 15** of the [Auth0 application configuration](#configure-an-auth0-application).
+   3. **Provider** - The provider’s name, `Auth0`.
+   4. **Label**: The label to use for the SSO login button. You can use any label name. If the label is not provided, Firebolt uses the value in the **Provider** field.
+   5. (Optional) **Sign-out URL** - An endpoint provided by Auth0 that facilitates the logout process by redirecting the user to this URL, ending their session.
+   6. **Signing certificate** - A digital certificate used to verify the authenticity of a signature used to communication between Auth0 and Firebolt. The certificate must be in Privacy Enhanced Mail (PEM) or CER format, and can be uploaded from your computer by selecting **Import certificate** or entered in the text box under **Signing certificate**.
+   7. **Field mapping** - A mapping used to match user attributes between Auth0 and Firebolt. Enter the **First name** and **Last name** in your Auth0 profile. Mapping is only required the first time a user logs in using SSO.
+   8. Select **Update changes**.
+
+### [](#configure-firebolt-to-integrate-with-auth0-using-sql)Configure Firebolt to integrate with Auth0 using SQL
+
+Login to Firebolt’s [Workspace](https://go.firebolt.io/login). If you haven’t yet registered with Firebolt, see [Get Started](/Guides/getting-started/). If you encounter any issues, reach out to [support@firebolt.io](mailto:support@firebolt.io) for help. Then, do the following:
+
+1. Select the Develop icon (![The Firebolt Develop Space icon.](../../../assets/images/develop-icon.png)).
+2. By default, when you login to **Firebolt’s Workspace** for the first time, Firebolt creates a tab in the **Develop Space** called **Script 1**. The following apply:
+
+<!--THE END-->
+
+- The database that Script 1 will run using is located directly below the tab name. If you want to change the database, select another database from the drop-down list.
+- An engine must be running to process the script in a selected tab. The name and status of the engine that Script 1 uses for computation is located to the right of the current selected database.
+
+Select system from the drop-down arrow next to the engine name. The system engine is always running, and you can use it to create a service account. You can also use an engine that you create.
+
+1. Use the syntax in the following example code to create an SSO connection in the **SQL Script Editor**:
+
+```
+ALTER ORGANIZATION vsko SET SSO = '{
+  "signOnUrl": "https://dev-1234567890123456.us.auth0.com/samlp/123456789012345678901234567890123",
+  "signoutURL": "http://your-sign-out-URL",
+  "issuer": "auth0",
+  "provider": "auth0",
+  "label": "Auth0 Company IdP",
+  "fieldMapping": {
+    "given_name": "name",
+    "family_name": "surname"
+  },
+  "certificate": "<certificate>"
+}';
+```
+
+In the previous code example, the following apply:
+
+- `signOnUrl`- The sign-on URL, provided by the SAML identity provider, where Firebolt will send SAML requests. The URL is specific to the IdP and is defined during configuration. For Auth0, this value corresponds to the Identity Provider Login URL value copied in **Step 15** of the [Auth0 application configuration](#configure-an-auth0-application).
+- (Optional)`signoutUrl`- An endpoint provided by Auth0 that facilitates the logout process by redirecting the user to this URL, ending their session.
+- `issuer` - A unique value generated by the SAML identity provider specifying the issuer value. The issuer corresponds to the **Issuer** value noted in **Step 15** of the [Auth0 application configuration](#configure-an-auth0-application).
+- `provider` - The provider’s name, `Auth0`.
+- `label` - The label to use for the SSO login button. You can use any label name. If the label is not provided, Firebolt uses the value in the **Provider** field.
+- `certificate` - A digital certificate used to verify the authenticity of a signature used to communication between Auth0 and Firebolt. The certificate must be in Privacy Enhanced Mail (PEM) or CER format.
+- `field mapping` - A mapping used to match user attributes between Auth0 and Firebolt. Enter the first name and surname in your Auth0 profile. Mapping is only required the first time a user logs in using SSO.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_sso_custom_sso.md b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_custom_sso.md
new file mode 100644
index 0000000..7637f79
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_custom_sso.md
@@ -0,0 +1,161 @@
+# [](#custom-identity-provider)Custom Identity Provider
+
+A custom Identity Provider (IdP) allows you to use your organization’s existing authentication system for secure access to Firebolt using Single Sign-On (SSO). By configuring a custom IdP, you ensure that your team can securely and efficiently access Firebolt resources using familiar credentials.
+
+To integrate a custom IdP with Firebolt’s platform, you need to [configure your IdP for Firebolt](#configure-custom-identity-provider-idp) and [Firebolt’s SSO for your custom IdP](#configure-firebolt-for-custom-idp). Detailed instructions can be found in the following sections:
+
+## [](#configure-custom-identity-provider-idp)Configure Custom Identity Provider (IdP)
+
+In order to set up a SAML 2.0 compliant service or application as your Identity Provider (IdP) for Single Sign-On (SSO) with Firebolt, follow these steps:
+
+1. **Define a custom SHA-256**
+   
+   In the service/application interface, define a custom SHA-256 application specifically for Firebolt. Follow the service or application’s instructions to create this custom application.
+2. **Create Users in the Service/Application**
+   
+   For each end-user that needs access to Firebolt:
+   
+   - Create a user in the service/application interface.
+   - Ensure that each user’s email address is correctly specified. Firebolt uses these email addresses to create corresponding logins in Firebolt. For more details, refer to [setting up SSO](/Guides/security/sso/).
+3. **Obtain required values for IdP setup**
+   
+   To properly configure your IdP, you’ll need to configure the **Audience URI and ACS (Assertion Consumer Service) URL**, which are crucial for successful SSO authentication. If not configured properly, authentication will fail.
+   
+   The **Audience URI** ensures that authentication requests are directed to the correct Firebolt tenant, and has the following format: `urn:auth0:app-firebolt-v2:<org_name>-<provider_name>`.
+   
+   The **ACS URL** is where the IdP sends authentication responses after login, and has the following format: `https://id.app.firebolt.io/login/callback?connection=<org_name>-<provider_name>&organization=<organization_identifier>`.
+   
+   In the previous example formats, the following apply:
+   
+   - **`<org_name>`** : The organizational name used to create your Firebolt account, as seen in your vanity URL.
+   - **`<provider>`** : The provider being configured as your IdP
+   - **`<organization_identifier>`** : A unique identifier for your organization. To retrieve this value, navigate to **Configure &gt; SSO** in the Firebolt UI and select **Copy organization SSO identifier**.
+   
+   For example, if your organization name is `acmeorg` and the provider name is `custom`, the values for Audience URI and ACS URL should be as follows:
+   
+   - Audience URI: `urn:auth0:app-firebolt-v2:acmeorg-custom`
+   - ACS URL: `https://id.app.firebolt.io/login/callback?connection=acmeorg-custom&organization=<organization_identifier>`
+   
+   The **Audience URI** (also known as Audience Restriction) defines the intended recipient of the SAML (Security Assertion Markup Language) Assertion. Depending on the vendor, this might also be referred to as the **Entity ID**.
+4. **Obtain SSO URL and Certificate**
+   
+   Retrieve the following from your custom IdP:
+   
+   - **SSO URL** : The endpoint where Firebolt sends SAML requests.
+   - **Certificate** : Used to verify communication between the IdP and Firebolt.
+
+With all required information, you are now ready to integrate your Identity Provider with Firebolt.
+
+## [](#configure-firebolt-for-custom-idp)Configure Firebolt for custom IdP
+
+Once your Identity Provider(IdP) is configured, you can now configure Firebolt to integrate with your IdP. This can be done using either the Firebolt UI, or using SQL.
+
+### [](#integrate-with-idp-using-the-ui)Integrate with IdP using the UI
+
+1. To configure the Firebolt SSO integration using the UI, Navigate to **Configure &gt; SSO** in Firebolt.
+2. Enter the following information:
+   
+   - `Sign-on URL`: The URL provided by your SAML identity provider where Firebolt sends SAML requests. This URL is IdP-specific and is determined during the identity provider’s configuration.
+
+Example (for Okta):  
+`https://okta_account_name.okta.com/app/okta_firebolt_app_id/sso/saml`
+
+- `Issuer`: A unique value generated by the SAML identity provider, identifying the issuer.
+- `Provider`: The name of your identity provider, such as `JumpCloud`.  
+  If you are using a SAML 2.0-compliant service or application as your IdP, select the **Custom** label.
+- `Label`: The text displayed on the SSO login button. If left blank, the value from the **Provider** field will be used.
+- `Certificate`: The certificate used to verify communication between the identity provider and Firebolt. It must be in PEM or CER format. You can upload it using the **Import certificate** button or paste it directly into the provided text box.
+- `Sign-out URL`: The URL provided by the application owner to redirect users when they sign out.
+- `Field mapping`: Mapping to your identity provider’s first and last name in key-value pairs. If additional fields are required, choose **Add another key-value pair**. Mapping is required for Firebolt to fill in the login’s given and last names the first time the user logs in using SSO. If this field remains empty when a login that represents the user is being created (read more in the [log in using SSO](#log-in-using-sso) section), the login’s first and last name fields will contain “NA”. Those fields can be updated later by running the [ALTER LOGIN](/sql_reference/commands/access-control/alter-login.html) command. Here’s an example of how to set up **Field mapping**:
+  
+  ```
+    {
+        "given_name": "name",
+        "family_name": "surname"
+    }
+  ```
+  
+  In this example:
+  
+  - given\_name (first name) is mapped to the `name` field from the IdP.
+  - family\_name (last name) is mapped to the `surname` field from the IdP.
+
+<!--THE END-->
+
+1. Select **Update changes**.
+
+### [](#integrate-with-idp-using-sql)Integrate with IdP using SQL
+
+To create your SSO connection in Firebolt, you can use the following SQL as an example:
+
+```
+ALTER ORGANIZATION vsko SET SSO = '{
+  "signOnUrl": "https://dev-a8jnpkgk4y7gylt5.us.auth0.com/samlp/9aLOXgDHcqxW1gWtBuWNxVLbKNyv1LQV",
+  "issuer": "okta",
+  "provider": "okta",
+  "label": "Okta Company IdP",
+  "fieldMapping": {
+    "given_name": "name",
+    "family_name": "surname"
+  },
+  "certificate": "-----BEGIN CERTIFICATE-----SampleCertificate-----END CERTIFICATE-----"
+}';
+```
+
+Make sure that the certificate value is provided as one string, without any line breaks or control characters such as `\r\n`.
+
+## [](#log-in-using-sso)Log in using SSO
+
+1. Visit [go.firebolt.io/login](https://go.firebolt.io/login).
+2. Enter your organization name and select **Continue to login**. If you don’t remember your organization name, select **Find out** next to **Don’t know your organization name?**.
+3. Enter the email address you use for Firebolt and select **Send link**.
+4. Check your inbox for an email containing a direct login link for your organization. Bookmark this link for future use.
+5. Select \*\*Login with \*\*. You’ll be redirected to your identity provider (IdP) for authentication. Once authenticated, you’ll return to Firebolt.
+
+**During Login**
+
+- **New Users**:  
+  If a login with your email doesn’t already exist, Firebolt will create one based on the email, first name, and last name provided in the SAML assertion from the IdP.  
+  The new login will be SSO-only, with the `IS_PASSWORD_ENABLED` property set to `False`.
+- **Existing Users**:  
+  If the login already exists and **Field Mapping** is set:
+  
+  - If your first or last name differs from what’s specified in the IdP, Firebolt will update those fields.
+  - If the names match or Field Mapping is empty, the existing fields will remain unchanged and it will authenticate as usual.
+
+## [](#edit-sso-settings)Edit SSO settings
+
+SSO settings can be edited in two ways - using SQL or the UI. To edit SSO settings using SQL, use the [ALTER ORGANIZATION](/sql_reference/commands/data-definition/alter-organization.html) statement. For example:
+
+```
+ALTER ORGANIZATION vsko SET SSO = '{
+  "signOnUrl": "https://abc.okta.com/app/okta_firebolt_app_id/sso/saml",
+  "signOutUrl": "https://myapp.exampleco.com/saml/logout", 
+  "issuer": "issuer",
+  "provider": "Okta", 
+  "label": "Okta",
+  "fieldMapping": "mapping",
+  "certificate": "-----BEGIN CERTIFICATE-----SampleCertificate-----END CERTIFICATE-----"
+}';
+```
+
+To edit SSO settings using the UI, see [Configure Firebolt to integrate with IdP using the UI](#integrate-with-idp-using-the-ui).
+
+## [](#delete-sso)Delete SSO
+
+To disable SSO login, you can delete the SSO settings using either SQL or the UI. To modify SSO settings using SQL, use the following command:
+
+```
+ALTER ORGANIZATION vsko SET SSO = DEFAULT;
+```
+
+To modify SSO settings using the UI:
+
+1. Select **Configure** to open the **Configure Space**, then choose **SSO**.
+2. Select **Clear SSO configuration**.
+3. Select **Update changes**.
+
+After the SSO configuration is deleted:
+
+- Users who were created through SSO will remain in your organization but will no longer be able to log in to Firebolt unless password-based login is enabled for them. You can enable this using the [ALTER LOGIN](/sql_reference/commands/access-control/alter-login.html) command.
+- All logins with `is_sso_provisioned=true` will automatically be updated to `sso_provisioned=false`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_sso_okta.md b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_okta.md
new file mode 100644
index 0000000..ac62053
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_okta.md
@@ -0,0 +1,95 @@
+# [](#okta)Okta
+
+Okta is an identity and access management platform that enables secure Single Sign-On (SSO). Integrating Okta with Firebolt allows users to login using their existing credentials, simplifying access while maintaining security. This setup helps you and your team centralize authentication and manage user access.
+
+To integrate Okta with Firebolt’s platform, you need to [configure your Okta application for Firebolt](#configure-okta-application) and [Firebolt’s SSO for Okta](#configure-okta-application). Detailed instructions can be found in the following sections:
+
+## [](#configure-okta-application)Configure Okta application
+
+01. In the Okta Admin Console, select **Applications** from the left navigation panel.
+02. Select **Applications** again.
+03. Select **Create a new app integration**.
+04. Select **SAML 2.0** as the sign-in method and choose **Next**.
+05. Fill out **General Settings** and navigate to the next section **Configure SAML**.
+06. Complete the following fields:
+    
+    - **Single sign-on URL.** This URL has the following format `https://id.app.firebolt.io/login/callback?connection=<org_name>-<provider>&organization=<organization_identifier>`
+      
+      - **`<org_name>`** represents the organization name used to create your Firebolt Account. This org name is referenced in your vanity URL.
+      - **`<provider>`** represents the provider we’re configuring as our IdP.
+      - **`<organization_identifier>`** - the unique identifier for your organization in Firebolt. To retrieve your **`<organization_identifier>`** , do the following:
+        
+        1. Login to the [Firebolt Workspace](https://go.firebolt.io/signup).
+        2. Select the **Configure** icon (![The Firebolt Configure Space icon.](../../../assets/images/configure-icon.png)).
+        3. Select **SSO** from the left navigation pane.
+        4. Select **Copy organization SSO identifier**.
+      
+      **Example:** https://id.app.firebolt.io/login/callback?connection=vsko-okta&amp;organization=org\_82u3nzTNQPA8RyoM
+    - **Audience URI (SP Entity ID).** This URI has the following format: `urn:auth0:<tenant_name>:<org_name>-<provider>`, where `<tenant_name>` is app-firebolt-v2, `<org_name>` is the name of organization provider and `<provider>` is the provider value set in Firebolt configuration step.
+    
+    **Example:** `urn:auth0:app-firebolt-v2:vsko-okta`
+07. Save the configuration.
+08. Open the **Sign On** tab of your created app integration, and select the **SAML 2.0** tab. Select **More details** to expand additional information.
+09. Copy or note down the value for **Sign on URL** and **Issuer**.
+10. Download the **Signing Certificate**.
+
+## [](#configure-firebolt-to-integrate-with-okta)Configure Firebolt to integrate with Okta
+
+Once your Identity Provider(IdP) is configured, you can now configure Firebolt to integrate with Okta either using SQL scripts in the **Develop Space** or through the user interface (UI) in the **Configure Space**.
+
+### [](#configure-firebolt-to-integrate-with-okta-using-the-ui)Configure Firebolt to integrate with Okta using the UI
+
+1. Login to the [Firebolt Workspace](https://go.firebolt.io/signup).
+2. Select the **Configure** icon (![The Firebolt Configure Space icon.](../../../assets/images/configure-icon.png)).
+3. Select **SSO** from the left navigation pane.
+4. Under **Configure SSO for your organization**, enter the following:
+   
+   1. **Sign-on URL** - Enter the sign-on URL, provided by the SAML identity provider, where Firebolt will send SAML requests. The URL is specific to the IdP and is defined during configuration. For Okta, this value corresponds to the Sign on URL value copied in **Step 6**.
+   2. **Issuer** - A unique value generated by the SAML identity provider specifying the issuer value. The issuer corresponds to the **Issuer** value noted in **Step 9**.
+   3. **Provider** - The provider’s name, `Okta`.
+   4. **Label**: The label to use for the SSO login button. You can use any label name. If the label is not provided, Firebolt uses the value in the **Provider** field.
+   5. (Optional) **Sign-out URL** - An endpoint provided by Okta that facilitates the logout process by redirecting the user to this URL, ending their session.
+   6. **Signing certificate** - A digital certificate used to verify the authenticity of a signature used to communication between Okta and Firebolt. The certificate needs to be in PEM or CER format, and can be uploaded from your computer by selecting **Import certificate** or entered in the text box under **Signing certificate**.
+   7. **Field mapping** - A mapping used to match user attributes between Okta and Firebolt. Enter the **First name** and **Last name** in your Okta profile. Mapping is only required the first time a user logs in using SSO.
+   8. Select **Update changes**.
+
+### [](#configure-firebolt-to-integrate-with-okta-using-sql)Configure Firebolt to integrate with Okta using SQL
+
+Login to Firebolt’s [Workspace](https://go.firebolt.io/login). Then, do the following:
+
+1. Select the Develop icon (![The Firebolt Develop Space icon.](../../../assets/images/develop-icon.png)).
+2. By default, when you login to **Firebolt’s Workspace** for the first time, Firebolt creates a tab in the **Develop Space** called **Script 1**. The following apply:
+
+<!--THE END-->
+
+- The database that Script 1 will run using is located directly below the tab name. If you want to change the database, select another database from the drop-down list.
+- An engine must be running to process the script in a selected tab. The name and status of the engine that Script 1 uses for computation is located to the right of the current selected database.
+
+Select system from the drop-down arrow next to the engine name. The system engine is always running, and you can use it to create a service account. You can also use an engine that you create.
+
+1. Use the syntax in the following example code to create an SSO connection in the **SQL Script Editor**:
+
+```
+ALTER ORGANIZATION vsko SET SSO = '{
+  "signOnUrl": "https://dev-1234567890123456.us.okta.com/samlp/123456789012345678901234567890123",
+  "signoutURL": "http://your-sign-out-URL",
+  "issuer": "okta",
+  "provider": "okta",
+  "label": "Okta Company IdP",
+  "fieldMapping": {
+    "given_name": "name",
+    "family_name": "surname"
+  },
+  "certificate": "<certificate>"
+}';
+```
+
+In the previous code example, the following apply:
+
+- `signOnUrl`- The sign-on URL, provided by the SAML identity provider, where Firebolt will send SAML requests. The URL is specific to the IdP and is defined during configuration. For Okta, this value corresponds to the **Sign on URL** value copied in **Step 9**.
+- (Optional)`signoutUrl`- An endpoint provided by Okta that facilitates the logout process by redirecting the user to this URL, ending their session.
+- `issuer` - A unique value generated by the SAML identity provider specifying the issuer value. The issuer corresponds to the **Issuer** value noted in **Step 9**.
+- `provider` - The provider’s name, `Okta`.
+- `label` - The label to use for the SSO login button. You can use any label name. If the label is not provided, Firebolt uses the value in the **Provider** field.
+- `certificate` - A digital certificate used to verify the authenticity of a signature used to communication between Okta and Firebolt. The certificate must be in Privacy Enhanced Mail (PEM) or CER format.
+- `field mapping` - A mapping used to match user attributes between Okta and Firebolt. Enter the first name and surname in your Okta profile. Mapping is only required the first time a user logs in using SSO.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_sso_onelogin.md b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_onelogin.md
new file mode 100644
index 0000000..9ef47ac
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_onelogin.md
@@ -0,0 +1,92 @@
+# [](#onelogin)OneLogin
+
+OneLogin is a cloud-based identity and access management platform that simplifies secure access to applications through single sign-on (SSO). Integrating OneLogin with Firebolt enhances security and streamlines user authentication for your team.
+
+To integrate OneLogin with Firebolt’s platform, you need to configure both a [OneLogin application for Firebolt](#configure-onelogin-application) and [Firebolt’s SSO for OneLogin](#configure-firebolt-for-onelogin). Detailed instructions can be found in the following sections:
+
+## [](#configure-onelogin-application)Configure OneLogin application
+
+1. In OneLogin, open to the dashboard and select **Applications** and **Add App**.
+2. Search for **SAML**, and select **SAML Test Connector (IdP w/attr)**.
+3. Change the Display Name of the app and select **Save**. This will be the name of the app that will appear in your OneLogin portal.
+4. Open the **SSO** tab and copy the value for the **SAML 2.0 Endpoint (HTTP)**. This value will later be used in the Firebolt Configuration step. Note that logout endpoint is not used at this time.
+5. Select the **View Details** link at the X.509 Certificate field and copy/download the certificate.
+6. Navigate to the **Configuration** tab and fill in the following values:
+   
+   - **Audience** - a URI in the following format: `urn:auth0:<tenant_name>:<org_name>-<provider>`, where `<tenant_name>` is app-firebolt-v2, `<org_name>` is the name of organization, and `<provider>` is the provider value set in Firebolt configuration step. **Example:** `urn:auth0:app-firebolt-v2:vsko2-onelogin`
+   - **ACS (Consumer) URL Validator** - a valid regular expression. This field is used to ensure OneLogin posts the response to the correct URL, and it validates the ACS URL field.
+   - **ACS (Consumer) URL** - the post-back URL for your organization. This is the URL in the following format: `https://id.app.firebolt.io/login/callback?connection=<organization_name>-<provider>&organization=<organization_identifier>`. The organization\_identifier is needed to select the correct organization during redirects. The authentication flow will fail if this is incorrectly provided or left blank. **Example:** https://id.app.firebolt.io/login/callback?connection=vsko2-onelogin&amp;organization=org\_82u3nzTNQPA8RyoM
+     
+     > **`<organization_name>`** represents the Organizational name used to create your Firebolt Account. The org name is referenced in your vanity URL.  
+     > **`<provider>`** represents the provider we’re configuring as our IdP. **`<organization_identifier>`** is the unique identifier for your Organization. To retrieve your **`<organization_identifier>`** , you can navigate to **Configure &gt; SSO** in the Firebolt UI, and **Click Copy organization SSO identifier**.
+
+## [](#configure-firebolt-for-onelogin)Configure Firebolt for OneLogin
+
+Once your OneLogin application is configured, you can now configure Firebolt to integrate with OneLogin. This can be done using the Firebolt UI, or with SQL.
+
+### [](#integrate-with-onelogin-using-the-ui)Integrate with OneLogin using the UI
+
+1. To configure the Firebolt SSO integration with OneLogin using the UI, Navigate to **Configure &gt; SSO** in Firebolt.
+2. Enter the following information:
+   
+   - `signOnUrl`: The sign-on URL, provided by the SAML identity provider, to which Firebolt sends the SAML requests. The URL is IdP-specific and is determined by the identity provider during configuration. In Onelogin, this is the **SAML 2.0 Endpoint (HTTP)** value we copied in step 4.
+   - `signoutUrl(optional)`: The sign-out URL, provided by the application owner, to be used when the user signs out of the application.\`\`\`
+   - `issuer`: A unique value generated by the SAML identity provider specifying the issuer value.
+   - `provider`: The provider’s name - for example: `OneLogin`.
+   - `label`: The label to use for the SSO login button. If not provided, the Provider field value is used.
+   - `certificate`: The certificate to verify the communication between the identity provider and Firebolt. The certificate needs to be in PEM or CER format, and can be uploaded from your computer by choosing **Import certificate** or entered in the text box.
+   - `field mapping`: Mapping to your identity provider’s first and last name in key-value pairs. If additional fields are required, choose **Add another key-value pair**. Mapping is required for Firebolt to fill in the login’s given and last names the first time the user logs in using SSO.
+   
+   Here’s an example of how to set up **Field mapping**:
+   
+   ```
+     {
+         "given_name": "name",
+         "family_name": "surname"
+     }
+   ```
+   
+   In the previous example:
+   
+   - given\_name (first name) is mapped to the `name` field from the IdP.
+   - family\_name (last name) is mapped to the `surname` field from the IdP.
+3. Select **Update changes**.
+
+### [](#integrate-with-idp-using-sql)Integrate with IdP using SQL
+
+To create your SSO connection in Firebolt, you can use the following SQL as an example:
+
+```
+ALTER ORGANIZATION vsko SET SSO = '{
+  "signOnUrl": "https://vsko-test.onelogin.com/trust/saml2/http-post/sso/aa",
+  "issuer": "onelogin",
+  "provider": "onelogin",
+  "label": "OneLogin Company App",
+  "fieldMapping": {
+    "given_name": "name",
+    "family_name": "surname"
+  },
+  "certificate": "<certificate>"
+}';
+```
+
+where
+
+- `organization_name` is the name of the organization in Firebolt,
+- `signOnUrl` is the SAML 2.0 Endpoint (HTTP) value copied during OneLogin setup,
+- `issuer` is the name of the issuer, ‘onelogin’ in this case,
+- `provider` is the IdP name, ‘onelogin’ in this case,
+- `label` is text that will appear on the **Sign in** form (this defaults to `<organization_name>-<provider>` if a value is not provided, for instance ‘acme-onelogin\`)
+- `certificate` is the X.509 Certificate copied during OneLogin setup, and
+- `field_mapping` includes additional fields to be mapped from the SAML assertion, based on what was configured during OneLogin setup. For exaxmple:
+
+```
+{
+  "given_name": "name",
+  "family_name": "surname"
+}
+```
+
+This corresponds to the following setup in OneLogin, where name/surname in OneLogin corresponds to values in JSON:
+
+![Edit first name](../../../assets/images/onelogexample1.png)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_sso_pingfederate.md b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_pingfederate.md
new file mode 100644
index 0000000..9d0d8c1
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_pingfederate.md
@@ -0,0 +1,74 @@
+# [](#pingfederate-ping-identity)PingFederate (Ping Identity)
+
+PingFederate is an identity and access management solution that enables secure single sign-on, identity federation, and authentication across multiple applications and platforms, supporting protocols like SAML, OAuth, and OpenID Connect. You can use PingFederate to enable secure single sign-on (SSO) and federated identity management for authentication across Firebolt.
+
+To integrate PingFederate with Firebolt’s platform, you need to configure both an [PingFederate application for Firebolt](#configure-pingfederate-application) and [Firebolt’s SSO for PingFederate](#configure-firebolt-for-pingfederate). Detailed instructions can be found in the following sections:
+
+#### [](#configure-pingfederate-application)Configure PingFederate application
+
+1. Select **Applications** in the administration menu. Then on the **Applications** page, select **+** to create a new application.
+2. Type in the application name (for instance, Firebolt) and description. Then select **SAML Application**, and select **Configure**.
+3. Choose **Manually Enter** to provide application metadata.
+   
+   - Fill the **ACS URLs** field with a URL in the following format: `https://id.app.firebolt.io/login/callback?connection=<organization_name>-<provider>&organization=<organization_identifier>` For example: `https://id.app.firebolt.io/login/callback?connection=acmeorg-pingfederate&organization=org_82u3nzTNQPA8RyoM`
+     
+     > **`<org_name>`** represents the Organizational name used to create your Firebolt Account. The org name is referenced in your vanity URL.  
+     > **`<provider>`** represents the provider we’re configuring as our IdP. **`<organization_identifier>`** is the unique identifier for your Organization. To retrieve your **`<organization_identifier>`** , you can navigate to **Configure &gt; SSO** in the Firebolt UI, and **Click Copy organization SSO identifier**.
+   - Fill in **Entity ID** with the value: `urn:auth0:app-firebolt-v2:<organization_name>-<provider>`, where
+   - `<organization_name>` is the name of the organization in Firebolt, and
+   - `<provider>` is the provider value set in Firebolt configuration step For example: `urn:auth0:app-firebolt-v2:acmeorg-pingfederate`
+4. Select **Save**.
+5. From the **Configuration** tab:
+   
+   - Download the signing certificate in X509 PEM format
+   - Save the value of Single SignOn Service
+6. Open the **Attribute Mappings** tab, and edit the saml\_subject PingOne Mapping to map to Email Address. Then **Save**.
+
+#### [](#configure-firebolt-for-pingfederate)Configure Firebolt for PingFederate
+
+Once your Identity Provider(IdP) is configured, you can now configure Firebolt to integrate with your IdP. This can be done either using the Firebolt UI, or using SQL.
+
+##### [](#ui)UI
+
+1. To configure the Firebolt SSO integration with PingFederate using the UI, Navigate to **Configure &gt; SSO** in Firebolt.
+2. Once there, enter your Sign-on URL, Issuer, Provider, Label, Certificate, and field-mappings, where
+   
+   - `signOnUrl`: The sign-on URL, provided by the SAML identity provider, to which Firebolt sends the SAML requests. The URL is IdP-specific and is determined by the identity provider during configuration.
+   - `signoutUrl(optional)`: The sign-out URL, provided by the application owner, to be used when the user signs out of the application. In Pingfederate, you can retrieve this value by copying the `Single Logout Service` URL found in **Application &gt; Configuration**.\`\`\`
+   - `issuer`: A unique value generated by the SAML identity provider specifying the issuer value.
+   - `provider`: The provider’s name - for example: `PingFederate`.
+   - `label`: The label to use for the SSO login button. If not provided, the Provider field value is used.
+   - `certificate`: The certificate to verify the communication between the identity provider and Firebolt. The certificate needs to be in PEM or CER format, and can be uploaded from your computer by choosing **Import certificate** or entered in the text box.
+   - `field mapping`: Mapping to your identity provider’s first and last name in key-value pairs. If additional fields are required, choose **Add another key-value pair**. Mapping is required for Firebolt to fill in the login’s given and last names the first time the user logs in using SSO. Here’s an example of how to set up field mapping:
+     
+     ```
+     {
+         "given_name": "name",
+         "family_name": "surname"
+     }   
+     ```
+   
+   In the previous code example, `given_name` is your first name, and is mapped to the “name” field from the IDP. The `family_name` is your last name, and is mapped from the “surname” field.
+3. Choose **Update changes**.
+
+##### [](#sql)SQL
+
+Values for SQL to create the SSO connection are as follows:
+
+```
+ALTER ORGANIZATION acmeorg SET SSO = '{
+  "signOnUrl": "https://auth.pingone.eu/74d536da-4d98-4fdd-83ae-63af461eb826/saml20/idp/sso",
+  "issuer": "pingfederate",
+  "provider": "pingfederate",
+  "label": "PingFederate Company App",
+  "certificate": "<certificate>"
+}';
+```
+
+where
+
+- `signOnURL` is the Single Sign On Service URL obtained during PingFederate configuration,
+- `issuer` is the name of the issuer, ‘pingfederate’ in this case,
+- `provider` is the IdP name, ‘pingfederate’ in this case,
+- `label` is the text that will appear on the **Sign in** form (this defaults to `<organization_name>-<provider` if a value is not provided, for instance ‘acme-pingfederate\`)
+- `certificate` is the X.509 certificate in PEM format downloaded in setup.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/guides_security_sso_salesforce.md b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_salesforce.md
new file mode 100644
index 0000000..8061b46
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/guides_security_sso_salesforce.md
@@ -0,0 +1,83 @@
+# [](#salesforce)Salesforce
+
+[Salesforce](https://www.salesforce.com/) is a cloud-based customer relationship management platform that offers applications for sales, marketing, commerce and IT. Salesforce supports implementing secure login systems with authentication methods including single-sign on (SS0).
+
+To integrate Salesforce with Firebolt’s platform, you must [configure your Salesforce organization](https://help.salesforce.com/s/articleView?id=sf.sso_sfdc_idp_saml_parent.htm&type=5) as a SAML identity provider (IdP) for an external service. Then, you must [configure Firebolt’s SSO to work with Salesforce](#configure-firebolt-for-salesforce). Detailed instructions can be found in the following sections:
+
+#### [](#configure-salesforce-application)Configure Salesforce application
+
+1. Login to [Salesforce](https://login.salesforce.com/). If you don’t yet have an account with Salesforce, you can [sign-up](https://www.salesforce.com/form/signup/freetrial-salesforce-starter/) to access their services.
+2. In the Salesforce Lightning user interface (UI), enter “Identity Provider” into the **Quick Find** text box at the top of the left navigation bar. For more information about the Lightning user interface, see [Find Your Way Around Setup in Lightning Experience](https://help.salesforce.com/s/articleView?id=sf.lex_find_your_way_around_setup.htm&type=5).
+3. From the search results, select **Identity Provider**.
+4. Select **Enable Identity Provider**.
+5. Select a certificate from the dropdown list. You can use the default self-signed certificate generated with the [SHA-256](https://en.wikipedia.org/wiki/SHA-2) signature algorithm or use your own. For more information, see Salesforce’s documentation for [Certificates and Keys](https://help.salesforce.com/s/articleView?id=sf.security_keys_about.htm&type=5).
+6. Select **Download Certificate**. This should download a certificate ending in `.crt` to a local drive.
+7. Navigate to the directory containing your downloaded certificate.
+8. Convert the certificate to [PEM format](https://en.wikipedia.org/wiki/Privacy-Enhanced_Mail) by entering the following code into a terminal or command prompt on a system where [OpenSSL](https://openssl-library.org/) is installed: `openssl x509 -in original.crt -out sfcert.pem -outform PEM` In the previous code example, replace `original.crt` with the name of your downloaded certificate.
+9. From the **Identity Provider** page in Saleforce’s Lightning UI, select **Download Metadata**.
+
+Open the downloaded xml file and find the SingleSignOnService binding, Location attribute, which ends with `../HttpPost`. It will look like: `https://<your-salesforce-account>.my.salesforce.com/idp/endpoint/HttpPost`. Save this value to be used as the SignOnURL in Firebolt SSO configuration.
+
+1. Select **Download Certificate**, and convert the downloaded .crt file to PEM format. You could do this using the following command: `openssl x509 -in original.crt -out sfcert.pem -outform PEM` where `original.crt` is the name of the downloaded .crt file.
+2. Select on the provided link to create a new connected app in Salesforce.
+3. You will be redirected to the **Manage Connected Apps / New Connected App** view. Fill in required fields **Connected App Name, API Name** (for instance, type ‘Firebolt’) and **Contact email**.
+4. Move to **Web App Settings,** and check the **Enable SAML** box.
+5. Fill in the Entity Id field with value: `urn:auth0:app-firebolt-v2:<organization_name>-<provider>`, where
+   
+   - `<organization_name>` is the name of the organization in Firebolt, and
+   - `<provider>` is the IdP name, ‘salesforce’ in this case For example: `urn:auth0:app-firebolt-v2:acmeorg-salesforce`
+6. Fill the ACS URL field with a URL in the following format (contact Firebolt to get your organization\_identifier) `https://id.app.firebolt.io/login/callback?connection=<organization_name>-<provider>&organization=<organization_identifier>` For example: `https://id.app.firebolt.io/login/callback?connection=acmeorg-salesforce&organization=org_82u3nzTNQPA8RyoM`
+   
+   > **`<org_name>`** represents the Organizational name used to create your Firebolt Account. The org name is referenced in your vanity URL.  
+   > **`<provider>`** represents the provider we’re configuring as our IdP. **`<organization_identifier>`** is the unique identifier for your Organization. To retrieve your **`<organization_identifier>`** , you can navigate to **Configure &gt; SSO** in the Firebolt UI, and **Click Copy organization SSO identifier**.
+7. Keep **Subject Type** as Username, and **Name ID Format** as unspecified. Select **Save**.
+
+#### [](#configure-firebolt-for-salesforce)Configure Firebolt for SalesForce
+
+Once your Identity Provider(IdP) is configured, you can now configure Firebolt to integrate with your IdP. This can be done using either the Firebolt UI, or using SQL.
+
+##### [](#ui)UI
+
+1. To configure the Firebolt SSO integration with Salesforce using the UI, Navigate to **Configure &gt; SSO** in Firebolt.
+2. Once there, enter your Sign-on URL, Issuer, Provider, Label, Certificate, and field-mappings, where
+
+<!--THE END-->
+
+- `signOnUrl`: The sign-on URL, provided by the SAML identity provider, to which Firebolt sends the SAML requests. The URL is IdP-specific and is determined by the identity provider during configuration.
+- `signoutUrl(optional)`: The sign-out URL, provided by the application owner, to be used when the user signs out of the application.\`\`\`
+- `issuer`: A unique value generated by the SAML identity provider specifying the issuer value.
+- `provider`: The provider’s name - for example: `Salesforce`.
+- `label`: The label to use for the SSO login button. If not provided, the Provider field value is used.
+- `certificate`: The certificate to verify the communication between the identity provider and Firebolt. The certificate needs to be in PEM or CER format, and can be uploaded from your computer by choosing **Import certificate** or entered in the text box.
+- `field mapping`: Mapping to your identity provider’s first and last name in key-value pairs. If additional fields are required, choose **Add another key-value pair**. Mapping is required for Firebolt to fill in the login’s given and last names the first time the user logs in using SSO. Here’s an example of how to set up field mapping:
+  
+  ```
+  {
+      "given_name": "name",
+      "family_name": "surname"
+  }
+  ```
+  
+  In the previous code example, `given_name` is your first name, and is mapped to the “name” field from the IDP. The `family_name` is your last name, and is mapped from the “surname” field. 3. Choose **Update changes**
+
+##### [](#sql)SQL
+
+Values for SQL to create the SSO connection are as follows:
+
+```
+ALTER ORGANIZATION acmeorg SET SSO = '{
+  "signOnUrl": "https://firebolttest-dev-ed.my.salesforce.com/idp/endpoint/HttpPost",
+  "issuer": "salesforce",
+  "provider": "salesforce",
+  "label": "Salesforce Company App",
+  "certificate": "<certificate>"
+}';
+```
+
+where
+
+- `signOnURL` is the SAML 2.0 endpoint value copied during Salesforce setup,
+- `issuer` is the name of the issuer, ‘salesforce’ in this case,
+- `provider` is the IdP name, ‘salesforce’ in this case,
+- `label` is text that will appear on the **Sign in** form (this defaults to ‘-’ if a value is not provided, for instance ‘acme-salesforce\`), and
+- `certificate` is the X.509 certificate in PEM format downloaded during setup.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/index.md b/cmd/docs-scrapper/fireboltdocs/index.md
new file mode 100644
index 0000000..1e13c9b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/index.md
@@ -0,0 +1,47 @@
+# Firebolt documentation
+
+Firebolt is a cloud data warehouse engineered ground up for low latency analytics on data sets of all sizes.
+
+Dive into our documentation to find solutions to common questions through our guides and resources built for your successful development and integration with Firebolt.
+
+## Top picks
+
+[**What is Firebolt?**  
+\
+Find out about Firebolt's product and key benefits.](../product/index.html)
+
+[**Get started**  
+\
+Explore our guide on creating a database and engine and loading data.](../Guides/getting-started/index.html)
+
+[**Load data**  
+\
+Use a wizard to load data quickly or use SQL scripts for a customized workflow.](../Guides/loading-data/loading-data.html)
+
+[**Engine fundamentals**  
+\
+Learn about Firebolt engines and how to use them to ingest data and execute DML queries.](../Overview/engine-fundamentals.html)
+
+[**Data modeling**  
+\
+Design your data model and use databases, tables, and indexes to optimize query performance.](../Overview/indexes/using-indexes.html)
+
+## Documentation resources
+
+![Overview Icon](../assets/images/overview-icon.svg)
+
+### Overview
+
+- [Architecture](../Overview/architecture-overview.html)[Pricing and billing](../Overview/billing/index.html)[Organization and accounts](../Overview/organizations-accounts.html)[Engine fundamentals](../Overview/engine-fundamentals.html)[Data modeling](../Overview/indexes/using-indexes.html)[Data management](../Overview/data-management.html)[Queries](../Overview/queries/index.html)[Security](../Overview/Security/security.html)
+
+![Guides Icon](../assets/images/guides-icon.png)
+
+### Guides
+
+- [Manage organizations](../Guides/managing-your-organization/index.html)[Get started](../Guides/getting-started/index.html)[Operate engines](../Guides/operate-engines/operate-engines.html)[Load data](../Guides/loading-data/loading-data.html)[Query data](../Guides/query-data/index.html)[Configure security](../Guides/security/index.html)[Develop with Firebolt](../Guides/developing-with-firebolt/index.html)[Integrate with Firebolt](../Guides/integrations/integrations.html)[Work with semi-structured data](../Guides/loading-data/working-with-semi-structured-data/working-with-semi-structured-data.html)[Export data](../Guides/exporting-data.html)
+
+![Reference Icon](../assets/images/reference-icon.png)
+
+### Reference
+
+- [Release notes](../Reference/release-notes/release-notes.html)[Available regions](../Reference/available-regions.html)[System settings](../Reference/system-settings.html)[Object identifiers](../Reference/object-identifiers.html)[Reserved words](../Reference/reserved-words.html)[Help menu](../Reference/help-menu.html)[SQL reference](../sql_reference/index.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview.md b/cmd/docs-scrapper/fireboltdocs/overview.md
new file mode 100644
index 0000000..970f091
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview.md
@@ -0,0 +1,14 @@
+# [](#overview)Overview
+
+Read about Firebolt architecture and how it enables differentiated speed, scale, concurrency and price-performance characteristics. Learn core Firebolt concepts such as Engines, loading data using COPY FROM and Data Management Lifecycle in Firebolt.
+
+* * *
+
+- [Architecture](/Overview/architecture-overview.html)
+- [Pricing and billing](/Overview/billing/)
+- [Organizations and accounts](/Overview/organizations-accounts.html)
+- [Engine Fundamentals](/Overview/engine-fundamentals.html)
+- [Data modeling](/Overview/indexes/using-indexes.html)
+- [Data management](/Overview/data-management.html)
+- [Queries](/Overview/queries/)
+- [Security](/Overview/Security/security.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_architecture_overview.md b/cmd/docs-scrapper/fireboltdocs/overview_architecture_overview.md
new file mode 100644
index 0000000..e51f945
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_architecture_overview.md
@@ -0,0 +1,39 @@
+# [](#firebolt-architecture)Firebolt architecture
+
+The following diagram gives a high-level overview of Firebolt’s structural architecture. Firebolt’s components, which include management, compute, and storage layers, interact with a variety of workloads to enhance performance, scalability, and resource efficiency.
+
+![Firebolt's architecture has management, compute, and storage layers that work with various workloads.](../../assets/images/fireboltarchitecture.png)
+
+## [](#management-layer)Management layer
+
+Firebolt’s **management layer** handles key administrative functions including managing metadata, security settings, and observability, all in one place. Through this layer, administrators can oversee and control user access, permissions, and roles, ensuring robust security. It also provides insights into system performance and resource usage, providing operational visibility. The management layer also streamlines workspace management, enabling seamless organization and monitoring of data environments, further simplifying the overall administration process.
+
+Firebolt’s management layer consists of the following:
+
+- **Administration** - Manage access control, user roles, permissions, and system configurations.
+- **Metadata** - Track and manage data definitions, schema information, and relationships within the database.
+- **Security** - Configure and enforce access controls, authentication, encryption, and user permissions to protect data and ensure compliance.
+- **Observability** - Monitor system performance, track query performance, and analyze resource utilization so that you can optimize operations and troubleshoot issues.
+- **Workspace** - Organize and manage data environments, resources, and project-specific configurations, enabling collaboration and streamlining data workflows.
+
+## [](#compute-layer)Compute layer
+
+Firebolt’s **compute layer** is responsible for running queries and processing data through its scalable engines. Engines use parallel processing to deliver high performance and efficiency. You can create and configure multiple engines tailored to different workflows, such as data integration or analytical queries supporting customer facing analytics. Engines can be configured for different needs like query latency, throughput, and concurrency, adapting to specific data processing tasks.
+
+Firebolt’s compute layer features the following:
+
+- **Scalable engines** - Firebolt’s compute layer provides scalable engines that process queries in parallel, ensuring high-speed performance and efficiency for diverse workloads.
+- **Customizable configurations** - You can tailor engine configurations to match your specific workflow needs.
+- **Multiple engines for workload isolation** - You can create multiple engines to handle mixed workloads. Each workload runs in an isolated compute environment, so that you can avoid performance issues caused by noisy neighbors.
+- **On-demand resource allocation** - Engines can be started, stopped, or resized based to match current workload demands.
+
+## [](#storage-layer)Storage layer
+
+Firebolt’s **storage layer** efficiently manages large amounts of data by keeping storage separate from the compute process, which means that you can store as much data as needed without impacting compute resources. It uses cloud-based storage for high availability and durability, while also reducing costs. Data is stored in a compressed, column-based format to save space and improve query performance. Firebolt’s indexing features further speed up data retrieval by reducing the need to scan large datasets. This separation between storage and compute allows users to scale their storage needs independently, making resource management more flexible and cost-efficient.
+
+Firebolt’s storage layer features the following:
+
+- **Separation of storage and compute** - You can scale data storage independently of the computing resources used for processing queries. This separation lets you adjust storage without affecting compute resources, allowing for flexible and efficient resource management.
+- **Cloud-based and cost-effective** - Firebolt leverages cloud storage for high availability, durability, and reduced costs.
+- **Columnar format** - Data is stored in a compressed, column-based format, optimizing both storage efficiency and query performance.
+- **Fast data retrieval with advanced indexing** - Indexing features including primary and aggregating indexes speed up queries by minimizing the need to scan large datasets.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_billing.md b/cmd/docs-scrapper/fireboltdocs/overview_billing.md
new file mode 100644
index 0000000..becf0bf
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_billing.md
@@ -0,0 +1,164 @@
+# [](#firebolt-pricing-and-deployment-models)Firebolt pricing and deployment models
+
+Firebolt offers flexible deployment models that provide scalability and cost efficiency to meet diverse business needs. Choose between fully-managed and self-managed solutions tailored to your infrastructure and workload requirements.
+
+![Firebolt offers fully-managed and self-managed deployment models](../../assets/images/deployment-models.png)
+
+## [](#choose-your-deployment-model)Choose your deployment model
+
+Firebolt offers two deployment models: **fully-managed** and **self-managed**. Each model includes specific editions and pricing options.
+
+- The [fully-managed](#fully-managed-editions-and-pricing) deployment option includes **Standard**, **Enterprise**, and **Dedicated** editions with Pay-As-You-Go or Committed-Use discount pricing
+- The [self-managed](#self-managed-editions-and-pricing) deployment model includes Firebolt’s **Firebolt Core** and **Private Cloud**, with pricing based on your infrastructure setup.
+
+All fully-managed and **Private Cloud** editions have associated [support plans and service-level agreements](#support-plans-and-service-level-agreements) that define a time to first response.
+
+The following sections outline the available deployment models, their editions, and associated pricing options.
+
+### [](#fully-managed-editions-and-pricing)Fully managed editions and pricing
+
+Firebolt manages compute infrastructure, software maintenance, and upgrades across all fully-managed editions. Firebolt handles multi-dimensional elasticity, high performance, scaling, maintenance, and performance optimizations.
+
+- [Fully-managed editions](#fully-managed-editions) – Firebolt offers the **Standard**, **Enterprise** and **Dedicated** editions.
+- [Fully-managed pricing model](#fully-managed-pricing-model) – Your total price consists of a storage and a compute cost.
+  
+  - [Data storage pricing](#data-storage-pricing) – The storage portion of your total cost.
+  - [Compute usage pricing](#compute-usage-pricing) – The compute portion of your total cost.
+- [Fully-managed pricing plans](#fully-managed-pricing-plans) – How to pay for resource usage.
+  
+  - [Billing setup and monitoring](#billing-setup-and-monitoring) – How to use the Billing dashboard to view resource consumption and set up billing and a plan.
+  - [Set up billing for fully-managed plans](#set-up-billing-for-fully-managed-plans) – How to set up pay-as-you-go billing through AWS Marketplace.
+  - [Sign up or change your fully-managed edition](#sign-up-or-change-your-fully-managed-edition) – How to set up or change your fully-managed edition type.
+
+#### [](#fully-managed-editions)Fully-managed editions
+
+There are three editions available: **Standard**, **Enterprise**, and **Dedicated**.
+
+![Firebolt offers the Standard, Enterprise, and Dedicated editions with different features.](../../assets/images/firebolt-fully-managed.png)
+
+**Standard edition**  
+The **Standard** edition is best for teams seeking a low-cost entry point without the need to manage compute infrastructure. It offers high performance with sub-second query latency, flexible compute scaling within a single cluster. Security features include Role-Based Access Control (RBAC), single sign-on (SSO), multi-factor authentication (MFA), and audit logging. **Standard** includes a flexible compute option that is optimized for either storage or for compute. Firebolt manages your compute infrastructure, software maintenance, and upgrades.
+
+**Enterprise edition**  
+The **Enterprise** edition is designed for organizations that need advanced security, compliance, and automatic compute scaling. It includes all the features in the **Standard** edition, plus multi-cluster scaling, auto-scaling for concurrency, [AWS PrivateLink](/Guides/security/privatelink.html), and HIPAA compliance support.
+
+**Dedicated edition**  
+The **Dedicated** edition is ideal for organizations that require high levels of security and isolation, such as those operating in government clouds. It includes all the features in the **Enterprise** edition, plus complete data isolation on a single-tenant infrastructure, offering the highest level of security.
+
+### [](#fully-managed-pricing-model)Fully-managed pricing model
+
+The total cost for Firebolt’s fully-managed editions consists of a **cost for data storage** plus a **cost for compute usage**. The compute usage cost depends on the type of engine that you select: compute-optimized or storage-optimized.
+
+![Total cost consists of data storage and compute usage with two types of compute options.](../../assets/images/compute-usage-cost.png)
+
+#### [](#data-storage-pricing)Data storage pricing
+
+Data storage costs are based on the amount of compressed data stored, including indexes and raw data. Pricing is based on Amazon S3 costs in your selected AWS region. There are no additional storage charges beyond S3 costs.
+
+Available AWS Regions Price per TB/month ($USD) US East (N. Virginia) $23.00 US West (Oregon) $23.00 Europe (Frankfurt) $24.50 Europe (Ireland) $23.00 Asia Pacific (Singapore) $25.00
+
+#### [](#compute-usage-pricing)Compute usage pricing
+
+Compute costs are measured in Firebolt Units (FBUs) and vary based on [engine](/Overview/engine-fundamentals.html) node type, number of nodes or cluster size, the number of clusters and usage duration. Costs are only billed for the time Firebolt engines are running. Firebolt offers two compute family options:
+
+- **Storage-optimized** (default): High SSD capacity for caching and production workloads.
+- **Compute-optimized**: About 2x cheaper; ideal for development and test environments or workloads with smaller active datasets.
+
+The following table outlines the available node types, their compute family, and the corresponding FBU sizing:
+
+Node type Compute family Sizing in FBU Small (S) Storage-optimized 8 Medium (M) Storage-optimized 16 Large (L) Storage-optimized 32 Extra Large (XL) Storage-optimized 64 Small (S) Compute-optimized 4 Medium (M) Compute-optimized 8 Large (L) Compute-optimized 16 Extra Large (XL) Compute-optimized 32
+
+Firebolt’s compute usage pricing is based on **FBUs**, which vary by node type and region. The following table provides hourly pricing for **storage-optimized** node types across **Standard** and **Enterprise** plans, distinguishing between **US and Non-US regions**. Compute costs are only incurred while Firebolt engines are running, with **per-second billing**.
+
+**Storage-optimized pricing for compute usage**
+
+Node Type Sizing in FBU Standard: US Region Pricing ($0.23/FBU/hr) Enterprise: US Region Pricing ($0.35/FBU/hr) Standard: Non-US Region Pricing ($0.28/FBU/hr) Enterprise: Non-US Region Pricing ($0.42/FBU/hr) **Small (S)** 8 $1.84 $2.80 $2.24 $3.36 **Medium (M)** 16 $3.68 $5.60 $4.48 $6.72 **Large (L)** 32 $7.36 $11.20 $8.96 $13.44 **Extra Large (XL)** 64 $14.72 $22.40 $17.92 $26.88
+
+The following table provides hourly pricing for **compute-optimized** node types across **Standard** and **Enterprise** plans, distinguishing between **US and Non-US regions**. Compute costs are only incurred while Firebolt engines are running, with **per-second billing**.
+
+**Compute-optimized pricing for compute usage**
+
+Node Type Sizing in FBU Standard: US Region Pricing ($0.23/FBU/hr) Enterprise: US Region Pricing ($0.35/FBU/hr) Standard: Non-US Region Pricing ($0.28/FBU/hr) Enterprise: Non-US Region Pricing ($0.42/FBU/hr) **Small (S)** 4 $0.92 $1.40 $1.12 $1.68 **Medium (M)** 8 $1.84 $2.80 $2.24 $3.36 **Large (L)** 16 $3.68 $5.60 $4.48 $6.72 **Extra Large (XL)** 32 $7.36 $11.20 $8.96 $13.44
+
+### [](#fully-managed-pricing-plans)Fully-managed pricing plans
+
+Firebolt offers two pricing options for the **Standard** and **Enterprise** editions:
+
+- **Pay-as-you-go**: A flexible plan that provides on-demand pricing with no upfront cost or commitment. This plan is ideal for startups or teams with unpredictable workloads. Customers get billed monthly based on actual usage and only pay for what they use with per-second billing.
+- **Committed-use discounts**: A consumption model that provides discounted rates against a prepaid usage commitment. This plan is ideal for organizations with consistent, high-volume workloads and results in lower total costs compared to the pay-as-you-go plan. Once all prepaid FBU credits are consumed, your plan switches to the pay-as-you-go pricing model. Customers can always continue using Firebolt, with consumption either drawing from prepaid credits or transitioning to the pay-as-you-go model when credits run out.
+
+Contact [support@firebolt.io](mailto:support@firebolt.io) to discuss a committed-use plan, annual pricing commitments, or **Dedicated** edition pricing.
+
+#### [](#billing-setup-and-monitoring)Billing setup and monitoring
+
+You can use Firebolt’s billing dashboard to monitor resource consumption, track expenses, monitor payments, and analyze billing trends efficiently. To view the billing dashboard, follow steps 1-3 in the following section to [set up billing for fully-managed plans](#set-up-billing-for-fully-managed-plans).
+
+Billing invoices are generated on a monthly basis, and provide a detailed breakdown of resource consumption and associated costs.
+
+#### [](#set-up-billing-for-fully-managed-plans)Set up billing for fully-managed plans
+
+**Pay-As-You-Go setup via AWS Marketplace:**
+
+1. Log in to [Firebolt’s Workspace](https://go.firebolt.io/login). If you haven’t yet registered with Firebolt, see the [Get Started](/Guides/getting-started/) guide.
+2. In the Firebolt Workspace, select the Configure(![The Firebolt Configure Space icon](../../assets/images/configure-icon.png)) icon from the left navigation pane.
+3. Under **Configure**, select **Billing**. This page allows you to view invoices and consumption details.
+4. Select **Connect to AWS Marketplace**.
+5. On AWS Marketplace, click **View Purchase Options** &gt; **Setup Your Account**.
+
+Firebolt will bill you monthly through **AWS Marketplace** based on usage.
+
+#### [](#sign-up-or-change-your-fully-managed-edition)Sign up or change your fully-managed edition
+
+If you want to sign up or upgrade your fully-managed edition type, you can choose the **Standard**, **Enterprise** or **Dedicated** plan. Select your new choice in the **Firebolt Workspace** as follows:
+
+1. Log in to [Firebolt’s Workspace](https://go.firebolt.io/login).
+2. In the Firebolt Workspace, select the Configure(![The Firebolt Configure Space icon](../../assets/images/configure-icon.png)) icon from the left navigation pane.
+3. Under **Configure**, expand the drop-down list next to **Billing**.
+4. Under **Billing**, select **Plan** to open the list of available plans. Your active plan is labeled as **Current Plan**. For information about each plan, select **Learn more** to be directed to Firebolt’s [Pricing](https://www.firebolt.io/pricing) page.
+5. Select your desired plan.
+   
+   1. To select the **Standard** or **Enterprise** plan, choose **Select plan** and confirm your selection.
+   2. To select the **Dedicated** plan, do the following:
+      
+      1. Choose **Talk to Sales**.
+      2. In the pop-up window, **Your email** is automatically populated with the email associated with your login.
+      3. Enter a **Subject** or accept the default **Pricing plan** entry.
+      4. Enter a **Description**.
+      5. Select **Send** to notify Firebolt’s support team.
+
+Changing your plan is **not immediate** and may take **up to 24 hours** to process. You will receive updates about the status of your request through email.
+
+### [](#self-managed-editions-and-pricing)Self-managed editions and pricing
+
+Firebolt offers two self-managed options, where you run Firebolt on your own infrastructure: **Firebolt Core** and **Private Cloud**.
+
+![Firebolt offers two self-managed editions. One that is free that you manage, and one for a private cloud.](../../assets/images/self-managed-editions.png)
+
+**Private Cloud (BYOC)**  
+The **Private Cloud** edition is a BYOC (bring your own cloud) offering for organizations that want Firebolt’s software but prefer to use their own cloud infrastructure. Customers manage their own infrastructure for both compute and storage, whereas Firebolt manages hosting, Firebolt upgrades and maintenance. For BYOC pricing, contact [support@firebolt.io](mailto:support@firebolt.io).
+
+**Firebolt Core**  
+The **Firebolt Core** edition is a free downloadable version that can be deployed on cloud, on-premises, or on a local machine. This option is best for teams needing full control over deployment with a lightweight Firebolt engine. Customers manage compute and storage infrastructure, hosting, all software upgrades, and maintenance.
+
+## [](#support-plans-and-service-level-agreements)Support plans and service level agreements
+
+Firebolt offers support options based on your selected edition for fully-managed and **Private Cloud** editions.
+
+Response Time Commitments (TFR = Time to First Response)
+
+Severity Level Issue Type Business support: TFR for Standard Edition Premium support: TFR for Enterprise, Dedicated or Private Cloud Critical (Sev1) Service outage or major disruption Response within 4 hours Response within 30 minutes High (Sev2) Significant performance degradation Response within 8 business hours Response within 2 hours Medium (Sev3) Minor impact or feature issue Response within 24 business hours Response within 6 business hours Low (Sev4) General inquiries or documentation questions Response within 48 business hours Response within 24 business hours
+
+**Premium support features**
+
+**Enterprise**, **Private Cloud**, and **Dedicated** edition customers receive the following additional support benefits beyond response time commitments:
+
+- **Proactive monitoring**: Alerts for issues and potential optimizations available to **Enterprise** edition customers.
+- **Enhanced support channels**: Support through Slack, email and the [help menu](/Reference/help-menu.html) in the **Firebolt Workspace**.
+- **Dedicated support engineer**: Customers are assigned a designated support engineer with deep knowledge of their environment, providing personalized support. This premium support level differs from **Standard** customers, who receive assistance from the general support pool.
+
+Contact [support@firebolt.io](mailto:support@firebolt.io) to learn more about **Enterprise** edition Support offerings.
+
+* * *
+
+- [Explore compute cost](/Overview/billing/compute-cost.html)
+- [Explore storage cost](/Overview/billing/storage-cost.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_billing_compute_cost.md b/cmd/docs-scrapper/fireboltdocs/overview_billing_compute_cost.md
new file mode 100644
index 0000000..aeef5a3
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_billing_compute_cost.md
@@ -0,0 +1,144 @@
+# [](#explore-compute-cost)Explore compute cost
+
+You can use data from the [`information_schema.engines_billing`](/sql_reference/information-schema/engines-billing.html) and [`information_schema.engine_history`](/sql_reference/information-schema/engine-history.html) views, to analyze and optimize compute costs related to engine usage, scaling, and auto-stop events. The following queries help track compute costs, identify cost patterns, and understand the impact of different configurations on your compute expenses.
+
+## [](#examples)Examples
+
+**Cost tracking and analysis**
+
+- [Track hourly average costs over time](#track-hourly-average-costs-over-time) – Learn how to track hourly patterns in compute costs.
+- [Find top users by cost](#find-top-users-by-cost) – Learn how to identify users that are responsible for the highest compute costs.
+- [Find the cost impact of auto-stop events](#find-the-cost-impact-of-auto-stop-events) – Learn how to query engine history before and after an auto-stop event to determine if the auto-stop functionality leads to cost savings.
+- [Calculate costs incurred after engine deletion](#calculate-costs-incurred-after-engine-deletion) – Learn how to track costs that continue to accumulate even an engine has stopped running.
+- [Calculate costs incurred after engine creation or scaling](#calculate-costs-incurred-after-engine-creation-or-scaling) – Learn how to calculate the cost of provisioning or resizing engines to optimize resource allocation.
+
+**Engine configuration and optimization**
+
+- [Rank engine configurations by total cost](#rank-engine-configurations-by-total-cost) – Learn how to analyze engine billing data understand which combinations of engine type, family, and node count drive the most cost.
+- [Rank efficiency by cluster count](#rank-efficiency-by-cluster-count) – Learn how to determine if single or multi-cluster setups are more efficient.
+- [Calculate cost savings through auto-stop](#calculate-cost-savings-through-auto-stop) – Learn how to compare the average cost of engines with auto-stop enabled versus disabled.
+
+### [](#track-hourly-average-costs-over-time)Track hourly average costs over time
+
+You can use `information_schema.engines_billing` to track hourly average costs over time and identify peak load hours, allowing you to pinpoint when engine usage and costs are highest. Use this data to enable more efficient resource allocation and better cost optimization. Analyze daily trends to identify peak load hours and better understand the times when engine usage and associated costs are the highest.
+
+The following code example calculates the average billed cost per hour over the past 7 days, grouping the results by hour of the day:
+
+```
+SELECT EXTRACT(HOUR FROM usage_date::TIMESTAMP) AS usage_hour, 
+       AVG(billed_cost) AS avg_hourly_cost
+FROM information_schema.engines_billing
+WHERE usage_date >= CURRENT_DATE - INTERVAL '7 days'
+GROUP BY EXTRACT(HOUR FROM usage_date::TIMESTAMP)
+ORDER BY usage_hour;
+```
+
+### [](#find-top-users-by-cost)Find top users by cost
+
+You can use `information_schema.engines_billing` and `information_schema.engine_history` to identify the top engine owners by analyzing engine billing data. Pinpoint the individuals or teams responsible for the highest engine costs over a specific period, fostering accountability and enabling more effective resource management.
+
+The following code example calculates the total billed cost for each engine owner between the specified dates, sorting the results in descending order to show the highest spenders first:
+
+```
+SELECT engine_history_table.engine_owner, SUM(engine_billing_table.billed_cost) AS total_cost
+FROM information_schema.engines_billing engine_billing_table
+JOIN information_schema.engine_history engine_history_table USING (engine_name)
+WHERE engine_billing_table.usage_date BETWEEN DATE '2025-02-24' AND DATE '2025-03-26'
+GROUP BY engine_history_table.engine_owner
+ORDER BY total_cost DESC;
+```
+
+### [](#find-the-cost-impact-of-auto-stop-events)Find the cost impact of auto-stop events
+
+When you [create an engine](/sql_reference/commands/engines/create-engine.html), you can set the `AUTO_STOP` parameter to automatically stop an engine after it has been idle for a specified number of minutes. Query the engine history before and after an auto-stop event to see if auto-stop functionality results in cost savings.
+
+The following code example calculates the billed cost for engines both before and after an auto-stop event, showing how the cost changes once the engine is stopped automatically:
+
+```
+SELECT engine_billing_table.engine_name,
+       CAST(engine_history_table.event_start_time AS DATE) AS auto_stop_date,
+       SUM(CASE WHEN engine_billing_table.usage_date < CAST(engine_history_table.event_start_time AS DATE) THEN engine_billing_table.billed_cost ELSE 0 END) AS cost_before,
+       SUM(CASE WHEN engine_billing_table.usage_date >= CAST(engine_history_table.event_start_time AS DATE) THEN engine_billing_table.billed_cost ELSE 0 END) AS cost_after
+FROM information_schema.engine_history engine_history_table
+JOIN information_schema.engines_billing engine_billing_table ON engine_history_table.engine_name = engine_billing_table.engine_name
+WHERE engine_history_table.event_type = 'AUTO_STOP'
+GROUP BY engine_billing_table.engine_name, CAST(engine_history_table.event_start_time AS DATE);
+```
+
+### [](#calculate-costs-incurred-after-engine-deletion)Calculate costs incurred after engine deletion
+
+Use engine history and billing information to identify any billing discrepancies that occur after an engine has been deleted. By examining any charges that incurred after an engine was deleted, you can detect any unresolved billing issues or configuration errors.
+
+The following code calculates the total billed cost incurred after an engine deletion event, identifying any charges that are incurred after the engine has been deleted, and grouping the results by engine name:
+
+```
+SELECT engine_billing_table.engine_name, MAX(engine_history_table.event_finish_time) AS deletion_time,
+       SUM(engine_billing_table.billed_cost) AS post_deletion_cost
+FROM information_schema.engine_history engine_history_table
+JOIN information_schema.engines_billing engine_billing_table ON engine_history_table.engine_name = engine_billing_table.engine_name
+WHERE engine_history_table.event_type = 'ENGINE_DELETE'
+  AND engine_billing_table.usage_date > CAST(engine_history_table.event_finish_time AS DATE)
+GROUP BY engine_billing_table.engine_name
+HAVING SUM(engine_billing_table.billed_cost) > 0;
+```
+
+### [](#calculate-costs-incurred-after-engine-creation-or-scaling)Calculate costs incurred after engine creation or scaling
+
+Analyze engine billing data to track the costs incurred after engine creation or scaling events to understand the immediate financial impact of provisioning or resizing engines and optimize resource allocation. Rank them to find top combinations of engine size and architecture by cost.
+
+The following code calculates the total billed cost for each engine after an `ENGINE_CREATE` or `SCALE_UP` event, grouping the results by engine name and event type, and sorting the output by the total cost in descending order:
+
+```
+SELECT engine_billing_table.engine_name, engine_history_table.event_type, CAST(engine_history_table.event_start_time AS DATE) AS event_date,
+       SUM(engine_billing_table.billed_cost) AS total_cost_after_event
+FROM information_schema.engine_history engine_history_table
+JOIN information_schema.engines_billing engine_billing_table ON engine_history_table.engine_name = engine_billing_table.engine_name
+WHERE engine_history_table.event_type IN ('ENGINE_CREATE', 'SCALE_UP')
+  AND engine_billing_table.usage_date > CAST(engine_history_table.event_start_time AS DATE)
+GROUP BY engine_billing_table.engine_name, engine_history_table.event_type, CAST(engine_history_table.event_start_time AS DATE)
+ORDER BY total_cost_after_event DESC;
+```
+
+### [](#rank-engine-configurations-by-total-cost)Rank engine configurations by total cost
+
+Analyze engine billing data to rank engine configurations by total cost, identifying those driving the highest expenses. Optimize resource allocation and more cost-effective decisions for your engine setup.
+
+The following code calculates the total billed cost for different engine configurations that ran of type, family, and node count, over a specified date range, and sorts the results by total cost in descending order:
+
+```
+SELECT engine_history_table.type, engine_history_table.family, engine_history_table.nodes, SUM(engine_billing_table.billed_cost) AS total_cost
+FROM information_schema.engines_billing engine_billing_table
+JOIN information_schema.engine_history engine_history_table USING (engine_name)
+WHERE engine_billing_table.usage_date BETWEEN DATE '2025-02-24' AND DATE '2025-03-26'
+GROUP BY engine_history_table.type, engine_history_table.family, engine_history_table.nodes
+ORDER BY total_cost DESC;
+```
+
+### [](#rank-efficiency-by-cluster-count)Rank efficiency by cluster count
+
+Ranking efficiency by cluster count helps assess the cost-effectiveness of single versus multi-cluster setups. Analyzing engine billing data enables you to track associated costs and optimize resource allocation based on cost efficiency.
+
+The following code example calculates the cost per [FBU](/Overview/engine-consumption.html#engine-consumption) for single or multi-cluster setups by dividing the total billed cost by the total consumed FBUs for each cluster configuration, and then sorting the results by cost per FBU in descending order:
+
+```
+SELECT engine_history_table.clusters, SUM(engine_billing_table.billed_cost) / NULLIF(SUM(engine_billing_table.consumed_fbu), 0) AS cost_per_fbu
+FROM information_schema.engines_billing engine_billing_table
+JOIN information_schema.engine_history engine_history_table USING (engine_name)
+WHERE engine_billing_table.usage_date BETWEEN DATE '2025-02-24' AND DATE '2025-03-26'
+GROUP BY engine_history_table.clusters
+ORDER BY cost_per_fbu DESC;
+```
+
+### [](#calculate-cost-savings-through-auto-stop)Calculate cost savings through auto-stop
+
+Calculating cost savings through auto-stop allows you to compare the daily costs of engines with auto-stop enabled and disabled, helping you understand its impact on costs and optimize resource allocation.
+
+The following code example calculates the average daily billed cost for engines with auto-stop enabled and disabled, grouping the results by the auto-stop setting to provide insights into the cost impact of having auto-stop turned on or off:
+
+```
+SELECT engine_history_table.auto_stop, AVG(engine_billing_table.billed_cost) AS avg_cost
+FROM information_schema.engines_billing engine_billing_table
+JOIN information_schema.engine_history engine_history_table USING (engine_name)
+WHERE engine_billing_table.usage_date BETWEEN DATE '2025-02-24' AND DATE '2025-03-26'
+GROUP BY engine_history_table.auto_stop;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_billing_storage_cost.md b/cmd/docs-scrapper/fireboltdocs/overview_billing_storage_cost.md
new file mode 100644
index 0000000..1d0dfca
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_billing_storage_cost.md
@@ -0,0 +1,164 @@
+# [](#explore-storage-cost)Explore storage cost
+
+You can use data from the [`information_schema.storage_billing`](/sql_reference/information-schema/storage-billing.html) and [`information_schema.storage_history`](/sql_reference/information-schema/storage-history.html) views to analyze and optimize storage costs across different regions, accounts, and data usage trends. The following queries will guide you in tracking storage expenses, understanding regional cost variations, and identifying storage inefficiencies.
+
+## [](#examples)Examples
+
+**Track and attribute storage costs**
+
+- [Track total storage cost over time](#track-total-storage-cost-over-time) – Learn how to monitor daily and monthly storage costs.
+- [Identify storage cost by region](#identify-storage-cost-by-region) – Learn how to determine which regions contribute most to storage expenses.
+- [Attribute storage costs to accounts](#attribute-storage-costs-to-accounts) – Learn how to attribute storage costs to specific customers or business units.
+- [Track storage credits usage](#track-storage-credits-usage) – Learn how to monitor what percentage of your storage cost is paid using Firebolt credits.
+
+**Monitor data efficiency**
+
+- [Monitor active vs inactive data trends](#monitor-active-vs-inactive-data-trends) – Learn how to track the proportion of active and inactive data in your storage.
+- [Identify databases with high inactive storage](#identify-databases-with-high-inactive-storage) – Learn how to find databases with significant amounts of inactive data.
+- [Track storage growth by catalog](#track-storage-growth-by-catalog) – Learn how to monitor storage growth trends across catalogs, which include tables, views, and schemas.
+
+**Evaluate cost efficiency and inactive data**
+
+- [Evaluate cost efficiency per unit of storage](#evaluate-cost-efficiency-per-unit-of-storage) – Learn how to calculate the cost per unit storage to assess the efficiency of your storage expenses relative to the amount of data stored.
+- [Assess inactive data as a percentage of total storage](#assess-inactive-data-as-a-percentage-of-total-storage) – Learn how to understand what percentage of your total storage is used by data that is inactive.
+- [Attribute storage billing to catalogs](#attribute-storage-billing-to-catalogs) – Learn how to attribute storage billing to specific tables, views, and schemas.
+
+### [](#track-total-storage-cost-over-time)Track total storage cost over time
+
+You can track total storage cost over time to monitor spending trends, identify potential cost increases, and ensure that storage usage aligns with budget expectations. Query `information_schema.storage_billing` to help you proactively manage costs, so you can make adjustments to optimize storage efficiency and prevent unexpected charges.
+
+The following code example calculates the daily storage cost and the total monthly storage cost by summing the billed costs for each day and using a window function to compute the monthly total for each day within the same month:
+
+```
+SELECT usage_date, 
+       SUM(billed_cost) AS total_cost,
+       DATE_TRUNC('month', usage_date) AS month, 
+       SUM(SUM(billed_cost)) OVER (PARTITION BY DATE_TRUNC('month', usage_date)) AS monthly_cost
+FROM information_schema.storage_billing
+GROUP BY usage_date
+ORDER BY usage_date;
+```
+
+### [](#identify-storage-cost-by-region)Identify storage cost by region
+
+Use [`information_schema.storage_billing`](/sql_reference/information-schema/storage-billing.html) inside a query to understand which regions incur the highest storage costs, helping you optimize resource allocation based on geographical pricing differences.
+
+The following code example calculates the total storage cost for each region and sorts the results in descending order of total cost:
+
+```
+SELECT region, SUM(billed_cost) AS total_cost
+FROM information_schema.storage_billing
+GROUP BY region
+ORDER BY total_cost DESC;
+```
+
+### [](#attribute-storage-costs-to-accounts)Attribute storage costs to accounts
+
+You can use `information_schema.storage_billing` to attribute storage costs to specific accounts or business units and gain visibility into where your storage expenses originate. This can help you track usage, optimize costs, and allocate resources more effectively.
+
+The following code example calculates the total storage cost for each account and sorts the results in descending order of total cost:
+
+```
+SELECT account_name, SUM(billed_cost) AS total_cost
+FROM information_schema.storage_billing
+GROUP BY account_name
+ORDER BY total_cost DESC;
+```
+
+### [](#track-storage-credits-usage)Track storage credits usage
+
+Analyzing how much of your storage costs is paid with Firebolt credits versus billed costs helps optimize expenses, track credit usage, identify cost-saving opportunities, and improve budget management. Use `information_schema.storage_billing` to analyze how much of your storage cost is paid using Firebolt credits and how much is billed.
+
+The following code example uses the `is_credit` field to calculate the total storage cost, grouped by whether the cost was paid through credits or billed:
+
+```
+SELECT is_credit, SUM(billed_cost) AS total_cost
+FROM information_schema.storage_billing
+GROUP BY is_credit;
+```
+
+### [](#monitor-active-vs-inactive-data-trends)Monitor active vs inactive data trends
+
+Inactive data refers to data that is no longer actively used or is infrequently accessed but still consumes storage resources. Retaining large volumes of inactive data can result in higher costs and wasted storage. Use [`information_schema.storage_history`](/sql_reference/information-schema/storage-history.html) to identify this data so that you can make decisions about optimizing storage to reduce unnecessary expenses.
+
+The following code example shows daily trends for active and inactive data in Gibibyte (GiB), which is equal to 1,073,741,824 bytes:
+
+```
+SELECT usage_date,
+       SUM(active_data_size_bytes)/1024/1024/1024 AS active_gib,
+       SUM(inactive_data_size_bytes)/1024/1024/1024 AS inactive_gib
+FROM information_schema.storage_history
+GROUP BY usage_date
+ORDER BY usage_date;
+```
+
+### [](#identify-databases-with-high-inactive-storage)Identify databases with high inactive storage
+
+You can identify databases that contain large amounts of inactive data, which may be a candidate for cleanup or archiving.
+
+The following code example calculates the total inactive data size for each database:
+
+```
+SELECT catalog_name,
+       SUM(inactive_data_size_bytes)/1024/1024/1024 AS inactive_gib
+FROM information_schema.storage_history
+GROUP BY catalog_name
+ORDER BY inactive_gib DESC;
+```
+
+### [](#track-storage-growth-by-catalog)Track storage growth by catalog
+
+You can use `information_schema.storage_history` to track storage growth by catalog, or objects that hold metadata and database objects such as tables, views, databases and schemas, to monitor how storage usage is changing across different databases or projects. Identify trends, optimize storage allocation, and ensure that resources are being used efficiently, while also providing insight into which catalogs may require further optimization or cost management.
+
+The following code example calculates the total storage size in GiB for each catalog by summing active and inactive data sizes and ordering the results by catalog and usage date:
+
+```
+SELECT catalog_name, usage_date,
+       (active_data_size_bytes + inactive_data_size_bytes)/1024/1024/1024 AS total_gib
+FROM information_schema.storage_history
+ORDER BY catalog_name, usage_date;
+```
+
+### [](#evaluate-cost-efficiency-per-unit-of-storage)Evaluate cost efficiency per unit of storage
+
+You can use `information_schema.storage_billing` to evaluate cost efficiency per unit of storage by assessing whether storage costs are proportional to the amount of data being stored. This can help you identify discrepancies, optimize spending, and ensure that storage resources are being utilized efficiently. Determine if your storage costs align with the volume of data stored by calculating the cost per GiB.
+
+The following code example calculates the cost per GiB of storage for each day by dividing the total billed cost by the total consumed GiB, and orders the results by usage data:
+
+```
+SELECT usage_date,
+       SUM(billed_cost) / NULLIF(SUM(consumed_gib_per_month), 0) AS cost_per_gib
+FROM information_schema.storage_billing
+GROUP BY usage_date
+ORDER BY usage_date;
+```
+
+### [](#assess-inactive-data-as-a-percentage-of-total-storage)Assess inactive data as a percentage of total storage
+
+You can use `information_schema.storage_history` to measure the amount of inactive data as a percentage of total storage to identify how much of storage is being underutilized. Assessing inactive data as a percentage of total storage helps you understand how much of your storage is underutilized, enabling you to optimize costs by cleaning up or archiving inactive data.
+
+The following code example calculates the percentage of inactive data relative to the total storage, composed of both active and inactive storage, for each day and orders the results by usage date:
+
+```
+SELECT usage_date,
+       100 * SUM(inactive_data_size_bytes)::FLOAT / 
+       NULLIF(SUM(active_data_size_bytes + inactive_data_size_bytes), 0) AS inactive_pct
+FROM information_schema.storage_history
+GROUP BY usage_date
+ORDER BY usage_date;
+```
+
+### [](#attribute-storage-billing-to-catalogs)Attribute storage billing to catalogs
+
+You can use `information_schema.storage_billing` to attribute storage billing to catalogs, or objects that hold metadata and database objects such as tables, databases, views, and schemas. Use this data to better understand and allocate storage costs to specific departments, projects, or business units, so that you can enable more accurate cost tracking, budgeting, and optimization across different catalogs.
+
+The following code example calculates the total storage billing cost for each catalog by joining storage billing data with catalog account mappings and storage history, and then sorts the results by total cost in descending order:
+
+```
+SELECT storage_history.catalog_name, SUM(storage_billing.billed_cost) AS total_cost
+FROM information_schema.storage_billing storage_billing
+JOIN some_catalog_account_mapping m ON storage_billing.account_name = m.account_name
+JOIN information_schema.storage_history sh ON m.catalog_name = storage_history.catalog_name AND storage_billing.usage_date = storage_history.usage_date
+GROUP BY storage_history.catalog_name
+ORDER BY total_cost DESC;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_data_management.md b/cmd/docs-scrapper/fireboltdocs/overview_data_management.md
new file mode 100644
index 0000000..e96d17b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_data_management.md
@@ -0,0 +1,161 @@
+# [](#data-management)Data management
+
+At Firebolt, the focus is on delivering the highest levels of performance and efficiency while minimizing the heavy lift that needs to be done by an end user. The foundational elements of Firebolt provide the full data management capabilities needed by modern data applications, including an optimized storage layer, parallel-pipelined data ingestion, ACID DML, primary and aggregated indexes, streamlined deletes and updates, and core database semantics.
+
+Delivering consistent performance and efficiency requires careful considerations, modeling and optimal indexing strategy. With automated index maintenance, Firebolt enables a hands-free approach to delivering consistent performance without the operational burden, even for cases where data modification functionality is needed. Various types of DML statements can impact system performance as it can result in storage fragmentation, negating the effectiveness of indexes. However, Firebolt addresses this with the choice of user-controlled or system-controlled backend optimization.
+
+This topic explains how Firebolt delivers full data management capabilities, including how to: 1) create a simple table, 2) ingest data into it using bulk insert and singleton insert capabilities, and finally, 3) modify the data by performing delete and update operations.
+
+Learn also what happens behind the scenes, how data is being stored internally and how internal data structures evolve as data gets manipulated and changed, as well as how Firebolt handles concurrency, managing indexes and optimizing storage.
+
+- [Transactions and concurrency](#transactions-and-concurrency)
+- [Creating tables](#creating-tables)
+- [Inserting data](#inserting-data)
+- [Deleting data](#deleting-data)
+- [Updating data](#updating-data)
+- [Optimizing storage](#optimizing-storage)
+- [Maintaining indexes](#maintaining-indexes)
+
+## [](#transactions-and-concurrency)Transactions and concurrency
+
+Before getting into how data manipulation and changes work in Firebolt, it is important to first explain transactions and concurrency controls that are implemented within the system.
+
+Firebolt treats each request or SQL statement as a new implicit transaction. Transactions guarantee the ACID properties: atomicity (all or nothing), consistency (will not transition to an invalid state), isolation (no interference between concurrent transactions, depending on isolation level, see below), durability (no data loss once committed).
+
+Firebolt supports two isolation levels:
+
+- DDL (CREATE, ALTER, DROP) and DCL (GRANT, REVOKE) work at *serializable isolation* level.
+- DQL (SELECT) and DML (INSERT, UPDATE, DELETE) work at *snapshot isolation* level.
+
+Serializable isolation means that the result of running concurrent statments is equivalent to as if they were run serially in some order.
+
+Snapshot isolation is weaker and guarantees that a transaction sees a consistent version of the database. Transactions fail if any written rows are being written concurrently by another transaction. It is a weaker isolation than serializable, because a transaction does not fail if read data is being changed concurrently. This makes it subject to so called write skew anomalies. As a user, you need to make sure that the write skew anomaly is harmless for your application or does not occur - for example by avoiding concurrent read-write operations. In exchange, Firebolt can deliver the performance, scale and throughput that data intensive applications need.
+
+## [](#creating-tables)Creating tables
+
+Let’s look at an example of how to [create a simple table](/sql_reference/commands/data-definition/create-fact-dimension-table.html) called rankings.
+
+```
+CREATE TABLE IF NOT EXISTS rankings (
+    GameID INTEGER,
+    PlayerID INTEGER,
+    MaxLevel INTEGER,
+    TotalScore BIGINT,
+    PlaceWon INTEGER,
+    TournamentID INTEGER,
+    SOURCE_FILE_NAME TEXT,
+    SOURCE_FILE_TIMESTAMP TIMESTAMP) 
+PRIMARY INDEX GameID, TournamentID, PlayerID;
+```
+
+The statement also contains a [primary index](/Overview/indexes/primary-index.html) definition. While primary index creation is optional in Firebolt, defining primary indexes on all tables is encouraged. Primary indexes, and indexes in general, are critical for delivering performance and achieving efficient query execution.
+
+How do indexes help with delivering this performance? Each table in Firebolt is composed of internal objects called tablets. Tablets store data in columnar format with built-in data compression, reducing disk io and resulting in efficient, performant query processing. Input data gets automatically converted into this columnar data format as the data gets ingested into the table. The size of individual tablets and the number of tablets per table is automatically determined and managed by the Firebolt system. When a table is defined as a partitioned table, individual tablets are bound to a particular partition, as tablets cannot span multiple partitions.
+
+![Tablets](/assets/images/tablets.png)
+
+Defining a primary index on a table forces data sorting within each tablet. Primary indexes can be defined using one or multiple columns, and data ordering follows that index definition. Implementing proper primary indexes and having data ordered correctly is critical for many reasons. First, since each tablet contains granular metadata information about data stored within the tablet itself, scalar predicates and semi-join queries that use primary index columns can be optimized by scanning only the data that is required (as a data pruning process). Second, only tablets needed to satisfy the query can be touched, even though a table may contain many tablets behind the scenes – unneeded tablets are skipped during querying time (as a tablet pruning process). Finally, the ordered dataset typically compresses to a smaller size, leading to reduced IO operations.
+
+In addition, in situations where users create partitioned tables, queries containing filters on partitioned columns can eliminate unnecessary data scans by querying only partitions needed for results (as a partition pruning process). All techniques mentioned above lead to efficiency when querying and processing data.
+
+## [](#inserting-data)Inserting data
+
+To support loading data from a data lake (Amazon S3) into Firebolt tables, Firebolt provides utilities for loading data in bulk. Users can perform both initial and incremental data ingestion using either a [COPY](/sql_reference/commands/data-management/copy-from.html) statement or [INSERT INTO SELECT FROM &lt;external\_table&gt;](/sql_reference/commands/data-management/insert.html) syntax.
+
+In addition, Firebolt supports singleton inserts via a `INSERT INTO VALUES` statement. Typical scenarios where singleton inserts come handy are:
+
+- Refreshing tables with small amounts of dimensional data, and
+- Implementing slowly changing dimension patterns.
+
+Let’s review how these utilities work in more detail, and their corresponding performance.
+
+### [](#bulk-inserts)**Bulk inserts**
+
+In Firebolt, bulk data ingestion utilities are designed to be inherently scalable. There are 4 major stages that each loading process goes through:
+
+1\) Reading data from Amazon S3
+
+2\) Converting data into tablets and columnstore
+
+3\) Merging tablets to optimize tablet quality (needed for efficient tablet pruning)
+
+4\) Uploading tablets into Amazon S3.
+
+As a distributed system and query engine, Firebolt supports both parallel and pipelined data processing, to scale loading processes. At the node level, Firebolt fully employs intra-node parallelism by having multiple reader/writer processes. Data loading parallelism automatically increases as the engine increases in scale (multi-node parallelism). Pipelined execution ensures that all deployed resources are kept busy while data is being streamed across transformation stages mentioned above. This way, users can ingest large amounts of data into Firebolt tables while utilizing deployed resources as efficiently as possible.
+
+![Ingest](/assets/images/ingest.png)
+
+As the bulk data load gets executed, Firebolt creates new tablets behind the scenes while preserving necessary metadata information about the data being ingested. Factors such as min/max values, tablet size, data offsets and ranges, tablet location, etc., are kept as metadata artifacts and used during query execution to deliver differentiated performance characteristics.
+
+Bulk insert statement example
+
+```
+COPY INTO rankings FROM 's3://Bucket/directory/'; 
+//The statement above copies all the files from a directory in an S3 bucket into the rankings table.
+```
+
+### [](#singleton-insert)**Singleton insert**
+
+While singleton insert is a supported pattern in Firebolt, using bulk insert utilities is recommended to optimize performance of large data ingestion.
+
+Data inserted by a singleton insert statement gets stored within a single tablet. From the tablet quality perspective, this creates a suboptimal situation, and can lead to table fragmentation in cases where many singleton inserts are executed. This in turn can lead to suboptimal query performance. One way to mitigate this situation is to use a mini batch pattern (a collection of `INSERT INTO VALUES` statements separated by a comma) whenever possible. When a batch of `INSERT INTO VALUES` statements are executed, Firebolt tries to create a single tablet, which will improve tablet quality and reduce table fragmentation.
+
+To minimize operational overhead and system maintenance that table fragmentation can cause, Firebolt implements a built-in optimization process that merges tablets with suboptimal size. This optimization process is fully autonomous and runs in the background. The background process searches on a periodic basis for suboptimal tablets and merges them while keeping tablet optimal size in mind. In addition, Firebolt supports the [VACUUM](/sql_reference/commands/data-management/vacuum.html) command that allows users full control to defragment tables on-demand.
+
+Singleton insert statement example
+
+```
+INSERT INTO rankings (GameID, PlayerID, MaxLevel, TotalScore, PlaceWon, TournamentID) VALUES (10, 231, 10, 1000020, 1, 5);
+```
+
+## [](#deleting-data)Deleting data
+
+Firebolt supports storing as much data as needed for as long as needed. However, there are situations where data does need to be deleted. Situations like data corrections that occur in the systems of records, or GDPR compliance where a single (or multiple) customer record(s) must be deleted to preserve privacy, have led to support for [DELETE](/sql_reference/commands/data-management/delete.html) statements in Firebolt.
+
+Firebolt supports deleting a single record in a table or deleting data in bulk. In addition to the tablet level metadata, each tablet comes with a delete log. As the records get deleted, the delete log is maintained. Given rich tablet-level metadata, only tablets that are affected by the delete operation are touched. In cases where `DELETE` query uses a primary key(s) as a predicate, Firebolt leverages primary key information to quickly find tablets and records that are affected by the DELETE operation, leading to performant deletes. Similarly, deleting all data that belongs to one or more partitions is almost instantaneous, as deleting data in these cases is only a metadata operation in Firebolt.
+
+Having frequent deletes in the system could lead to tablet fragmentation, so there’s a background process that continuously and automatically optimizes tablets behind the scenes. For more information, refer to [optimizing storage](#optimizing-storage) below.
+
+For optimal performance, leverage primary key(s) for deleting the data whenever possible.
+
+Bulk delete statement example
+
+```
+DELETE FROM rankings WHERE PlayerID = 231;
+```
+
+Singleton delete statement example
+
+```
+DELETE FROM rankings WHERE GameID = 10 AND TournamentID = 5 AND PlayerID = 231;
+```
+
+## [](#updating-data)Updating data
+
+In real life, data updates happen often. Individuals regularly update their contact information as their residency changes, prospects change their contact preference for marketing campaigns, an order changes its status as it goes through the fulfillment process, all causing data stored in the data warehouses to be updated.
+
+An [UPDATE](/sql_reference/commands/data-management/update.html) can be represented as a composite operation of `DELETE` followed by an `INSERT` operation. This holds true for both singleton as well as bulk update statements. Firebolt supports both simple as well as complex update functionality, including complex predicates and multi-table joins. Similarly, any column defined in a Firebolt table can be updated, including partitioning columns. While updating values for a partitioning column may lead to a longer execution time (depending on the number of records that exist in the partition, as updated data may need to be moved to newly assigned partitions), this functionality simplifies usage and avoids the need for manual workarounds to be done by our users.
+
+Update statement example
+
+```
+UPDATE rankings SET GameID = 11 WHERE GameID = 10 AND TournamentID = 5 AND PlayerID = 231;
+```
+
+## [](#optimizing-storage)Optimizing storage
+
+As mentioned in earlier sections, certain data modification scenarios (deletes/updates) could lead to situations where tables get fragmented. To help spot fragmentation situations and identify tables that are fragmented, Firebolt provides a view called [information\_schema.tables](/sql_reference/information-schema/tables.html).
+
+The `information_schema.tables` view provides a number of useful columns, such as the number of rows, compressed and uncompressed table size, among others. For our purposes here, two columns are of interest as fragmentation metrics: 1) `number_of_tablets` and 2) `fragmentation`. As the name suggests, the `number_of_tablets` column projects information about the total number of tablets in each table. The fragmentation column specifies the table fragmentation percentage (number between 0-100). As a best practice and general guidance, it’s recommend to keep fragmentation below 80.
+
+Tables that are fragmented have been identified, now what? There are two paths that Firebolt provides to tackle fragmentation state:
+
+1\) the user-driven option of using a `VACUUM` statement, and 2) system-driven clean up that runs in the background.
+
+Both options lead to optimizing fragmented tablets and merging them into tablets with ideal sizes. `VACUUM` functionality leverages the user-defined engine to perform this optimization task, while system-driven behavior runs completely autonomously and uses Firebolt-provided capacity. The column `number_of_tablets` can be used to identify the total number of tablets before and after optimization tasks are performed. Similarly, the fragmentation metrics from `information_schema.tables` can be used to monitor progress and assess effectiveness of the background process to keep the table in a healthy state.
+
+The background process is recommended due to ease of the management and administration, but both options are available to users to fit their desired behavior and needs.
+
+## [](#maintaining-indexes)Maintaining indexes
+
+Aggregating indexes are one of the key features in Firebolt that help accelerate query performance. Users can create these indexes while using one or more Firebolt supported [aggregate functions](/sql_reference/functions-reference/aggregation/), such as `COUNT, SUM, AVG, MIN, MAX, COUNT(DISTINCT)`, etc. One of the key promises that databases have is that indexes are automatically maintained and updated as the data in the base table change – this is no different with Firebolt. However, data modifications (and specifically deletes) are not the friendliest operations when it comes to maintaining aggregated indexes. Aggregated functions such as `COUNT, SUM, AVG` are composable aggregates, and as such can be easily updated/modified as data changes. However, aggregates such as `MIN, MAX, COUNT(DISTINCT)` do not fall into that category.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_engine_consumption.md b/cmd/docs-scrapper/fireboltdocs/overview_engine_consumption.md
new file mode 100644
index 0000000..9da7995
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_engine_consumption.md
@@ -0,0 +1,86 @@
+# [](#engine-consumption)Engine Consumption
+
+This page explains the engine consumption metric, Firebolt Units (FBUs), and provides detailed examples showing how to calculate the following:
+
+- The FBUs available to an engine.
+- The actual FBUs consumed by a running engine.
+
+For more information about Firebolt engines, see [Understanding Engine Fundamentals](/Overview/engine-fundamentals.html).
+
+Firebolt uses a metric called Firebolt Units (FBU) to track engine consumption. The number of FBUs available to an engine is determined by the following engine attributes:
+
+- The node type.
+- The number of nodes.
+- The number of clusters.
+
+Each node type provides a minimum number of FBUs as shown in the following table:
+
+Node type Compute family Firebolt Units (FBUs) per hour Small (S) Storage-optimized 8 Medium (M) Storage-optimized 16 Large (L) Storage-optimized 32 Extra Large (XL) Storage-optimized 64 Small (S) Compute-optimized 4 Medium (M) Compute-optimized 8 Large (L) Compute-optimized 16 Extra Large (XL) Compute-optimized 32
+
+Small and medium engines are available for use right away. If you want to use a large or extra-large engine, reach out to support@firebolt.io.
+
+As you add more nodes and more clusters to your engine, the number of FBUs available to the engine increases linearly. The available FBUs for a given engine configuration are calculated as follows:
+
+## [](#fbu-per-hour-for-a-given-engine--fbu-of-node-type-x-nodes-x-clusters)FBU-per-hour for a given Engine = (FBU of node Type x Nodes x Clusters)
+
+### [](#calculating-fbus-per-hour-for-a-given-engine---example-1)Calculating FBUs-per-hour for a given Engine - Example 1:
+
+- If you create an engine with the following configuration: TYPE = “S”, NODES = 2, CLUSTERS=1, it will have 16 FBUs available per hour (8 x 2 x 1).
+- If you scale out the engine configuration to use 3 nodes instead of 2, the available FBUs per hour increases to 24 FBUs (8 x 3 x 1).
+
+### [](#calculating-fbus-per-hour-for-a-given-engine---example-2)Calculating FBUs-per-hour for a given Engine - Example 2:
+
+- If you create an engine with the following configuration: TYPE = “L”, NODES = 3, CLUSTERS=2, it will have 192 FBUs available per hour (32 x 3 x 2).
+- If you scale down the engine to use a “M” type node, the available FBUs per hour will decrease to 96 FBUs (16 x 3 x 2).
+
+FBUs are consumed only when an engine is in a running state. The FBUs consumed by an engine depends on both the current configuration of the engine (node type, number of nodes and number of clusters) and the duration for which the engine has been running in that configuration. Since Firebolt provides per-second billing, the consumed FBU is calculated at per-second granularity, as shown in the following examples:
+
+## [](#fbus-consumed---fbus-per-hour--3600-x-engine-runtime-in-seconds)FBUs Consumed = (FBUs per hour / 3600) x (engine runtime in seconds)
+
+### [](#consumed-fbu---example-1)Consumed FBU - Example 1:
+
+If you create an engine with the following configuration: TYPE = “S”, NODES = 2, CLUSTERS=1, it has 16 available FBUs per hour. If the engine runs for only 15 minutes of that hour, then the engine consumes 4 FBUs.
+
+### [](#consumed-fbu---example-2)Consumed FBU - Example 2:
+
+If you create an engine with the following configuration: TYPE = “L”, NODES = 3, CLUSTERS=2, it has 192 FBUs available per hour. If the engine was only running for 40 seconds to quickly ingest a small amount of data. The consumed FBU is calculated as follows:
+
+FBU Consumed = (192/3600) x 40 = 2.13
+
+## [](#the-impact-of-resize-operations-on-engine-consumption)The impact of resize operations on engine consumption
+
+If you perform scaling operations on an engine, you add additional compute resources (clusters) to the engine. These operations include scaling up or down, and scaling out or in.
+
+Any new clusters resulting from a resizing operation will have the new **node type** for a scale up or down operation. Any new clusters will have the desired **number of nodes** for a scale in or out operation. Existing clusters will be removed after they finish running any currently running queries. New queries will run on the new resized clusters. This can result in a temporary overlap when both old and new clusters are running concurrently, which will be reflected in the engine’s consumption.
+
+### [](#example-1)Example 1:
+
+If you create an engine with the following configuration: TYPE = “S”, NODES = 2, CLUSTERS=1, there are 16 available FBUs per hour.
+
+- **First 15 minutes during the hour:** The engine is running in the previous configuration.
+- **After first 15 minutes:** The engine is scaled out to use five nodes, keeping the same node type and same number of clusters. The old cluster with two nodes continues to run for 5 minutes to finish executing the queries. The new cluster with five nodes runs for the next fifteen minutes.
+
+The consumed FBUs are calculated as follows:
+
+- **Minutes 1-15:** Only one cluster with two nodes is running, consuming 4 FBUs.
+- **Minutes 16-20:** Two clusters are running. the cluster with nodes consumes 1.3 FBUs, and the cluster with five nodes consumes 3.3 FBUs.
+- **Minutes 20-30:** Only the cluster with five nodes is running and consumes 6.7 FBUs.
+
+Total number of FBUs consumed for the hour = 4 + 1.3 + 3.3 + 6.7 = 15.3 FBUs.
+
+### [](#example-2)Example 2:
+
+If you create an engine with the following configuration: TYPE = “L”, NODES = 2, CLUSTERS=1, there are 64 available FBUs per hour.
+
+- **First 15 minutes during the hour:** The engine is running in the above configuration.
+- **After first 15 minutes:** The engine is scaled down to use “M” type nodes, keeping the same number of nodes and same number of clusters. The old cluster with “L” type nodes continues to run for 5 minutes to finish running the queries. The new cluster with “M” type nodes runs for the next fifteen minutes.
+
+The consumed FBUs are calculated as follows:
+
+- **Minutes 1-15:** Only one cluster with two “L” type nodes is running, consuming 16 FBUs.
+- **Minutes 16-20:** Two clusters running. Cluster with two “L” type nodes consumes 5.3 FBU and Cluster with two “M” type nodes consumes 2.7 FBU.
+- **Minutes 20-30:** Only the cluster with two “M” type nodes is running, consuming 5.3 FBUs.
+
+Total number of FBUs consumed for the hour = 16 + 5.3 + 2.7 + 5.3 = 29.3 FBUs.
+
+Firebolt Engines are priced based on the amount of FBUs consumed by a given engine. For more details on engine pricing, including examples, visit the [Pricing page](https://www.firebolt.io/pricing).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_engine_fundamentals.md b/cmd/docs-scrapper/fireboltdocs/overview_engine_fundamentals.md
new file mode 100644
index 0000000..14b91f7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_engine_fundamentals.md
@@ -0,0 +1,164 @@
+# [](#firebolt-engines)Firebolt Engines
+
+Engines are compute resources that process data and serve queries in Firebolt. Use engines to load data into Firebolt and run queries on the ingested data.
+
+Firebolt engines provide **full workload isolation**, so that multiple workloads run independently while sharing the same data. Engines are **decoupled from databases**, meaning:
+
+- A single engine can run queries on multiple databases.
+- A database can be queried using multiple engines.
+
+Start, stop and modify engines at any time using the SQL API. You can also **dynamically scale engines** based on workload needs without stopping them.
+
+This document explains engine configuration, scaling, monitoring, security and connection options.
+
+**Topics**
+
+- [Key engine concepts](#key-engine-concepts) – Learn about the `TYPE`, `NODES`, and `CLUSTERS` attributes that define a Firebolt engine’s configuration and scaling options.
+- [Multi-dimensional elasticity](#multi-dimensional-elasticity) – Scale engines dynamically by adjusting engine attributes without stopping workloads.
+- [Connecting to engines](#connecting-to-engines) – How to connect to a Firebolt engine using the UI, Engine URL, or third-party tools.
+- [Monitoring engine usage](#monitoring-engine-usage) – Track engine performance using observability views in `information_schema` to optimize resource allocation.
+- [Engine governance and security](#engine-governance-and-security) – Control engine access using [Role-Based Access Control (RBAC)](/Overview/Security/Role-Based%20Access%20Control/) and account-level isolation to enforce security policies.
+- [Viewing and understanding engine status](#viewing-and-understanding-engine-status) – Learn how to use `SHOW ENGINES` to check the status of all engines, including running, resizing, and stopped states.
+
+## [](#key-engine-concepts)Key engine concepts
+
+Engines in Firebolt are defined by three attributes: **Type**, **Nodes**, and **Clusters**. These attributes determine the engine’s configuration and scaling options.
+
+**Family**  
+Compute nodes can also be storage-optimized with larger cache sizes or compute-optimized which have smaller caches. The default is storage optimized.
+
+**Nodes**  
+This attribute represents the number (1 - 128) of compute nodes, allowing granular horizontal scaling to fine-tune query performance characteristics while avoiding overprovisioning and unnecessary cost. Both scaling in and out are supported.
+
+**Clusters**  
+A cluster is a collection of compute resources, described by “Type” and “Nodes” attributes. A given Firebolt engine can contain one or more clusters. The maximum number of clusters is specified by the Clusters attribute. Only homogeneous cluster configurations (clusters with the same number of Nodes and Type) are supported within a single engine. Users can leverage the “Clusters” attribute to support query concurrency scaling.
+
+![An engine cluster in Firebolt](/assets/images/engine_cluster_type_M.png)  
+**An engine cluster with four nodes of type ‘M’**
+
+![A Firebolt engine with two clusters, each cluster containing four nodes of type 'M'](/assets/images/Engine_two_clusters_type_M.png)  
+**A Firebolt engine with two clusters, each cluster containing four nodes of type ‘M’**
+
+The three attributes: `TYPE`, `NODES` and `CLUSTERS` – form the configuration of an engine.
+
+To create an engine, use the [CREATE ENGINE command](/sql_reference/commands/engines/create-engine.html), specifying the node type to be used for the engine, number of clusters and number of nodes per cluster.
+
+The following code example creates two clusters, each containing four nodes of type `M`:
+
+```
+CREATE ENGINE IF NOT EXISTS MyEngine 
+WITH TYPE = M 
+NODES = 4 
+CLUSTERS = 2;
+```
+
+For a full list of engine attributes, see [CREATE ENGINE](/sql_reference/commands/engines/create-engine.html)
+
+## [](#multi-dimensional-elasticity)Multi-dimensional elasticity
+
+Firebolt engines enable dynamic and fully online scaling operations, meaning you do not need to stop your engines to scale them. You can scale an engine along three dimensions:
+
+Scaling Type Action Example SQL Command **Vertical Scaling** Change the node type `ALTER ENGINE MyEngine SET TYPE = L;` **Horizontal Scaling** Change the number of nodes `ALTER ENGINE MyEngine SET NODES = 3;` **Concurrency Scaling** Change the number of clusters `ALTER ENGINE MyEngine SET CLUSTERS = 2;`
+
+You can scale up or down using the engine type, scaling out or in with number of nodes and add or remove clusters for concurrency scaling. This multidimensional scaling allows you to fine-tune the price-performance characteristics of engines and dynamically scale your compute resources based on your workload requirements.
+
+Use the [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html) to modify the configuration of an engine to dynamically scale the engine even while it is running, without impacting the workload.
+
+**Best practices**
+
+- Use a **larger node type** to improve performance for both single queries and multiple concurrent queries, especially as data size grows
+- Increase the number of nodes for finer control over scaling, such as distributing workloads across multiple smaller nodes or when further vertical scaling is not possible.
+- Increase the **number of clusters** to support higher query concurrency.
+
+The following code example uses `ALTER ENGINE` to horizontally scale an engine from two to three nodes:
+
+```
+ALTER ENGINE MyEngine SET NODES = 3;
+```
+
+The following code example changes the type of node used in an engine from ‘M’ to ‘L’:
+
+```
+ALTER ENGINE MyEngine SET TYPE = L;
+```
+
+The following code example changes more than one attribute at the same time:
+
+```
+ALTER ENGINE MyEngine SET NODES = 3 TYPE = L;
+```
+
+For more information on modifying engines, see [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html).
+
+## [](#connecting-to-engines)Connecting to engines
+
+You can connect to an engine using the following methods:
+
+- Firebolt’s [user interface](https://go.firebolt.io/login).
+- An engine URL.
+- Third-party [connectors](/Guides/integrations/integrations.html) such as Airflow and DBT.
+
+The engine URL is based on your account name and org name, with the following format:
+
+`<account-name>.<org-name>.region.firebolt.io`
+
+The combined length of `account-name` and `org-name` must not exceed 62 characters.
+
+## [](#monitoring-engine-usage)Monitoring engine usage
+
+You can use the observability views in `information_schema` to track engine performance and usage.
+
+View Description `engine_metrics_history` Captures CPU and RAM usage every **30 seconds** and retains data for **30 days**. `engine_running_queries` Lists active queries and queries waiting to be processed.
+
+You can use the information in the previous [information\_schema views](/sql_reference/information-schema/) to decide whether you need to change the engine configuration type, number of nodes or clusters based on your workload needs.
+
+The [engine\_metrics\_history](/sql_reference/information-schema/engine-metrics-history.html) view gathers engine resource utilization metrics such as CPU and RAM consumption at a given time snapshot. Utilization snapshots are captured every 30 seconds and retained for 30 days, allowing users to understand engine utilization and consumption trends.
+
+The following code example retrieves CPU and RAM usage for `MyEngine`:
+
+```
+SELECT * 
+FROM information_schema.engine_metrics_history 
+WHERE engine_name = 'MyEngine' 
+ORDER BY event_time DESC;
+```
+
+The [engine\_running\_queries](/sql_reference/information-schema/engine-running-queries.html) view exposes information about queries currently running or waiting to be run in the system. Based on the number of queries that are queued and waiting to run, you can modify the engine configuration to best suit your performance requirements.
+
+The following code example retrieves currently running queries:
+
+```
+SELECT * 
+FROM information_schema.engine_running_queries;
+```
+
+If the previous query shows that queries remain in the queue for too long, increase the number of nodes or clusters.
+
+To understand how information views can help with engine resizing, see [Working with Engines](/Guides/operate-engines/sizing-engines.html).
+
+## [](#engine-governance-and-security)Engine governance and security
+
+Firebolt provides **account-level isolation** and **Role Based Access Control (RBAC)** to provide strict governance over data access and infrastructure costs.
+
+**Account isolation**
+
+You can create multiple accounts within a given organization, where each account can represent a fully isolated environment such as development, test, or production. This enables engines across different environments to be fully isolated from each other.
+
+**RBAC for engine management**
+
+The Firebolt [RBAC model](/Guides/security/rbac.html) allows administrators to control user actions on resources that are created within a given account. For example, administrators can control which users are allowed to modify the configuration of engines and control which users can create new engines.
+
+The following code example creates an engine administrator role and grants it full permissions on `MyEngine`:
+
+```
+CREATE ROLE engine_admin;
+GRANT ALL PRIVILEGES ON ENGINE MyEngine TO engine_admin;
+```
+
+For more information on using RBAC for engines, see [Governing Engines](/Guides/operate-engines/rbac-for-engines.html).
+
+## [](#viewing-and-understanding-engine-status)Viewing and understanding engine status
+
+Use [SHOW ENGINES](/sql_reference/commands/metadata/show-engines.html) to list all engines and their statuses in your Firebolt account as follows:
+
+`SHOW ENGINES` and UI Description STARTING The engine is provisioning resources, and will be ready to use soon. RUNNING The engine is running queries or available to run queries. The engine can be modified while it is running. RESIZING The engine is currently being resized after an `ALTER ENGINE` command. The engine will be in this state when the user has issued a request to change the engine `TYPE`, number of `NODES` or number of `CLUSTERS`. DRAINING The engine is completing running queries before shutting down. STOPPING The engine is shutting down and cannot accept new queries. STOPPED The engine is fully stopped and not available to run queries.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_indexes_aggregating_index.md b/cmd/docs-scrapper/fireboltdocs/overview_indexes_aggregating_index.md
new file mode 100644
index 0000000..ae7310d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_indexes_aggregating_index.md
@@ -0,0 +1,75 @@
+# [](#aggregating-index)Aggregating index
+
+Firebolt’s aggregating index is a powerful tool for improving performance in large-scale analytics. Similar to a materialized view, it precomputes and stores the results of aggregate functions, allowing queries to access data directly from the index instead of scanning the entire table. This approach greatly reduces compute overhead and speeds up query times, making it especially useful for repetitive tasks like generating dashboards and reports.
+
+Aggregating indexes are automatically updated in real-time whenever new data is added or when changes, such as `DELETE` or `UPDATE` operations, are made to the base table. Firebolt also enhances performance by dividing aggregating indexes into smaller segments that are distributed across multiple engine nodes. This allows queries to run in parallel across these nodes, improving both scalability and efficiency while ensuring that the data remains consistent and accurate.
+
+Topics:
+
+- [Aggregating index](#aggregating-index)
+  
+  - [Key features](#key-features)
+  - [Syntax](#syntax)
+    
+    - [Parameters](#parameters)
+  - [Example](#example)
+  - [Considerations](#considerations)
+
+## [](#key-features)Key features
+
+- **Automatic synchronization**
+  
+  The aggregating index is automatically updated in real-time to reflect changes in the base table after each transaction including **DELETE** or **UPDATE** operations.
+- **Automatic `COUNT(*)` aggregations**
+  
+  A `COUNT(*)` aggregation is automatically added to every aggregating index unless explicitly specified by the user. This ensures the index can accurately handle `DELETE` operations by tracking the number of rows affected. The aggregating index adjusts its precomputed results to remain synchronized with the base table, maintaining consistency and ensuring accurate query results.
+- **Primary index deduction**
+  
+  The primary index for a Firebolt table is established based on the order of the **GROUP BY** keys specified during the creation of an aggregating index. Firebolt physically organizes the data according to these keys, which align with how queries group and aggregate the data. This optimization enables effective data pruning and reduces scan times, making data retrieval more efficient.
+
+## [](#syntax)Syntax
+
+```
+CREATE AGGREGATING INDEX <index_name>
+ON <table_name> (
+   <grouping_element>
+     [, ...],
+     <aggregation_element>
+     [, ...]
+);
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<index_name>` The name of the aggregating index. `<table_name>` The name of the table on which the index is created. `<grouping_element>` Expressions specified as grouping keys or dimensions when creating the index. `<aggregation_element>` Aggregation functions applied to specific expressions.
+
+## [](#example)Example
+
+The following example creates an aggregating index `sales_agg_index` on the `sales` table and precomputes the `SUM` and `COUNT` aggregations:
+
+```
+CREATE AGGREGATING INDEX sales_agg_index
+ON sales(product_id, region, SUM(sales_amount), COUNT(DISTINCT order_id));
+```
+
+In the previous code example, `product_id` and `region` are grouping keys that are grouped together as `grouping_element`. These keys define how the data is grouped for aggregation, similar to the `GROUP BY` clause in a SQL query. Subsequent queries using these aggregations can retrieve the precomputed values directly from the index, avoiding a full table scan.
+
+Because the code example precomputes `SUM` and `COUNT`, subsequent queries using these aggregations can retrieve the precomputed values directly from the index, avoiding a full table scan.
+
+## [](#considerations)Considerations
+
+**Ingestion Overhead**
+
+Maintaining an aggregating index adds processing overhead during data loading, which can slow down Data Manipulation Language (DML) operations such as `INSERT`, `DELETE`, and `UPDATE` on the base table.
+
+**Vacuuming**
+
+To ensure optimal query performance, you should periodically **vacuum** the aggregating index. [VACUUM](/sql_reference/commands/data-management/vacuum.html) helps to:
+
+- Defragment data in the aggregating index table.
+- Remove stale or deleted items from disk after `DELETE` operations on the base table.
+
+Regular vacuuming can improve query performance, especially for the following:
+
+- **Frequent batch inserts** – These inserts can lead to fragmented data in the aggregating index table.
+- **Base table mutations** – Operations like `DELETE` or `UPDATE` on the base table can also cause fragmentation, impacting query performance.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_indexes_primary_index.md b/cmd/docs-scrapper/fireboltdocs/overview_indexes_primary_index.md
new file mode 100644
index 0000000..d6d3038
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_indexes_primary_index.md
@@ -0,0 +1,122 @@
+# [](#primary-index)Primary index
+
+The Firebolt primary index optimizes data retrieval by organizing it based on column values. This enables efficient data pruning and high-performance queries for large-scale analytics. The primary index ensures that queries target only the most relevant portions of the data, significantly reducing the volume of unnecessary scans. This selectivity is especially powerful when the indexed columns align closely with query patterns, allowing the database to quickly locate and retrieve the required data. As a result, query performance is not only optimized but also remains consistent even as data volumes grow.
+
+Topics:
+
+- [Key features](#key-features)
+- [Syntax](#syntax)
+- [Parameters](#parameters)
+- [Example](#example)
+- [Considerations](#considerations)
+- [Advanced option: index granularity](#advanced-option-index-granularity)
+
+## [](#key-features)Key features
+
+- **Customizable indexing**:
+  
+  - Unlike traditional databases, Firebolt allows primary indexes on any column, so that you have the flexibility to align with query patterns.
+  - Primary key constraints are not enforced, allowing for greater customization.
+- **Tablet-based data organization**:
+  
+  - Data is divided into tablets, which are self-contained, fixed-size data chunks approximately 3GB each, sorted by primary index keys for efficient querying.
+  - Within each tablet, your data is further segmented into intra-tablet ranges, approximately 8,000 rows each, for faster access.
+- **Support for compound indexes**:
+  
+  - Multiple columns can be included in the primary index, optimizing complex query patterns by allowing efficient pruning and retrieval for queries that filter or group data based on combinations of these columns, such as filtering by both a date range and a category or joining fact and dimension tables on multiple keys.
+- **Sparse indexing**:
+  
+  - Firebolt employs a sparse indexing approach, storing only the first row of each tablet range. This approach allows target reads and parallel processing, significantly reducing index size while increasing query performance.
+- **Automatic metadata updates**:
+  
+  - The primary index is automatically maintained during data inserts, deletions, and updates ensuring optimal performance.
+- **Handling low-cardinality clauses**:
+  
+  - Starting the primary index with low-cardinality columns can enhance pruning efficiency by creating long ordered runs of data. Low-cardinality columns are those with a limited number of unique values such as months, regions, or statuses, which group similar rows together. This reduces the number of tablet ranges Firebolt needs to scan, enabling faster query execution and better data pruning.
+- **Inclusion of join key columns**:
+  
+  - In star schema designs, including join key columns, or foreign keys, in the primary index of fact tables can accelerate queries by facilitating efficient data retrieval.
+- **Leverage indexed columns directly**:
+  
+  - Design queries to use indexed columns directly in WHERE clauses without transformations, ensuring that the primary index can be utilized to its full potential for faster data pruning and query execution.
+
+## [](#syntax)Syntax
+
+To define a primary index, use the following syntax within a `CREATE TABLE` statement:
+
+```
+CREATE TABLE <table_name> (
+   <column1> <data_type>
+   [, <column2> <data_type>,
+   ...]
+)
+PRIMARY INDEX <column_name1>[, <column_name2>, ...]
+[WITH ( index_granularity = <index_granularity> ) ];
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `table_name` The name of the table where the primary index is applied. `column_name1, ...` The columns chosen to be included in the primary index. `index_granularity` The maximum number of rows in each granule. See [Index granularity](#advanced-option-index-granularity).
+
+## [](#example)Example
+
+The following example creates a table with a primary index optimized for query performance by filtering for `SubmitDate` and `EngineName`:
+
+```
+CREATE [FACT|DIMENSION] TABLE QueryHistory (
+  QueryID TEXT,
+  QueryText TEXT,
+  SubmitDate DATE,
+  EngineName TEXT,
+  SubmitTime DATE,
+  Latency INT
+)
+PRIMARY INDEX SubmitDate, EngineName;
+```
+
+## [](#considerations)Considerations
+
+- **Non-enforced primary key constraint**:  
+  Firebolt does not enforce primary key constraints, so users must manage data integrity externally.
+- **Managing fragmentation**:  
+  Fragmentation can occur as you insert, delete, or update data in a table, which impacts storage efficiency and potentially affects your query performance. Firebolt provides tools to help mitigate this effect:
+  
+  - **Efficient deletion management**:  
+    Instead of immediately removing rows from the table, Firebolt uses a deletion mask vector to flag rows as deleted. This vector marks rows for exclusion during queries while keeping the underlying data intact until cleanup is performed.  
+    This approach ensures consistency and avoids disrupting the primary index during updates or deletions.
+  - **fragmentation metric**:  
+    Use the `information_schema.tables` to access the fragmentation metric to assess fragmentation levels and determine whether maintenance actions are needed.
+  - **[VACUUM](/sql_reference/commands/data-management/vacuum.html) command**:  
+    You can use the `VACUUM` command to clean up rows flagged for deletion and reorganize fragmented data. It is particularly useful when large numbers of rows have been deleted or updates have introduced significant fragmentation.
+- **Query Performance Overhead**:  
+  While sparse indexes enable targeted reads and parallel processing to improve query performance, they may still require scanning one tablet range from multiple tablets, even for highly selective filters. This can result in more data being scanned compared to a globally sorted index, potentially affecting performance in certain scenarios.
+- **Column Selection**:  
+  Choose columns with high selectivity and relevance to query patterns for optimal performance. **Selectivity** refers to the ability of a column to significantly narrow down the dataset when filtered, typically measured by the proportion of unique values in the column. Columns with higher selectivity, such as IDs or timestamps, help reduce the number of rows scanned, leading to faster query execution and better resource efficiency.
+
+Using Firebolt’s primary indexes can help you enhance your query performance, optimize data management, and scale efficiently for modern analytics workloads.
+
+## [](#advanced-option-index-granularity)Advanced option: index granularity
+
+The `index_granularity` [storage parameter](/sql_reference/commands/data-definition/create-fact-dimension-table.html#storage-parameters), specified in the `WITH` clause, is an advanced setting that may be useful for improving performance in very specific query patterns. It defines the maximum number of rows per granule, which directly impacts how data is indexed and queried.
+
+### [](#how-index-granularity-works)How index granularity works
+
+A granule is the smallest block of rows that Firebolt can skip or read during query filtering. Index granularity defines the number of rows in each granule. In other words, it sets the smallest group of rows the engine can access independently.
+
+- **Lower index granularity** creates smaller granules, allowing more precise filtering and reducing unnecessary row scans in selective queries. However, lower index granularity also increases memory usage and overhead from managing more granules.
+- **Higher index granularity values** creates larger granules, lowering memory usage and management overhead but increasing the chance of scanning irrelevant rows, especially in selective queries.
+
+For more information about the fundamentals of Firebolt’s primary indexes and granules, see Firebolt’s blog post on [primary indexes](https://www.firebolt.io/blog/primary-indexes-in-firebolt-a-comprehensive-guide-to-understanding-managing-and-selecting).
+
+### [](#accepted-values)Accepted values
+
+`<index_granularity>` must be a power of 2, ranging from 128 to 8192. The default value is 8192. We recommend using the default value, but lower values can decrease query latency by 10x or more in some query patterns.
+
+### [](#best-practices)Best practices
+
+Use the default value of `index_granularity`, which should translate to good performance for most queries. The following workload patterns may benefit from higher or lower values for `index_granularity`:
+
+- If your queries access only a few rows per granule, such as single-row queries or individual rows spread throughout a table, setting a **lower** `index_granularity` value can reduce unnecessary row scans and improve efficiency. However, this increases static memory usage for storing the index.
+- If most of your queries scan large portions of the table, such as a large bounded range of primary index columns, a **higher** `index_granularity` value is more efficient, as it reduces index memory usage and overhead introduced by each granule boundary.
+
+If you want to adjust `index_granularity`, start with the default value, then create duplicate tables with different settings to compare both the query latency and memory usage.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_indexes_using_indexes.md b/cmd/docs-scrapper/fireboltdocs/overview_indexes_using_indexes.md
new file mode 100644
index 0000000..f358d8f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_indexes_using_indexes.md
@@ -0,0 +1,446 @@
+# [](#data-modeling)Data modeling
+
+Firebolt optimizes data storage and retrieval by using indexing, partitioning, and compute scaling to enhance query efficiency. Design your data model and use databases, tables, and indexes to optimize query performance.
+
+- **Minimizing data scans**  
+  Firebolt indexes retrieve only the specific data ranges needed to satisfy a query, reducing the amount of data scanned.
+- **Automatic index maintenance**  
+  During data loading, Firebolt automatically sorts, compresses, and incrementally updates indexes to keep them optimized.
+- **Tablet-based optimization**  
+  Data and indexes are committed as tablets, which Firebolt automatically merges and optimizes as the data evolves.
+- **Best practices for performance**  
+  This guide provides recommendations for organizing tables, indexes, and data to achieve fast query results and peak performance.
+
+## [](#how-it-works)How it works
+
+Firebolt’s indexing and partitioning strategies are designed to take advantage of a cloud-based architecture that scales to handle very large data sets. Data is queried using multiple nodes for parallel processing. Data is also stored by columns, which allows for:
+
+- **Optimized read operations**
+- **Less disk space for storage**
+- **Vectorized processing**
+
+Firebolt also separates compute resources from storage resources so you can scale either up or down depending on your use case. Optimize your resources based on your changing workloads, and pay only for what you use.
+
+Firebolt’s data modeling strategies work best with **Firebolt’s managed tables**, which leverage Firebolt’s performance optimizations. External tables, which allow users to access data without loading it into Firebolt, provide flexibility for querying external data sources like Amazon S3, but they do not offer the same performance benefits as managed tables.
+
+The following sections show you how to use the previous data modeling strategies to decrease the number of bytes scanned to improve query performance, reduce storage costs, and optimize compute resources.
+
+Topics:
+
+- [Data modeling](#data-modeling)
+  
+  - [How it works](#how-it-works)
+    
+    - [Databases](#databases)
+      
+      - [Create a database](#create-a-database)
+      - [Manage a database](#manage-a-database)
+      - [Database best practices](#database-best-practices)
+        
+        - [Database best practice example](#database-best-practice-example)
+      - [Evaluate your database for performance](#evaluate-your-database-for-performance)
+    - [Schema](#schema)
+      
+      - [Schema best practices](#schema-best-practices)
+    - [Tables](#tables)
+      
+      - [Firebolt-managed tables](#firebolt-managed-tables)
+      - [External tables](#external-tables)
+      - [Editing and deleting tables](#editing-and-deleting-tables)
+      - [Primary indexes in tables](#primary-indexes-in-tables)
+        
+        - [Create a primary index](#create-a-primary-index)
+        - [Primary index best practices](#primary-index-best-practices)
+      - [Aggregating indexes in tables](#aggregating-indexes-in-tables)
+        
+        - [Create an aggregating index](#create-an-aggregating-index)
+        - [Best practices for aggregate indexes](#best-practices-for-aggregate-indexes)
+      - [Partitions in tables](#partitions-in-tables)
+        
+        - [Create a partition](#create-a-partition)
+      - [Suggested indexes and partitions](#suggested-indexes-and-partitions)
+    - [Additional resources](#additional-resources)
+
+* * *
+
+### [](#databases)Databases
+
+**Logical structure**  
+In Firebolt, a database is a logical structure that organizes and stores data for efficient querying and management. Databases are created using the `CREATE DATABASE` statement and can be modified or deleted using `ALTER` and `DROP`.
+
+**Compute and storage separation**  
+Firebolt separates compute and storage layers, ensuring databases are efficiently managed without impacting processing power.
+
+**Data Security**  
+Databases integrate with Firebolt’s data security layers, enforcing access controls and user permissions to safeguard sensitive information.
+
+**Performance and integration**
+
+- **Fast analytics**: Firebolt databases enable quick querying of large datasets, supporting fast analytics.
+- **Third-Party integration**: They are easily integrated with third-party tools through APIs and drivers for programming languages like Python and .NET.
+
+Database topics:
+
+- [Create a database](#create-a-database) – Use a system or user engine to create a database.
+- [Manage a database](#manage-a-database) – How to edit and delete databases.
+- [Database best practices](#database-best-practices) – How to organize your databases for the best performance.
+- [Evaluate your database for performance](#evaluate-your-database-for-performance).
+
+#### [](#create-a-database)Create a database
+
+Use [CREATE DATABASE](/sql_reference/commands/data-definition/create-database.html), which requires only the name of the database, and an **engine** to create a database.
+
+Firebolt provides two types of engines:
+
+- **System engines** handle administrative tasks like creating and managing databases and tables without any need for configuration. They are always available but cannot process user data. **User engines** perform both administrative tasks and handle queries that access and process user data. User engines provide the flexibility needed for data processing and analysis.
+
+The following code example creates a `test_library` database with an optional description:
+
+```
+CREATE DATABASE IF NOT EXISTS test_library 
+    WITH DESCRIPTION = 'database about library';
+```
+
+#### [](#manage-a-database)Manage a database
+
+After you create a database, you can create additional objects and run queries within it. You can also modify the database parameters.
+
+The following code example modifies the description of a database:
+
+```
+ALTER DATABASE library SET DESCRIPTION = 'database about library';
+```
+
+You can delete a database with [DROP DATABASE](/sql_reference/commands/data-definition/drop-database.html), which permanently deletes the database and all its contents. Since this action cannot be undone, use it carefully. Create a backup before dropping the database to prevent data loss.
+
+The following code example uses the optional `IF EXISTS` clause to see if the `test_library` database exists, and then deletes it:
+
+```
+DROP DATABASE IF EXISTS test_library;
+```
+
+Active queries will continue using the latest version of the database, but new queries submitted after the database is dropped will fail. To minimize disruptions, monitor active queries and notify users in advance.
+
+#### [](#database-best-practices)Database best practices
+
+Efficient database design in Firebolt is key to optimizing query performance, managing scalability, and ensuring workload isolation. By using databases to logically separate data, workloads from each other. You can reduce the impact of schema changes, minimize query latency, and enhance access control through role-based policies. For example, when managing data for applications that operate across multiple regions, understanding when to use a single database versus separate databases can significantly affect performance and operational efficiency. The following best practices outline how to structure databases in Firebolt to achieve these goals:
+
+- **Use databases to logically separate workloads** – Organize data into separate databases to isolate workloads and reduce the impact of schema changes on unrelated queries.
+- **Group related tables in the same database** – Only include related tables within the same database to minimize the overhead caused by metadata synchronization during schema changes.
+- **Separate data for different regions or use cases** – For multi-region applications, create separate databases for each region to avoid conflicts such as overlapping primary keys, and to prevent schema changes in one region from affecting query performance in another.
+- **Minimize the number of tables in a single database** – Avoid adding too many unique tables to a single database, as schema changes require the metadata service to synchronize all associated schemas, potentially increasing query latency.
+- **Leverage logical separation for access control** – Use separate databases to enforce role-based access control policies, ensuring users can only access data relevant to their roles and restricting queries across databases.
+- **Consider metadata sync impacts on query latency** – Metadata synchronization can introduce slight query latencies after schema changes, especially as the number of tables in a database grows.
+
+##### [](#database-best-practice-example)Database best practice example
+
+The maker of the fictional [UltraFast game](https://help.firebolt.io/t/ultra-fast-gaming-firebolt-sample-dataset/250) plans to expand into a second region, where the game will generate data with the same structure and format as the first region but potentially overlapping primary keys.
+
+The developers have two options:
+
+1. Store the new region’s data in the existing database.
+2. Create a separate database specifically for the new region.
+
+**Recommended solution** Create a separate database for the new region for the following reasons:
+
+- **Optimal Query Performance** – Firebolt’s decoupled architecture requires metadata synchronization for schema changes. As the number of tables in a database grows, this synchronization can introduce slight query latency. Storing data for each region in separate databases eliminates this risk and ensures efficient query performance.
+- **Improved data isolation** – Queries for one region are not impacted by schema changes in another. Separate databases allow role-based access control, restricting access to data by region, which enhances security and operational control.
+
+By creating a dedicated database for each region, the developers ensure optimal performance, scalability, and data management tailored to the needs of the UltraFast game expansion.
+
+#### [](#evaluate-your-database-for-performance)Evaluate your database for performance
+
+You can use the code in the [Firebolt DDL Performance GitHub repository](https://github.com/wagjamin/firebolt-ddl-performance/tree/main) to measure the efficiency of your database design. Use the code to generate a set of pdf plots for latency to evaluate your choices including the following:
+
+- How increasing the number of tables impacts schema synchronization times.
+- Analyze whether separating unrelated tables into different databases improves performance.
+- Validate the benefits of isolating data for different use cases or regions in separate databases.
+- Understand the trade-offs of schema changes on query latency and how to mitigate them through better database organization.
+
+* * *
+
+### [](#schema)Schema
+
+A schema serves as a blueprint for how data is organized within a database, acting as a logical framework that groups tables, views, and indexes. Understanding how to structure and manage schemas is crucial for maintaining an organized database environment, making it easier to optimize queries and manage access. While schemas don’t directly improve query performance, the way you organize your data within them can significantly impact how efficiently queries run, especially as your data grows.
+
+#### [](#schema-best-practices)Schema best practices
+
+To enhance query performance, simplify access control, and ensure scalability as your data grows, use the following best practices:
+
+- **Logical Organization** – Grouping related tables, views, and indexes within a schema, to create a logical structure that makes it easier to navigate and optimize your queries. Well-organized data allows for clearer queries, reducing complexity and improving readability.
+- **Simplified Access Control** – Using schemas to manage access to certain tables or views ensures that only relevant data is queried by specific users or roles. This prevents unnecessary data scans or joins, which can improve query execution time.
+- **Scalability** – As your database grows, a well-structured schema becomes even more important. Organizing data in a way that scales efficiently prevents bottlenecks, ensuring that queries can continue to run quickly even with larger datasets.
+
+* * *
+
+### [](#tables)Tables
+
+In Firebolt, tables are the key components for organizing and storing data. They consist of rows (records) and columns (attributes), making them an integral tool in data modeling. Firebolt supports two main types of tables:
+
+Table topics:
+
+- [Firebolt-managed tables](#firebolt-managed-tables) – Fast and dimension tables make the best use of Firebolt’s optimization strategies.
+- [External tables](#external-tables) – Users can access and query data without loading it into Firebolt. External tables generally have poorer performance compared to Firebolt-managed tables.
+- [Editing and deleting tables](#editing-and-deleting-tables) – You can edit and delete an existing table.
+- [Primary indexes in tables](#primary-indexes-in-tables) – Select the most efficient primary index for your tables based on your query patterns and data characteristics.
+- [Aggregating indexes in tables](#aggregating-indexes-in-tables) – Precompute and update aggregation results for fast calculations and to save compute resources.
+- [Partitions in tables](#partitions-in-tables) – Organize data based on date ranges, regions, customer types or other categories.
+- [Suggested indexes and partitions](#suggested-indexes-and-partitions) – Use Firebolt’s [RECOMMEND\_DDL](/sql_reference/commands/queries/recommend_ddl.html) tool to suggest indexes and partitions based on your query history.
+
+#### [](#firebolt-managed-tables)Firebolt-managed tables
+
+Tables that are fully controlled by Firebolt make the best use of Firebolt’s optimization strategies. There are two types of managed tables, which serve different but complementary purposes:
+
+- **Fact tables** – store large volumes of quantitative data, such as sales metrics or user interactions, and are used for analysis and reporting.
+- **Dimension tables** – which hold descriptive data for enriching analyses, such as customer details or product categories. These tables are often duplicated across all nodes, and can dramatically improve query performance by providing fast access to frequently referenced information.
+
+By designing tables with both fact and dimension roles, users can optimize data management for reporting and analytics.
+
+**Fact tables**
+
+The following code example creates a **fact table**:
+
+```
+CREATE TABLE borrowedbooks (
+	transaction_id INT,
+	book_id INT,
+	member_id INT,
+	checkout_date DATE,
+	return_date DATE,
+	late_fees NUMERIC
+);
+```
+
+The internal structure of a fact table facilitates fast access to data even for very large datasets.
+
+**Dimension tables**
+
+Dimension tables are often replicated across all nodes, which enhances query performance and ensures quick access to frequently referenced information.
+
+The following code example creates a **dimension table**:
+
+```
+CREATE DIMENSION TABLE books (
+	book_id INT,
+	title TEXT,
+	author TEXT,
+	genre TEXT,
+	publication_year INT
+);
+```
+
+In the previous example, the `books` table stores details about the publication and is ideal for joining with fact tables like `borrowedbooks` to analyze borrowing patterns or book popularity.
+
+#### [](#external-tables)External tables
+
+External tables allow users to access and query data stored outside the database, such as in Amazon S3, without loading it into Firebolt. This capability is particularly useful when working with large datasets stored externally that don’t require frequent access, enabling cost-efficient querying and avoiding data duplication. External tables generally have poorer performance compared to Firebolt managed tables because the data is not stored within Firebolt’s optimized infrastructure.
+
+#### [](#editing-and-deleting-tables)Editing and deleting tables
+
+After you create a table, you can modify your table ownership, delete it including all of its dependencies. Use the following SQL commands to manage your table:
+
+**Change table ownership**
+
+To change the ownership of a table, use the ALTER TABLE statement with the OWNER TO clause.
+
+The following command assigns a new owner to the `borrowedbooks` table:
+
+```
+ALTER TABLE borrowedbooks OWNER TO 'new_owner';
+```
+
+**Delete a managed table**
+
+Dropping a Firebolt managed table permanently deletes it along with all its data.
+
+The following code checks to see if the `borrowedbooks` table exists and then deletes it:
+
+```
+DROP TABLE IF EXISTS borrowedbooks;
+```
+
+**Delete a managed table that has dependencies**
+
+If the table that you want to delete has dependent objects such as views or aggregating indexes, you can use the `CASCADE` option to remove all dependencies together.
+
+The following code deletes the `borrowedbooks` table and all related objects:
+
+```
+DROP TABLE borrowedbooks CASCADE;
+```
+
+**Drop an external table**
+
+If you drop an external table, you only remove its definition from Firebolt. The actual data remains in the external source. The following code drops the `external_books` external table:
+
+```
+DROP TABLE external_books;
+```
+
+* * *
+
+#### [](#primary-indexes-in-tables)Primary indexes in tables
+
+Primary indexes optimize query performance by logically organizing data for efficient access based on key columns, using sparse indexing to minimize unnecessary scans during queries. This allows Firebolt’s engine to prune unnecessary data during queries, minimizing the amount of data read from disk, and accelerating query execution. By selecting columns frequently used in filters, the primary index enables fast, efficient data retrieval, which is crucial for large-scale, data-intensive applications. Properly configuring primary indexes ensures that Firebolt can maintain high performance, even with complex queries and large datasets.
+
+**How Firebolt uses a primary index to optimize performance**
+
+When new data is inserted into a table, Firebolt organizes it into tablets, which are logical partitions of the table. Each tablet holds a portion of the data, sorted according to the primary index. During query processing, Firebolt uses these indexes to eliminate blocks of rows not matching query predicate and scan only the necessary data, minimizing input and output operations, and optimizing performance.
+
+For updates, Firebolt follows a “delete-and-insert” approach: the original row is marked for deletion, and the updated row is inserted into a new tablet. Deleted rows are not removed immediately but are flagged and later cleaned up during maintenance tasks.
+
+##### [](#create-a-primary-index)Create a primary index
+
+A primary index can only be defined when creating a new table, so if you need to modify the index, you’ll have to create a new table. To define a primary index, use the `PRIMARY INDEX` clause to specify your columns, as shown in the following example:
+
+```
+CREATE TABLE borrowedbooks_pi(
+  transaction_id INT,
+  book_id INT,
+  member_id INT,
+  checkout_date DATE,
+  return_date DATE,
+  late_fees NUMERIC)
+PRIMARY INDEX (book_id, checkout_date);
+```
+
+In the previous example, [CREATE TABLE](/sql_reference/commands/data-definition/create-fact-dimension-table.html) creates a fact table by default, and the primary index acts as a composite index of both the `book_id` and `checkout_date` columns.
+
+You can also create a primary index on a dimension table as shown in the following code example:
+
+```
+CREATE dimension TABLE books_pi(
+  book_id INT,
+  title TEXT,
+  author TEXT,
+  genre TEXT,
+  publication_year INT
+)
+PRIMARY INDEX (book_id, title);
+```
+
+The primary index should include columns that are often used in queries that filter or aggregate data, including those that use `WHERE` and `GROUP BY` clauses, so that Firebolt can use these columns for efficient retrieval. Firebolt physically clusters the data in the table by the columns of the primary index. The primary index significantly improves query performance because it reduces the time spent scanning irrelevant rows and allows the query engine to retrieve only the necessary data.
+
+##### [](#primary-index-best-practices)Primary index best practices
+
+To optimize query performance and maximize indexing efficiency, use the following best practices for designing composite primary indexes:
+
+- **Column selection** – Carefully select which columns to include in a composite primary index based on query patterns, cardinality, and the specific use cases for your table. Adding unnecessary columns can negatively impact performance.
+- **Column order** – The order of columns in a composite primary index is critical. Place the most selective, or highest cardinality columns first in a composite primary index. Firebolt will search based on the order of columns in the primary index. High-cardinality columns, which have many distinct values, improve index efficiency by reducing the number of rows that need to be scanned during queries.
+
+#### [](#aggregating-indexes-in-tables)Aggregating indexes in tables
+
+Aggregating indexes precompute and store aggregation results from aggregation functions like `SUM`, `COUNT`, and `AVG`, as well as more complex calculations. When the underlying data is changed, Firebolt recalculates aggregate indexes automatically, so that they are always updated when you query them. Firebolt handles the following scenarios:
+
+- Inserts – When new rows are added to a table included in an aggregating index, Firebolt recalculates the value to include the new data.
+- Updates – If existing rows are updated, Firebolt adjusts the aggregation values to reflect the changes.
+- Deletions – When rows are deleted, the aggregating index is recalculated to remove the row from the precomputed aggregated values.
+
+When you utilize an aggregating index through a query, Firebolt utilizes the pre-calculated values instead of computing them in real-time. This reduces the computational burden at runtime and significantly speeds up query response times, especially for large datasets with high concurrency demands. Aggregating indexes are especially useful for frequently run queries that involve repeated aggregation operations, such as calculating totals, averages, or counts.
+
+Aggregating indexes do require additional storage, because the precomputed data needs to be maintained. In write-heavy environments, frequent updates, inserts, or deletes can lead to increased computational overhead as the indexes must be recalculated and kept up to date. This can result in higher compute costs. It’s important to consider the performance benefits of faster queries against the additional storage and processing costs, especially for frequently changing datasets.
+
+##### [](#create-an-aggregating-index)Create an aggregating index
+
+Aggregating indexes can be created at the time a new table is made or afterward. You can define it as needed based on query patterns and performance.
+
+The following code example shows how to create an aggregating index to precompute the number of transactions per borrower and their average late fee on the existing `borrowedbooks` table created in the previous **Fact tables** section in [Firebolt managed-tables](#firebolt-managed-tables):
+
+```
+CREATE AGGREGATING INDEX agg_borrower_statistics
+   ON borrowedbooks (
+  	borrower_id,
+  	COUNT(transaction_id),
+  	AVG(late_fee)
+   );
+```
+
+When Firebolt runs a query that accesses either `transaction_id` or `late_fee`, it retrieves the precomputed results from the aggregating index, rather than computing them.
+
+The following code example shows how to create an aggregating index to precompute the total late fees accumulated for each book:
+
+```
+CREATE AGGREGATING INDEX agg_total_late_fees
+   ON borrowedbooks (
+                   	book_id,
+                   	SUM(late_fee)
+               	);
+```
+
+Additionally, aggregating indexes integrate seamlessly with Firebolt’s partitioning strategies, further improving query performance by allowing the query engine to access only the relevant partitions. This reduces the amount of data scanned and processed, particularly when dealing with large, partitioned datasets. The combination of partition pruning and aggregate indexing helps achieve superior query performance in data-intensive environments, allowing for quicker insights and more efficient use of system resources.
+
+##### [](#best-practices-for-aggregate-indexes)Best practices for aggregate indexes
+
+To optimize query performance and manage resources effectively, follow these best practices for creating and maintaining aggregating indexes:
+
+- **Focus on frequently run queries** – Create aggregating indexes for queries that use frequent aggregations including `SUM`, `COUNT`, and `AVG` that are run repeatedly.
+- **Choose columns used in aggregations** – Select columns commonly used in GROUP BY and aggregation functions such as `borrower_id` or `book_id` from the examples in this section.
+- **Choose columns strategically** – Build indexes on columns that are frequently queried for aggregations such as `customer_id` or `order_id` from the examples in this section. Avoid creating multiple indexes with overlapping aggregations on the same columns to minimize unnecessary overhead and costs.
+- **Consider Data Freshness** – Ensure the performance gains of precomputed values outweigh the index maintenance costs for frequently changing data.
+
+#### [](#partitions-in-tables)Partitions in tables
+
+Firebolt’s table partitioning supports efficient data lifecycle management by organizing data based on specific criteria: date ranges, regions, product categories, or customer types. This helps streamline data retention, archiving, and access, ensuring optimal performance. Partitioning reduces the amount of data scanned during queries, improving speed, particularly when query patterns consistently filter data by columns like date or region. It also enables data pruning, skipping partitions that don’t match the query criteria, making tasks like vacuuming and archiving more efficient.
+
+##### [](#create-a-partition)Create a partition
+
+You can create a partition for a new table; however, it’s recommended to define the partition when creating a new table to ensure the data is organized from the start.
+
+The following code example **creates a new table** with a primary index, and partitions the table by month:
+
+```
+CREATE TABLE librarybooks (
+	transaction_id INT,
+	book_id INT,
+	borrower_id INT,
+	checkout_date DATE,
+	due_date DATE,
+	return_date DATE,
+	late_fee DECIMAL(10, 2)
+)
+PRIMARY INDEX transaction_id
+PARTITION BY DATE_TRUNC('month', checkout_date);
+```
+
+In the previous example, the new `librarybooks` table is partitioned by the month of `checkout_date`, so that Firebolt can prune irrelevant partitions and speed up queries for specific date ranges.
+
+You can **drop** an existing partition as shown in the following code example, which removes a partition for January 1, 2023:
+
+```
+ALTER TABLE borrowedbooks
+DROP PARTITION '2023-01-01';
+```
+
+#### [](#suggested-indexes-and-partitions)Suggested indexes and partitions
+
+If you understand your data and query patterns, you should select high-cardinality columns frequently used in `WHERE`, `JOIN`, or `GROUP BY` clauses to minimize the amount of data scanned and improve query efficiency.
+
+If you don’t know how to effectively select a primary index or partition your data, you can use Firebolt’s [RECOMMEND\_DDL](/sql_reference/commands/queries/recommend_ddl.html) tool to provide automated insights. `RECOMMEND_DDL` will make recommendations to optimize database performance by analyzing your query patterns and suggesting the most efficient configurations for primary indexes and partitioning. By examining historical query data, the tool identifies columns frequently used in filtering, grouping, or aggregating operations and recommends appropriate primary indexes and partition keys. These suggestions help reduce the amount of data scanned during queries, enabling faster execution and improved resource utilization.
+
+`RECOMMEND_DDL` is particularly useful in complex environments where query patterns evolve over time. By reviewing historical query data, Firebolt identifies columns that are frequently used in filtering or aggregation and recommends appropriate primary index and partitioning strategies.
+
+The following code example uses `RECOMMEND_DDL` to analyze query patterns on the books table, created in the \*\*Dimension tables \** section under [Firebolt managed-tables](#firebolt-managed-tables), based on queries run in the past week:
+
+```
+CALL recommend_ddl(
+  books,
+  (SELECT query_text FROM information_schema.engine_query_history WHERE query_start_ts > NOW() - INTERVAL '1 week')
+);
+```
+
+If the `books` table is frequently queried based on `genre` and `book_id`, Firebolt’s `RECOMMEND_DDL` command might provide the following example output:
+
+recommended\_partition\_key recommended\_primary\_index average\_pruning\_improvement analyzed\_queries DATE\_TRUNC(‘month’, borrow\_date) book\_id, borrower\_id 0.35 200
+
+The example output under `recommended_partition_key` suggests partitioning the `borrowedbooks` table by month based on the `borrow_date` column. The `recommended_primary_index` suggests creating a primary index on the `book_id` and `borrower_id` columns. An average pruning improvement of 0.35 indicates 35% less data will be scanned on average by applying these recommendations. The analyzed queries column shows that 200 queries were analyzed to generate these suggestions.
+
+### [](#additional-resources)Additional resources
+
+- [Working with tables](/Overview/indexes/using-indexes.html#firebolt-managed-tables) – An overview of how to create, manage, and optimize tables.
+- [Partitions in tables](/Overview/indexes/using-indexes.html#partitions-in-tables) – How to divide large tables into smaller partitions for optimal query efficiency and performance.
+- [RECOMMEND\_DDL](/sql_reference/commands/queries/recommend_ddl.html) – Information on syntax, parameters and examples of using Firebolt’s tool to automatically recommend optimal primary index and partition strategies.
+
+* * *
+
+- [Aggregating index](/Overview/indexes/aggregating-index.html)
+- [Primary index](/Overview/indexes/primary-index.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_organizations_accounts.md b/cmd/docs-scrapper/fireboltdocs/overview_organizations_accounts.md
new file mode 100644
index 0000000..7e2bc11
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_organizations_accounts.md
@@ -0,0 +1,228 @@
+# [](#organizations-and-accounts)Organizations and accounts
+
+A governance model can help manage cloud data warehouse resources by addressing challenges such as data security, cost management, resource isolation, and observability. For example, development, staging, and production environments often require isolation to prevent unintentional changes in development from affecting production or to restrict developers’ access to only their code and data. Similarly, departments may need isolated access to their resources while limiting access to others. Additionally, governance models can support consolidated billing while providing visibility into consumption by department or development environment.
+
+To address these requirements, Firebolt supports concepts of organizations and accounts. You can have different accounts within your organization and additionally benefit from consolidated billing, unified authentication, and efficient account management across all accounts.
+
+**Topics**
+
+- [Organizations and accounts](#organizations-and-accounts)
+  
+  - [Organizations](#organizations)
+  - [Accounts](#accounts)
+    
+    - [Users](#users)
+    - [Roles](#roles)
+      
+      - [Firebolt built-in roles](#firebolt-built-in-roles)
+        
+        - [Public role](#public-role)
+        - [System administrative role](#system-administrative-role)
+        - [Account administrative role](#account-administrative-role)
+        - [Organizational administrative role](#organizational-administrative-role)
+  - [Additional resources](#additional-resources)
+    
+    - [Billing](#billing)
+    - [Security](#security)
+    - [Available regions](#available-regions)
+
+The Firebolt object model is hierarchical and comes with strong containment properties in that parent objects can contain one or more child objects. Child objects are sole children of their parent objects and cannot be shared. Furthermore, there are two classes of objects: global and regional. Global objects are managed globally and can contain objects that are deployed and grouped regionally.
+
+The following Firebolt object model depicts an **organization** at the highest level, with **four** layers directly underneath it:
+
+![Firebolt's organizational structure has four layers](../../assets/images/manage-organization-org-structure.png)
+
+## [](#organizations)Organizations
+
+An organization is a fundamental object in Firebolt, providing a logical structure for managing accounts, billing, and authentication. When registering to Firebolt, the organization name you’ll provide is the same as the domain name you use in your email. Organization names are globally unique. No two organizations can have the same name, but organizations can contain multiple accounts. Each account can contain multiple objects including users, roles, databases, tables, views, and engines.
+
+In the Firebolt object model, an organization has the following levels:
+
+- **Login** - an email associated with a user that is used for identification. A single login can be associated with users across multiple accounts, but can only be associated with one user per account. For more information about logins, see [Manage logins](/Guides/managing-your-organization/managing-logins.html).
+- **Service account** - Use a service account to access Firebolt programmatically through an API. For more information about how to set up and manage a service account, see [Manage programmatic access](/Guides/managing-your-organization/service-accounts.html).
+- **Network policy** - Set a network security configuration that controls and restricts network access to specific resources within Firebolt based on IP addresses or IP ranges. See [Manage network policies](/Guides/security/network-policies.html).
+- **Account** - A group of resources which can include a database, an engine and several users with associated logins or service accounts and roles. See the following [Accounts](#accounts) section for high-level information about accounts and [Manage accounts](/Guides/managing-your-organization/managing-accounts.html) for more detailed information. Under account are the following levels:
+  
+  - **User** - An individual with specific permissions and roles that allow access to and interaction with the database and engine within an account. A user must be associated with a login (or service account), and with an account. See the following [Users](#users) section for more high-level information and [Manage users and roles](/Guides/managing-your-organization/managing-users.html) for more detailed information.
+  - **Role** - A set of permissions that defines a user’s access and capabilities, which can be assigned to one or more users to manage their privileges. See the following Roles section for more high-level information and Manage users and roles for more detailed information.
+  - **Database** - A logical collection of schemas and data objects, such as tables and views, that organizes and manages user data and metadata for querying and data processing. For more information about databases see [Create a Database](/Guides/getting-started/get-started-sql.html#create-a-database) in the [Get started using SQL](/Guides/getting-started/get-started-sql.html) guide. Under database are the following levels:
+    
+    - **Schema** - A collection of system views containing metadata about objects in the current database, including tables, columns, indexes, and other database components. For more information, see [Information Schema Views](/sql_reference/information-schema/). Under schema are the following levels:
+      
+      - **External table** - Tables that store metadata objects that reference files stored in an Amazon S3 bucket, rather than actual data. For more information, see [Work with external tables](/Guides/loading-data/working-with-external-tables.html).
+      - **Managed table** - A Firebolt-managed internal structured data object within a database that stores rows and columns of data. Firebolt’s managed tables have built-in optimizations for fast query processing times. For more information, see [Tables](/Overview/indexes/using-indexes.html#tables).
+      - **View** - A virtual table that represents the result of a stored query, including both user-defined views and [information schema views](/sql_reference/information-schema/), which provide metadata about database objects like tables, columns, and indexes.
+      - **Index** - A database structure that optimizes data retrieval by organizing specific columns, improving query performance and enabling efficient filtering, sorting, and joining of datasets. For more information about indexes, see [Data modeling](/Overview/indexes/using-indexes.html).
+  - **Engine** - A compute resource that processes queries and manages data operations and can be scaled independently and turned on or off as needed. For more information, see [Firebolt Engines](/Overview/engine-fundamentals.html).
+
+When you [register for the first time](/Guides/managing-your-organization/creating-an-organization.html), Firebolt sets up an organization for you. During registration, you’ll set up your first account, with one user. The first user that is added is the account administrator, as shown in the following diagram:
+
+![When you first register, Firebolt sets up an organization with one account and user that has account administrator privileges.](../../assets/images/manage-organization-first-registration.png)
+
+Then, you can add resources and users to this account. The following apply:
+
+- You can have multiple users within an account.
+- A user should be associated with either a login email for personal access or to a service account, for programmatic access.
+- You can have multiple accounts in an organization.
+- Each account name within an organization must be unique.
+- You can’t have one account in multiple AWS regions.
+- You can add resources such as databases and engines to the account.
+
+**Example**
+
+In the following example structure, an organization has an account set up for their marketing department and for managers in two different AWS regions:
+
+![An account can span only one AWS region.](../../assets/images/manage-organization-accounts-regions.png)
+
+In the previous diagram, the organization has three separate accounts:
+
+- A `marketing_account`, which has access to resources associated with marketing tasks, and two different users. The `user_1` user is associated with a `login_1` linked to an email account.
+- A `manager_account_region_1`, which has access to resources associated with a manager account in one AWS region, and one `user_3` that is associated with login\_1 linked to the same email account as `user_1` in marketing\_account.
+- A `manager_account_region_2`, which has access to resources in a different region than `manager_account_region_1`, and one user also associated with `login_1`.
+
+The manager of the marketing department, `user_1`, is associated with `login_1`, which is associated with both the marketing account and both manager accounts. These accounts have access to a different set of resources and permissions. The users `user_1`, `user_3`, and `user_4` are all the same person because they have the same login and email. The manager also manages projects across AWS regions and must access those resources in a **different** account. Another employee, `user_2`, works in the marketing department and has access to only the marketing resources designated to `marketing_account` using permissions defined by his role.
+
+## [](#accounts)Accounts
+
+An account in Firebolt is an object within an organization that encapsulates resources for storing, querying, and managing data. Accounts provide:
+
+- **Access control:** Firebolt implements role-based access control (RBAC). Every object in the Firebolt object model is a securable and it comes with a set of privileges. Privileges allow administrators to control functionality Firebolt users can exercise when logged in.
+- **Data modeling:** Using objects including databases, tables, views, and indexes, developers and architects can design their data warehouses and describe various business entities without compromising to deliver on ever-demanding performance needs.
+- **Cost control:** With engines, system administrators can deploy engines that fit the need while achieving desired price-performance characteristics. Engines can scale vertically up and down, and horizontally out and in to meet business needs while allowing granular cost control.
+- **Workload management:** Firebolt offers full workload isolation for computations, data and metadata. Firebolt users can deploy separate engines to support heterogeneous workloads, while having access to the same data. Firebolt supports a variety of workloads, including data-intensive applications requiring instant data access, complex business-critical dashboards needing timely updates, and intricate Extract-Load-Transform (ELT) processes for data ingestion.
+
+Each account in Firebolt exists in a single AWS region, and can have engines and databases associated with it. Initially after registration, an account contains no resources, and only one user that has an account administrator role. An account can contain many users, as shown in the following diagram:
+
+![In Firebolt, an account can contain many users, an engine and database.](../../assets/images/manage-organization-accounts-contents.png)
+
+### [](#users)Users
+
+A user must be associated with a role, which grants them permission to access resources. These users can be associated with different roles within a single account. Each user must be associated with either a login for personal access or a service account for programmatic access, as shown in the following diagram:
+
+![A user must be associated with either a login or a service account.](../../assets/images/user_login_service-account.png)
+
+A login consists of an **email address**. This login uniquely identifies the user.
+
+**Example**
+
+In the following example account structure, `user_1` has a manager role that grants access to engines and databases associated with human resources tasks, as well as a marketing role that grants them access to everything that their employee has access to. A marketing employee, `user_2`, has read-only access to the tables in the database in `marketing_account`, but they cannot insert new entries or delete entries from a table.
+
+![A user can have multiple roles in an account.](../../assets/images/manage-organization-marketing-accounts-example.png)
+
+### [](#roles)Roles
+
+In Firebolt, each user is associated with either a **login**, which is an email address, or a **service account**. Each user must also have a role, as shown in the following diagram:
+
+![A user must be associated with either a login or a service account.](../../assets/images/user_login_service-account.png)
+
+The role grants the user permission to access resources inside the account that they are associated with. A user can have several roles associated with them at the same time. Firebolt has built-in roles with defined permissions. You can also define a [custom role](/Overview/Security/Role-Based%20Access%20Control/role-management/custom-roles.html) that grants permissions specific to your use case.
+
+#### [](#firebolt-built-in-roles)Firebolt built-in roles
+
+Firebolt has the following built-in roles with associated permissions for objects including databases, engines, users, network policies, and accounts:
+
+- [Organizations and accounts](#organizations-and-accounts)
+  
+  - [Organizations](#organizations)
+  - [Accounts](#accounts)
+    
+    - [Users](#users)
+    - [Roles](#roles)
+      
+      - [Firebolt built-in roles](#firebolt-built-in-roles)
+        
+        - [Public role](#public-role)
+        - [System administrative role](#system-administrative-role)
+        - [Account administrative role](#account-administrative-role)
+        - [Organizational administrative role](#organizational-administrative-role)
+  - [Additional resources](#additional-resources)
+    
+    - [Billing](#billing)
+    - [Security](#security)
+    - [Available regions](#available-regions)
+
+##### [](#public-role)Public role
+
+A public role is associated with a user that can:
+
+- Use a database.
+- Use a public schema.
+- Create a public table.
+- Create a public view.
+- Create a public index.
+- Create a public external table.
+
+A public role has the **lowest** access privileges of all roles in Firebolt, as shown in the following diagram:
+
+![The public role has permission for schema and its underlying components.](../../assets/images/manage-organization-public-role.png)
+
+##### [](#system-administrative-role)System administrative role
+
+A system administrative role has privileges to manage databases, engines, schemas, and objects within those schemas. A system administrator can:
+
+- Create a database in an account.
+- Create an engine in an account.
+- Monitor engine use.
+- Has all privileges for:
+  
+  - Any database and its properties.
+  - Any engine and its properties.
+  - Any schema.
+  - Any view.
+  - Any external table.
+
+The previous system administrative privileges are shown in the following diagram:
+
+![The system admin role has privileges in database, engine, and schema plus children.](../../assets/images/manage-organization-sys-admin-role.png)
+
+##### [](#account-administrative-role)Account administrative role
+
+An account administrative role includes all privileges associated with system administrators and can also manage accounts and users. An account administrator has:
+
+- All system administrator privileges.
+- All privileges for an account.
+- The ability to meter and monitor account use.
+- The ability to cancel a query on any engine in an account.
+
+The previous account administrative privileges are shown in the following diagram:
+
+![An account admin has privileges over the account and all its children.](../../assets/images/manage-organization-account-admin-role.png)
+
+##### [](#organizational-administrative-role)Organizational administrative role
+
+An organizational administrative role has all privileges associated with system administrators and can also manage accounts and users. An organizational administrator has:
+
+- All privileges for an organization.
+- All privileges for any account in an organization.
+- All privileges for any login in an organization.
+- All privileges for any service account in an organization.
+- All privileges for any network policies in an organization.
+- The ability to monitor any usage in the organization.
+- The ability to set any organization-related property.
+
+An organizational administrative role has the **highest** access privileges of all roles in Firebolt, as shown in the following diagram:
+
+![An org admin has privileges over the entire organization and all of its children.](../../assets/images/manage-organization-org-admin-role.png)
+
+- **Global authentication method:** Firebolt handles user authentication and access control at the organization level. A login (represented by an email) is created for each user accessing Firebolt.
+- **Programmatic access:** [Service accounts](/Guides/managing-your-organization/service-accounts.html) enable programmatic access to Firebolt.
+- **Network policy enforcement:** [Network policies](/Guides/security/network-policies.html) provide fine-grain control of IP ranges that are allowed or blocked from accessing an organization.
+
+## [](#additional-resources)Additional resources
+
+### [](#billing)Billing
+
+Firebolt provides billing at the organization level, but gives you billing observability at both organization and account levels. This allows:
+
+- **Organization-level governance:** Monitor and analyze the overall billing for all accounts to gain insights into the organization’s cost distribution and resource utilization at the organization level.
+- **Account-level observability:** Delve into detailed billing information specific to each account, allowing you to track individual accounts’ usage, costs, storage, and compute consumption patterns.
+
+Firebolt bills are based on the consumption of resources within each account in your organization. This includes the total amount of data stored and engine usage. Learn how to [manage billing](/Guides/managing-your-organization/billing.html).
+
+### [](#security)Security
+
+Learn about authentication methods, role-based access control, network policies, and object ownership in [Configure security](/Guides/security/).
+
+### [](#available-regions)Available regions
+
+View the [AWS regions](/Reference/available-regions.html) where you can use Firebolt.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_queries.md b/cmd/docs-scrapper/fireboltdocs/overview_queries.md
new file mode 100644
index 0000000..7572c43
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_queries.md
@@ -0,0 +1,25 @@
+# [](#queries)Queries
+
+Firebolt is designed to run SQL queries efficiently, using advanced optimizations at both the query and workload levels. This section provides an overview of how Firebolt processes queries, the optimizations applied during query handling, and the tools available for monitoring and improving performance. For guidance on how to run queries and interact with data in Firebolt, see [Query data](/Guides/query-data/).
+
+## [](#optimizations-on-a-per-query-basis)Optimizations on a per-query basis
+
+Firebolt applies specific optimizations at the individual query level to ensure efficient performance, even for complex queries. These optimizations take effect immediately when you create an account and start your first engine.
+
+- [Spilling intermediate query state](/Overview/queries/understand-spilling.html) to the local SSD cache. This allows processing queries whose working set exceeds main memory.
+- Firebolt has advanced support for correlated subqueries. These are automatically decorrelated by our query planner to maximize performance.
+
+## [](#workload-level-optimizations)Workload-level optimizations
+
+Homogeneous workloads with repeated query structures can benefit significantly from workload-level optimizations. Examples for such workloads are customer-facing, high-concurrency data apps, or internal BI workloads. For these workloads, Firebolt leverages multiple different optimizations.
+
+- [Reusing query sub-results and result caching](/Overview/queries/understand-query-performance-subresult.html) to reduce redundant calculations across queries.
+- [History-based query optimization](/Overview/queries/understand-query-performance-hbs.html), which leverages past query patterns to improve query plans for new queries.
+
+## [](#query-telemetry-and-monitoring)Query telemetry and monitoring
+
+Firebolt provides the following tools to monitor and analyze query performance:
+
+- **`EXPLAIN` command**: View the query plan to understand how Firebolt executes your query.
+- **Telemetry data**: Analyze metrics such as runtime, memory usage, and data processed.
+- **Query history**: Use views like `information_schema.engine_query_history` to monitor query performance details over time.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_queries_understand_query_performance_hbs.md b/cmd/docs-scrapper/fireboltdocs/overview_queries_understand_query_performance_hbs.md
new file mode 100644
index 0000000..02a9182
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_queries_understand_query_performance_hbs.md
@@ -0,0 +1,58 @@
+# [](#understanding-history-based-optimization)Understanding history-based optimization
+
+Firebolt’s query plans adapt and evolve with your workload over time. Through a feedback loop, Firebolt’s query optimizer learns from previous queries and progressively generates more efficient plans, steadily improving query performance towards optimal runtimes.
+
+**Topics**
+
+- [Scope of history-based optimization](#scope-of-history-based-optimization) – Learn which processes utilize history-based optimization.
+- [How it works](#how-it-works) – Learn how telemetry data and query history help optimize future query plans and performance.
+  
+  - [How recording query history works](#how-recording-query-history-works) – Learn what is recorded in query history and how information is protected.
+  - [How planning queries based on history work](#how-planning-queries-based-on-history-work) – Learn how history-based snapshots are continually updated to improve query performance across all engines in the same database and account.
+- [Observability](#observability) – Learn how to check if history-based optimization is used in your query plan.
+
+## [](#scope-of-history-based-optimization)Scope of history-based optimization
+
+Firebolt’s history-based optimization techniques include the following:
+
+- **Join ordering** — The sequence in which tables are joined during query processing, especially in complex queries with multiple tables, can significantly affect query performance. Firebolt uses query statistics and historical patterns to determine the most efficient join order that optimizes both run times and resource utilization.
+- **Aggregating index selection** — Firebolt analyzes historical query patterns to identify the most frequently used aggregating indexes, which store pre-computed aggregates such as `SUM`, `AVG`, and `COUNT`. It then suggests indexes to reduce computational load during query processing.
+- **Semi-join and anti-join planning** — Firebolt’s query planner selects the most efficient way to run semi-joins, which return matching rows, and anti-joins, which return rows with no match in another table.
+- **Broadcast and shuffle strategies for multi-node engines** — Firebolt uses a broadcast strategy for small datasets that can be efficiently distributed across all nodes to minimize data movement, and a shuffle strategy when both datasets are large. Implementing these strategies can greatly improve query performance for distributed joins by optimizing how data is distributed and processed across multiple nodes.
+
+## [](#how-it-works)How it works
+
+When you run a query, Firebolt’s query optimizer constructs a query plan to run the process efficiently. After running the query, the collected telemetry is fed back into Firebolt’s history snapshot. When you run the next query, the query optimizer accesses the telemetry that was collected in that history snapshot and extracts from it statistical information. Consequently, previously run queries aid the query optimizer in finding better query plans for subsequent queries and thereby improve performance.
+
+![Telemetry data flows back from the runtime into the query optimizer where the next run is planned.](../../assets/images/history-based-optimization.png)
+
+### [](#how-recording-query-history-works)How recording query history works
+
+Firebolt’s query optimizer improves runtime performance by automatically collecting and analyzing telemetry data from past queries, without requiring user intervention.
+
+Only the query plan and its related telemetry data are stored in the history snapshot. This telemetry includes metrics for each query operator, such as the number of rows and bytes processed, time elapsed, and memory usage. The query plan itself retains the original query string, meaning if the query contains personally identifiable information (PII), it will appear in the snapshot. However, the query result is not used in optimization, so PII in the result is not stored. While PII in the query string is stored, the history snapshot is securely protected. Access is restricted to engines on the same database and account, as well as to authorized Firebolt personnel only.
+
+### [](#how-planning-queries-based-on-history-work)How planning queries based on history work
+
+When you submit a query, Firebolt analyzes its recorded history to predict how different query plans will perform, and chooses one that should deliver the best performance. This query history is released to the query optimizer every `10` minutes in the form of a history-based statistics (HBS) snapshot.
+
+Each engine has a dedicated HBS component that is always active, continuously generating snapshots for the engine to reference during query planning. These snapshots are saved and shared among all engines running on the same database within the same account. Consequently, an engine can benefit from the query history from another engine, improving performance across all engines without needing to restart the analysis process. After engine restart, the engine retrieves the latest HBS snapshot.
+
+## [](#observability)Observability
+
+The Firebolt query optimizer uses HBS in the scenarios listed in the scope section above. To see whether history-based statistics were used when planning your query, use `EXPLAIN` with the `statistics` option, as follows:
+
+```
+EXPLAIN (statistics)
+select ...  -- your query goes here
+```
+
+The `EXPLAIN` option `statistics` annotates all nodes of the query plan with the sources of statistics used in its cost estimation. An example of the `EXPLAIN (statistics)` output below shows `source: history`, and we know that the estimates were made based on history.
+
+```plain
+[Logical Profile]: [source: history]
+```
+
+For more information about output from `EXPLAIN (statistics)`, including various possible values that the source field can take, see [Explain: Example with statistics](../../sql_reference/commands/queries/explain.html#example-with-statistics).
+
+The `EXPLAIN(statistics)` output will not show `source:history` during the first run of an alternate query plan if the optimizer finds that the initial query plan was not optimal. This absence occurs because the alternative plan has not yet gathered telemetry data during its initial run. In the next execution of the same query, the optimizer understands that it should choose an alternative plan to avoid the slow execution. This means, that history-based statistics are in effect, but we may not see `history` shown in sources of the `EXPLAIN (statistics)` output for the new run. It could be that for the alternative plan we have not collected its execution telemetry yet.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_queries_understand_query_performance_subresult.md b/cmd/docs-scrapper/fireboltdocs/overview_queries_understand_query_performance_subresult.md
new file mode 100644
index 0000000..0a116ad
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_queries_understand_query_performance_subresult.md
@@ -0,0 +1,81 @@
+# [](#subresult-reuse-and-result-caching)Subresult reuse and result caching
+
+*Learn about subresult reuse in Firebolt in more detail in our blog post [Caching &amp; Reuse of Subresults across Queries](https://www.firebolt.io/blog/caching-reuse-of-subresults-across-queries).*
+
+Workloads using repetitive query patterns can benefit tremendously from reuse and caching. Firebolt can cache subresults from various operators within the query plan, including hash tables from hash-joins.
+
+**Topics**
+
+- [How firebolt caches subresults](#how-firebolt-caches-subresults) – An overview about how and when Firebolt caches subresults.
+- [Example](#example) – How Firebolt’s subresult cashing and hash table reuse improve query performance for repetitive and partially similar queries.
+- [Recognizing subresult reuse in query telemetry](#recognizing-subresult-reuse-in-query-telemetry) – How to view results from `EXPLAIN (ANALYZE)` to check for subresult reuse.
+- [Limitations](#limitations) – Understand the situations where subresults cannot be cached or used.
+- [Disabling subresult reuse](#disabling-subresult-reuse) – How to turn off subresult caching for benchmarking or other tests.
+
+## [](#how-firebolt-caches-subresults)How Firebolt caches subresults
+
+Subresults are placed in an in-memory FireCache, which can use up to 20% of the available RAM. If a sub-plan is reused in a different query, Firebolt’s caching system detects it and can retrieve cached subresults, even if the rest of the query differs. Firebolt uses the following guidelines to determine which subresults to cache:
+
+- Firebolt’s optimizer may insert a `MaybeCache` operator above any node in the query plan, which may cache a subresult if it isn’t too large. The `MaybeCache` operator may later retrieve and reuse the cached subresult if the same subplan, with the same underlying data, is evaluated again. Currently, the optimizer places a `MaybeCache` operator in the following places:
+  
+  - At the top of the query plan to cache the full result.
+  - At nodes where “sideways information passing” occurs, optimizing joins where the probe-side has an indexed key.
+  
+  The `MaybeCache` operator is versatile, and it can be placed anywhere in the plan.
+- Firebolt stores subresult hash-tables created for `Join` operators in the FireCache, provided they are not too large. These hash tables are costly to compute, so reusing them when similar consecutive queries run offers significant performance advantages.
+
+Subresult reuse in Firebolt is fully transactional. When any changes occur in a base table (such as through an `INSERT`, `UPDATE`, or `DELETE`), outdated cache entries are no longer used.
+
+### [](#example)Example
+
+The following query, based on the [TPC-H benchmark](https://www.tpc.org/tpch/) schema, calculates the total order price and the number of orders for each nation by joining the `orders`, `customer`, and `nation` tables:
+
+```SQL
+SELECT n_name as nation, SUM(o_totalprice), COUNT(*)
+  FROM orders, customer, nation
+ WHERE o_custkey = c_custkey AND c_nationkey = n_nationkey
+ GROUP BY ALL;
+```
+
+The simplified plan for this example query would look like the following:
+
+![A query plan using subresult reuse.](../../assets/images/subresult_reuse.png)
+
+In this example, a `MaybeCache` operator positioned at the top of the plan caches the subresult from the first run into the FireCache. Additionally, both `Join` operators store their respective hash tables in the cache. On a subsequent run of exactly the same query (over unchanged data), the `MaybeCache` operator fetches the subresult from the cache, allowing the entire evaluation to be skipped. As a result, query latency is reduced to mere milliseconds. In this example, it leads to a speed improvement of over 100x on a single node, medium engine running TPC-H with scale factor of 100.
+
+If the `WHERE` condition is changed to add `... AND o_orderdate >= '1998-01-01'::Date ...`, the subresult cached by the `MaybeCache` operator cannot be used because the query plan below it has changed. However, the subplan below the upper `Join` remains unchanged, allowing the previously cached hash table to be reused in that `JOIN` operator. This eliminates the need to re-evaluate the subplan and rebuild the hash table. This results in more than 5x speed improvement on subsequent queries, even when each query has a different date restriction.
+
+### [](#recognizing-subresult-reuse-in-query-telemetry)Recognizing subresult reuse in query telemetry
+
+Firebolt transparently leverages subresult reuse. If you want to see whether subresult reuse helped to speed up your query, look for `Nothing was executed` in the [EXPLAIN (ANALYZE)](/sql_reference/commands/queries/explain.html) output. This shows that an operator was skipped because a higher level operator retrieved the subresult from the FireCache. For example, in the following `EXPLAIN (ANALYZE)` output, the `MaybeCache` operator retrieved the result from the cache, bypassing the need to run the entire query:
+
+```
+[0] [MaybeCache]
+|   [RowType]: date not null, text not null, bigint not null, double precision null
+|   [Execution Metrics]: output cardinality = 10000, thread time = 0ms, cpu time = 0ms
+ \_[1] [Projection] ref_2, ref_1, ref_0, ref_3
+   |   [RowType]: date not null, text not null, bigint not null, double precision null
+   |   [Execution Metrics]: Optimized out
+    \_[2] [SortMerge] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last] Limit: [10000]
+      |   [RowType]: bigint not null, text not null, date not null, double precision null
+      |   [Execution Metrics]: Nothing was executed
+[...]
+```
+
+### [](#limitations)Limitations
+
+Firebolt supports subresult caching for as many queries as possible. The following are specific limitations where subresult caching cannot be applied:
+
+- **Result cache size** – The result cache is limited 1 MB per result to ensure that large results do not evict smaller cached subresults needed for other queries.
+- **Nondeterministic functions** – Queries that use nondeterministic functions such as `RANDOM` cannot cache subresults. If an operator in the query plan depends directly or indirectly on the output of a nondeterministic function, caching is disabled.
+- **External table scans** – Results from external table scans cannot be cached. These tables rely on external data sources, which may change independently of Firebolt’s caching mechanism.
+- **Non-equality joins** – Cross joins and joins that use a join condition that’s not an equality (for example, joining on `left_side.colum1 < right_side.column2`) cannot use subresult caching directly. The result cache can still be used for queries using such joins.
+
+### [](#disabling-subresult-reuse)Disabling subresult reuse
+
+Firebolt exposes [system settings](/Reference/system-settings.html) that allow turning off subresult caching at a per-query basis:
+
+- Setting `enable_result_cache` to `FALSE` ensures that full query results aren’t retrieved from cache, while still allowing for semantic cross-query subresult reuse.
+- Setting `enable_subresult_cache` to `FALSE` disables Firebolt’s entire subresult caching layer.
+
+For most benchmarking scenarios, disable the result cache. This approach affects only the final result caching while preserving the benefits of cross-query subresult optimizations.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_queries_understand_spilling.md b/cmd/docs-scrapper/fireboltdocs/overview_queries_understand_spilling.md
new file mode 100644
index 0000000..1da30b6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_queries_understand_spilling.md
@@ -0,0 +1,47 @@
+# [](#understand-spilling)Understand spilling
+
+Most query execution operators in Firebolt can react dynamically to memory pressure and take measures to prevent query failure. While on a technical level there are two different mechanisms at play, they share the same goal: allowing an engine to successfully finish the vast majority of queries that would otherwise fail with an “Out of memory” error. Both mechanisms (called “spilling” and “flushing”) are applied automatically when necessary without any user intervention.
+
+Firebolt implements spilling for aggregations and joins, and we will explore it in more detail in the sections below.
+
+## [](#how-spilling-works)How spilling works
+
+The fundamental idea of spilling is to write intermediate state to disk in a partitioned way when the data set is too big to process entirely in memory, and then process the partitions in memory one by one. The following sketch illustrates this:
+
+![If a working set exceeds memory, it can be processed if split into four partitions.](../../assets/images/spilling.png)
+
+Spilling-enabled operators continuously monitor how much memory remains available for use on each node of the engine. When they detect that the available amount is likely to be insufficient to complete the query, they temporarily stop accepting new data and start spilling part or all of the state that they have built up to the local SSD cache. This frees up memory to continue processing input data. If the available memory once again falls below the amount required to finish the operation, the operator spills additional parts of its state. Once the operator has read all of its input data, it needs to read the spilled data back from the SSD cache to produce the correct output. Because we already know that we do not have enough memory to process everything in memory, we read the spilled data *partition by partition*. These partitions are designed to be processed individually, without needing to refer to any other partitions to produce the operator’s result for a given partition. By using 256 partitions, we can process up to 200 times more data with spilling than in memory.
+
+Note that spilling only kicks in when absolutely necessarily. This makes sure that when the working set of a query fits fully into main-memory, it is executed as efficiently as possible.
+
+## [](#implications-of-spilling)Implications of spilling
+
+When an operator spills, it has to write a significant amount of data to the SSD cache and later read it back. This comes at a performance cost. If the engine has only slightly too little memory, using a bigger engine – whether by scaling up or by scaling out – can avoid the need for spilling and result in significantly reduced latency.
+
+## [](#observability)Observability
+
+If a query made use of spilling, you will see a non-zero value in the `spilled_bytes` column of [information\_schema.engine\_query\_history](/sql_reference/information-schema/engine-query-history.html) describing how many bytes were spilled to the SSD cache in total by all spilling operators in the query. Additionally, you can monitor the amount of spilled data on the SSD cache at any particular time in the `spilled_bytes` column of [information\_schema.engine\_metrics\_history](/sql_reference/information-schema/engine-metrics-history.html) or in the “engine monitoring” section of the Firebolt Web Interface.
+
+## [](#example)Example
+
+You can easily test spilling for yourself with the following query on an engine with a single node of type “small”:
+
+```
+SELECT min(x), max(x), x FROM generate_series(1, 1000000000) r(x) GROUP BY x;
+```
+
+This aggregation uses one billion groups, and the aggregate state is too large to process in memory on a single small node. As a result, the engine spills some data to disk (around 8 GB) before merging it again. You can observe how the `spilled_bytes` metric in `information_schema.engine_metrics_history` increases while the aggregation processes and spills input, and then starts decreasing again as spilled data is merged and deleted.
+
+## [](#limitations)Limitations
+
+Not all queries can benefit from spilling. Spilling is not implemented for the `ORDER BY` operator and for [window functions](/sql_reference/functions-reference/window/). Additionally, aggregations where the size of a single key’s state exceeds the available memory, such as a `count(distinct)` without a `GROUP BY` clause on a column with a huge amount of distinct values, cannot currently spill. Such queries could still fail with an out-of-memory error if spilling in other queries or operators cannot free up enough memory for these non-spilling-enabled operators.
+
+Spilling is also limited by the available SSD cache. Once the cache is full and no non-essential data remains to be evicted from cache, spilling cannot proceed, and the query will fail. Of course, any leftover spilled files will be cleaned up in such cases, ensuring that the SSD cache capacity is made available again for caching or spilled data from other queries.
+
+## [](#technical-details-spilling-vs-flushing)Technical details: spilling vs. flushing
+
+Many operators, such as filters or projections (function evaluations), do not keep significant amounts of data in memory at any given time.
+
+Some operators have an over-pressure relief valve and can *flush* excess data. This applies to both insertion operators, which can reduce the amount of tablet merging applied during insert and thereby reduce their memory requirements, as well as partial aggregations in a distributed aggregation plan, which can flush their partially aggregated data to the merge stage early to continue the aggregation there. Because distributed aggregations are partitioned, this distributes the excess load over the cluster, and additionally reduces total memory usage because the merge stage eliminates any duplication found in the different nodes’ inputs.
+
+Other operators do not have this ability, and must *spill* data to the SSD cache to avoid going out of memory and later process the data piece by piece to produce the result. This affects all operators that need to fully process the input data before they can start producing output. Firebolt implements this for the joins as well as the merge stage of aggregations.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control.md
new file mode 100644
index 0000000..940964c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control.md
@@ -0,0 +1,60 @@
+# [](#role-based-access-control-rbac)Role-Based Access Control (RBAC)
+
+Firebolt uses Role-Based Access Control (RBAC) to manage permissions and ensure that users and roles have only the necessary access to perform operations within the system. RBAC follows the [principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege), where access is restricted to the minimum required for tasks.
+
+Permissions in Firebolt are managed through roles, which control access to databases, schemas, tables, engines, and other objects. Permissions propagate from higher-level objects to their related objects, simplifying access management.
+
+With RBAC you can:
+
+- Assign roles to users and other roles to streamline permissions.
+- Grant or revoke access at **global**, **regional**, or **object-specific** levels.
+- Control operations across your Firebolt environment, such as managing data, creating resources, or executing queries.
+
+## [](#firebolts-hierarchical-object-model-and-rbac-structure)Firebolt’s hierarchical object model and RBAC structure
+
+Firebolt uses an object model to organize resources in a way that complements how organizations manage their data warehouses. This model enforces a one-to-many structure where:
+
+- An object can encompass multiple related objects beneath it.
+- Each related object is associated with a single higher-level object and cannot be shared across multiple higher-level objects.
+- Permissions flow from higher-level objects to related objects. For example, granting a role usage on a database also provides access to all schemas and tables within that database.
+
+Objects in the Firebolt object model are securable and come with a set of permissions, enabling administrators to control what identities they have access to when accessing their Firebolt cluster.
+
+For more information about the organizational and account structure in Firebolt’s object model , see [Organization and accounts](/Overview/organizations-accounts.html).
+
+## [](#key-object-types)Key object types
+
+Firebolt divides objects into **global** and **regional** types, depending on their scope and management level.
+
+- **Global objects**: Managed globally at the [organization](/Overview/organizations-accounts.html#organizations) level, they can contain objects that are deployed and grouped regionally, including the following:
+  
+  - Network Policies
+  - Logins
+  - Service Accounts
+  - Accounts
+- **Regional objects**: Tied to specific regions grouped under an [account](/Overview/organizations-accounts.html#accounts), they can include the following:
+  
+  - Users
+  - Roles
+  - Databases
+    
+    - Schemas
+      
+      - External Tables
+      - Managed Tables
+      - Views
+      - Indexes
+  - Engines
+
+Firebolt provides the [organization\_admin](/Overview/organizations-accounts.html#organizational-administrative-role) role to manage organizational resources. While granular RBAC is currently only available at the account level, Firebolt plans to include making RBAC available at the organizational level in a future release.
+
+For more information about Firebolt’s RBAC model &amp; how to administer your Firebolt cluster, access the sections below:
+
+* * *
+
+- [Database permissions](/Overview/Security/Role-Based%20Access%20Control/database-permissions/)
+- [Account Permissions](/Overview/Security/Role-Based%20Access%20Control/account-permissions.html)
+- [Engine Permissions](/Overview/Security/Role-Based%20Access%20Control/engine-permissions.html)
+- [Ownership](/Overview/Security/Role-Based%20Access%20Control/ownership.html)
+- [Check Assigned Privileges](/Overview/Security/Role-Based%20Access%20Control/check-privileges.html)
+- [Role Management](/Overview/Security/Role-Based%20Access%20Control/role-management/)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_account_permissions.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_account_permissions.md
new file mode 100644
index 0000000..b2d4194
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_account_permissions.md
@@ -0,0 +1,105 @@
+# [](#account-permissions)Account permissions
+
+Accounts represent the physical instance of your data warehouse in Firebolt and are created in Firebolt-supported regions. All objects within an account—such as databases, engines, roles, and users—are scoped to that specific account.
+
+Privilege Description GRANT Syntax REVOKE Syntax CREATE DATABASE Allows creating new databases in an account. `GRANT CREATE DATABASE ON ACCOUNT <account_name> TO <role>;` `REVOKE CREATE DATABASE ON ACCOUNT <account_name> FROM <role>;` USAGE ANY DATABASE Allows using all current and future databases in an account. `GRANT USAGE ANY DATABASE ON ACCOUNT <account_name> TO <role>;` `REVOKE USAGE ANY DATABASE ON ACCOUNT <account_name> FROM <role>;` MODIFY ANY DATABASE Allows editing all current and future databases in an account. `GRANT MODIFY ANY DATABASE ON ACCOUNT <account_name> TO <role>;` `REVOKE MODIFY ANY DATABASE ON ACCOUNT <account_name> FROM <role>;` [CREATE ENGINE](/sql_reference/commands/engines/create-engine.html) Allows creating new engines in an account. `GRANT CREATE ENGINE ON ACCOUNT <account_name> TO <role>;` `REVOKE CREATE ENGINE ON ACCOUNT <account_name> FROM <role>;` USAGE ANY ENGINE Allows using all current and future engines in an account. `GRANT USAGE ANY ENGINE ON ACCOUNT <account_name> TO <role>;` `REVOKE USAGE ANY ENGINE ON ACCOUNT <account_name> FROM <role>;` OPERATE ANY ENGINE Allows starting and stopping all current and future engines in the account. `GRANT OPERATE ANY ENGINE ON ACCOUNT <account_name> TO <role>;` `REVOKE OPERATE ANY ENGINE ON ACCOUNT <account_name> FROM <role>;` MODIFY ANY ENGINE Allows editing all current and future engines in the account. `GRANT MODIFY ANY ENGINE ON ACCOUNT <account_name> TO <role>;` `REVOKE MODIFY ANY ENGINE ON ACCOUNT <account_name> FROM <role>;` [CREATE ROLE](/sql_reference/commands/access-control/create-role.html) Allows creating new roles in the account. `GRANT CREATE ROLE ON ACCOUNT <account_name> TO <role>;` `REVOKE CREATE ROLE ON ACCOUNT <account_name> FROM <role>;` MODIFY ANY ROLE Allows editing all current and future roles in the account. `GRANT MODIFY ANY ROLE ON ACCOUNT <account_name> TO <role>;` `REVOKE MODIFY ANY ROLE ON ACCOUNT <account_name> FROM <role>;` [CREATE USER](/sql_reference/commands/access-control/create-user.html) Allows creating new users in the account. `GRANT CREATE USER ON ACCOUNT <account_name> TO <role>;` `REVOKE CREATE USER ON ACCOUNT <account_name> FROM <role>;` MODIFY ANY USER Allows editing all current and future users in the account. `GRANT MODIFY ANY USER ON ACCOUNT <account_name> TO <role>;` `REVOKE MODIFY ANY USER ON ACCOUNT <account_name> FROM <role>;` MONITOR \[ANY USAGE] Enables the tracking of engine queries through the `engine_running_queries` view for active queries and the `engine_query_history` view for past queries in `information_schema`. `GRANT MONITOR ANY USAGE ON ACCOUNT <account_name> TO <role>;` `REVOKE MONITOR ANY USAGE ON ACCOUNT <account_name> FROM <role>;` ALL \[PRIVILEGES] Grants all direct privileges for a specified account to a specified role. `GRANT ALL ON ACCOUNT <account_name> TO <role>;` `REVOKE ALL ON ACCOUNT <account_name> FROM <role>;`
+
+Revoking a privilege removes it from a role but does not explicitly deny the privilege. If the privilege was not previously granted, revoking it has no effect.
+
+## [](#examples-of-granting-account-level-permissions)Examples of granting account-level permissions
+
+### [](#create-database-permission)CREATE DATABASE permission
+
+The following code example [grants](/sql_reference/commands/access-control/grant.html) the role `developer_role` permission to create new databases within the `account_name`:
+
+```
+GRANT CREATE DATABASE ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#usage-any-database-permission)USAGE ANY DATABASE permission
+
+The following code example gives permission to the role `developer_role` to access all current and future databases within the `account_name`:
+
+```
+GRANT USAGE ANY DATABASE ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#modify-any-database-permission)MODIFY ANY DATABASE permission
+
+The following code example grants the role `developer_role` permission to modify or delete all current and future databases within the `account_name`:
+
+```
+GRANT MODIFY ANY DATABASE ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#create-engine-permission)[CREATE ENGINE](/sql_reference/commands/engines/create-engine.html) permission
+
+The following code example gives the role `developer_role` permission to create new engines within the `account_name`:
+
+```
+GRANT CREATE ENGINE ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#usage-any-engine-permission)USAGE ANY ENGINE permission
+
+The following code example grants the role `developer_role` permission to use all current and future engines within the `account_name`:
+
+```
+GRANT USAGE ANY ENGINE ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#operate-any-engine-permission)OPERATE ANY ENGINE permission
+
+The following code example gives the role `developer_role` permission to start and stop all current and future engines within the `account_name`:
+
+```
+GRANT USAGE ANY DATABASE ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#modify-any-engine-permission)MODIFY ANY ENGINE permission
+
+The following code example grants the role `developer_role` permission to modify or delete all current and future engines within the `account_name`:
+
+```
+GRANT MODIFY ANY ENGINE ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#create-role-permission)[CREATE ROLE](/sql_reference/commands/access-control/create-role.html) permission
+
+The following code example gives the role `developer_role` permission to create new roles within the `account_name`:
+
+```
+GRANT CREATE ROLE ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#modify-any-role-permission)MODIFY ANY ROLE permission
+
+The following code example grants the role `developer_role` permission to modify or delete all current and future roles within the `account_name`:
+
+```
+GRANT MODIFY ANY ROLE ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#create-user-permission)[CREATE USER](/sql_reference/commands/access-control/create-user.html) permission
+
+The following code example gives the role `developer_role` permission to create new users within the `account_name`:
+
+```
+GRANT CREATE USER ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#modify-any-user-permission)MODIFY ANY USER permission
+
+The following code example grants the role `developer_role` permission to modify or delete all current and future users within the `account_name`:
+
+```
+GRANT MODIFY ANY USER ON ACCOUNT account_name TO developer_role;
+```
+
+### [](#monitor-any-usage-permission)MONITOR \[ANY USAGE] permission
+
+The following code example grants the role `developer_role` permission to see the query history and currently running queries on all the engines within `account_name`:
+
+```
+GRANT MONITOR ANY USAGE ON ACCOUNT "account-1" TO developer_role;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_check_privileges.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_check_privileges.md
new file mode 100644
index 0000000..5ca45c2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_check_privileges.md
@@ -0,0 +1,81 @@
+# [](#check-assigned-privileges)Check assigned privileges
+
+The Firebolt information schema provides system views that allow you to view metadata and permissions for objects within your current account or database. This page explains how to query and validate user and role privileges at both the **account** and **database** levels.
+
+## [](#viewing-effective-privileges)Viewing effective privileges
+
+The following code example shows how to view the effective privileges of the current user:
+
+```
+SELECT
+  AR.grantee,
+  AR.role_name,
+  OP.privilege_type,
+  OP.object_type,
+  OP.object_name
+FROM information_schema.transitive_applicable_roles AS AR
+JOIN information_schema.object_privileges AS OP
+ON (AR.role_name = OP.grantee)
+WHERE
+  AR.grantee = session_user();
+```
+
+## [](#usage-examples)Usage examples
+
+The following examples demonstrate how to validate privileges at both the **account** level and the **database** level. By running a query against the `information_schema` views, you can check the effective permissions granted to a user or role. Each scenario includes an example query and output to illustrate the scope of the retrieved privileges.
+
+### [](#validating-privileges-at-the-account-level)Validating privileges at the account level
+
+If no database is selected, the query runs at the account level and shows account-scoped privileges.
+
+**Example**
+
+In the following code example, a user `test_user` with an [account\_admin](/Overview/organizations-accounts.html#account-administrative-role) role retrieves their privileges and associated roles for their current user session:
+
+```
+SELECT
+  AR.grantee,
+  AR.role_name,
+  OP.privilege_type,
+  OP.object_type,
+  OP.object_name
+FROM information_schema.transitive_applicable_roles AS AR
+JOIN information_schema.object_privileges AS OP
+ON (AR.role_name = OP.grantee)
+WHERE
+  AR.grantee = session_user();
+```
+
+**Returns**
+
+Grantee role\_name privilege\_type object\_type object\_name test\_user account\_admin `MODIFY ANY ENGINE` account account-1 test\_user account\_admin `MODIFY ANY DATABASE` account account-1 test\_user account\_admin `OPERATE ANY ENGINE` account account-1 test\_user account\_admin `MODIFY ANY ROLE` account account-1 test\_user account\_admin `USAGE ANY DATABASE` account account-1 test\_user account\_admin `MONITOR ANY USAGE` account account-1 test\_user account\_admin `MANAGE GRANTS` account account-1 test\_user account\_admin `USAGE ANY ENGINE` account account-1 test\_user account\_admin `MODIFY ANY USER` account account-1 test\_user account\_admin `METER USAGE` account account-1 test\_user account\_admin `CREATE SCHEMA` database UltraFast test\_user account\_admin `CREATE USER` account account-1 test\_user account\_admin `CREATE DATABASE` account account-1 test\_user account\_admin `CREATE ROLE` account account-1 test\_user account\_admin `CREATE ENGINE` account account-1
+
+The previous table confirms that `test_user` has account-level privileges, such as permission to create engines, roles, and databases, as well as permission to modify users and engines.
+
+### [](#validating-privileges-at-the-database-level)Validating privileges at the database level
+
+When a specific database is selected, the query retrieves privileges scoped to that database.
+
+**Example**
+
+The following code example retrieves the applicable roles and associated privileges, object types, and object names for `test_user`, who holds an `account_admin` role from the information schema.
+
+```
+SELECT
+  AR.grantee,
+  AR.role_name,
+  OP.privilege_type,
+  OP.object_type,
+  OP.object_name
+FROM information_schema.transitive_applicable_roles AS AR
+JOIN information_schema.object_privileges AS OP
+ON (AR.role_name = OP.grantee)
+WHERE
+  AR.grantee = session_user();
+```
+
+**Returns**
+
+Grantee role\_name privilege\_type object\_type object\_name test\_user account\_admin `SELECT ANY` schema public test\_user account\_admin `DELETE ANY` schema public test\_user account\_admin `VACUUM ANY` schema public test\_user account\_admin `INSERT ANY` schema public test\_user account\_admin `MODIFY` schema public test\_user account\_admin `CREATE` schema public test\_user account\_admin `USAGE` schema public test\_user account\_admin `MODIFY ANY` schema public test\_user account\_admin `TRUNCATE ANY` schema public
+
+The previous output confirms that `test_user` has database-level privileges, such as `SELECT`, `INSERT`, `DELETE`, and schema-level `MODIFY` permissions.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions.md
new file mode 100644
index 0000000..aba21c9
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions.md
@@ -0,0 +1,59 @@
+# [](#database-permissions)Database permissions
+
+In Firebolt, a **database** is a logical container that organizes your data warehouse by holding components such as **tables**, **views**, **indexes**, and other database objects, as shown in the following diagram:
+
+![Firebolt's object model contains schema under databases, and tables, views, and indexes under schema.](../../../../assets/images/database-hierarchy.png)
+
+Database-level permissions define what actions roles can perform within a database and its associated objects.
+
+## [](#database-level-privileges)Database-level privileges
+
+Privilege Description GRANT Syntax REVOKE Syntax USAGE Allows access to the database and enables attaching engines to it. `GRANT USAGE ON DATABASE <database_name> TO <role>;` `REVOKE USAGE ON DATABASE <database_name> FROM <role>;` MODIFY Allows altering database properties and dropping the database. `GRANT MODIFY ON DATABASE <database_name> TO <role>;` `REVOKE MODIFY ON DATABASE <database_name> FROM <role>;` USAGE ANY SCHEMA Allows access to all current and future schemas within the database. `GRANT USAGE ANY SCHEMA ON DATABASE <database_name> TO <role>;` `REVOKE USAGE ANY SCHEMA ON DATABASE <database_name> FROM <role>;` [VACUUM](/sql_reference/commands/data-management/vacuum.html) ANY Allows running the `VACUUM` operation on all current and future tables. `GRANT VACUUM ANY ON DATABASE <database_name> TO <role>;` `REVOKE VACUUM ANY ON DATABASE <database_name> FROM <role>;` ALL \[PRIVILEGES] Grants all direct privileges over the database to a role. `GRANT ALL ON DATABASE <database_name> TO <role>;` `REVOKE ALL ON DATABASE <database_name> FROM <role>;`
+
+## [](#examples-of-granting-database-permissions)Examples of granting database permissions
+
+### [](#usage-permission)USAGE permission
+
+The following code example [grants](/sql_reference/commands/access-control/grant.html) the role `developer_role` access to use the specified database:
+
+```
+GRANT USAGE ON DATABASE "database-1" TO developer_role;
+```
+
+### [](#modify-permission)MODIFY permission
+
+The following code example gives the role `developer_role` permission to alter properties or drop the specified database:
+
+```
+GRANT MODIFY ON DATABASE "database-1" TO developer_role;
+```
+
+### [](#usage-any-schema-permission)USAGE ANY SCHEMA permission
+
+The following code example grants the role `developer_role` access to all current and future schemas within the specified database:
+
+```
+GRANT USAGE ANY SCHEMA ON DATABASE "database-1" TO developer_role;
+```
+
+### [](#vacuum-any-permission)VACUUM ANY permission
+
+The following code example gives the role `developer_role` permission to run [VACUUM](/sql_reference/commands/data-management/vacuum.html) operations on all current and future tables in the specified database:
+
+```
+GRANT VACUUM ANY ON DATABASE "database-1" TO developer_role;
+```
+
+### [](#all-permissions)ALL permissions
+
+The following code example gives the role `developer_role` all the direct permissions over database `database-1`:
+
+```
+GRANT ALL ON DATABASE "database-1" TO developer_role;
+```
+
+* * *
+
+- [Schema permissions](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html)
+- [Table permissions](/Overview/Security/Role-Based%20Access%20Control/database-permissions/table-permissions.html)
+- [View permissions](/Overview/Security/Role-Based%20Access%20Control/database-permissions/view-permissions.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_schema_permissions.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_schema_permissions.md
new file mode 100644
index 0000000..d9c1b99
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_schema_permissions.md
@@ -0,0 +1,99 @@
+# [](#schema-permissions)Schema permissions
+
+In Firebolt, a **schema** is a logical namespace within a database that organizes **tables**, **views**, and other objects. Schema-level permissions allow roles to perform specific actions, such as accessing, modifying, or managing objects within a schema.
+
+To perform actions on a schema or its objects, the role must also have the **USAGE** privilege on the schema’s parent database.
+
+## [](#schema-level-privileges)Schema-level privileges
+
+Privilege Description GRANT Syntax REVOKE Syntax USAGE Allows access to the schema and its objects `GRANT USAGE ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE USAGE ON SCHEMA public IN <database_name> FROM <role_name>;` MODIFY Allows altering the schema properties, including renaming or dropping the schema them. `GRANT MODIFY ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE MODIFY ON SCHEMA public IN <database_name> FROM <role_name>;` CREATE Allows creating new objects, such as tables and views, within the schema. `GRANT CREATE ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE CREATE ON SCHEMA public IN <database_name> FROM <role_name>;` [DELETE](/sql_reference/commands/data-management/delete.html) ANY Allows deleting rows and partitions from all current and future tables. `GRANT DELETE ANY ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE DELETE ANY ON SCHEMA public IN <database_name> FROM <role_name>;` [INSERT](/sql_reference/commands/data-management/insert.html) ANY Allows inserting rows into all current and future tables within the schema. `GRANT INSERT ANY ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE INSERT ANY ON SCHEMA public IN <database_name> FROM <role_name>;` [UPDATE](/sql_reference/commands/data-management/update.html) ANY Allows updating rows in all current and future tables within the schema. `GRANT UPDATE ANY ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE UPDATE ANY ON SCHEMA public IN <database_name> FROM <role_name>;` [TRUNCATE](/sql_reference/commands/data-management/truncate-table.html) ANY Allows truncating all current and future tables within the schema. `GRANT TRUNCATE ANY ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE TRUNCATE ANY ON SCHEMA public IN <database_name> FROM <role_name>;` [VACUUM](/sql_reference/commands/data-management/vacuum.html) ANY Allows running the `VACUUM` operation on all current and future tables. `GRANT VACUUM ANY ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE VACUUM ANY ON SCHEMA public IN <database_name> FROM <role_name>;` MODIFY ANY Allows modifying or dropping all current and future objects in the schema. `GRANT MODIFY ANY ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE MODIFY ANY ON SCHEMA public IN <database_name> FROM <role_name>;` SELECT ANY Allows reading data from all current and future objects within the schema. `GRANT SELECT ANY ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE SELECT ANY ON SCHEMA public IN <database_name> FROM <role_name>;` ALL \[PRIVILEGES] Grants all direct privileges over the schema to a role. `GRANT ALL ON SCHEMA public IN <database_name> TO <role_name>;` `REVOKE ALL ON SCHEMA public IN <database_name> FROM <role_name>;`
+
+## [](#examples-of-granting-schema-permissions)Examples of granting schema permissions
+
+### [](#usage-permission)USAGE permission
+
+The following code example [grants](/sql_reference/commands/access-control/grant.html) the role `developer_role` permission to use the specified schema.
+
+```
+GRANT USAGE ON SCHEMA "public" TO developer_role;
+```
+
+### [](#modify-permission)MODIFY permission
+
+The following code example gives the role `developer_role` permission to alter properties or drop the specified schema.
+
+```
+GRANT MODIFY ON SCHEMA "public" TO developer_role;
+```
+
+### [](#create-permission)CREATE permission
+
+The following code example grants the role `developer_role` the ability to create new objects in the specified schema:
+
+```
+GRANT CREATE ON SCHEMA "public" TO developer_role;
+```
+
+### [](#delete-any-permission)DELETE ANY permission
+
+The following code example gives the role `developer_role` permission to [delete](/sql_reference/commands/data-management/delete.html) rows and partitions from all current and future tables in the specified schema:
+
+```
+GRANT DELETE ANY ON SCHEMA "public" TO developer_role;
+```
+
+### [](#insert-any-permission)INSERT ANY permission
+
+The following code example grants the role `developer_role` permission to [insert](/sql_reference/commands/data-management/insert.html) rows into all current and future tables in the specified schema:
+
+```
+GRANT INSERT ANY ON SCHEMA "public" TO developer_role;
+```
+
+### [](#update-any-permission)UPDATE ANY permission
+
+The following code example gives the role `developer_role` permission to [update](/sql_reference/commands/data-management/update.html) rows in all current and future tables in the specified schema:
+
+```
+GRANT UPDATE ANY ON SCHEMA "public" TO developer_role;
+```
+
+### [](#truncate-any-permission)TRUNCATE ANY permission
+
+The following code example grants the role `developer_role` the ability to [truncate](/sql_reference/commands/data-management/truncate-table.html) all current and future tables in the specified schema:
+
+```
+GRANT TRUNCATE ANY ON SCHEMA "public" TO developer_role;
+```
+
+### [](#vacuum-any-permission)VACUUM ANY permission
+
+The following code example gives the role `developer_role` permission to run [`VACUUM`](/sql_reference/commands/data-management/vacuum.html) operations on all current and future tables in the specified schema:
+
+```
+GRANT VACUUM ANY ON SCHEMA "public" TO developer_role;
+```
+
+### [](#modify-any-permission)MODIFY ANY permission
+
+The following code example grants the role `developer_role` permission to modify or drop all current and future objects in the specified schema:
+
+```
+GRANT MODIFY ANY ON SCHEMA "public" TO developer_role;
+```
+
+### [](#select-any-permission)SELECT ANY permission
+
+The following code example gives the role `developer_role` permission to select data from all current and future objects in the specified schema:
+
+```
+GRANT SELECT ANY ON SCHEMA "public" TO developer_role;
+```
+
+### [](#all-permissions)ALL permissions
+
+The following code example gives the role `developer_role` all the direct permissions over schema `public`:
+
+```
+GRANT ALL ON SCHEMA "public" TO developer_role;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_table_permissions.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_table_permissions.md
new file mode 100644
index 0000000..d1ac525
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_table_permissions.md
@@ -0,0 +1,101 @@
+# [](#table-permissions)Table permissions
+
+In Firebolt, a **table** is a structured data object within a database, composed of rows and columns. Tables are the foundational units for organizing, querying, and managing data in your Firebolt data warehouse. Table-level permissions allow roles to perform actions such as selecting, modifying, or managing data within specific tables.
+
+To perform actions on a table, roles must also have **USAGE** permissions on both the parent schema and the parent database of the table.
+
+## [](#table-level-privileges)Table-level privileges
+
+Privilege Description GRANT Syntax REVOKE Syntax SELECT Allows selecting rows from the table. `GRANT SELECT ON TABLE <table_name> TO <role_name>;` `REVOKE SELECT ON TABLE <table_name> FROM <role_name>;` [INSERT](/sql_reference/commands/data-management/insert.html) Allows inserting rows into the table. Applies to managed tables only. `GRANT INSERT ON TABLE <table_name> TO <role_name>;` `REVOKE INSERT ON TABLE <table_name> FROM <role_name>;` MODIFY Allows modifying and dropping the table. `GRANT MODIFY ON TABLE <table_name> TO <role_name>;` `REVOKE MODIFY ON TABLE <table_name> FROM <role_name>;` [DELETE](/sql_reference/commands/data-management/delete.html) Allows deleting rows and dropping partitions from the table. Applies to managed tables only. `GRANT DELETE ON TABLE “<table_name>” TO <role_name>;` `REVOKE DELETE ON TABLE “<table_name>” FROM <role_name>;` [UPDATE](/sql_reference/commands/data-management/update.html) Allows updating rows in the table. Applies to managed tables only. `GRANT UPDATE ON TABLE <table_name> TO <role_name>;` `REVOKE UPDATE ON TABLE <table_name> FROM <role_name>;` [TRUNCATE](/sql_reference/commands/data-management/truncate-table.html) Allows truncating a table. Applies to managed tables only. `GRANT TRUNCATE ON TABLE <table_name> TO <role_name>;` `REVOKE TRUNCATE ON TABLE <table_name> FROM <role_name>;` [VACUUM](/sql_reference/commands/data-management/vacuum.html) Allows running the `VACUUM` operation. Applies to managed tables only. `GRANT VACUUM ON TABLE <table_name> TO <role_name>;` `REVOKE VACUUM ON TABLE <table_name> FROM <role_name>;` ALL \[PRIVILEGES] Grants all privileges over the table to a role. `GRANT ALL ON TABLE <table_name> TO <role_name>;` `REVOKE ALL ON TABLE <table_name> FROM <role_name>;`
+
+To grant permissions across all tables in a schema, use [schema-level privileges](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html). For example, privileges like **SELECT ANY**, **INSERT ANY**, or **DELETE ANY** at the schema level will apply to all current and future tables within that schema.
+
+## [](#aggregating-indexes)Aggregating Indexes
+
+An [aggregating index](/Overview/indexes/aggregating-index.html) in Firebolt accelerates queries involving aggregate functions on large tables. This reduces compute usage and improves query performance.
+
+To **create** or **drop** an aggregating index, a role must have the following permissions:
+
+- `MODIFY` permission on the table.
+- `CREATE` permission on the parent schema.
+- `USAGE` permission on the parent schema.
+- `USAGE` permission on the parent database.
+
+To drop an aggregating index, the role requires:
+
+- `MODIFY` permission on the table.
+- `USAGE` permission on the parent schema.
+- `USAGE` permission on the parent database.
+
+## [](#examples-of-modifying-table-permissions)Examples of modifying table permissions
+
+The following example use [`GRANT`](/sql_reference/commands/access-control/grant.html) to grant permissions. You can also replace `GRANT` with [REVOKE](/sql_reference/commands/access-control/revoke.html) in any of the examples to remove any granted privileges.
+
+### [](#select-permission)SELECT permission
+
+The following code example [grants](/sql_reference/commands/access-control/grant.html) the role `developer_role` permission to read data from the `games` table:
+
+```
+GRANT SELECT ON TABLE games TO developer_role;
+```
+
+### [](#insert-permission)INSERT permission
+
+The following code example gives the role `developer_role` permissions to [insert](/sql_reference/commands/data-management/insert.html) rows into the `games` table:
+
+```
+GRANT INSERT ON TABLE games TO developer_role;
+```
+
+### [](#modify-permission)MODIFY permission
+
+The following code example grants the role `developer_role` permission to alter or drop the `games` table:
+
+```
+GRANT MODIFY ON TABLE games TO developer_role;
+```
+
+### [](#delete-permission)DELETE permission
+
+The following code example gives the role `developer_role` permission to [delete](/sql_reference/commands/data-management/delete.html) rows or partitions from the `games` table:
+
+```
+GRANT DELETE ON TABLE games TO developer_role;
+```
+
+### [](#update-permission)UPDATE permission
+
+The following code example grants the role `developer_role` permission to [update](/sql_reference/commands/data-management/update.html) rows in the `games` table:
+
+```
+GRANT UPDATE ON TABLE games TO developer_role;
+```
+
+### [](#truncate-permission)TRUNCATE permission
+
+The following code example gives the role `developer_role` permission to [truncate](/sql_reference/commands/data-management/truncate-table.html) the `games` table, removing all rows:
+
+```
+GRANT TRUNCATE ON TABLE games TO developer_role;
+```
+
+### [](#vacuum-permission)VACUUM permission
+
+The following code example grants the role `developer_role` permission to run the [`VACUUM`](/sql_reference/commands/data-management/vacuum.html) operation on the `games` table:
+
+```
+GRANT VACUUM ON TABLE games TO developer_role;
+```
+
+### [](#all-permissions)ALL permissions
+
+The following code example grants the role `developer_role` with all permissions on the table `games`:
+
+```
+GRANT ALL ON TABLE games TO developer_role;
+```
+
+## [](#considerations)Considerations
+
+- Use the [REVOKE](/sql_reference/commands/access-control/revoke.html) statement to remove any granted privileges. Replace [`GRANT`](/sql_reference/commands/access-control/grant.html) with [`REVOKE`](/sql_reference/commands/access-control/revoke.html) in the examples above.
+- Table-level permissions apply only to the specified table. For broader control, consider granting schema-level privileges.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_view_permissions.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_view_permissions.md
new file mode 100644
index 0000000..a131472
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_database_permissions_view_permissions.md
@@ -0,0 +1,45 @@
+# [](#view-permissions)View permissions
+
+In Firebolt, **views** are objects that allow users to query data from one or more underlying tables or views. Permissions on these views determine who can interact with the view and what actions they can perform.
+
+To interact with a view, roles must also have **USAGE** permissions on the parent schema and the parent database.
+
+## [](#view-level-privileges)View-level privileges
+
+Privilege Description GRANT Syntax REVOKE Syntax   SELECT Allows selecting data from a view. `GRANT SELECT ON VIEW <view_name> TO <role_name>;` `REVOKE SELECT ON VIEW <view_name> FROM <role_name>;`   MODIFY Allows modifying and dropping a view. `GRANT MODIFY ON VIEW <view_name> TO <role_name>;` `REVOKE MODIFY ON VIEW <view_name> FROM <role_name>;`   ALL \[PRIVLEGES] Grants all privileges over the view to a role. `GRANT ALL ON VIEW <view_name> TO <role_name>;` `REVOKE ALL ON VIEW <view_name> FROM <role_name>;`  
+
+Views are created at the schema level. To grant privileges to create views, refer to the [schema-level privileges documentation](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html).
+
+## [](#examples-of-granting-view-permissions)Examples of granting view permissions
+
+### [](#select-permission)SELECT permission
+
+To allow querying data from a view, the role must have **SELECT** privileges on the view. Additionally, the **view owner** must have **SELECT** privileges on all underlying tables or views referenced within the view.
+
+The following examples [grant](/sql_reference/commands/access-control/grant.html) the role `read_role` permission to query data from the `viewtest` view and ensure the `view_owner` has the necessary permission to read data from the `referenced_table` table, allowing the view to function correctly.
+
+```
+-- Grant SELECT on the view to a user:
+GRANT SELECT ON VIEW "viewtest" TO read_role;
+
+-- Grant SELECT on the referenced table to the view owner:
+GRANT SELECT ON TABLE "referenced_table" TO view_owner;
+```
+
+If the **view owner** loses access to any of these referenced objects, users with **SELECT** on the view will no longer be able to query it, even if their **SELECT** privilege remains.
+
+### [](#modify-permission)MODIFY permission
+
+The following code example grants the role `developer_role` permission to alter or drop the `my_view` view:
+
+```
+GRANT MODIFY ON VIEW my_view TO read_role;
+```
+
+### [](#all-permissions)ALL permissions
+
+The following code example grants the role `developer_role` with all permissions over the `my_view` view:
+
+```
+GRANT ALL ON VIEW my_view TO read_role;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_engine_permissions.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_engine_permissions.md
new file mode 100644
index 0000000..41b79af
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_engine_permissions.md
@@ -0,0 +1,54 @@
+# [](#engine-permissions)Engine permissions
+
+In Firebolt, an **engine** is a compute resource that processes data and serves queries. Engines provide **full workload isolation**, allowing multiple workloads to run independently while sharing access to the same data. Engines are also **decoupled from databases**, which means:
+
+- An engine can connect to multiple databases.
+- A database can be accessed by multiple engines.
+
+The following table outlines the privileges that can be granted for engines within a particular account:
+
+Privilege Description GRANT Syntax REVOKE Syntax USAGE Allows using an engine to run queries. `GRANT USAGE ON ENGINE <engine_name> TO <role>;` `REVOKE USAGE ON ENGINE <engine_name> FROM <role>;` OPERATE Allows stopping and starting an engine. `GRANT OPERATE ON ENGINE <engine_name> TO <role>;` `REVOKE OPERATE ON ENGINE <engine_name> FROM <role>;` MODIFY Allows altering engine properties or dropping the engine. `GRANT MODIFY ON ENGINE <engine_name> TO <role>;` `REVOKE MODIFY ON ENGINE <engine_name> FROM <role>;` MONITOR \[USAGE] Enables the tracking of engine queries through the `engine_running_queries` view for active queries and the `engine_query_history` view for past queries in `information_schema`. `GRANT MONITOR USAGE ON ENGINE <engine_name> TO <role>;` `REVOKE MONITOR USAGE ON ENGINE <engine_name> FROM <role>;` ALL \[PRIVILEGES] Grants all privileges over the engine to a role. `GRANT ALL ON ENGINE <engine_name> TO <role>;` `REVOKE ALL ON ENGINE <engine_name> FROM <role>;`
+
+If a user lacks **USAGE** and **OPERATE** privileges for an engine, they will not be able to select or interact with the engine via the Firebolt UI.
+
+## [](#examples-of-granting-engine-permissions)Examples of granting engine permissions
+
+### [](#usage-permission)USAGE permission
+
+The following code example grants the role `developer_role` permission to use the `myEngine` engine for executing queries:
+
+```
+GRANT USAGE ON ENGINE "myEngine" TO developer_role;
+```
+
+### [](#operate-permission)OPERATE permission
+
+The following code example gives the role `developer_role` permission to start and stop the `myEngine` engine:
+
+```
+GRANT OPERATE ON ENGINE "myEngine" TO developer_role;
+```
+
+### [](#modify-permission)MODIFY permission
+
+The following code example grants the role `developer_role` permission to alter properties or drop the `myEngine` engine:
+
+```
+GRANT MODIFY ON ENGINE "myEngine" TO developer_role;
+```
+
+### [](#monitor-usage-permission)MONITOR \[USAGE] permission
+
+The following code example grants the role `developer_role` permission to see the query history and currently running queries for the engine `myEngine`:
+
+```
+GRANT MONITOR USAGE ON ENGINE "myEngine" TO developer_role;
+```
+
+### [](#all-permissions)ALL permissions
+
+The following code example grants the role `developer_role` with all engine permissions on `myEngine`:
+
+```
+GRANT ALL ON ENGINE "myEngine" TO developer_role;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_ownership.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_ownership.md
new file mode 100644
index 0000000..576c132
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_ownership.md
@@ -0,0 +1,62 @@
+# [](#ownership)Ownership
+
+When you create an object in Firebolt, you become its owner. As the owner, you have full control and can perform all operations on the object without needing additional privileges. This allows you to use objects immediately after creating them.
+
+As the owner of an object, you can do the following:
+
+- Grant privileges on the object to any role.
+- Grant roles you own to other users or roles without needing administrator permissions.
+
+## [](#supported-object-types)Supported object types
+
+The following object types support ownership:
+
+- **Role**
+- **User**
+- **Engine**
+- **Database**
+- **Schema**
+- **Table**
+- **View**
+
+The current owner of an object can be viewed in the corresponding `information_schema` view:
+
+Role Name View Role N/A User `information_schema.users` Database `information_schema.catalogs` Engine `information_schema.engines` Schema `information_schema.schemata` Table `information_schema.tables` View `information_schema.views` or `information_schema.tables`
+
+Indexes inherit ownership from their parent table. In `information_schema.indexes`, the table owner is displayed as the index owner.
+
+## [](#changing-an-objects-owner)Changing an object’s owner
+
+The following code example shows how to transfer the ownership of an object:
+
+```
+ALTER <object type>  <object name> OWNER TO <user>
+```
+
+## [](#examples-of-updating-ownership-permissions)Examples of updating ownership permissions
+
+The following are examples of how to change the ownership of different object types.
+
+### [](#changing-object-ownership)Changing object ownership
+
+The following code example uses `ALTER` to transfer ownership of a database, engine, role, user, schema, table, and view to a new owner:
+
+```
+ALTER DATABASE db OWNER TO new_owner
+ALTER ENGINE eng OWNER TO new_owner
+ALTER ROLE r OWNER TO new_owner
+ALTER USER u OWNER TO new_owner
+ALTER SCHEMA public OWNER TO new_owner
+ALTER TABLE t OWNER TO new_owner
+ALTER VIEW v OWNER TO new_owner
+```
+
+### [](#dropping-users-that-own-objects)Dropping users that own objects
+
+Before dropping a user who owns objects, you must either drop the objects owned by the owner or transfer ownership of them to another user.
+
+The following code example shows how to drop a table that has dependent views not owned by the table’s owner using the `CASCADE` parameter to enforce the drop:
+
+```
+DROP TABLE <table_name> CASCADE;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management.md
new file mode 100644
index 0000000..173f4e6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management.md
@@ -0,0 +1,10 @@
+# [](#role-management-in-firebolt)Role management in Firebolt
+
+Role management in Firebolt allows you to control access to resources within your data warehouse by assigning specific privileges to users and roles. Firebolt supports two types of roles: [system roles](/Overview/Security/Role-Based%20Access%20Control/role-management/system-roles.html) and [custom roles](/Overview/Security/Role-Based%20Access%20Control/role-management/custom-roles.html).
+
+Privileges can be granted to custom roles either by the [account\_admin](/Overview/organizations-accounts.html#account-administrative-role) or the [resource owner](/Overview/Security/Role-Based%20Access%20Control/ownership.html).
+
+* * *
+
+- [Default System Roles](/Overview/Security/Role-Based%20Access%20Control/role-management/system-roles.html)
+- [Custom Roles](/Overview/Security/Role-Based%20Access%20Control/role-management/custom-roles.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management_custom_roles.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management_custom_roles.md
new file mode 100644
index 0000000..7c62835
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management_custom_roles.md
@@ -0,0 +1,7 @@
+# [](#custom-roles)Custom roles
+
+In Firebolt, custom roles can be created at the account level to manage access control and permissions. Only users with the [account\_admin](/Overview/organizations-accounts.html#account-administrative-role) system role or those granted the [CREATE ROLE](/sql_reference/commands/access-control/create-role.html) privilege can create custom roles. Once created, custom roles can be assigned to any user or existing role by the `account_admin` or the resource owner.
+
+Privileges can be granted to custom roles by `account_admin` or the [resource owner](/Overview/Security/Role-Based%20Access%20Control/ownership.html). For example, the owner of a table can grant `SELECT` privileges on that table to a custom role.
+
+For more information about creating roles, see [creating a custom role via SQL or the Firebolt UI](/Guides/managing-your-organization/managing-users.html#create-a-role).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management_system_roles.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management_system_roles.md
new file mode 100644
index 0000000..0c0ea72
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_management_system_roles.md
@@ -0,0 +1,15 @@
+# [](#default-system-roles)Default system roles
+
+In Firebolt, **system-defined** roles are automatically created for each organization and account. These roles provide predefined privileges and serve specific purposes. While system-defined roles **cannot** be modified or dropped, you can grant them additional privileges as needed.
+
+## [](#organization-system-roles)Organization system roles
+
+Role Name Description organization\_admin Enables all the permissions and the ability to manage the organization.
+
+The [organization\_admin](/Overview/organizations-accounts.html#organizational-administrative-role) role cannot be granted using SQL. It can only be granted using the [Firebolt Workspace](https://go.firebolt.io/signup) user interface (UI). To manage resources at the organization level, you must assign the `organization_admin` role to your login using the UI.
+
+## [](#account-system-roles)Account system roles
+
+Role Name Description public Includes `USAGE` on all databases and both `USAGE` and `CREATE` on every public schema. system\_admin Enables managing databases, engines, schemas, tables, and views. This includes setting database and engine properties as well as access to the observability functionality on all engines. account\_admin Grants full permissions to manage the organization.
+
+By default, every newly created user is granted the [public](/Overview/organizations-accounts.html#public-role) role. You can also revoke this role from a user.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_permissions.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_permissions.md
new file mode 100644
index 0000000..0eec590
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_role_permissions.md
@@ -0,0 +1,17 @@
+# [](#role-permissions)Role permissions
+
+In Firebolt, a [role](/Overview/organizations-accounts.html#roles) is a group of permissions that can have privileges assigned to it. You can [grant](/sql_reference/commands/access-control/grant.html#grant-role) a role to another role or to users.
+
+The following table outlines the privileges that can be granted for roles within a particular account:
+
+Privilege Description GRANT Syntax REVOKE Syntax MODIFY Grants the ability to drop the specified role. `GRANT MODIFY ON ROLE <role_name> TO <role>;` `REVOKE MODIFY ON ROLE <role_name> FROM <role>;`
+
+## [](#examples-of-granting-role-permissions)Examples of granting role permissions
+
+### [](#modify-permission)MODIFY permission
+
+The following code example grants the role `developer_role` permission to drop the `my_role` role:
+
+```
+GRANT MODIFY ON ROLE my_role TO developer_role;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_user_permissions.md b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_user_permissions.md
new file mode 100644
index 0000000..4fc2d2b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_role_based%20access%20control_user_permissions.md
@@ -0,0 +1,19 @@
+# [](#user-permissions)User permissions
+
+In Firebolt, a [user](/Overview/organizations-accounts.html#users) is associated with a [login](/Guides/managing-your-organization/managing-logins.html) or [service account](/Guides/managing-your-organization/service-accounts.html), which grants them access to that account. You can assign a [role](/Overview/organizations-accounts.html#roles) to a user, and the role determines the specific actions they are authorized to perform within the account.
+
+The following table outlines the privileges that can be granted for users within a particular account:
+
+Privilege Description GRANT Syntax REVOKE Syntax MODIFY Grants the ability to drop the specified user. `GRANT MODIFY ON USER <user_name> TO <role>;` `REVOKE MODIFY ON USER <user_name> FROM <role>;`
+
+Users can modify most of their own account settings without requiring [RBAC](/Overview/Security/Role-Based%20Access%20Control/#role-based-access-control-rbac) permissions, except when altering [LOGIN](/Guides/managing-your-organization/managing-logins.html) configurations or a [SERVICE ACCOUNT](/Guides/managing-your-organization/service-accounts.html).
+
+## [](#examples-of-granting-user-permissions)Examples of granting user permissions
+
+### [](#modify-permission)MODIFY permission
+
+The following code example grants the role `developer_role` permission to drop the `my_user` user:
+
+```
+GRANT MODIFY ON USER my_user TO developer_role;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/overview_security_security.md b/cmd/docs-scrapper/fireboltdocs/overview_security_security.md
new file mode 100644
index 0000000..34163de
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/overview_security_security.md
@@ -0,0 +1,197 @@
+# [](#security)Security
+
+Firebolt employs a layered security strategy to deliver a secure and trusted cloud data warehouse tailored to modern enterprise needs. By integrating advanced security features and industry best practices, Firebolt ensures that its security practices are compliant with security standards. Your data is protected, remains secure, and is accessible only to authorized individuals. Access to objects and resources is managed through accounts, establishing clear boundaries to isolate and secure data.
+
+Firebolt’s layered security model has the following key areas:
+
+- [Security](#security)
+  
+  - [Network security](#network-security)
+  - [Identity management](#identity-management)
+    
+    - [Single sign-On (SSO)](#single-sign-on-sso)
+    - [Multi-factor authentication (MFA)](#multi-factor-authentication-mfa)
+  - [Access control](#access-control)
+    
+    - [Roles](#roles)
+    - [Users](#users)
+    - [Objects and permissions](#objects-and-permissions)
+  - [Data protection](#data-protection)
+    
+    - [Data at rest](#data-at-rest)
+    - [Data in motion](#data-in-motion)
+    - [Secure communication protocols](#secure-communication-protocols)
+    - [AWS PrivateLink](#aws-privatelink)
+    - [HIPAA compliance](#hipaa-compliance)
+
+## [](#network-security)Network security
+
+Firebolt ensures secure data transmission by implementing end-to-end encryption with Transport Layer Security (TLS) version 1.2, protecting data as it moves between end users and the cloud service.
+
+Firebolt supports the creation of custom [network policies](/Guides/security/network-policies.html), adding an extra layer of security to your applications. This functionality allows administrators to exercise fine-grained control over which IP ranges can access Firebolt.
+
+In Firebolt, network policies contain `allowed_IP_list` and `blocked_IP_list` properties that capture definition of IP address ranges. Each property is a list that can contain one or more IP ranges.
+
+Firebolt supports individual and programmatic access through the following:
+
+- [Login](/Guides/managing-your-organization/managing-logins.html) - A login object represents an individual user, identified by an email address, who will authenticate by verifying their identity to access Firebolt.
+- [Service account](/Guides/managing-your-organization/service-accounts.html) - A service account object is used to represent a machine or application that will authenticate and interact with Firebolt without human intervention.
+
+**Example**
+
+The following code example creates a network policy `my_network_policy` with a description that allows only two IP addresses:
+
+```
+CREATE NETWORK POLICY IF NOT EXISTS my_network_policy WITH ALLOWED_IP_LIST = (‘4.5.6.1’, ‘2.4.5.1’) 
+DESCRIPTION = 'my new network policy'
+```
+
+A network policy can be attached to [an organization](/Guides/managing-your-organization/creating-an-organization.html), individual logins, and service accounts.
+
+**Example**
+
+The following code example applies `my_network_policy` to `my_organization` and to the login associated with `kate@acme.com`, which restricts access according to the rules of that policy:
+
+```
+ALTER ORGANIZATION my_organization SET NETWORK_POLICY = my_network_policy;
+ALTER LOGIN 'kate@acme.com' SET NETWORK_POLICY = my_network_policy;
+```
+
+For more information, see [network policies](/Guides/security/network-policies.html).
+
+## [](#identity-management)Identity management
+
+Identity management is a multi-step verification process designed to ensure that only authorized individuals, services, and applications can access organizational resources. Identity management involves both identifying users and verifying their identity through authentication.
+
+Firebolt uses [Auth0](https://auth0.com/) as its identity provider for managing customer registration. All authentication data stored in Auth0 is protected with industry-standard cryptography. Authentication information is securely exchanged using the [SAML 2.0 protocol](https://auth0.com/intro-to-iam/what-is-saml).
+
+Firebolt provides the SSO and MFA authentication methods.
+
+### [](#single-sign-on-sso)Single sign-On (SSO)
+
+[Single Sign-On (SSO)](/Guides/security/sso/) is an authentication method that allows users to access multiple applications or services using a single set of login credentials, simplifying the authentication process and improving security through centralized identity management. Firebolt uses SSO to simplify and streamline implementation of secure access to its platform, enhancing the overall security posture and protecting against unauthorized access and data breaches. SSO configuration is accessible to users with the `org_account` built-in role.
+
+### [](#multi-factor-authentication-mfa)Multi-factor authentication (MFA)
+
+[MFA](/Guides/security/enabling-mfa.html) strengthens security by requiring users to provide multiple forms of authentication to access their accounts. Many industries have compliance and regulatory standards that require the use of MFA for securing certain types of data and systems. Firebolt fully supports these standards by offering MFA configuration and implementation directly linked to the login object, ensuring secure and compliant access control.
+
+**Example**
+
+The following code example creates a login for a user, enables password-based authentication, and requires MFA to authenticate:
+
+```
+CREATE LOGIN "kate@acme.com" WITH
+FIRST_NAME = 'Kate'
+LAST_NAME = 'Peterson'
+IS_PASSWORD_ENABLED = TRUE
+IS_MFA_ENABLED = TRUE;
+```
+
+## [](#access-control)Access control
+
+Access control ensures that users have the necessary and appropriate permissions to engage with Firebolt’s system or resources. Firebolt implements [role-based access control](/Guides/security/rbac.html) (RBAC) to manage permissions.
+
+The RBAC model is centered around the following principles:
+
+- All objects can be secured.
+- Every supported statement requires explicit permission, preventing unauthorized actions.
+- The RBAC model is composable, which means that a user’s total permissions are the result of combining all the roles assigned to them, giving them the collective access granted by each role.
+- Roles are hierarchical and allow permissions to be inherited through role relationships.
+
+The RBAC model contains the following:
+
+- [Roles](#roles)
+- [Users](#users)
+- [Objects and permissions](#objects-and-permissions).
+
+### [](#roles)Roles
+
+A role is a set of permissions assigned to a user or group that defines what actions they are authorized to perform and what resources they can access within Firebolt. Firebolt has the following types of roles:
+
+1\) **Built-in roles** have a set of pre-defined permissions and custom user-defined roles that can allow for more specific use cases. You can use [GRANT](/sql_reference/commands/access-control/grant.html) and [REVOKE](/sql_reference/commands/access-control/revoke.html) statements to modify permissions for custom roles. Built-in roles become available as soon as a new organization is created, and the first account is set up.
+
+2\) **User-defined roles** are custom roles that administrators can create to grant a specific set of permissions.
+
+3\) **System-defined roles** align with common user personas and responsibilities including `public`, which is granted to each new user by default, a `system_admin` role, and an `account_admin` role. For more information about these roles, see [System-defined roles](/Overview/Security/Role-Based%20Access%20Control/role-management/system-roles.html).
+
+You can create a role by using either the **Firebolt Workspace** or using the [CREATE ROLE](/sql_reference/commands/access-control/create-role.html) SQL statement.
+
+**Example**
+
+The following example creates a new role `sales`, which can later be assigned specific permissions and granted to users to inherit those permissions:
+
+```
+CREATE ROLE sales;
+```
+
+### [](#users)Users
+
+Users are linked to either a login or service account in order to gain access to Firebolt. They can be created using the [CREATE USER](/sql_reference/commands/access-control/create-user.html) statement in SQL or through the **Firebolt Workspace**.
+
+**Example**
+
+The following code creates a new users `kate` and `bob`:
+
+```
+CREATE USER kate;
+CREATE USER bob;
+```
+
+**Example**
+
+The following code example grants the permissions associated with the `sales` role to `kate` and revokes it from `bob`:
+
+```
+GRANT ROLE sales TO USER kate;
+REVOKE ROLE sales FROM USER bob; 
+```
+
+### [](#objects-and-permissions)Objects and permissions
+
+Permissions in Firebolt define the actions or operations that can be performed, such as managing databases and engines, running queries, or accessing data. Each instance of a securable object, or an object that can be protected by access controls, has specific permissions that are associated with it, controlling what users can do with it. Examples of securable objects include databases, tables, and engines. If there are multiple instances of an engine object, each instance has its own set of predefined permissions. For a full list of available permissions, see [role-based access control](/Overview/Security/Role-Based%20Access%20Control/)
+
+Any permission that Firebolt supports can be [granted](/sql_reference/commands/access-control/grant.html) or [revoked](/sql_reference/commands/access-control/revoke.html) to or from roles.
+
+Privileges can be granted or revoked only for roles, not directly for users. Once a role has the necessary permissions, it can then be assigned to users, allowing them to inherit those privileges.
+
+**Example**
+
+The following code example grants the `sales` role permission to use the `sales_db` database, allows the role to access any database within `dev_account`, and revokes the ability of the `sales` role to start or stop the `sales_eng` engine:
+
+```
+GRANT USAGE ON DATABASE sales_db TO sales;    -- grants the ability to use sales_db database to the sales role
+GRANT USAGE ANY DATABASE ON ACCOUNT dev_account TO sales;    -- grants the ability to use any database in dev_account to the sales role
+REVOKE OPERATE ON ENGINE sales_eng FROM sales;   -- revokes the ability to START and STOP the sales_eng engine from sales role
+```
+
+## [](#data-protection)Data protection
+
+Firebolt is firmly committed to data security, privacy, and compliance by ensuring that all data it manages is properly safeguarded and protected through strict encryption standards for data both in motion and at rest. The following security functionality is automatically available to customers:
+
+### [](#data-at-rest)Data at rest
+
+By default, all data at rest is encrypted and stored using Amazon Simple Storage Service (S3). All new objects are automatically encrypted using either Amazon S3-managed keys or AWS Key Management Service (KMS) keys, which are securely managed through AWS KMS.
+
+### [](#data-in-motion)Data in motion
+
+Firebolt automatically encrypts sensitive data being transmitted between service components, ensuring that it remains secure as it moves across networks and cannot be intercepted by unauthorized parties.
+
+### [](#secure-communication-protocols)Secure communication protocols
+
+Firebolt uses secure communication protocols, such as Transport Layer Security (TLS), to provide an additional layer of protection against man-in-the-middle attacks. These attacks occur when an unauthorized party intercepts or alters data as it is transmitted between two points. By encrypting data and ensuring secure connections, Firebolt prevents unauthorized access or tampering during data transmission, safeguarding sensitive information as it moves between systems.
+
+### [](#aws-privatelink)AWS PrivateLink
+
+AWS PrivateLink enables secure connectivity between your VPC and Firebolt without routing traffic over the public internet. Firebolt supports AWS PrivateLink to provide a private, one-way connection from your VPC to the Firebolt private API, ensuring data confidentiality, integrity, and availability during transit.
+
+Users with an [account administrator](/Overview/organizations-accounts.html#account-administrative-role) or [organizational administrative](/Overview/organizations-accounts.html#organizational-administrative-role) role can request access to PrivateLink. For more information, see [Request PrivateLink access](/Guides/security/privatelink.html#request-aws-privatelink-access).
+
+### [](#hipaa-compliance)HIPAA compliance
+
+HIPAA compliance consists of federal regulations designed to safeguard the privacy and security of patient health information. Firebolt supports HIPAA compliance to ensure the confidentiality, integrity, and availability of electronic protected health information (ePHI) stored within its platform.
+
+To modify the state of HIPAA compliance for your account, contact the [Firebolt support team](mailto:support@firebolt.io).
+
+* * *
+
+- [Role-Based Access Control](/Overview/Security/Role-Based%20Access%20Control/)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/product.md b/cmd/docs-scrapper/fireboltdocs/product.md
new file mode 100644
index 0000000..ac2ecaf
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/product.md
@@ -0,0 +1,87 @@
+# [](#what-is-firebolt)What is Firebolt?
+
+Firebolt is a next-generation cloud data warehouse designed for organizations that require lightning-fast analytics at scale. Whether you’re dealing with complex data applications, high-concurrency workloads, or low-latency queries, Firebolt empowers you to unlock the full potential of your data without compromising on performance or cost.
+
+# [](#why-firebolt)Why Firebolt?
+
+Firebolt is designed specifically to address the demands of modern data workloads, prioritizing **exceptional efficiency** and **low cost** while delivering industry-leading performance for data-intensive applications.
+
+Firebolt addresses the following challenges:
+
+- High latency and costly performance during data processing and retrieval.
+- Poor query performance under heavy loads.
+- Scaling difficulties when managing large datasets.
+- Complexity in managing and optimizing data workflows while working with unfamiliar languages.
+
+The following sections highlight Firebolt’s key benefits, as well as its compatibility with various frameworks and workloads for seamless data integration and processing:
+
+- [Key benefits](#key-benefits)
+- [Eco-system and integrations](#eco-system-and-integrations)
+
+# [](#key-benefits)Key benefits
+
+Firebolt is inherently **scalable** helping you to adapt rapidly to changes in your data and workloads. Key benefits include:
+
+- [High Efficiency](#-high-efficiency) — Achieve exceptional price-to-performance ratios, delivering fast analytics without high costs.
+- [Concurrency at Scale](#-concurrency-at-scale) — Run thousands of queries concurrently, maintaining sub-second performance even under heavy loads.
+- [Elasticity](#-elasticity) — Seamlessly scale to handle hundreds of terabytes of data without sacrificing speed or efficiency.
+- [SQL Simplicity](#-sql-simplicity) — Use a subset of PostgreSQL-compatible SQL, allowing teams to adapt easily with minimal training.
+
+### [](#-high-efficiency)![Icon for efficiency.](../../assets/images/icon-efficiency.png) High efficiency
+
+Firebolt delivers low-latency, high performance analytics with one of the best price-to-performance ratios in the industry. Its architecture is optimized for fast query execution through features like vectorized processing and sparse indexing, which minimize data scans and optimize CPU usage. These features enable fast responses to data-intensive queries, even at petabyte scale, without overloading compute resources. Whether analyzing structured or semi-structured data, Firebolt delivers millisecond-level query responses, backed by ACID compliance to ensure data consistency, integrity, and reliability.
+
+### [](#-concurrency-at-scale)![Icon for concurrency at scale.](../../assets/images/icon-concurrency.png) Concurrency at scale
+
+Firebolt enables thousands of concurrent queries, ensuring your applications can manage heavy query loads with consistent, reliable performance. Its fine-grained scaling capabilities allow for high query throughput efficiently, even during peak workloads, ensuring optimal resource allocation and minimizing query latency.
+
+### [](#-elasticity)![Icon for elasticity or vertical, horizontal or concurrent scaling.](../../assets/images/icon-elasticity.png) Elasticity
+
+Firebolt’s fully decoupled architecture and multi-dimensional elasticity allow compute, storage, and management resources to scale independently, optimizing both performance and cost efficiency. This architecture enables fine-grained control over resources as your workloads evolve, including scaling out to accommodate massive datasets. You can access any database from any engine, giving you flexibility to access any data while offering workload isolation to achieve predictable performance. Furthermore, Firebolt’s system allows fine-grained control over provisioned resources for achieving needed price-performance characteristics and minimizing cost. Firebolt’s architecture supports:
+
+- **Vertical scaling** - Scale up to increase the capacity of your engine to process complex queries for data-intensive workloads.
+- **Horizontal scaling** - Scale out by adding more compute nodes to handle higher data processing demands efficiently.
+- **Concurrent scaling** - Run multiple clusters within a single engine, which can scale up to ten clusters simultaneously. Firebolt manages concurrency scaling transparently to user applications without requiring any endpoint changes.
+
+The following diagram includes code examples of how to scale vertically, horizontally or scale for concurrency using SQL in the **Firebolt Workspace**:
+
+![You can scale vertically, horizontally, or concurrently in the Firebolt Workspace.](../../assets/images/product-scaling-engines.png)
+
+Firebolt’s multi-dimensional approach to elasticity allows it to dynamically adapt to any workload, ensuring optimal system performance while keeping costs under control.
+
+### [](#-sql-simplicity)![Icon for SQL simplicity.](../../assets/images/icon-simplicity.png) SQL simplicity
+
+Firebolt supports a PostgreSQL-compliant SQL dialect, allowing your teams to leverage Firebolt’s capabilities without needing to learn a new query language. This simplifies integration with existing workflows that contain tasks that include data provisioning, processing, and management. With support for both structured and [semi-structured data](/Guides/loading-data/working-with-semi-structured-data/working-with-semi-structured-data.html), Firebolt allows you to analyze diverse datasets within a single platform.
+
+# [](#eco-system-and-integrations)Eco-system and integrations
+
+Firebolt’s platform is optimized for integration within modern data workflows. It supports ingesting data efficiently through ELT tools, making it easy to move data from data lakes, relational databases, and other source systems into Firebolt. With support for Amazon S3 cloud storage and popular file formats like Avro, Parquet, and ORC, Firebolt allows you to centralize and query your data with ultra-fast analytics, seamlessly fitting into your existing data architecture.
+
+You can leverage industry-standard tools like Apache Airflow, dbt, and Superset for orchestration and visualization. Firebolt’s SDKs offer wide support for language clients like Python, Node.js, Java, and .NET. This flexibility empowers your team to build and query data using their preferred environments, ensuring smooth data workflows from ingestion to advanced analytics.
+
+![Firebolt supports popular SDKs and connectors to integrate with many workflows.](../../assets/images/firebolt-framework.png)
+
+### [](#-workload-isolation-for-smooth-operations)![Icon for workload isolation.](../../assets/images/icon-isolation.png) Workload isolation for smooth operations
+
+Firebolt optimizes workloads by considering configuration, resource utilization, and history-based statistics to balance both latency and throughput. Any Firebolt engine can handle both read and write operations on any database, ensuring strong consistency across all engines. Workloads are managed independently with dedicated compute resources, allowing you to run complex ELT processes, fast queries, BI reports, among others, without interference. Workload isolation ensures that resource-heavy tasks do not impact your most critical applications and dashboards, enabling smooth operations across diverse use cases.
+
+# [](#next-steps)Next steps
+
+Read about Firebolt’s [platform capabilities](/product/product-platform.html).
+
+# [](#more-firebolt-resources)More Firebolt resources
+
+Learn how to load and query your data with our [Get Started](/Guides/getting-started/) and [Load data](/Guides/loading-data/loading-data.html) guides or use one of Firebolt’s [test data sets](https://www.firebolt.io/free-sample-datasets).
+
+[Sign up](https://go.firebolt.io/signup) to access your $200 Firebolt credit for your first 30 days. No credit card needed.
+
+- See news, blog posts, whitepapers, events, and videos at [Firebolt’s Knowledge center](https://www.firebolt.io/knowledge-center).
+- Explore our [competitive pricing options](https://www.firebolt.io/pricing).
+
+Need help? Firebolt’s support team at [support@firebolt.io](mailto:support@firebolt.io) is here to assist you with:
+
+- Onboarding support.
+- Troubleshooting query performance.
+- Optimizing database configurations.
+- Addressing data loading issues.
+- Getting best practices for data modeling.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/product_product_platform.md b/cmd/docs-scrapper/fireboltdocs/product_product_platform.md
new file mode 100644
index 0000000..8835743
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/product_product_platform.md
@@ -0,0 +1,33 @@
+# [](#firebolt-platform-capabilities)Firebolt platform capabilities
+
+## [](#-data-management)![Icon for data management.](../../assets/images/icon-data_management.png) Data management
+
+Firebolt is built for performance and efficiency, with built-in features that reduce manual effort. Its robust architecture supports parallel data ingestion, ACID-compliant DML, and optimized storage, allowing it to manage large and complex datasets. Automated indexing and backend optimization ensure consistent query performance, even during data modifications like inserts, updates, and deletes. Firebolt also supports both structured and semi-structured data, making it easy to integrate into existing workflows for tasks such as table creation, data ingestion, and transaction management.
+
+For more information, see [Data management](/Overview/data-management.html).
+
+## [](#-query-processing)![Icon for query processing.](../../assets/images/icon-processing.png) Query processing
+
+Firebolt’s query processing is optimized for low latency, high concurrency, and dynamic scaling to meet workload demands. Its optimizer creates efficient execution plans by evaluating data distribution, indexing, and previous query patterns. The distributed runtime system leverages multithreading and tiered caching for faster processing, while resource-aware scheduling and efficient memory management enhance cluster performance. This setup ensures fast, consistent query execution, even for complex queries and large datasets.
+
+You can also use the Firebolt API for programmatic access to performing tasks including querying, managing resources, and automating workflows.
+
+For more information, see the [Firebolt API](/Guides/query-data/using-the-api.html), and the Firebolt [functions glossary](/sql_reference/functions-reference/functions-glossary.html).
+
+## [](#-security)![Icon for security.](../../assets/images/icon-security.png) Security
+
+Firebolt employs a multi-layered approach to data protection, utilizing industry-standard encryption, secure key management, and granular access control to meet the needs of organizations that build [large, data-intensive applications and products](https://www.firebolt.io/knowledge-center/case-studies). With HIPAA and SOC 2 compliance, Firebolt ensures the confidentiality, integrity, and availability of your data. Identity management combines username/password authentication, Single Sign-On (SSO), and Multi-Factor Authentication (MFA) to secure access to resources. Role-Based Access Control (RBAC) assigns permissions through hierarchical and composable roles, allowing only authorized users to access critical data and system resources.
+
+![Firebolt's security layers include access control, identity management, infrastructure and network security.](../../assets/images/firebolt-security-layers.png)
+
+For more information, see [Security](/Overview/Security/security.html).
+
+## [](#-observability)![Icon for observability.](../../assets/images/icon-observability.png) Observability
+
+Firebolt’s observability features provide detailed metrics on CPU, RAM, disk usage, and cache efficiency through the `engine_metrics_history` and `engine_running_queries` views. These metrics help optimize engine configurations and resource allocation. Firebolt also integrates with OpenTelemetry, enabling users to track telemetry data for deeper insights into performance across distributed systems. This integration enhances observability and supports data-driven adjustments. Access to these tools is managed through Role-Based Access Control (RBAC), ensuring secure management of system resources.
+
+## [](#-collaborative-workspace)![Icon for collaboration.](../../assets/images/icon-collaboration.png) Collaborative workspace
+
+Delivering insights and data products requires collaboration among multiple roles, including data architects, engineers, developers, and IT operations. The **Firebolt Workspace** facilitates team coordination by providing visibility across the entire data lifecycle. It includes dedicated areas for security and governance, data modeling, exploration, SQL development, and performance management, ensuring each role can contribute effectively.
+
+In the Firebolt **Develop Space**, you can edit and run SQL scripts, manage databases, and view query results. This space features a document editor with auto-complete and script templates. You can also rename, copy, or export scripts, and execute SQL snippets or entire scripts with real-time result display. The **Develop Space** interface supports light and dark modes and allows for exporting query results for further use.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference.md b/cmd/docs-scrapper/fireboltdocs/reference.md
new file mode 100644
index 0000000..8ce4fd7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference.md
@@ -0,0 +1,12 @@
+# [](#general-reference)General reference
+
+Get product updates from release notes, and general reference material for advanced Firebolt specifications.
+
+* * *
+
+- [Release notes](/Reference/release-notes/release-notes.html)
+- [Available regions](/Reference/available-regions.html)
+- [System settings](/Reference/system-settings.html)
+- [Object identifers](/Reference/object-identifiers.html)
+- [Reserved words](/Reference/reserved-words.html)
+- [Help menu](/Reference/help-menu.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference_available_regions.md b/cmd/docs-scrapper/fireboltdocs/reference_available_regions.md
new file mode 100644
index 0000000..da967e5
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference_available_regions.md
@@ -0,0 +1,7 @@
+# [](#available-aws-regions)Available AWS regions
+
+Firebolt is available in the following AWS regions:
+
+Region name Region ID US West (Oregon) us-west-2 US East (N. Virginia) us-east-1 Europe (Frankfurt) eu-central-1 Europe (Ireland) eu-west-1 Asia Pacific (Singapore) ap-southeast-1
+
+To request additional regions, contact Firebolt’s support team at [support@firebolt.io](mailto:support@firebolt.io).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference_help_menu.md b/cmd/docs-scrapper/fireboltdocs/reference_help_menu.md
new file mode 100644
index 0000000..1813644
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference_help_menu.md
@@ -0,0 +1,108 @@
+# [](#help-menu)Help menu
+
+The **Firebolt Help menu** is found in the bottom left corner of the screen, appearing as a question mark (`?`).
+
+![Help Menu](/assets/images/getting_to_help.png)
+
+## [](#menu-options)Menu options
+
+The help menu has the following options:
+
+- Status Page
+- Release Notes
+- Contact Support
+- Firebolt Support Access
+- Documentation
+
+### [](#status-page)Status page
+
+The status page allows you to view the operational status of systems in real time, as well as descriptions of historical incidents.
+
+You can subscribe to notifications whenever Firebolt **creates**, **updates**, or **resolves** an incident through the following options:
+
+1. **Email notification** - by providing your email address.
+2. **Text notifications** - by providing your phone number. *You will only receive text notifications when Firebolt either creates or resolves an incident.*
+3. **Slack notifications** - by connecting via Slack. *You can receive maintenance status updates through Slack*
+4. **RSS updates** - by connecting via your RSS/Atom application.
+
+### [](#release-notes)Release Notes
+
+The Release Notes link brings you to Firebolt’s [latest version release notes](/Reference/release-notes/release-notes.html).
+
+### [](#contact-support---reaching-out-to-firebolt-support)Contact Support - Reaching out to Firebolt Support
+
+**Contact Support** allows you to create a support case for Firebolt’s support team.
+
+To create a case:
+
+1. Select **Contact Support**.
+2. A support form will appear, with the following information populated **automatically**:
+   
+   - **First Name**
+   - **Last Name**
+   - **Organization**
+   - **Email**
+3. Fill in the following:
+   
+   - **Account** - Select the name of your account within your organization.
+   - **Severity** - Select the severity of your case according to the following categories:
+     
+     - *Critical*: You are currently experiencing a loss of critical functionality. For example, your engine is unable to start.
+     - *Urgent*: Your critical functionality is being intermittently impacted. For example, your engine intermittently becomes unresponsive.
+     - *Tolerable*: Your services remain operational, though non-critical functionality may be impacted. For example, a specific SQL query generates an error.
+     - *Question*: Your operations are running smoothly with no disruptions. You may have a question or want to report a minor issue with the user interface.
+   - **Engine name** - Enter the name of the engine with the issue.
+   - **Subject** - Provide a clear and descriptive subject.
+   - **Description** - Provide any relevant details including the following:
+     
+     - What were you trying to do when the issue occurred?
+     - What was your expected outcome?
+     - What actually happened?
+     - What errors were returned?
+4. Select **Submit**.
+5. Your case will be sent to our Support team, and you will receive a confirmation email.
+
+### [](#firebolt-support-access)Firebolt Support Access
+
+Firebolt Support Access allows you to manage and control the level of access that Firebolt’s support team has to your account.
+
+For new accounts, support access is enabled by default; however you can revoke it at any time.
+
+All support team activity is logged and can be viewed in the [query history](../sql_reference/information-schema/engine-query-history).
+
+To grant access to the support team:
+
+1. Select “Firebolt Support Access”
+2. A support access form will appear, with the following information populated **automatically**:
+   
+   - **Account Name**
+   - **Duration**
+   - **Assign Roles**
+3. Fill in the following:
+   
+   - **Duration** - Specify the duration for which you’d like to grant access to the support team. Once this period ends, access will be automatically revoked.
+   - **Assign Roles** - Select the role(s) that you want to assign to the support team. Their access will be limited to these roles. You can create a dedicated role by following the [instructions here](/Overview/Security/Role-Based%20Access%20Control/role-management/custom-roles.html). Note that the support team will have full access data at the organization level.
+4. Select **Grant Access**.
+
+Once access is granted, an additional icon will appear in the bottom left corner of the screen, indicating that Firebolt’s support team has access to your account, as shown below:
+
+![Support Access](/assets/images/support_access_menu.png)
+
+To edit support team access:
+
+1. Select the icon that appeared when you granted access to the support team. You can find this icon in the bottom left corner of your **Firebolt Workspace**.
+2. Select **Manage access**. You can also open the same screen by selecting **Firebolt Support Access** in the **Help** menu.
+3. Select **Edit Access**.
+4. After you have made your changes, select **Update Access**.
+
+To revoke support team access:
+
+1. Select the icon that appeared when you granted access to the support team. You can find this icon in the bottom left corner of your **Firebolt Workspace**.
+2. Select **Manage access**. You can also open the same screen by selecting **Firebolt Support Access** in the **Help** menu.
+3. Select **Revoke Access**.
+
+Once revoked, the support access icon will disappear from the bottom left corner of the screen.
+
+### [](#documentation)Documentation
+
+The Documentation link brings you to Firebolt’s docs (where you are now!)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference_interval_arithmetic.md b/cmd/docs-scrapper/fireboltdocs/reference_interval_arithmetic.md
new file mode 100644
index 0000000..c1a1863
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference_interval_arithmetic.md
@@ -0,0 +1,96 @@
+# [](#arithmetic-with-intervals)Arithmetic with intervals
+
+This topic describes the Firebolt implementation of arithmetic with intervals.
+
+- [Overview](#overview)
+- [Literal string interpretation](#literal-string-interpretation)
+  
+  - [Format examples](#format-examples)
+- [Arithmetic between interval and TIMESTAMPTZ](#arithmetic-between-interval-and-timestamptz)
+- [Examples](#examples)
+
+## [](#overview)Overview
+
+An `interval` represents a duration. In Firebolt, values of type `interval` can be used to add or subtract a duration to/from a date or timestamp. `Interval` cannot be used as the data type of a column.
+
+The `+` and `*` operators shown below come in commutative pairs (e.g., both `DATE + interval` and `interval + DATE` are accepted).
+
+Operator Description `DATE + interval -> TIMESTAMP` Add an `interval` to a `DATE` `DATE - interval -> TIMESTAMP` Subtract an `interval` from a `DATE` `TIMESTAMP + interval -> TIMESTAMP` Add an `interval` to a `TIMESTAMP` `TIMESTAMP - interval -> TIMESTAMP` Subtract an `interval` from a `TIMESTAMP` `TIMESTAMPTZ + interval -> TIMESTAMPTZ` Add an `interval` to a `TIMESTAMPTZ` `TIMESTAMPTZ - interval -> TIMESTAMPTZ` Subtract an `interval` from a `TIMESTAMPTZ` `interval * DOUBLE PRECISION -> interval` Multiply an `interval` by a scalar
+
+## [](#literal-string-interpretation)Literal string interpretation
+
+`Interval` literals can be specified in two formats.
+
+### [](#format-examples)Format examples
+
+**Cast from text literal**  
+The following examples demonstrate different ways to cast a text literal to an interval in SQL. Each method converts a string representing a time interval into the `INTERVAL` data type using various casting syntaxes.
+
+Using interval keyword:
+
+```
+interval 'quantity unit [quantity unit...] [direction]'
+```
+
+Using double colon:
+
+```
+'quantity unit [quantity unit...] [direction]'::interval
+```
+
+Using `CAST` function:
+
+```
+CAST('quantity unit [quantity unit...] [direction]' AS interval)
+```
+
+In these examples, `direction` can be either `ago` or left empty. Using `ago` negates all specified quantities. The `quantity` represents a signed or unsigned integer, and `unit` refers to one of the following time units, matched case-insensitively:
+
+Unit microsecond\[s] / us millisecond\[s] / ms second\[s] / s minute\[s] / m hour\[s] / h day\[s] / d week\[s] / w month\[s] / mon\[s] year\[s] / y decade\[s] / dec\[s] century / centuries / c millennium\[s] / mil\[s]
+
+Each `unit` can appear only once in an interval literal. The value of the interval is determined by adding the quantities of the specified units with the appropriate signs.
+
+**Unit outside of text literal**  
+The following example demonstrates how to cast a numeric value to an interval by placing the unit outside of the text literal.
+
+```
+interval 'N' unit
+```
+
+In this format, `N` represents a signed or unsigned integer, and `unit` specifies the time unit, matched case-insensitively, from the following options:
+
+Unit second minute hour day week month year
+
+## [](#arithmetic-between-interval-and-timestamptz)Arithmetic between interval and TIMESTAMPTZ
+
+Interval arithmetic with `TIMESTAMPTZ` values works as follows:
+
+1. Convert the `TIMESTAMPTZ` value from Unix time to local time according to the rules of the time zone specified by the session’s `time_zone` setting.
+2. Add the `millennium`, `century`, `decade`, `year`, `month`, `week` and `day` components of the interval to the local time.
+3. Convert the local time back to Unix time according to the rules of the time zone specified by the session’s `time_zone` setting.
+4. Add the `hour`, `minute`, `second`, `millisecond`, and `microsecond` components of the interval to the Unix time.
+
+The back and forth between Unix time and local time is necessary to handle the fact that not all days consist of 24 hours due to daylight savings time transitions. For instance, `SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '1 day'` returns `2022-10-31 00:00:00+01` but `SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '24 hours'` returns `2022-10-30 23:00:00+01` (assuming the value of the session’s `time_zone` setting is `'Europe/Berlin'`). Still, the dependence on the session’s `time_zone` setting should be kept in mind when doing arithmetic between interval and `TIMESTAMPTZ`.
+
+### [](#multiplying-an-interval-by-a-scalar)Multiplying an interval by a scalar
+
+You can use the expression `date_time + INTERVAL * d` where `date_time` is a constant or column reference of type `DATE`, `TIMESTAMP`, or `TIMESTAMPTZ`, and `d` is a constant or column reference of type `DOUBLE PRECISION`. The effect is that the INTERVAL is scaled by `d`, and the resulting INTERVAL is added to `date_time`. E.g., `INTERVAL '1 day' * 3` -&gt; `INTERVAL '3 days'`.
+
+## [](#examples)Examples
+
+```
+SELECT DATE '1996-09-03' - interval '1 millennium 5 years 42 day 42 ms';  --> 0991-07-22 23:59:59.958
+SELECT TIMESTAMP '1996-09-03 11:19:42' + interval '10 years 5 months 42 days 7 seconds';  --> 2007-03-17 11:19:49
+
+SELECT TIMESTAMP '2023-10-20 11:49:52' + interval '1 year 6 months 4 weeks 7 hours' * 7.5;  --> 2035-08-20 16:19:52
+SELECT DATE '2023-10-20' - 42 * interval '1 months 1 day 1 hour';  --> 2020-03-07 06:00:00
+
+-- The following example shows a daylight savings time change in the time zone 'Europe/Berlin'
+SET time_zone = 'Europe/Berlin';
+SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '1 day';  --> 2022-10-31 00:00:00+01
+SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '24' hour;  --> 2022-10-30 23:00:00+01
+
+SET time_zone = 'US/Pacific';
+SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '1 day';  --> 2022-10-30 15:00:00-07
+SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '24' hour;  --> 2022-10-30 15:00:00-07
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference_object_identifiers.md b/cmd/docs-scrapper/fireboltdocs/reference_object_identifiers.md
new file mode 100644
index 0000000..1b0c651
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference_object_identifiers.md
@@ -0,0 +1,55 @@
+# [](#object-identifers)Object identifers
+
+Firebolt object identifiers are used to refer to database items such as columns, tables, indexes, views, and engines.
+
+## [](#syntax)Syntax
+
+Identifiers must contain at least one character, and no more than `255` characters total.
+
+## [](#unquoted-identifiers)Unquoted identifiers
+
+Unquoted identifiers must adhere to the following syntax:
+
+1. The **first character** must be a letter (a-z), or an underscore (`_`).
+2. After the first character, **subsequent characters** can include letters, underscores, or digits (0-9).
+
+Firebolt evaluates unquoted identifiers such as table and column names **entirely in lowercase**. The following queries:
+
+```
+SELECT my_column FROM my_table
+SELECT MY_COLUMN FROM MY_TABLE
+SELECT mY_cOlUmn FROM mY_tAbLe
+```
+
+are all equivalent to:
+
+```
+SELECT my_column FROM my_table
+```
+
+You can keep uppercase identifiers by enclosing them in double-quotes. For example, the following identifiers are unique:
+
+```
+"COLUMN_NAME"
+"column_name"
+"CoLuMn_NaMe"
+```
+
+## [](#quoted-identifiers)Quoted identifiers
+
+Quoted identifiers can contain any UTF-8 characters of the following [Unicode general category values](https://www.unicode.org/reports/tr44/#General_Category_Values):
+
+1. Any letter in any language, as represented by the Unicode general category value for **Letter**.
+2. Any numeric character in any language as represented by the Unicode general category value for **Number**.
+3. Special characters beyond standard alphanumeric characters. Examples include `@`, `#`, `-`, `$`, `%`, `?`, and others. Any object identifier that contains special characters, spaces, or are case-sensitive must be enclosed in double quotes (`"`) as follows: `"my-column"` or `"User@Name"`.
+4. Underscores, as represented by the Unicode general category value for **Connector\_Punctuation**.
+
+## [](#user-names)User names
+
+User names must conform to the following rules:
+
+- They must be between 3 to 63 characters in length.
+- They can contain alphanumeric characters including upper and lowercase letters and numbers.
+- The first and last characters must be either a letter or a digit.
+- You can use the following special characters: ``@ ! # $ % & ' * + - = ? ^ _ ` { | } ~ .``
+- You can not use consecutive dots (..).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference_proof_of_concept_guide.md b/cmd/docs-scrapper/fireboltdocs/reference_proof_of_concept_guide.md
new file mode 100644
index 0000000..a9d9c1a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference_proof_of_concept_guide.md
@@ -0,0 +1,60 @@
+# [](#firebolt-proof-of-concept-technical-guidelines)Firebolt proof of concept technical guidelines
+
+> This guide should be used after you have met with your Firebolt designated sales team. If you are looking to try out Firebolt and have yet to contact us, [get started here.](https://www.firebolt.io/getting-started-now)
+
+- [Step 1 - Provide access to S3](#step-1---provide-access-to-s3)
+- [Step 2 - Provide your Firebolt team with relevant assets](#step-2---provide-your-firebolt-team-with-relevant-assets)
+
+## [](#step-1---provide-access-to-s3)Step 1 - Provide access to S3
+
+The data used in the proof of concept should be made available in an S3 region ([any region](/Reference/available-regions.html) is fine). To ensure the proof of concept accurately reflects your production workload, it’s recommended to have all or a significant portion of the data available.
+
+Firebolt pays for data transfer costs if such occurs. You can find additional information in [this AWS guide.](https://docs.aws.amazon.com/AmazonS3/latest/userguide/RequesterPaysBuckets.html)
+
+Please go through the following steps to grant Firebolt access to the relevant S3 bucket. You can find additional information in [this AWS guide.](https://docs.aws.amazon.com/AmazonS3/latest/userguide/add-bucket-policy.html)
+
+1. Connect to the AWS console and click on the relevant S3 bucket.
+2. Go to *Permissions* and then scroll down and edit *Bucket Policy*.
+3. Copy the following policy. Make sure you replace `<bucket>` with the actual bucket name.
+   
+   ```
+    {
+     "Version": "2012-10-17",
+     "Statement": [
+    {
+      "Effect": "Allow",
+      "Principal": {
+        "AWS": "arn:aws:iam::231290928314:root"
+      },
+      "Action": [
+        "s3:GetObject",
+        "s3:GetObjectTagging",
+        "s3:PutObject",
+        "s3:PutObjectTagging",
+        "s3:ListBucket",
+        "s3:GetBucketLocation"
+      ],
+      "Resource": [
+        "arn:aws:s3:::<bucket>",
+        "arn:aws:s3:::<bucket>/*"
+      ]
+    }
+     ]
+   }
+   
+   ```
+4. Save changes
+
+## [](#step-2---provide-your-firebolt-team-with-relevant-assets)Step 2 - Provide your Firebolt team with relevant assets
+
+Please share the following assets with your Firebolt team through your designated Slack channel or email.
+
+Please make sure all files are saved as a `sql` file type (i.e, `file_name.sql`)
+
+1. **Schema** - this file should include the DDL commands that we should use to create the desired database schema.
+2. **Sample queries &amp; average durations** - this file should include a set of queries to be executed over the data set. These queries might be:
+   
+   - A good representation of queries you usually run
+   - Queries that are slow and you would like to see improved
+   
+   For each query, add a comment in the file describing the average duration, or any additional metric that might be relevant.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference_release_notes_release_notes.md b/cmd/docs-scrapper/fireboltdocs/reference_release_notes_release_notes.md
new file mode 100644
index 0000000..757fe96
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference_release_notes_release_notes.md
@@ -0,0 +1,39 @@
+# [](#release-notes)Release notes
+
+Firebolt continuously releases updates so that you can benefit from the latest and most stable service. These updates might happen daily, but we aggregate release notes to cover a longer time period for easier reference. The most recent release notes from the latest version are below.
+
+- See the [Release notes archive](/Reference/release-notes/release-notes-archive.html) for earlier-version release notes.
+
+Firebolt might roll out releases in phases. New features and changes may not yet be available to all accounts on the release date shown.
+
+## [](#firebolt-release-notes---version-418)Firebolt Release Notes - Version 4.18
+
+### [](#new-features)New Features
+
+**Users can now ALTER their corresponding USER object without administrative or RBAC permissions**  
+Users can now [ALTER](/sql_reference/commands/access-control/alter-user.html) their corresponding [USER](/Overview/organizations-accounts.html#users) object and change its properties without needing role-based access control permissions ([RBAC](/Overview/Security/Role-Based%20Access%20Control/)). This enhancement simplifies user self-management by reducing the dependency on administrative permissions. Restrictions remain for sensitive properties including [logins or service accounts](/Overview/organizations-accounts.html#organizations), which require higher-level permissions.
+
+**Use a LOCATION object to store credentials for authentication**  
+You can now use [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html) to create a `LOCATION` object in your Firebolt account. Use `LOCATION` to store credentials and authenticate to external systems without needing to provide static credentials each time you run a query or create a table. `LOCATION` works with ([RBAC](/Overview/Security/Role-Based%20Access%20Control/)) so you can manage permissions securely. You can view detailed information about your locations including source type, URL, description, owner, and creation time in [information\_schema.locations](/sql_reference/information-schema/locations.html).
+
+**Added creation timestamps for tables, views, indexes, and locations**  
+Use creation timestamps in `information_schema` views for [tables](/sql_reference/information-schema/tables.html), [views](/sql_reference/information-schema/views.html), [indexes](/sql_reference/information-schema/indexes.html), and [locations](/sql_reference/information-schema/locations.html) to help track objects for data management.
+
+**Added support for SQL pipe syntax**  
+Firebolt now supports [SQL Pipe syntax](/sql_reference/commands/queries/pipe.html), an alternative way to structure SQL queries using the `|>` operator. This syntax allows for a linear, step-by-step flow of query transformations, improving readability and simplifying query composition. It supports all standard SQL operations and can be combined with traditional SQL syntax.
+
+**Added wildcard character functionality to `READ_PARQUET` and `READ_CSV` to simultaneously read multiple files**  
+You can use wildcard characters such as `*` or `?` to specify a file URL as a [glob pattern](https://en.wikipedia.org/wiki/Glob_%28programming%29) in the [READ\_PARQUET](/sql_reference/functions-reference/table-valued/read_parquet.html) and [READ\_CSV](/sql_reference/functions-reference/table-valued/read_csv.html) table-valued functions to read multiple files simultaneously. This enhancement simplifies managing large datasets by reducing the need to make multiple function calls.
+
+**Added functionality to transfer ownership of objects in the Firebolt Workspace**  
+You can now [transfer ownership](/Guides/security/ownership.html#transfer-ownership-using-the-firebolt-workspace) of Firebolt objects through the **Firebolt Workspace** user interface (UI). You can transfer ownership of individual objects or bulk transfer owned by a specific user. You can also delete individual objects or in bulk, helping to simplify the management of object ownership within the UI.
+
+### [](#performance-improvements)Performance Improvements
+
+**Enabled result and subresult caching for queries with window functions**  
+Enabled [result and subresult caching](/Overview/queries/understand-query-performance-subresult.html) for queries that contain [window functions](/sql_reference/functions-reference/window/), which can reduce query runtimes by storing previous results and enhance overall query performance and efficiency.
+
+### [](#bug-fixes)Bug Fixes
+
+**Fixed an issue where `CREATE VIEW` statements did not preserve the order of named function parameters**  
+An issue was resolved where [CREATE VIEW](/sql_reference/commands/data-definition/create-view.html) statements did not maintain the correct order of named function parameters, which could lead to syntax errors when querying the view. This fix improves query reliability by ensuring the proper order of function parameters.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference_release_notes_release_notes_archive.md b/cmd/docs-scrapper/fireboltdocs/reference_release_notes_release_notes_archive.md
new file mode 100644
index 0000000..435ea8c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference_release_notes_release_notes_archive.md
@@ -0,0 +1,1425 @@
+# [](#release-notes-archive)Release notes archive
+
+We provide an archive of release notes for your historical reference.
+
+- [Firebolt Release Notes - Version 4.17](#firebolt-release-notes---version-417)
+  
+  - [New Features](#new-features)
+  - [Performance Improvements](#performance-improvements)
+  - [Bug Fixes](#bug-fixes)
+- [Firebolt Release Notes - Version 4.16](#firebolt-release-notes---version-416)
+  
+  - [New Features](#new-features-1)
+  - [Performance Improvements](#performance-improvements-1)
+  - [Bug Fixes](#bug-fixes-1)
+- [Firebolt Release Notes - Version 4.15](#firebolt-release-notes---version-415)
+  
+  - [New Features](#new-features-2)
+  - [Performance Improvements](#performance-improvements-2)
+  - [Behavior Changes](#behavior-changes)
+  - [Bug Fixes](#bug-fixes-2)
+- [Firebolt Release Notes - Version 4.14](#firebolt-release-notes---version-414)
+  
+  - [New Features](#new-features-3)
+  - [Performance Improvements](#performance-improvements-3)
+  - [Bug Fixes](#bug-fixes-3)
+- [Firebolt Release Notes - Version 4.13](#firebolt-release-notes---version-413)
+  
+  - [New Features](#new-features-4)
+  - [Behavior Changes](#behavior-changes-1)
+  - [Bug Fixes](#bug-fixes-4)
+- [Firebolt Release Notes - Version 4.12](#firebolt-release-notes---version-412)
+  
+  - [New Features](#new-features-5)
+  - [Performance Improvements](#performance-improvements-4)
+  - [Behavior Changes](#behavior-changes-2)
+  - [Bug Fixes](#bug-fixes-5)
+- [Firebolt Release Notes - Version 4.11](#firebolt-release-notes---version-411)
+  
+  - [New Features](#new-features-6)
+- [Firebolt Release Notes - Version 4.10](#firebolt-release-notes---version-410)
+  
+  - [New Features](#new-features-7)
+  - [Behavior Changes](#behavior-changes-3)
+  - [Bug Fixes](#bug-fixes-6)
+- [Firebolt Release Notes - Version 4.9](#firebolt-release-notes---version-49)
+  
+  - [New Features](#new-features-8)
+  - [Performance Improvements](#performance-improvements-5)
+  - [Bug Fixes](#bug-fixes-7)
+- [Firebolt Release Notes - Version 4.8](#firebolt-release-notes---version-48)
+  
+  - [New Features](#new-features-9)
+  - [Performance Improvements](#performance-improvements-6)
+  - [Bug Fixes](#bug-fixes-8)
+- [DB version 4.7](#db-version-47)
+  
+  - [New Features](#new-features-10)
+  - [Performance Improvements](#performance-improvements-7)
+  - [Behavior Changes](#behavior-changes-4)
+  - [Bug Fixes](#bug-fixes-9)
+- [DB version 4.6](#db-version-46)
+  
+  - [New Features](#new-features-11)
+  - [Behavior Changes](#behavior-changes-5)
+  - [Bug Fixes](#bug-fixes-10)
+- [DB version 4.5](#db-version-45)
+  
+  - [New Features](#new-features-12)
+  - [Bug Fixes](#bug-fixes-11)
+- [DB version 4.4](#db-version-44)
+  
+  - [New Features](#new-features-13)
+  - [Breaking Changes](#breaking-changes)
+  - [Bug Fixes](#bug-fixes-12)
+- [DB version 4.3](#db-version-43)
+  
+  - [New Features](#new-features-14)
+  - [Performance Improvements](#performance-improvements-8)
+  - [Bug Fixes](#bug-fixes-13)
+  - [Breaking Changes](#breaking-changes-1)
+- [DB version 4.2](#db-version-42)
+  
+  - [New features](#new-features-15)
+  - [Enhancements, changes and new integrations](#enhancements-changes-and-new-integrations)
+  - [Breaking Changes](#breaking-changes-2)
+- [DB version 4.1](#db-version-41)
+  
+  - [Resolved issues](#resolved-issues)
+- [DB version 4.0](#db-version-40)
+  
+  - [Enhancements, changes and new integrations](#enhancements-changes-and-new-integrations-1)
+  - [Breaking Changes](#breaking-changes-3)
+- [DB version 3.34](#db-version-334)
+  
+  - [Enhancements, changes and new integrations](#enhancements-changes-and-new-integrations-2)
+  - [Resolved issues](#resolved-issues-1)
+- [DB version 3.33](#db-version-333)
+  
+  - [Enhancements, changes and new integrations](#enhancements-changes-and-new-integrations-3)
+  - [Resolved issues](#resolved-issues-2)
+- [DB version 3.32](#db-version-332)
+  
+  - [New features](#new-features-16)
+  - [Enhancements, changes and new integrations](#enhancements-changes-and-new-integrations-4)
+  - [Resolved issues](#resolved-issues-3)
+- [DB version 3.31](#db-version-331)
+  
+  - [New features](#new-features-17)
+  - [Enhancements, changes and new integrations](#enhancements-changes-and-new-integrations-5)
+  - [Resolved issues](#resolved-issues-4)
+- [DB version 3.30](#db-version-330)
+- [DB version 3.29](#db-version-329)
+- [DB version 3.28](#db-version-328)
+
+## [](#firebolt-release-notes---version-417)Firebolt Release Notes - Version 4.17
+
+### [](#new-features)New Features
+
+**Introduced the `IF` function to enhance query readability and simplify conditional expressions**  
+The new [`IF`](/sql_reference/functions-reference/conditional-and-miscellaneous/if.html) function simplifies query writing as a more concise alternative to the `CASE WHEN` expression.  
+You can now use `IF(<cond_expr>, <then_expr>, <else_expr>)` as a shorter equivalent to `CASE WHEN <cond_expr> THEN <then_expr> ELSE <else_expr> END`.
+
+**Added `INCREMENTAL` index optimization with `VACUUM`**  
+The [`VACUUM`](/sql_reference/commands/data-management/vacuum.html) statement now supports an `INDEXES = INCREMENTAL` option, allowing incremental optimization of related indexes. This new mode uses fewer resources compared to a full reevaluation, improving index layouts. Although incremental optimization may not achieve the optimal layout of a full reevaluation, it maintains a balance between performance and resource usage.
+
+**Added `MAX_CONCURRENCY` option to `VACUUM` statement**  
+The `VACUUM` command now supports the `MAX_CONCURRENCY` option, enabling you to limit concurrent processes during optimization. This allows for control of the number of concurrent processes in a `VACUUM` operation, optimizing resource usage and improving performance in multi-threaded environments.
+
+**Added longitude wrapping for `GEOGRAPHY` data**  
+Firebolt now automatically wraps longitude values outside the range of -180 to 180 degrees when parsing `GEOGRAPHY` data from WKT, GeoJSON, WKB, or using the `ST_GeogPoint` function. For example, `POINT(180.5 1)` is now correctly interpreted as `POINT(-179.5 1)`. This improvement simplifies geographic data handling.
+
+**Enhanced the `EXPLAIN` function to support all SQL statements except for DDL and DCL**  
+The [`EXPLAIN`](/sql_reference/commands/queries/explain.html) feature now supports analysis of all SQL statements. However, it does not provide output details for DDL (Data Definition Language) and DCL (Data Control Language) statements.
+
+### [](#performance-improvements)Performance Improvements
+
+**Optimized `COPY FROM` filtering performance**  
+Filters applied to pseudo columns, such as `$SOURCE_FILE_NAME` and `$SOURCE_FILE_TIMESTAMP`, are now pushed down to the file listing during the `COPY FROM` process when using multiple URL and pattern locations. This enhancement improves performance by reducing unnecessary data processing and speeds up data loading operations.
+
+### [](#bug-fixes)Bug Fixes
+
+**Fixed latitude handling for `LineString` in WKT**  
+Fixed an issue where latitudes outside the valid range of -90 to 90 degrees, in `LineString` data were incorrectly accepted when parsing from WKT. For example, `LINESTRING(0.5 1, 1 90.5)` now correctly returns an error instead of being interpreted as `LINESTRING(0.5 1, -179 89.5)`. This fix enhances data integrity and prevents erroneous geographic entries.
+
+## [](#firebolt-release-notes---version-416)Firebolt Release Notes - Version 4.16
+
+### [](#new-features-1)New Features
+
+**Added `MAX_CONCURRENCY` option to the `VACUUM` statement for enhanced concurrency control**  
+The [VACUUM](/sql_reference/commands/data-management/vacuum.html) statement now includes the `MAX_CONCURRENCY` option, allowing users to limit the number of concurrent streams. This improves control over resource usage during `VACUUM` operations.
+
+**Introduced the `INDEXES = ALL | NONE` for the `VACUUM` statement**  
+The [VACUUM](/sql_reference/commands/data-management/vacuum.html) statement now supports the `INDEXES = ALL | NONE` option, giving users control over whether indexes are optimized during `VACUUM` operations.
+
+**`VACUUM` now runs automatically**  
+Firebolt now automatically evaluates the data layout of tables and runs [VACUUM](/sql_reference/commands/data-management/vacuum.html) to optimize performance and storage efficiency. After [INSERT](/sql_reference/commands/data-management/insert.html), [UPDATE](/sql_reference/commands/data-management/update.html), or [DELETE](/sql_reference/commands/data-management/delete.html) operations modify data, the engine that performed the operation determines whether `VACUUM` is required. This decision is based on factors such as the number of deleted rows and the need to consolidate storage for faster query performance and reduced disk space usage.
+
+**Added support for casting text literals to interval literals**  
+Firebolt now supports casting text literals to interval literals using expressions like `'1 month'::INTERVAL`, making it easier to define time intervals in queries.
+
+**Added default value support for `GEOGRAPHY` columns**  
+Firebolt now supports default values for columns with the [GEOGRAPHY](/sql_reference/geography-data-type.html#geography-data-type) data type. For example, `CREATE TABLE geo_table (geo_column GEOGRAPHY DEFAULT 'GEOMETRYCOLLECTION EMPTY')` ensures consistency across database entries when no explicit value is provided.
+
+**Added `MIN_CLUSTERS` and `MAX_CLUSTERS` columns to `INFORMATION_SCHEMA.ENGINES`**  
+The [INFORMATION\_SCHEMA.ENGINES](/sql_reference/information-schema/engines.html) table now includes `MIN_CLUSTERS` and `MAX_CLUSTERS` columns, providing visibility into cluster configuration for improved database management.
+
+**Added support for `STATEMENT_TIMEOUT` to manage query run time limits**  
+Added support for `STATEMENT_TIMEOUT`. This feature specifies the number of milliseconds a statement is allowed to run. Any statement or query exceeding the specified time is canceled. A value of zero disables the timeout by default. Using `STATEMENT_TIMEOUT` helps prevent excessively long-running queries, improving system efficiency and resource use.
+
+**Added the PostgreSQL function `DATE(<arg>)` as an alternative to `<arg>::DATE`**  
+Firebolt now supports the `DATE(<arg>)` function, offering an alternative to the `<arg>::DATE` syntax for improved readability and usability in SQL queries.
+
+**Added support for `FROM` first syntax**  
+SQL queries can now use `FROM` before `SELECT`, allowing for more flexible query structures such as `FROM t SELECT a, SUM(b) GROUP BY a` or even `FROM t` without a `SELECT` clause.
+
+**Support for AWS PrivateLink is now in public preview**  
+[Firebolt now supports AWS PrivateLink](/Guides/security/privatelink.html), allowing Firebolt Enterprise customers to securely access the Firebolt API without exposing traffic to the public internet. AWS PrivateLink enhances security, minimizes data exposure, and improves network reliability by keeping traffic within AWS.
+
+**Added concurrency auto-scaling**  
+Engines can now be created with concurrency auto-scaling enabled, or modified to enable concurrency auto-scaling. Setting the `MIN_CLUSTERS` and `MAX_CLUSTERS` parameters on [CREATE ENGINE](/sql_reference/commands/engines/create-engine.html) and [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html) commands turns on concurrency auto-scaling: the engine will dynamically resize between the specified `MIN_CLUSTERS` and `MAX_CLUSTERS` values to match demand.
+
+**Firebolt introduces three fully managed editions**
+
+Firebolt now offers **Standard, Enterprise, and Dedicated editions**, each designed for different capabilities, security, and scalability needs.
+
+- **Standard**: High-performance, elastic scaling – in and out, up and down – for cost-efficient, fully managed analytics on a single cluster.
+- **Enterprise &amp; Dedicated**: Includes scaling capabilities like **multi-cluster scaling**, as well as advanced security features like **AWS PrivateLink**.
+- **Dedicated**: Built for regulated industries (finance, healthcare) with **single-tenant infrastructure** and compliance with **HIPAA, SOC 2, ISO**.
+
+Enterprise and Dedicated customers also get **24/7 support** with **faster support response times**, **Slack-based support**, and support from a **designated engineer**. For more information on Firebolt’s editions, refer to the [Pricing and billing](/Overview/billing/) page.
+
+### [](#performance-improvements-1)Performance Improvements
+
+**Introduced pruning for `GEOGRAPHY` columns at the tablet level to enhance query performance**  
+Firebolt now prunes [GEOGRAPHY](/sql_reference/geography-data-type.html#geography-data-type) data at the tablet level to enhance query performance. To activate spatial pruning on tables created before this release, run `VACUUM`. For additional details, see our [blog post](https://www.firebolt.io/blog/architecture-and-internal-representation-of-the-geography-data-type).
+
+**Added `INDEX_GRANULARITY` storage parameter to optimize table storage**  
+The `CREATE TABLE` statement now supports the `INDEX_GRANULARITY` storage parameter, allowing users to configure internal tablet range sizes for better performance based on query patterns.
+
+### [](#bug-fixes-1)Bug Fixes
+
+**Fixed permission conflicts on public schemas across multiple databases**  
+Resolved an issue where granting identical permissions on public schemas in different databases caused conflicts. This fix ensures correct permission application for improved database security.
+
+## [](#firebolt-release-notes---version-415)Firebolt Release Notes - Version 4.15
+
+### [](#new-features-2)New Features
+
+**Improved `EXPLAIN (STATISTICS)` to include estimated row counts and column distinct counts**
+
+The [EXPLAIN (STATISTICS)](/sql_reference/commands/queries/explain.html) function now provides estimated row counts and column distinct counts, when available. This enhancement offers more detailed insights for analyzing query performance.
+
+**Added a Tableau connector for the current version of Firebolt**
+
+[Tableau](https://www.tableau.com/) is a visual analytics platform that empowers users to explore, analyze, and present data through interactive visualizations. The current Firebolt connector in Tableau Exchange supports only an older version of Firebolt. You can now download the latest connector directly from Firebolt and integrate it with [Tableau Desktop](https://www.tableau.com/products/desktop) or [Tableau Server](https://www.tableau.com/products/server). Follow the installation instructions in [Integrate with Tableau](/Guides/integrations/tableau.html) to set up the updated connector.
+
+**Added a DBeaver connector for the current version of Firebolt**
+
+[DBeaver](https://dbeaver.io/) is a free, open-source database administration tool that supports multiple database types, provides a graphical interface for managing databases, running queries, and analyzing data. You can now connect to DBeaver using the [Firebolt JDBC driver](https://docs.firebolt.io/Guides/developing-with-firebolt/connecting-with-jdbc.html). Follow the instructions in [Integrate with DBeaver](/Guides/integrations/dbeaver.html) to set up a connection to DBeaver.
+
+**Added the Firebolt Resource Center to the Firebolt Workspace**
+
+The [Firebolt Resource Center](https://www.firebolt.io/resources) is now accessible from the **Firebolt Workspace**. Select the Firebolt icon in the bottom-right corner to access resources including the [Get started guide](/Guides/getting-started/), [Knowledge Center](https://www.firebolt.io/knowledge-center), [Documentation](https://docs.firebolt.io/), [Release notes](/Reference/release-notes/release-notes.html), Announcements, and a unified search tool covering all Firebolt resources.
+
+### [](#performance-improvements-2)Performance Improvements
+
+**Optimized `LEFT JOIN` conversion for better query performance**
+
+A nested `LEFT JOIN` can now be automatically replaced with a more efficient join when its results are not needed due to filtering in a later step. This optimization occurs when a `LEFT JOIN` removes rows where the right-hand side contains `NULL` values, effectively discarding the extra rows introduced by the earlier `LEFT JOIN`. In such cases, simplifying the join structure improves efficiency without altering query results. This conversion reduces unnecessary operations, lowering computational overhead and enhancing performance.
+
+**Improved performance by allowing multiple `INSERT INTO <tbl> VALUES ...` statements to be combined in a single request**
+
+Workloads that send multiple consecutive `INSERT INTO <tbl> VALUES ...` statements into the same table can now run much faster by sending all statements in a single request separated by semicolons. These statements are now automatically merged and processed together on the server within a single transaction, which means that either all of them succeed or fail. This improvement reduces network overhead and enhances performance for batch data insertion.
+
+### [](#behavior-changes)Behavior Changes
+
+**Use `NULL` instead of empty strings for passing unset TVF parameters**
+
+Table-valued functions (TVFs) such as [LIST\_OBJECTS](/sql_reference/functions-reference/table-valued/list-objects.html), [READ\_PARQUET](/sql_reference/functions-reference/table-valued/read_parquet.html), and [READ\_CSV](/sql_reference/functions-reference/table-valued/read_csv.html) that accept string named parameters like `aws_access_key_id` and `aws_role_arn` will no longer treat empty strings (`''`) as unset arguments. The empty strings will instead be forwarded to the credential provider and may return errors. If you want to pass an explicitly unset parameter, use `NULL` instead.
+
+### [](#bug-fixes-2)Bug Fixes
+
+**Resolved issue in distributed `GROUP BY` and `JOIN` planning**
+
+Resolved a bug in the optimization process for distributed `GROUP BY` and `JOIN` operators. This bug sometimes led to missed optimization opportunities and, in rare cases, incorrect results.
+
+**Fixed a bug in correlated `EXISTS` subqueries that caused duplicated outer tuples in query results**
+
+Fixed a bug with non-trivial correlated `EXISTS` subquery, which is a dependent subquery inside an `EXISTS` condition that references a column from an outer query. An example of this kind of query follows:
+
+```
+SELECT *,
+  EXISTS(SELECT 1 FROM table2 where COALESCE(table2.col_1, table2.col_2) = table1.col_1)
+FROM table1
+```
+
+Previously, if an outer table contained a value, and the inner table had two matching values, the outer table’s row would appear twice in the final result instead of just once. This happened because the query checked for matches individually for each row in the inner table, rather than treating the condition as a simple existence check.
+
+This bug fix corrected this issue by ensuring that the `EXISTS` condition only determines whether at least one match exists, without duplicating rows in the outer table. Now, each row in the outer table correctly appears once, with `TRUE` if a match exists and `FALSE` otherwise, improving the accuracy of query results.
+
+## [](#firebolt-release-notes---version-414)Firebolt Release Notes - Version 4.14
+
+### [](#new-features-3)New Features
+
+**Added `E2E_DURATION_US` to include total query time in Firebolt infrastructure for enhanced performance monitoring and optimization**
+
+Added a new column `E2E_DURATION_US` in the system tables `INFORMATION_SCHEMA.ENGINE_RUNNING_QUERIES`, `INFORMATION_SCHEMA.ENGINE_QUERY_HISTORY`, and `INFORMATION_SCHEMA.ENGINE_USER_QUERY_HISTORY` which shows the total time a query has spent within the Firebolt infrastructure. In contrast, `DURATION_US` measures only the time spent using the engine without considering retries or routing. The `E2E_DURATION_US` metric measures the total time a query takes from initiation to final result delivery, and includes all sub-components of latency such as routing, preparation, queuing, compilation, retries, and runtimes. For example, if a query starts a stopped engine, the engine’s startup time is included in the query’s end-to-end duration. This update provides a more accurate representation of total query latency, for performance monitoring and optimization.
+
+**Unhid `scanned_storage_bytes` and `scanned_cache_bytes` from information schema views**
+
+Unhid `scanned_storage_bytes` and `scanned_cache_bytes` columns from `information_schema.engine_query_history` and `information_schema.engine_user_query_history` views. These columns were previously accessible when explicitly used in a `SELECT` clause, but will now appear by default when you use `SELECT *`.
+
+### [](#performance-improvements-3)Performance Improvements
+
+**Enhanced data ingestion performance for `GEOGRAPHY` objects of type `POINT`**
+
+Improved data loading performance for `GEOGRAPHY` objects of type `POINT`, enabling up to four times faster loading of geographical point data for more efficient data integration and analysis.
+
+**Improved file listing times for large external scans**
+
+In operations that read data from Amazon S3 buckets such as external table scans or `COPY FROM` queries, Firebolt lists files in a URL to an Amazon S3 bucket. This process is constrained by the AWS API, which limits file listing to 1,000 files per request. Firebolt has increased the number of concurrent operations so that listing a large number of files is up to 3.5 times faster.
+
+**Added result cache support for cross and complex joins for improved performance**
+
+The [query result cache](/Reference/system-settings.html#result-cache) now supports queries using cross joins or complex joins with `OR` conditions and inequalities. This change reduces redundant calculations, improving query performance.
+
+### [](#bug-fixes-3)Bug Fixes
+
+**`USAGE` permissions are now required to access `INFORMATION_SCHEMA` views**
+
+Accessing `INFORMATION_SCHEMA` views now requires `USAGE` permissions on the database. Queries to `INFORMATION_SCHEMA` will fail if these permissions are missing, ensuring consistent enforcement across permission-restricted queries. Ensure that your database has the necessary permissions to prevent access issues.
+
+**Improved `EXPLAIN` command accuracy for default values of `DATE`, `TIMESTAMP`, and `TIMESTAMPTZ` columns**
+
+The `EXPLAIN` command now displays default values for columns of type `DATE`, `TIMESTAMP`, and `TIMESTAMPTZ` columns. This update fixes a bug that previously caused default values to be shown incompletely, improving clarity and accuracy in query plan analysis.
+
+**Resolved filtering issue for views in `information_schema.tables` to enforce user permissions**
+
+Fixed a bug in `information_schema.tables` which previously listed views that users were not authorized to access. Even though querying these views would fail, users could still see that they existed. Now `information_schema.tables` only lists views that users are allowed to access.
+
+## [](#firebolt-release-notes---version-413)Firebolt Release Notes - Version 4.13
+
+### [](#new-features-4)New Features
+
+**`GRANT ALL ON ACCOUNT` and `REVOKE ALL ON ACCOUNT` statements for role-based privileges**  
+The statements `GRANT ALL ON ACCOUNT account_name TO role_name` and `REVOKE ALL ON ACCOUNT account_name FROM role_name` are now supported. They grant or revoke all account-related privileges to the specified role `role_name`.
+
+**Support for nested arrays in Parquet files**  
+You can now ingest Parquet files containing nested array structures at any depth. For example: `array(array(array(string)))`.
+
+### [](#behavior-changes-1)Behavior Changes
+
+**Removed secured objects from `information_schema` views**  
+Users can now only access information about objects for which they have the appropriate permissions or ownership for in [information\_schema views](/sql_reference/information-schema/views.html).
+
+### [](#bug-fixes-4)Bug Fixes
+
+**`@` character support restored in usernames**  
+The usage of character `@` is allowed in usernames again, which was previously restricted. The following statements are now valid and will not cause errors:
+
+```
+CREATE USER "user@example.com";
+ALTER USER user_name RENAME TO "user@example.com";
+```
+
+**Resolved memory overuse during CSV import**  
+Resolved a memory overconsumption problem that occurred when importing CSV files into existing tables.
+
+**Resolved `EXPLAIN VACUUM` and `EXPLAIN` to improve error handling and result accuracy**  
+The following behavior of `EXPLAIN VACUUM` has been updated:
+
+1. If a table is fully vacuumed, no further actions are performed, and the message “Table is fully vacuumed, no vacuum jobs were executed” is returned to the user.
+2. The `EXPLAIN VACUUM` output no longer returns an empty result when the vacuumed object is an aggregating index.
+3. `EXPLAIN` has been updated to show an error if the specified relation does not exist.
+
+**Fixed incorrect evaluation of `IS NULL` in outer joins**  
+Fixed an issue where `IS NULL` predicates on non-nullable columns from the non-preserving side of an outer join were incorrectly reduced to `FALSE` during common table expression (CTE) optimization. When the optimizer attempted to fuse multiple CTEs, it mistakenly replaced `t2.x IS NULL` with `FALSE`, altering query semantics and producing incorrect results. This occurred because `t2.x`, though defined as non-nullable, became nullable when used in a left join. The fix ensures that `IS NULL` predicates are correctly preserved during optimization.
+
+## [](#firebolt-release-notes---version-412)Firebolt Release Notes - Version 4.12
+
+### [](#new-features-5)New Features
+
+**Added `ST_S2CELLIDFROMPOINT` to retrieve the [S2 Cell ID](http://s2geometry.io/devguide/s2cell_hierarchy) of a `GEOGRAPHY` Point**
+
+You can now use [ST\_S2CELLIDFROMPOINT](/sql_reference/functions-reference/geospatial/st_s2cellidfrompoint.html) to retrieve the S2 cell ID, which identifies the region on Earth that fully contains, or covers, a single Point `GEOGRAPHY` object. You can also specify a cell resolution level.
+
+**Added keyboard shortcuts to the Firebolt Develop Space**
+
+The Firebolt **Develop Space** user interface added the following Windows/Mac [keyboard shortcuts](/Guides/query-data/using-the-develop-workspace.html#keyboard-shortcuts-for-the-develop-space):
+
+- Ctrl + Alt + E / Ctrl + ⌘ + E – Toggle expanding or collapsing query results.
+- Ctrl + Alt + N / Ctrl + ⌘ + N – Create a new script.
+- Ctrl + Alt + [ / Ctrl + ⌘ + [ – Jump to the previous script.
+- Ctrl + Alt + ] / Ctrl + ⌘ + ] – Jump to the next script.
+
+**Introduced the `INFORMATION_SCHEMA.ROUTINES` view for built-in functions and operators**
+
+Added the [INFORMATION\_SCHEMA.ROUTINES](/sql_reference/information-schema/routines.html) view to return information about all of Firebolt’s built-in functions and operators including their database, schema, name, type, return data type, parameter data types, and whether they are deterministic.
+
+**Added support for the `GEOGRAPHY` data type in external tables using CSV and JSON formats**
+
+Firebolt can now read columns of type `GEOGRAPHY` from external tables in CSV or JSON format, which allows the querying of geospatial data including Points and Polygons.
+
+**Added a new `MONITOR USAGE` privilege**
+
+You can use the `MONITOR USAGE` privilege to view all queries running on an engine using [information\_schema.engine\_query\_history](/sql_reference/information-schema/engine-query-history.html) or [information\_schema.engine\_running\_queries](/sql_reference/information-schema/engine-running-queries.html) views.
+
+**Introduced support for network policy `ADD`/`REMOVE` commands**  
+Admins can now append or remove specific IP addresses in `ALLOW` or `BLOCK` lists without overriding existing values. This update simplifies network policy management when handling large IP lists and reduces the risk of concurrent updates overwriting each other.
+
+### [](#performance-improvements-4)Performance Improvements
+
+**Improved performance of the `ST_COVERS`, `ST_CONTAINS`, and `ST_INTERSECTS` functions**
+
+Optimized the [ST\_COVERS](/sql_reference/functions-reference/geospatial/st_covers.html), [ST\_CONTAINS](/sql_reference/functions-reference/geospatial/st_contains.html), and [ST\_INTERSECTS](/sql_reference/functions-reference/geospatial/st_intersects.html) functions to improve performance when processing LineStrings and Points with non-intersecting inputs, and Polygons with inputs that do not intersect their boundaries.
+
+**Improved performance of the `REGEXP_LIKE_ANY` function**
+
+The [REGEXP\_LIKE\_ANY](/sql_reference/functions-reference/string/regexp-like-any.html) function now performs more efficiently when matching against multiple patterns by compiling a single combined [RE2](https://github.com/google/re2/) regular expression object instead of evaluating each pattern separately.
+
+### [](#behavior-changes-2)Behavior Changes
+
+**Updated user name rules to improve consistency and validation**
+
+The following changes affect the use of user names in [CREATE USER](/sql_reference/commands/access-control/create-user.html) AND [ALTER USER](/sql_reference/commands/access-control/alter-user.html):
+
+- The `@` character is no longer allowed in user names.
+- The range of permissible characters in user names is expanded. For more information, see [CREATE USER](/sql_reference/commands/access-control/create-user.html).
+- When renaming a user with [ALTER USER](/sql_reference/commands/access-control/alter-user.html) `old_name RENAME TO new_name`, the `new_name` must now comply with the updated user name rules.
+- Any new names created with [CREATE USER](/sql_reference/commands/access-control/create-user.html) must now comply with the updated user name rules.
+
+### [](#bug-fixes-5)Bug Fixes
+
+**Fixed an error where `APACHE_DATASKETCHES_HLL_ESTIMATE` failed for `NULL` inputs**
+
+Resolved an error in the [APACHE\_DATASKETCHES\_HLL\_ESTIMATE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-estimate.html) function that occurred if any of its input values were `NULL`. The function can now process `NULL` inputs.
+
+**Resolved issue that allowed account lockout on last login**
+
+Fixed an issue where the `ALTER USER SET LOGIN/SERVICE_ACCOUNT=...` statement could lock out the only active login in an account, rendering the account inaccessible. The operation now fails with an explicit error message in such cases.
+
+**Fixed incorrect ownership modification for `information_schema`**
+
+The statement `ALTER SCHEMA information_schema SET OWNER owner_name;` previously succeeded, which was incorrect, because `information_schema` cannot be modified. The operation now fails with an explicit error message.
+
+**Fixed an out-of-memory error during large CSV imports**
+
+Updated the ingestion pipeline for [COPY FROM](/sql_reference/commands/data-management/copy-from.html) to ensure that large CSV files without a predefined schema can load into new tables without causing memory errors. This error did not affect external tables.
+
+**Prevent running queries when using a dropped database**
+
+When the current database does not exist, such as when it has been dropped, most queries fail as expected. We fixed a bug where some queries against specific `information_schema` views, such as `engines`, `catalogs`, `applicable_roles`, would still succeed in such cases. These queries now fail consistently, like all other queries against a non-existent database. For example, running `SELECT * FROM information_schema.engines` when the database is dropped previously worked, but now fails.
+
+## [](#firebolt-release-notes---version-411)Firebolt Release Notes - Version 4.11
+
+### [](#new-features-6)New Features
+
+**Introduced the `GEOGRAPHY` data type and functions for geospatial data handling \[public preview]**
+
+Added a new [GEOGRAPHY](/sql_reference/geography-data-type.html) data type and functions for working with geospatial data. Firebolt supports the three industry standard formats [Well-Known Text (WKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry), [Well-Known Binary (WKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary), and [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946) for geospatial data.
+
+This public preview release includes the following functions:
+
+- [ST\_ASBINARY](/sql_reference/functions-reference/geospatial/st_asbinary.html) – Converts shapes of the `GEOGRAPHY` data type to the [Well-Known Binary (WKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary) format for geographic objects.
+- [ST\_ASEWKB](/sql_reference/functions-reference/geospatial/st_asewkb.html) – Converts shapes of the `GEOGRAPHY` data type to the [extended Well-Known Binary (EWKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Format_variations) format using Spatial Reference Identifier (SRID) 4326, which corresponds to the [WGS84](https://en.wikipedia.org/wiki/World_Geodetic_System#WGS_84) coordinate system.
+- [ST\_ASGEOJSON](/sql_reference/functions-reference/geospatial/st_asgeojson.html) – Converts shapes of the `GEOGRAPHY` data type to the [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946) format.
+- [ST\_ASTEXT](/sql_reference/functions-reference/geospatial/st_astext.html) – Converts shapes of the `GEOGRAPHY` data type to the [Well-Known Text (WKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) format.
+- [ST\_CONTAINS](/sql_reference/functions-reference/geospatial/st_contains.html) – Determines if one `GEOGRAPHY` object fully contains another.
+- [ST\_COVERS](/sql_reference/functions-reference/geospatial/st_covers.html) – Determines if one `GEOGRAPHY` object fully encompasses another.
+- [ST\_DISTANCE](/sql_reference/functions-reference/geospatial/st_distance.html) – Calculates the shortest distance, measured as a geodesic arc between two `GEOGRAPHY` objects, measured in meters.
+- [ST\_GEOGFROMGEOJSON](/sql_reference/functions-reference/geospatial/st_geogfromgeojson.html) – Constructs a `GEOGRAPHY` object from a [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946) string.
+- [ST\_GEOGFROMTEXT](/sql_reference/functions-reference/geospatial/st_geogfromtext.html) – Constructs a `GEOGRAPHY` object from a [Well-Known Text (WKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) string.
+- [ST\_GEOGFROMWKB](/sql_reference/functions-reference/geospatial/st_geogfromwkb.html) – Constructs a `GEOGRAPHY` object from a [Well-Known Binary](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary) (WKB) byte string.
+- [ST\_GEOGPOINT](/sql_reference/functions-reference/geospatial/st_geogpoint.html) – Constructs a Point in the `GEOGRAPHY` data type created from specified longitude and latitude coordinates.
+- [ST\_INTERSECTS](/sql_reference/functions-reference/geospatial/st_intersects.html) – Determines whether two input `GEOGRAPHY` objects intersect each other.
+- [ST\_X](/sql_reference/functions-reference/geospatial/st_x.html) – Extracts the longitude coordinate of a `GEOGRAPHY` Point.
+- [ST\_Y](/sql_reference/functions-reference/geospatial/st_y.html) – Extracts the latitude coordinate of a `GEOGRAPHY` Point.
+
+**Added keyboard shortcuts to the Firebolt Develop Space**
+
+The user interface in the Firebolt **Develop Space** added the following [keyboard shortcuts](/Guides/query-data/using-the-develop-workspace.html#keyboard-shortcuts-for-the-develop-space):
+
+- Cmd + Enter – Runs the current query.
+- Cmd+Shift+Enter – Runs all queries in a script.
+
+**Added the window function `FIRST_VALUE`**
+
+Added a new [FIRST\_VALUE](/sql_reference/functions-reference/window/first-value.html) window function that returns the first value evaluated in a specified window frame.
+
+## [](#firebolt-release-notes---version-410)Firebolt Release Notes - Version 4.10
+
+### [](#new-features-7)New Features
+
+**Added `CREATE TABLE CLONE` to clone an existing table in a database**
+
+You can create a clone of an existing table in a database using `CREATE TABLE CLONE`, which is extremely fast because it copies the table structure and references without duplicating the data. The clone functions independently of the original table. Any changes to the data or schema of either table will not affect the other.
+
+**Added 3-part identifier support for specifying databases in queries**
+
+You can now reference a database other than the current one in queries by using 3-part identifiers, which specify the database, schema, and object. For example, even if you previously selected a database `db` by using `USE DATABASE db`, you can still query a different database by using a query such as `SELECT * FROM other_db.public.t`. The limitation still exists that every query only addresses a single database.
+
+**Added `ALTER TABLE ADD COLUMN` to add a column to an existing table**
+
+You can now use `ALTER TABLE ADD COLUMN` to add columns to Firebolt-managed tables. This functionality is temporarily limited to tables that were created on Firebolt version 4.10 or higher.
+
+**Added support of `ALTER TABLE RENAME` command** You can use `ALTER TABLE RENAME` to change the name of Firebolt-managed tables. This functionality is temporarily limited to tables created on Firebolt version 4.10 or higher.
+
+**Added support for external file access using AWS session tokens**
+
+You can now use `<AWS_SESSION_TOKEN>` with access keys to securely authenticate and access external files on AWS with the following features:
+
+- The [COPY TO](/sql_reference/commands/data-management/copy-to.html) and [COPY FROM](/sql_reference/commands/data-management/copy-from.html) commands.
+- [External tables](/Guides/loading-data/working-with-external-tables.html) located in an Amazon S3 bucket.
+- The following table-valued functions: `read_parquet`, `read_csv`, and `list_objects`.
+
+### [](#behavior-changes-3)Behavior Changes
+
+**Enhanced PostgreSQL compliance for casting data types from text to float**
+
+Cast from text to floating-point types is now compliant with PostgreSQL with the following improvements:
+
+1. **The correct parsing of positive floats** – A plus sign (`+`) preceding a float is now handled correctly. Example: `'+3.4'`.
+2. **Exponent-only input** – Float values starting with an exponent `'e'` or `'E'` are rejected. Example: `'E4'`.
+3. **Incomplete exponents** – Float values ending with an exponent without a subsequent exponent value are rejected. Example: `'4e+'`.
+
+**Account-level rate limits implemented for the system engine**
+
+Firebolt has implemented account-level rate limits to ensure equitable resource usage among all users of the system engine. When these limits are exceeded, requests will be rejected with the following error message: `429: Account system engine resources usage limit exceeded`. This rate limit targets accounts with exceptionally high resource consumption. Accounts with typical resource usage should not be affected and require no further action.
+
+### [](#bug-fixes-6)Bug Fixes
+
+**Corrected runtime reporting**
+
+Resolved an issue where the runtime displayed in Firebolt’s user interface and JSON responses omitted including processing times for some query steps.
+
+**Resolved “Invalid Input Aggregate State Type” error with aggregating indexes**
+
+Fixed an issue where the “invalid input aggregate state type” error could occur when queries read from aggregating indexes that defined a `COUNT(*)` aggregate function before other aggregate functions. After this fix, such aggregating indexes can now be queried correctly without needing to be rebuilt.
+
+**Fixed a rare bug in subresult caching logic**
+
+Addressed a rare issue in the logic for caching and reusing subresults that could cause query failures with specific query patterns. This issue did not impact the correctness of query results.
+
+**Resolved issue preventing schema owners from granting “ANY” privileges**
+
+Fixed an issue where schema owners were unable to grant “ANY” privileges on their schema to other users.  
+For example:
+
+```
+GRANT SELECT ANY ON SCHEMA public TO ...
+```
+
+Schema owners can now execute this command which allows the specified user or role to perform SELECT operations on any table.
+
+## [](#firebolt-release-notes---version-49)Firebolt Release Notes - Version 4.9
+
+### [](#new-features-8)New Features
+
+**Added the `enable_result_cache` setting for controlling query result caching during benchmarking**
+
+You can set `enable_result_cache` to `FALSE` to disable the use of Firebolt’s result cache, which is set to `TRUE` by default. Disabling result cashing can be useful for benchmarking query performance. When `enable_result_cache` is disabled, resubmitting the same query will recompute the results rather than retrieving them from cache. For more information, see [Result Cache](/Reference/system-settings.html#result-cache).
+
+**Added `LAG` and `LEAD` support for negative offsets.**
+
+The second parameter in both [LAG](/sql_reference/functions-reference/window/lag.html) and [LEAD](/sql_reference/functions-reference/window/lead.html) can now accept negative numbers. Given a negative number, a `LAG` will become a `LEAD` and vice versa. For example, `LAG(x,-5,3)` is the same as `LEAD(x,5,3)`.
+
+### [](#performance-improvements-5)Performance Improvements
+
+**Faster string searches for case-insensitive simple regular expressions in `REGEXP_LIKE`**
+
+Simple regular expressions in [REGEXP\_LIKE](/sql_reference/functions-reference/string/regexp-like.html) with case-insensitive matching, using the `i` flag, now use the same optimized string search implementation as [ILIKE](/sql_reference/functions-reference/string/ilike.html), achieving up to three times faster runtimes in observed cases.
+
+### [](#bug-fixes-7)Bug Fixes
+
+**Empty character classes in regular expressions**
+
+Fixed a rare case where empty character classes were mistakenly interpreted as valid character classes instead of being treated as raw characters. In cases like `[]a]`, the expression is now correctly interpreted as a pattern that matches any single character from the list `]a`, rather than treating `[]` as an empty character class followed by `a]`.
+
+**Trailing backslash in regular expressions**
+
+Fixed a rare case where invalid regular expressions with a trailing backslash `\` were accepted.
+
+## [](#firebolt-release-notes---version-48)Firebolt Release Notes - Version 4.8
+
+### [](#new-features-9)New Features
+
+**Introduced new bitwise shift functions `BIT_SHIFT_RIGHT` and `BIT_SHIFT_LEFT`**
+
+The following bitwise shift functions are now supported:
+
+- `BIT_SHIFT_RIGHT` shifts the bits of a number to the right by a specified number of positions, which effectively divides the number by `2` for each position shifted.
+- `BIT_SHIFT_LEFT` shifts the bits of a number to the left by a specified number of positions, which effectively multiples the number by `2` for each position shifted.
+
+**Introduced new trigonometric functions `ACOS`, `ATAN`, `ASIN`, `COS`, `COT`, `TAN`, `DEGREES`, and `PI`**
+
+The following trigonometric functions are now supported:
+
+- `ACOS` calculates the arccosine of a value in radians.
+- `ATAN` calculates the arctangent of a value in radians.
+- `ASIN` calculates the arcsine of a value in radians.
+- `COS` calculates the cosine of a value in radians.
+- `COT` calculates the cotangent of a value in radians.
+- `TAN` calculates the tangent of a value in radians.
+- `DEGREES` converts a value in radians to degrees.
+- `PI` returns π as a value of type `DOUBLE PRECISION`.
+
+**Introduced the `timezone` query-level setting with `time_zone` as an alias**
+
+Added the `timezone` query-level setting. The previous `time_zone` query setting still works, and is now an alias for `timezone`.
+
+**Introduced new `PERCENTILE_CONT` and `MEDIAN` aggregate functions**
+
+Added the following aggregate functions:
+
+- `PERCENTILE_CONT` calculates a specified percentile of values in an ordered dataset.
+- `MEDIAN` returns the median of a given column. It is equivalent to `PERCENTILE_CONT(0.5)`: half the values in the column are smaller, and half are bigger than the returned value. If the number of values in the column is even, `MEDIAN` returns the arithmetic mean of the two middle values.
+
+**Added support to meet HIPAA regulations for health information**
+
+Added [support to meet federal HIPAA regulations](/Overview/Security/security.html#hipaa-compliance) to ensure the confidentiality, integrity, and availability of electronic protected health information within the Firebolt platform.
+
+### [](#performance-improvements-6)Performance Improvements
+
+**Improved expression comparison logic within queries**
+
+Improved expression comparison logic to better recognize identical expressions within queries. This enhancement supports a broader range of queries and boosts the overall quality of query plans.
+
+**Improving cold reads by reducing the amount of Amazon S3 requests needed to load data**
+
+Improved the performance of cold reads by minimizing the number of Amazon S3 requests required to load data. In the case of tiny tablets, this improvement lead to a 50% improvement in performance.
+
+### [](#bug-fixes-8)Bug Fixes
+
+**Fixed a bug preventing view creation with type conversions to array types**
+
+Fixed an issue that prevented users from creating database views that involve type conversion to array types.
+
+## [](#db-version-47)DB version 4.7
+
+### [](#new-features-10)New Features
+
+**Added Snappy compression support to the COPY TO command for PARQUET output format**  
+You can now apply Snappy compression, which is faster than GZIP, when using `COPY TO` with `TYPE=PARQUET`. Specify `COMPRESSION=SNAPPY` within `COPY TO` to enable this.
+
+**Added `information_schema.engine_user_query_history` view to log only user-initiated queries**  
+Added a new query history view, `information_schema.engine_user_query_history`, which shows all queries initiated by users. This view filters information from `information_schema.engine_query_history` view, which logs all engine queries including system-generated ones like UI updates and page-load requests.
+
+**Added support for `information_schema.enabled_roles`**  
+Added a new view `information_schema.enabled_roles` which lists the roles available in the account.
+
+**Added a system setting `enable_subresult_cache` for controlling subresult reuse**  
+A new system setting `enable_subresult_cache` allows users to enable or disable caching of query subresults for subsequent reuse. Caching remains enabled by default. This setting allows users to temporarily disabling caching, e.g. for benchmarking purposes.
+
+**Added “FROM first” syntax allowing the `FROM` clause to precede the `SELECT` clause**  
+Added support for the “FROM first” syntax, which allows placing the `FROM` clause before the `SELECT` clause, for example `FROM t SELECT a, SUM(b) GROUP BY a`. You can now also omit the `SELECT` clause, as in `FROM t`.
+
+**Introduced a new function `GEN_RANDOM_UUID_TEXT` to generate a universally unique identifier (UUID)**  
+The new function `GEN_RANDOM_UUID_TEXT` accepts no arguments and returns a version `4` UUID as defined by [RFC-4122](https://tools.ietf.org/html/rfc4122#section-4.4) as a `TEXT` value.
+
+**Introduced `~` and `!~` operators as aliases for `REGEXP_LIKE` and `NOT REGEXP_LIKE`**  
+Added the `~` operator as an alias for `REGEXP_LIKE`, and the `!~` operator, which serves as an alias for `NOT REGEXP_LIKE`.
+
+**Introduced JSON functions `JSON_POINTER_EXTRACT_KEYS`, `JSON_POINTER_EXTRACT_VALUES`, `JSON_POINTER_EXTRACT_TEXT`**  
+The following new JSON functions are now supported:
+
+- `JSON_POINTER_EXTRACT_KEYS` extracts keys from a JSON object
+- `JSON_POINTER_EXTRACT_VALUES` extracts values from a JSON object
+- `JSON_POINTER_EXTRACT_TEXT` extracts the JSON string value as SQL TEXT
+
+**Introduced trigonometric functions `RADIANS`, `SIN`, `ATAN2`**  
+The following trigonometric functions are now supported:
+
+- `RADIANS` to convert degrees into radians
+- `SIN` to compute the sine in radians
+- `ATAN2` to calculate the arctangent with two arguments. `ATAN2(y,x)` is the angle between the positive x-axis and the line from the origin to the point `(x,y)`, expressed in radians.
+
+**Introduced new functions to calculate standard deviation and variance for both samples and populations**  
+New functions that accept `REAL` and `DOUBLE` inputs and return standard deviations and variances:
+
+- `STDDEV_SAMP` - Returns the sample standard deviation of all non-`NULL` numeric values produced by an expression, which measures how spread out values are in a sample.
+- `STDDEV_POP` - Returns the population standard deviation of all non-`NULL` numeric values produced by an expression, which measures how spread out values are in an entire population.
+- `VAR_SAMP` - Returns the sample variance of all non-`NULL` numeric values produced by an expression, which measures the average of the squared differences from the sample mean, indicating how spread out the values are within a sample.
+- `VAR_POP` - Returns the population variance of all non-`NULL` numeric values produced by an expression. The population variance measures the average of the squared differences from the population mean, indicating how spread out the values are within the entire population.
+
+**Introduced new array functions `ARRAY_ALL_MATCH` and `ARRAY_ANY_MATCH`**  
+The new functions `ARRAY_ALL_MATCH` and `ARRAY_ANY_MATCH` accept an (optional) lambda function and an array and return `TRUE` if all elements (`ARRAY_ALL_MATCH`) or any element (`ARRAY_ANY_MATCH`) satisfy the lambda condition, and `FALSE` otherwise. When no lambda is passed, the array has to be of type `BOOLEAN`, and the identity lambda `x -> x` is used.
+
+### [](#performance-improvements-7)Performance Improvements
+
+**Improved performance of `JSON_EXTRACT`, `JSON_EXTRACT_ARRAY`, and `JSON_VALUE` functions**  
+Enhanced the performance of the `JSON_EXTRACT`, `JSON_EXTRACT_ARRAY`, and `JSON_VALUE` functions.
+
+### [](#behavior-changes-4)Behavior Changes
+
+**Updated sorting method for array columns with `NULL` values to align with PostgreSQL behavior**
+
+The sorting method for array columns containing `NULL` values has been updated to ensure that `ASC NULLS FIRST` places `NULL` values before arrays, and `DESC NULLS LAST` places `NULL` values after arrays, which aligns with PostgreSQL behavior.
+
+The following code example creates a temporary table `tbl` which contains three rows: a `NULL` array, an array with the value `1`, and an array with a `NULL` element. Then, a `SELECT` statement sorts all rows in ascending order:
+
+```
+WITH tbl(i) AS (
+  SELECT NULL::INT[]
+  UNION ALL
+  SELECT ARRAY[1]::INT[]
+  UNION ALL
+  SELECT ARRAY[NULL]::INT[]
+)
+SELECT * FROM tbl ORDER BY i ASC NULLS FIRST;
+```
+
+The query previously returned `{NULL}, {1}, NULL`, but now returns `NULL, {1}, {NULL}`.
+
+`NULLS FIRST` and `NULLS LAST` apply to the array itself, not to its elements. By default, ascending order (`ASC`) assumes `NULLS LAST`, while descending order (`DESC`) assumes `NULLS FIRST` when sorting arrays.
+
+**Allowed use of the SESSION\_USER function without parentheses**
+
+The `SESSION_USER` function can now be used without parentheses, like this: `SELECT SESSION_USER`. As a result, any column named `session_user` now needs to be enclosed in double quotes as follows: `SELECT 1 AS "session_user"` or `SELECT "session_user" FROM table`.
+
+### [](#bug-fixes-9)Bug Fixes
+
+**Corrected JSON output format to display NaN values consistently as `nan`**  
+The JSON output format previously showed some NaN values as `-nan`. This was corrected to consistently display NaN values as `nan` in the JSON output.
+
+**Resolved an issue with `CHECKSUM` and `HASH_AGG` failing when combining literals and table columns**  
+Fixed an issue where the `CHECKSUM` and `HASH_AGG` functions failed when used with a combination of literals and table columns.
+
+**Fixed a rare inaccuracy that could cause incorrect results on multi-node engines when performing certain `UNION ALL` operations**  
+Fixed a rare inaccuracy when performing certain `UNION ALL` operations on subqueries that are the result of aggregations or joins on overlapping but distinct keys, followed by an aggregation or join on the common keys of the subqueries’ aggregations or joins.
+
+**Fixed a rare inaccuracy that could cause incorrect results with CTEs using `RANDOM()` in specific join scenarios**  
+Fixed a rare inaccuracy that caused incorrect results when a common table expression using the `RANDOM()` function was used multiple times, and at least one of these uses was on the probe side of a join involving a primary index key of the underlying table.
+
+## [](#db-version-46)DB version 4.6
+
+**September 2024**
+
+### [](#new-features-11)New Features
+
+**`COPY TO` support for the `SNAPPY` compression type**
+
+[COPY TO](/sql_reference/commands/data-management/copy-to.html) now supports `SNAPPY` as a new compression option for Parquet files. This enhancement offers greater flexibility for managing file size and performance, particularly for workloads requiring faster compression. Each file is written in Parquet format, with the specified compression applied to the data pages in the column chunks.
+
+**`COPY FROM` support for filtering by source file metadata**
+
+[COPY FROM](/sql_reference/commands/data-management/copy-from.html) now supports filtering by source file metadata using the `WHERE` clause.
+
+**Added support for vector distance calculations with new functions**
+
+Firebolt has added support for vector distance and similarity calculations with the following new functions: [VECTOR\_COSINE\_DISTANCE](/sql_reference/functions-reference/vector/vector-cosine-distance.html), [VECTOR\_MANHATTAN\_DISTANCE](/sql_reference/functions-reference/vector/vector-manhattan-distance.html), [VECTOR\_EUCLIDEAN\_DISTANCE](/sql_reference/functions-reference/vector/vector-euclidean-distance.html), [VECTOR\_SQUARED\_EUCLIDEAN\_DISTANCE](/sql_reference/functions-reference/vector/vector-squared-euclidean-distance.html), [VECTOR\_COSINE\_SIMILARITY](/sql_reference/functions-reference/vector/vector-cosine-similarity.html), and [VECTOR\_INNER\_PRODUCT](/sql_reference/functions-reference/vector/vector-inner-product.html).
+
+### [](#behavior-changes-5)Behavior Changes
+
+**Introduced `SHOW CATALOGS` statement and aliased `SHOW DATABASES` to it while deprecating `SHOW DATABASE X`**
+
+A new statement `SHOW CATALOGS` now acts as an alias for `SHOW DATABASES`. The statement `SHOW DATABASE X` is no longer supported.
+
+**`COPY FROM` now unzips Parquet files with gzip extensions**
+
+Before version 4.6, the `COPY FROM` command did not apply file-level decompression to Parquet files with a `.gzip` or `.gz` extension. The command treated these files as standard Parquet files, assuming that any compression existed only within the internal Parquet format structure.
+
+With the release of version 4.6, `COPY FROM` now processes Parquet files similarly to other formats. When a Parquet file has a `.gz` or `.gzip` extension, the command will first decompress the file before reading it as a Parquet format file. Hence, it will now fail while reading internally compressed Parquet files with gzip extensions. Users experiencing issues with loading files after this change should contact the support team at support@firebolt.io for assistance.
+
+### [](#bug-fixes-10)Bug Fixes
+
+**Fixed a rare bug that caused some query failures from incorrect computation of cacheable subresults**
+
+Fixed a rare bug impacting the logic that determined which subresults could be cached and reused. This issue could have caused query failures in certain patterns, but it did not impact the accuracy of the query outcomes.
+
+**Updated name of aggregatefunction2 to aggregatefunction in explain output**
+
+The name `aggregatefunction2` has been updated to `aggregatefunction` in the [EXPLAIN](/sql_reference/commands/queries/explain.html) output.
+
+**Fixed incorrect results in `ARRAY_AGG` expressions by excluding `NULL` values for false conditions in aggregating indexes**
+
+Aggregate expressions like `ARRAY_AGG(CASE WHEN <cond> THEN <column> ELSE NULL END)` previously returned incorrect results by excluding `NULL` values for rows when the condition was `FALSE`.
+
+## [](#db-version-45)DB version 4.5
+
+**September 2024**
+
+### [](#new-features-12)New Features
+
+**Allowed casting from `TEXT` to `DATE` with truncation of timestamp-related fields** Casting from `TEXT` to `DATE` now supports text values containing fields related to timestamps. These fields are accepted, but truncated during conversion to `DATE`.
+
+The following code example casts the `TEXT` representation of the timestamp `2024-08-07 12:34:56.789` to the `DATE` data type. The conversion truncates the time portion, leaving only the date, as follows:
+
+Example:
+
+```
+SELECT '2024-08-07 12:34:56.789'::DATE`
+```
+
+Results in
+
+```
+DATE `2024-08-07`
+```
+
+**Added the `CONVERT_FROM` function**
+
+Added the `CONVERT_FROM` function that converts a `BYTEA` value with a given encoding to a `TEXT` value encoded in UTF-8.
+
+**Added the BITWISE aggregate functions**
+
+Added support for the following functions: BIT\_OR (bitwise OR), BIT\_XOR (bitwise exclusive OR), and BIT\_AND (bitwise AND).
+
+**Added the `REGEXP_LIKE_ANY` function**
+
+Added the `REGEXP_LIKE_ANY` function that checks whether a given string matches any regular expression pattern from a specified list of patterns.
+
+### [](#bug-fixes-11)Bug Fixes
+
+**Updated `created` and `last_altered` column types in `information_schema.views` from `TIMESTAMP` to `TIMESTAMPTZ`** The data types of the `created` and `last_altered` columns in `information_schema.views` have been changed from `TIMESTAMP` to `TIMESTAMPTZ`.
+
+**Fixed runtime constant handling in the sort operator** Fixed the handling of runtime constants in the sort operator. Now, the sort operator can be correctly combined with `GENERATE_SERIES`. For example, the query `SELECT x, GENERATE_SERIES(1,7,3) FROM GENERATE_SERIES(1,3) t(x)` now correctly displays values `1` to `3` in the first column, instead of just `1`.
+
+## [](#db-version-44)DB version 4.4
+
+**August 2024**
+
+### [](#new-features-13)New Features
+
+**Extended support for date arithmetic**
+
+Now you can subtract two dates to get the number of elapsed days. For example, `DATE '2023-03-03' - DATE '1996-09-03'` produces `9677`.
+
+**Role-based permissions for COPY FROM and external tables**
+
+Added support for role-based permissions (ARNs) to the COPY FROM command and external table operations.
+
+**Added `trust_policy_role` column to `information_schema.accounts` view for S3 access**
+
+Added a new column `trust_policy_role` to the `information_schema.accounts` view. This column shows the role used by Firebolt to access customer S3 buckets.
+
+**Enabled selection of external tables’ pseudo columns without adding data columns**
+
+Users can now select an external table’s pseudo columns (source file name, timestamp, size, and etag) without adding any data columns. For example, `select $source_file_timestamp from t_external` returns the file timestamps for each row. The query `select count($source_file_timestamp) from t_external` returns the total number of rows in the external table, similar to `count(*)`. The query `select count(distinct $source_file_name) from t_external` returns the number of distinct objects containing at least one row in the source S3 location. Regarding `count(*)` performance, formats like CSV or JSON still require reading the data fully to determine an external file’s row count. However, Parquet files provide the row count as part of the file header, and this is now used instead of reading the full data.
+
+**Extended support for arbitrary join conditions, including multiple inequality predicates**
+
+We now support more join conditions. As long as there is one equality predicate comparing a left column to a right column of the join (not part of an OR expression), the remaining join condition can now be an arbitrary expression. The limitation on the number of inequality predicates was removed.
+
+**New functions `URL_ENCODE` and `URL_DECODE`**
+
+We added support for the `URL_ENCODE` and `URL_DECODE` functions.
+
+**New logarithm functions `ln`, `log`**
+
+We added support for calculating logarithms. The natural logarithm is available using `ln(val double precision)`. The base 10 logarithm is available using `log(val double precision)`. Logarithms with custom bases are available using `log(base double precision, val double precision)`.
+
+**New function \`SQRT**
+
+Added support for the `SQRT` function to compute the square root.
+
+**New functions `JSON_VALUE`, `JSON_VALUE_ARRAY`, `JSON_EXTRACT_ARRAY`**
+
+Added support for the functions `JSON_VALUE`, `JSON_VALUE_ARRAY`, and `JSON_EXTRACT_ARRAY`.
+
+**New function `SESSION_USER`**
+
+Support has been added for the `SESSION_USER` function, which retrieves the current user name.
+
+**New columns in `information_schema.engine_query_history`**
+
+Added two new columns to `information_schema.engine_query_history`: `query_text_normalized_hash` and `query_text_normalized`.
+
+### [](#breaking-changes)Breaking Changes
+
+**Reserved the keyword GEOGRAPHY, requiring double quotes for use as an identifier**
+
+The word GEOGRAPHY is now a reserved keyword and must be quoted using double quotes for use as an identifier. For example, `create table geography(geography int);` will now fail, but `create table "geography" ("geography" int);` will succeed.
+
+**Deprecated the legacy HTTP ClickHouse headers**
+
+We no longer accept or return the legacy HTTP ClickHouse header format `X-ClickHouse-*`.
+
+**Fixed `json_value` zero-byte handling**
+
+The `json_value` function no longer returns null characters (0x00), as the TEXT datatype does not support them. For example, `select json_value('"\u0000"');` now results in an error.
+
+**Change default values for NODES and TYPE during CREATE ENGINE**
+
+When performing a CREATE ENGINE, the default values for NODES and TYPE parameters have changed. NODES defaults to `2` (previously `1`) and TYPE defaults to `M` (previously `S`). To create an engine with the previous default values, run the following command:
+
+```
+CREATE ENGINE my_engine WITH NODES=1 TYPE=S
+```
+
+### [](#bug-fixes-12)Bug Fixes
+
+**Fixed directory structure duplication in the S3 path when using the COPY TO statement with SINGLE\_FILE set to FALSE**
+
+Fixed an issue in `COPY TO` when `SINGLE_FILE=FALSE`. Previously, the specified directory structure in the location was repeated twice in the S3 path. For example, files were output to “s3://my-bucket/out/path/out/path/” instead of “s3://my-bucket/out/path/”.
+
+**Fixed the file extension in the S3 path when using the COPY TO statement with GZIP-Parquet format**
+
+Fixed an issue in `COPY TO` when `TYPE=PARQUET` and `COMPRESSION=GZIP`, which uses the Parquet file format with internal GZIP compression for the columns. Previously, the output files would have the extension “.parquet.gz”. Now, the extension is “.gz.parquet”.
+
+## [](#db-version-43)DB version 4.3
+
+**August 2024**
+
+### [](#new-features-14)New Features
+
+**Role-based permissions for COPY FROM and External Table processes**
+
+Enabled role-based permissions for COPY FROM and External Table processes.
+
+**HLL-based count distinct functions compatible with the Apache DataSketches library**
+
+Firebolt now supports count-distinct functions using the HLL (HyperLogLog) algorithm, compatible with the Apache DataSketches library. For details and examples, see documentation on the functions [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html), [APACHE\_DATASKETCHES\_HLL\_MERGE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-merge.html), and [APACHE\_DATASKETCHES\_HLL\_ESTIMATE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-estimate.html).
+
+**Supported additional join conditions and removed the restriction on the number of inequality predicates**
+
+Firebolt has added enhanced support for more join conditions. As long as there is one equality predicate comparing a left column to a right column of the join, which is not part of a disjunctive (OR) expression, the remaining join condition can be arbitrary. The previous limitation on the number of inequality predicates has been removed.
+
+### [](#performance-improvements-8)Performance Improvements
+
+**Multi-node query performance**
+
+Firebolt has improved the performance of data transfer between nodes, resulting in faster overall query execution times.
+
+**Enhanced Interval Arithmetic Support**
+
+Firebolt has enhanced support for interval arithmetic. You can now use expressions of the form `date_time + INTERVAL * d`, where `date_time` is a expression of type Date, Timestamp, TimestampTz, and `d` is an expression of type DOUBLE PRECISION. The interval is now scaled by `d` before being added to `date_time`. For example, writing `INTERVAL '1 day' * 3` is equivalent to writing `INTERVAL '3 days'`.
+
+**Optimized selective inner and right joins on primary index and partition by columns to reduce rows scanned**
+
+Selective inner and right joins on primary index and partition by columns now can now benefit from pruning. This reduces the number of rows scanned by filtering out rows that are not part of the join result early in the process. This optimization works best when joining on the first primary index column or a partition by column. The optimization is applied automatically when applicable, and no action is required. Queries that used this optimization will display “Prune:” labels on the table scan in the EXPLAIN (PHYSICAL) or EXPLAIN (ANALYZE) output.
+
+### [](#bug-fixes-13)Bug Fixes
+
+**Fixed a bug in the combination of cross join and the `index_of` function**
+
+Resolved an issue where the `index_of` function would fail when applied to the result of a cross join that produced a single row.
+
+### [](#breaking-changes-1)Breaking Changes
+
+**Temporarily restricted column DEFAULT expressions in CREATE TABLE statements**
+
+Column DEFAULT expressions in CREATE TABLE statements have been temporarily restricted, they can only consist of literals and the following functions: `CURRENT_DATE()`, `LOCALTIMESTAMP()`, `CURRENT_TIMESTAMP()`, `NOW()`. Existing tables with column DEFAULT expressions are not affected.
+
+**Underflow detection while casting from TEXT to floating point data types**
+
+Firebolt now detects underflow, a condition where a numeric value becomes smaller than the minimum limit that a data type can represent, when casting from TEXT to floating point data types. For example, the query `select '10e-70'::float4;` now returns an error, while it previously returned `0.0`.
+
+**Returning query execution errors in JSON format through the HTTP API**
+
+Firebolt’s HTTP API now returns query execution errors in JSON format, allowing for future enhancements like including metadata such as error codes, or the location of a failing expression within the SQL script.
+
+**Changed default of case\_sensitive\_column\_mapping parameter in COPY FROM**
+
+The default value for the `CASE_SENSITIVE_COLUMN_MAPPING` parameter in `COPY FROM` is now `FALSE`, meaning that if a target table contains column names in uppercase and the source file to ingest has the same columns in lowercase, the ingestion will consider them the same column and ingest the data.
+
+**`extract` function returns Numeric(38,9) for Epoch, second, and millisecond extraction**
+
+The result data type of the `extract` function for epoch, second, and millisecond was changed to return the type Numeric(38,9) instead of a narrower Numeric type. For example, `select extract(second from '2024-04-22 07:10:20'::timestamp);` now returns Numeric(38,9) instead of Numeric(8,6).
+
+## [](#db-version-42)DB version 4.2
+
+**July 2024**
+
+### [](#new-features-15)New features
+
+**New `ntile` window function**
+
+Firebolt now supports the `ntile` window function. Refer to our [NTILE](/sql_reference/functions-reference/window/ntile.html) documentation for examples and usage.
+
+### [](#enhancements-changes-and-new-integrations)Enhancements, changes and new integrations
+
+**Improved query performance**
+
+Queries with “`SELECT [project_list] FROM [table] LIMIT [limit]`” on large tables are now significantly faster.
+
+**Updated table level RBAC**
+
+Table level RBAC is now supported by Firebolt. This means that RBAC checks also cover schemas, tables, views and aggregating indexes. Refer to our [RBAC](/Guides/security/rbac.html) docs for a detailed overview of this new feature. The new Firebolt version inhibits the following change:
+
+- System built-in roles are promoted to contain table level RBAC information. This means that new privileges are added to `account_admin`, `system_admin` and `public` roles. The effect is transparent— any user assigned with those roles will not be affected.
+
+**Removal of Deprecated Columns from `INFORMATION_SCHEMA.ENGINES`**
+
+We removed the following columns from `INFORMATION_SCHEMA.ENGINES` that were only for FB 1.0 compatibility: `region`, `spec`, `scale`, `warmup`, and `attached_to`. These columns were always empty. (These columns are hidden and do not appear in `SELECT *` queries, but they will still work if referenced explicitly.)
+
+### [](#breaking-changes-2)Breaking Changes
+
+**Improved rounding precision for floating point to integer casting**
+
+Casting from floating point to integers now uses Banker’s Rounding, matching PostgreSQL’s behavior. This means that numbers that are equidistant from the two nearest integers are rounded to the nearest even integer:
+
+Examples:
+
+```
+SELECT 0.5::real::int
+```
+
+This returns 0.
+
+```
+SELECT 1.5::real::int
+```
+
+This returns 2.
+
+Rounding behavior has not changed for numbers that are strictly closer to one integer than to all others.
+
+**JSON functions update**
+
+Removed support for `json_extract_raw`, `json_extract_array_raw`, `json_extract_values`, and `json_extract_keys`. Updated `json_extract` function: the third argument is now `path_syntax`, which is a JSON pointer expression. See [JSON\_EXTRACT](/sql_reference/functions-reference/JSON/json-extract.html) for examples and usage.
+
+**Cluster ordinal update**
+
+Replaced `engine_cluster` with [cluster\_ordinal](/sql_reference/information-schema/engine-metrics-history.html) in `information_schema.engine_metrics_history`. The new column is an integer representing the cluster number.
+
+**Configurable cancellation behavior on connection drop**
+
+Introduced the `cancel_query_on_connection_drop` setting, allowing clients to control query cancellation on HTTP connection drop. Options include `NONE`, `ALL`, and `TYPE_DEPENDENT`. Refer to [system settings](/Reference/system-settings.html#query-cancellation-mode-on-connection-drop) for examples and usage.
+
+**JSON format as default for error output**
+
+The HTTP API now returns query execution errors in JSON format by default. This change allows for the inclusion of meta information such as error codes and the location of failing expressions in SQL scripts.
+
+**STOP ENGINE will drain currently running queries first**
+
+`STOP ENGINE` command now supports graceful drain, meaning any currently running queries will be run to completion. Once all the queries are completed, the engine will be fully stopped and terminated. If you want to stop the engine immediately, you can issue a STOP ENGINE command use the TERMINATE option. For example, to immediately stop an engine, my\_engine, you can use:
+
+```
+ STOP ENGINE myEngine WITH TERMINATE = TRUE
+```
+
+**Scaling engines will not terminate currently running queries**
+
+`ALTER ENGINE` command now supports graceful drain, meaning when you scale an engine (vertically or horizontally), any currently running queries will not be terminated. New queries after the scaling operation will be directed to a new cluster, while queries running on the old cluster will be run to completion.
+
+**Updated RBAC ownership management**
+
+We have introduced several updates to role and privilege management:
+
+- The `security_admin` role will be removed temporarily and re-introduced in a later release.
+- `Information_object_privileges` includes more privileges. Switching to to a specific user database (e.g by executing `use database db`) will only show privileges relevant for that database. Account-level privileges no longer show up when attached to a specific database.
+- Every newly created user is granted with a `public` role. This grant can be revoked.
+
+## [](#db-version-41)DB version 4.1
+
+**June 2024**
+
+- [Resolved issues](#resolved-issues)
+
+### [](#resolved-issues)Resolved issues
+
+- Fixed an issue causing errors when using `WHERE column IN (...)` filters on external table scans.
+
+## [](#db-version-40)DB version 4.0
+
+**June 2024**
+
+- [Enhancements, changes, and new integrations](#enhancements-changes-and-new-integrations)
+- [Breaking Changes](#breaking-changes)
+
+### [](#enhancements-changes-and-new-integrations-1)Enhancements, changes and new integrations
+
+**Query Cancelation on HTTP Connection Drop**
+
+Going forward, when the network connection between the client and Firebolt is dropped (for example because the Firebolt UI tab was closed or due to network issues), DML queries (INSERT, UPDATE, DELETE, etc) are no longer canceled automatically, but will keep running in the background. You can continue to monitor their progress in `information_schema.engine_running_queries` or cancel them manually using the `cancel query` statement if desired. DQL queries (SELECT) are still canceled automatically on connection drop.
+
+**New Aggregate Functions: `CHECKSUM` and `hash_agg`**
+
+`CHECKSUM` and `hash_agg` functions are now supported for aggregating indexes. Note that when the `hash_agg` function doesn’t receive rows, the result is 0.
+
+### [](#breaking-changes-3)Breaking Changes
+
+**Array Casting Nullability Update**
+
+Cast to array will no longer support specifying nullability of the inner type. Example:
+
+```
+a::array(int null)
+```
+
+or
+
+```
+cast(a as array(int not null)) 
+```
+
+will now fail, and need to be rewritten as:
+
+```
+a::array(int) 
+```
+
+or
+
+```
+cast(a as array(int)). 
+```
+
+**Postgres-compliant Cast**
+
+Casts now behave the same across the product and adhere to the list of supported casts. Some usages of casts (explicit, implicit, or assignment cast) that were previously allowed are no longer supported and now result in errors. For more details on list of supported casts, see the documentation [here](/sql_reference/data-types.html#type-conversion).
+
+## [](#db-version-334)DB version 3.34
+
+**May 2024**
+
+- [Enhancements, changes, and new integrations](#enhancements-changes-and-new-integrations)
+- [Resolved issues](#resolved-issues)
+
+### [](#enhancements-changes-and-new-integrations-2)Enhancements, changes and new integrations
+
+**Removed `MATCH` function**
+
+The `match` function has been removed and replaced with [regexp\_like](/sql_reference/functions-reference/string/regexp-like.html).
+
+**Producing an error for array function failure instead of NULL**
+
+Array function queries that accept two or more array arguments now produce an error. If you call an array function such as `array_transform(..)` or `array_sort(..)` with multiple array arguments, the arrays must have the same size. For example:
+
+```
+array_transform(x, y -> x + y, arr1, arr2)
+```
+
+This raises an error if `array_length(arr1) != array_length(arr2)`. We now also perform this check for NULL literals. If you previously used `array_transform(x, y -> x + y, NULL::INT[], Array[5, 6])`, you got back `NULL`. Now, the query using that expression will raise an error.
+
+**Added ARRAY\_FIRST function**
+
+The [array\_first](../../sql_reference/functions-reference/Lambda/array-first.html) function has been added. It returns the first element in the given array for which the given function returns `true`.
+
+**New name for `any_match`**
+
+A new name for `any_match` has been added: [array\_any\_match](/sql_reference/functions-reference/Lambda/array-any-match.html). `any_match` will be kept as an alias.
+
+**Updated ARRAY\_SUM return types**
+
+The `array_sum` function of `bigint[]` now returns a numeric value and `array_sum` of `real[]` returns a real value.
+
+**Precedence of operators**
+
+Breaking change in operator precedence between comparison operators such as `=`, `<`, `>`, and `IS` operator. New behavior is compatible with Postgres.
+
+Examples of query that changed behavior:
+
+```
+select 1 is null = 2 is null
+```
+
+This used to be `true`, because it was interpreted as `select (1 is null) = (2 is null)`. It now becomes an error of incompatible types in `=`
+
+```
+select false = false is not null
+```
+
+The result used to be `false` - `select false = (false is not null)`, but now is `true` - `select (false = false) is not null`.
+
+**Dropping the role**
+
+Role cannot be dropped if there are permissions granted to the role. The error message will be displayed if you need to manually drop permissions associated to the role.
+
+**Coalesce Short-Circuiting**
+
+`COALESCE` now supports short-circuiting in Firebolt. Queries such as `COALESCE(a, 1 / 0) FROM t` could fail before, even when there were no NULLs in t. Only `CASE WHEN` supported short circuiting. Firebolt is now aligned with PostgreSQL and supports short circuiting in `COALESCE` as well.
+
+**Create table under I\_S schema**
+
+You can now execute `CREATE TABLE`/`VIEW`/`AGGREGATING INDEX` only under the public schema.
+
+**Improved error message for JSON `PARSE_AS_TEXT` format**
+
+The error message for external tables created with JSON `PARSE_AS_TEXT` format has been revised. This format reads specifically into a *single* column of type either TEXT or `TEXT NOT NULL`. (Note there may be external table partition columns defined after the single TEXT column, and they are okay). Now, only the error message regarding the `CREATE EXTERNAL TABLE` statement on a user’s first attempt to use `SELECT` will be seen. Support for reading format JSON `PARSE_AS_TEXT=TRUE` into a `TEXT NOT NULL` column has been added.
+
+**Implemented column\_mismatch**
+
+Support for `ALLOW_COLUMN_MISMATCH` in `COPY INTO` has been added.
+
+**Corrected NULL behavior of `STRING_TO_ARRAY`**
+
+The behavior of `string_to_array` now matches its behavior in PostgreSQL. The change affects NULL delimiters where the string is split into individual characters, as well as empty strings and where the output is now an empty array.
+
+**Changed city\_hash behavior for nullable inputs**
+
+The behavior for `city_hash` has changed for nullable inputs. For example:
+
+```
+SELECT CITY_HASH([null]) = CITY_HASH([''])
+```
+
+This is now false.
+
+**Function `ARRAY_AGG` now preserves NULLS**
+
+The `array_agg` function has been changed to return PostgreSQL-compliant results:
+
+- `array_agg` now preserves `NULL` values in its input, e.g. `select array_agg(x) from unnest(array [1,NULL,2] x)` returns `{1,NULL,2}`
+- `array_agg` now returns `NULL` instead of an empty array if there are no input values
+
+**Lambda parameters are no longer supported by `array_sum`**
+
+Array aggregate functions no longer support lambda parameters. To get the old behavior for conditional lambda functions, use transform instead. For example:
+
+```
+array_sum(transform(...))
+```
+
+**Explicit Parquet conversion from DATE to INT is now needed**
+
+A breaking change has been implemented in raising an error on reading a Parquet/ORC `DATE`/`TIMESTAMP` column if the `EXTERNAL TABLE` expects the column to have type `INT`/`BIGINT`. `DATE`/`TIMESTAMP` cannot be cast to `INT`/`BIGINT`, and external table scans will no longer allow this cast either. You need to explicitly transform the Parquet/ORC `DATE`/`TIMESTAMP` column with `EXTRACT`(`EPOCH FROM` col) to insert it into an `INT`/`BIGINT` column.
+
+### [](#resolved-issues-1)Resolved issues
+
+- Fixed a bug where negation did not check for overflows correctly.
+
+## [](#db-version-333)DB version 3.33
+
+**April 2024**
+
+- [Enhancements, changes, and new integrations](#enhancements-changes-and-new-integrations)
+- [Resolved issues](#resolved-issues)
+
+### [](#enhancements-changes-and-new-integrations-3)Enhancements, changes and new integrations
+
+**Removed ‘element\_at’ Function**
+
+The `element_at` function for arrays has been removed and replaced with the `[]` operator.
+
+**Change of return type from BIGINT to INTEGER**
+
+The `index_of`/`array_position` function now returns INTEGER instead of BIGINT.
+
+**Removed LIMIT DISTINCT syntax**
+
+The `LIMIT_DISTINCT` syntax is no longer supported by Firebolt.
+
+**Updated CAST function behavior**
+
+All cast logic has been moved to runtime in Firebolt. The `castColumn` function is now replaced by `fbCastColumn`, ensuring consistent casting behavior and resolving issues with the `COPY FROM` operation and other cast calls. Uses of implicit/explicit `CAST` may result in errors due to this fix.
+
+New breaking change.
+
+### [](#resolved-issues-2)Resolved issues
+
+- Fixed a bug in `array_position` where searching for `NULL` in an array with non-null elements incorrectly returned a match in some cases.
+
+## [](#db-version-332)DB version 3.32
+
+**April 2024**
+
+- [New features](#new-features)
+- [Enhancements, changes, and new integrations](#enhancements-changes-and-new-integrations)
+- [Resolved issues](#resolved-issues)
+
+### [](#new-features-16)New features
+
+**Expose and document ‘typeof’ as a toTypeName function**
+
+The `typeof` function has been added, which returns the data type of a SQL expression as a string.
+
+### [](#enhancements-changes-and-new-integrations-4)Enhancements, changes and new integrations
+
+**Spilling Aggregations**
+
+Firebolt can now process most aggregations that exceed the available main memory of the engine by spilling to the SSD cache when needed. This happens transparently to the user. A query that made use of this capability will populate the `spilled_bytes` column in `information_schema.query_history`. Spilling does not support aggregations where a single group exceeds the available memory (e.g., `select count(distinct high_cardinality_column) from huge_table`) and may not yet work reliably for all aggregate functions or engine specs. We will continue improving the feature in upcoming releases.
+
+**No overflow detected in cast from FLOAT to DECIMAL**
+
+Fix results of casting from `float32` to decimals with precision &gt; 18. In addition to the correct results breaking change, there are certain queries that was working before that now will fail involving overflow.
+
+Example query:
+
+- `SELECT` 17014118346046923173168730371588410572::REAL::DECIMAL(37,0).
+
+Previously, this was working and returned a wrong result, but now it will fail with an overflow error.
+
+**ARRAY\_COUNT returns 0 instead of NULL**
+
+`ARRAY_COUNT` on `NULL` array now returns `0` instead of `NULL`.
+
+**No overflow check in arithmetic operations**
+
+Arithmetic operators (i.e. multiplication, addition, subtraction, and division) now perform correct overflow checking. This means that queries that used to return wrong results in the past now throw runtime errors.
+
+Example queries:
+
+- `SELECT` 4294967296 * 4294967296 -&gt; now throws an error, before it would return 0
+- `SELECT` 9223372036854775807 + 9223372036854775807 -&gt; now throws an error, before it would return -2
+- `SELECT` (a + b) * c -&gt; this might throw runtime errors if there are large values in the column, but this is highly data dependent.
+
+**Implement bool\_or/bool\_and aggregation functions**
+
+New aggregate functions bool\_or and bool\_and have been added.
+
+**Remove old deprecate REGENERATE AGGREGATING INDEX**
+
+‘REGENERATE AGGREGATING INDEX’ syntax has now been removed.
+
+**Align the syntax of our “escape” string literals with PostgreSQL**
+
+Escape [string literals](/sql_reference/data-types.html) now support octal and Unicode escape sequences. As a result, escape string literals now behave exactly like PostgreSQL. Example: `SELECT E'\U0001F525b\x6F\154t';` returns `🔥bolt`. If the setting `standard_conforming_strings` is not enabled for you, regular string literals (e.g., `SELECT 'foo';`) will also recognize the new escape sequences. However, we recommend exclusively using escape string literals for using escape sequences. Please be aware that you will get different results if you previously used (escape) string literals containing the syntax we now use for Unicode and octal escape sequences.
+
+**Change return value of length and octet\_length to INT**
+
+Length and array\_length now return INTEGER instead of BIGINT.
+
+**Subqueries in the GROUP BY/HAVING/ORDER BY clauses change**
+
+Subqueries in `GROUP BY/HAVING/ORDER BY` can no longer references columns from the selection list of the outer query via their aliases as per PG compliance. `select 1 + 1 as a order by (select a);` used to work, but now fails with `unresolved name a` error.
+
+**Bytea serialization to CSV fix**
+
+Changed Bytea to CSV export: from escaped to non escaped.
+
+Example:
+
+- `COPY` (select ‘a’::bytea) to ‘s3…’; the results will now be “\\x61” instead of “\\x61”.
+
+### [](#resolved-issues-3)Resolved issues
+
+- Fixed results of casting literal float to numeric. In the past the float literal was casted to float first then to numeric, this caused us to lose precision.
+
+Examples:
+
+- `SELECT` 5000000000000000000000000000000000000.0::DECIMAL(38,1); -&gt; 5000000000000000000000000000000000000.0
+- `SELECT` (5000000000000000000000000000000000000.0::DECIMAL(38,1)+5000000000000000000000000000000000000.0::DECIMAL(38 1)); -&gt; ERROR: overflow.
+
+Note that before, it was not an error and resulted in: 9999999999999999775261218463046128332.8.
+
+- Fixed a longstanding bug with &gt;= comparison on external table source\_file\_name. Whereas this would previously have scraped fewer files than expected off the remote S3 bucket, you will now get all files properly (lexicographically) compared against the input predicate.
+
+<!--THE END-->
+
+- Fixed a bug when `USAGE ANY ENGINE` (and similar) privileges were shown for * account. Now it is being show for current account.
+
+<!--THE END-->
+
+- Fixed a bug involving [‘btrim’](/sql_reference/functions-reference/string/btrim.html) string characters, where invoking `btrim`, `ltrim`, `rtrim`, or `trim` with a literal string but non-literal trim characters could result in an error.
+
+## [](#db-version-331)DB version 3.31
+
+**March 2024**
+
+- [New features](#new-features)
+- [Enhancements, changes, and new integrations](#enhancements-changes-and-new-integrations)
+- [Resolved issues](#resolved-issues)
+
+### [](#new-features-17)New features
+
+**PG compliant division**
+
+LQP2 has a new division operator that is PG compliant, by default.
+
+**Prevents usage of new line delimeter for schema inference**
+
+An error will now occur if schema inference is used with the option “delimiter” set to something other than the default.
+
+### [](#enhancements-changes-and-new-integrations-5)Enhancements, changes and new integrations
+
+**Simplified table protobuf representation**
+
+Unique constraints in tables will be blocked for new accounts.
+
+**Support for nullable arrays**
+
+Support has been added to allow the [ARRAY\_ANY\_MATCH](/sql_reference/functions-reference/Lambda/array-any-match.html) lambda function to work with nullable arrays.
+
+**Updated AWS billing error message**
+
+The error message for an AWS billing issue on Engine Start was on Engine Start was changed to add more information and clarity.
+
+**New requirements updated for EXPLAIN**
+
+For `EXPLAIN` queries, we now allow only one of the following options at the same time: `ALL`, `LOGICAL`, `PHYSICAL`, `ANALYZE`.`EXPLAIN (ALL)` now returns the plans in multiple rows instead of multiple columns.
+
+**Disabled Unix Time Functions**
+
+The following functions are not supported anymore: ‘from\_unixtime’ ‘to\_unix\_timestamp’ ‘to\_unix\_time’
+
+**Renamed spilled metrics columns**
+
+The columns `spilled_bytes_uncompressed` and `spilled_bytes_compressed` of `information_schema.query_history` have been replaced by a single column `spilled_bytes`. It contains the amount of data that was spilled to disk temporarily while executing the query.
+
+**Aggregating index placement**
+
+Aggregating index is now placed in the same namespace as tables and views.
+
+**Syntax and planner support for LATERAL scoping**
+
+[LATERAL](/Reference/reserved-words.html) is now a reserved keyword. It must now be used within double-quotes when using it as an object identifier.
+
+### [](#resolved-issues-4)Resolved issues
+
+Changed return for division by 0 from null to fail.
+
+Updated error log for upload failure for clarity.
+
+Fixed a bug in ‘unnest’ table function that occurred when not all of the ‘unnest’ columns were projected.
+
+Changed the behavior of [split\_part](/sql_reference/functions-reference/string/split-part.html) when an empty string is used as delimiter.
+
+Fixed a bug where floating point values `-0.0` and `+0.0`, as well as `-nan` and `+nan` were not considered equal in distributed queries.
+
+TRY\_CAST from TEXT to NUMERIC now works as expected: if the value cannot be parsed as NUMERIC it produces null.
+
+## [](#db-version-330)DB version 3.30
+
+**November 2023**
+
+- [New features](#new-features)
+- [Enhancements, changes, and new integrations](#enhancements-changes-and-new-integrations)
+- [Resolved issues](#resolved-issues)
+
+### [](#new-features-18)New features
+
+**New comparison operators**
+
+[New comparison operators](/sql_reference/operators.html) `IS DISTINCT FROM` and `IS NOT DISTINCT FROM` have been added.
+
+### [](#enhancements-changes-and-new-integrations-6)Enhancements, changes and new integrations
+
+**Support for nullable arrays**
+
+Support has been added to allow the ANY\_MATCH lambda function to work with nullable arrays
+
+### [](#resolved-issues-5)Resolved issues
+
+- Indirectly granted privileges have been removed from the `information_schema.object_privileges` view.
+- Fixed an issue where `ARRAY_FIRST` and `ARRAY_FIRST_INDEX` returned an error if the given input was nullable.
+
+## [](#db-version-329)DB version 3.29
+
+**October 2023**
+
+- [New features](#new-features)
+- [Enhancements, changes, and new integrations](#enhancements-changes-and-new-integrations)
+
+### [](#new-features-19)New features
+
+**EXPLAIN ANALYZE now available for detailed query metrics**
+
+You can now use the [EXPLAIN command](/sql_reference/commands/queries/explain.html) to execute `EXPLAIN (ANALYZE) <select statement>` and get detailed metrics about how much time is spent on each operator in the query plan, and how much data is processed. The query plan shown there is the physical query plan, which you can inspect using `EXPLAIN (PHYSICAL) <select statement>` without executing the query. It shows how query processing is distributed over the nodes of an engine.
+
+### [](#enhancements-changes-and-new-integrations-7)Enhancements, changes and new integrations
+
+**Virtual column ‘source\_file\_timestamp’ uses new data type**
+
+The virtual column `source_file_timestamp` has been migrated from the data type `TIMESTAMP` (legacy timestamp type without time zone) to the type `TIMESTAMPTZ` (new timestamp type with time zone).
+
+Despite the increased resolution, the data is still in second precision as AWS S3 provides them only as unix seconds.
+
+Use `source_file_timestamp - NOW()` instead of `DATE_DIFF('second', source_file_timestamp, NOW())`
+
+**New function added**
+
+A new alias [ARRAY\_TO\_STRING](/sql_reference/functions-reference/array/array-to-string.html) has been added to function `ARRAY_JOIN`.
+
+## [](#db-version-328)DB version 3.28
+
+**September 2023**
+
+- [Resolved issues](#resolved-issues)
+
+### [](#resolved-issues-6)Resolved issues
+
+- `IN` expressions with scalar arguments now return Postgres-compliant results if there are `NULL`s in the `IN` list.
+- information\_schema.running\_queries returns ID of a user that issued the running query, not the current user.
+- Update error message to explain upper case behavior
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference_reserved_words.md b/cmd/docs-scrapper/fireboltdocs/reference_reserved_words.md
new file mode 100644
index 0000000..14636c2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference_reserved_words.md
@@ -0,0 +1,117 @@
+# [](#reserved-words)Reserved words
+
+Reserved words have special meanings to the Firebolt SQL engine. We recommend that you do not use these words for naming databases, tables, columns, variables, or other objects that you define. If you must use a reserved word in this way, enclose it in quotation marks.
+
+- ALL
+- ALTER
+- AND
+- ARRAY
+- BETWEEN
+- BIGINT
+- BOOL
+- BOOLEAN
+- BOTH
+- CALL
+- CASE
+- CAST
+- CHAR
+- CONCAT
+- COPY
+- CREATE
+- CROSS
+- CURRENT\_DATE
+- CURRENT\_TIMESTAMP
+- DATABASE
+- DATE
+- DATETIME
+- DECIMAL
+- DELETE
+- DESCRIBE
+- DISTINCT
+- DOUBLE
+- DOUBLECOLON
+- DOW
+- DOY
+- DROP
+- EMPTY\_IDENTIFIER
+- ENGINE
+- EPOCH
+- EXCEPT
+- EXECUTE
+- EXISTS
+- EXPLAIN
+- EXTRACT
+- FALSE
+- FETCH
+- FIRST
+- FLOAT
+- FROM
+- FULL
+- GENERATE
+- GROUP
+- HAVING
+- IF
+- ILIKE
+- IN
+- INNER
+- INSERT
+- INT
+- INTEGER
+- INTERSECT
+- INTERVAL
+- IS
+- ISNULL
+- JOIN
+- JOIN\_TYPE
+- LATERAL
+- LEADING
+- LEFT
+- LIKE
+- LIMIT
+- LIMIT\_DISTINCT
+- LOCALTIMESTAMP
+- LONG
+- NATURAL
+- NEXT
+- NOT
+- NULL
+- NUMERIC
+- OFFSET
+- ON
+- ONLY
+- OR
+- ORDER
+- OUTER
+- OVER
+- PARTITION
+- PRECISION
+- PREPARE
+- PRIMARY
+- QUARTER
+- RIGHT
+- ROW
+- ROWS
+- SAMPLE
+- SELECT
+- SET
+- SHOW
+- SYSTEM
+- TEXT
+- TIME
+- TIMESTAMP
+- TOP
+- TRAILING
+- TRIM
+- TRUE
+- TRUNCATE
+- UNION
+- UNKNOWN\_CHAR
+- UNNEST
+- UNTERMINATED\_STRING
+- UPDATE
+- USING
+- VARCHAR
+- WEEK
+- WHEN
+- WHERE
+- WITH
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/reference_system_settings.md b/cmd/docs-scrapper/fireboltdocs/reference_system_settings.md
new file mode 100644
index 0000000..6943775
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/reference_system_settings.md
@@ -0,0 +1,218 @@
+# [](#firebolt-system-settings)Firebolt system settings
+
+You can use a `SET` statement in a SQL script to configure aspects of Firebolt’s system behavior. Each statement is a query in its own right and must be terminated with a semi-colon (;). The `SET` statement cannot be included in other queries. This topic provides a list of available settings by function.
+
+## [](#setting-the-time-zone)Setting the time zone
+
+Use this setting to specify the session time zone. Time zone names are from the [Time Zone Database](http://www.iana.org/time-zones). You can see the list of tz database time zones [here](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones). For times in the future, the latest known rule for the given time zone is applied. Firebolt does not support time zone abbreviations, as they cannot account for daylight savings time transitions, and some time zone abbreviations have meant different UTC offsets at different times. The default value of the `timezone` setting is UTC.
+
+### [](#syntax)Syntax
+
+```
+SET timezone = '<time_zone>'
+```
+
+### [](#example)Example
+
+The following code example demonstrates how setting the timezone parameter affects the interpretation and conversion of `TIMESTAMPTZ` values:
+
+```
+SET timezone = 'UTC';
+SELECT TIMESTAMPTZ '1996-09-03 11:19:33.123456 Europe/Berlin';  --> 1996-09-03 09:19:33.123456+00
+SELECT TIMESTAMPTZ '2023-1-29 6:3:42.7-3:30';  --> 2023-01-29 09:33:42.7+00
+
+SET timezone = 'Israel';
+SELECT TIMESTAMPTZ '2023-1-29 12:21:49';  --> 2023-01-29 12:21:49+02
+SELECT TIMESTAMPTZ '2023-1-29Z';  --> 2023-01-29 02:00:00+02
+```
+
+## [](#enable-parsing-for-literal-strings)Enable parsing for literal strings
+
+If set to `true`, strings are parsed without escaping, treating backslashes literally. By default, this setting is enabled.
+
+### [](#syntax-1)Syntax
+
+```
+SET standard_conforming_strings = [true|false]
+```
+
+### [](#example-1)Example
+
+The following code example demonstrates how setting `standard_conforming_strings` affects the interpretation of escape sequences in string literals:
+
+```
+SET standard_conforming_strings = false;
+SELECT '\x3132'; --> 132
+
+SET standard_conforming_strings = true;
+SELECT '\x3132'; --> \x3132
+```
+
+## [](#statement-timeout)Statement timeout
+
+Specifies the number of milliseconds a SQL statement is allowed to run. Any SQL statement or query exceeding the specified time is canceled. A value of zero disables the timeout by default.
+
+### [](#syntax-2)Syntax
+
+```
+SET statement_timeout = <number_of_milliseconds>;
+```
+
+### [](#example-2)Example
+
+The following SQL example sets the query timeout to three seconds:
+
+```
+SET statement_timeout = 3000;
+```
+
+## [](#limit-the-number-of-result-rows)Limit the number of result rows
+
+When set to a value greater than zero, this setting limits the number of rows returned by `SELECT` statements. The query is executed as if an additional `LIMIT` clause is added to the SQL query. A value of zero or less means that no limit is applied. By default, no limit to the number of result rows is applied.
+
+### [](#syntax-3)Syntax
+
+```
+SET max_result_rows = <integer>;
+```
+
+### [](#example-3)Example
+
+The following queries all return the same result. For the first query, no explicit settings are set:
+
+```
+SELECT * FROM table LIMIT 10000;
+
+SET max_result_rows = 10000;
+SELECT * FROM table;
+
+SET max_result_rows = 10000;
+SELECT * FROM table LIMIT 20000;
+```
+
+## [](#query-cancellation-mode-on-connection-drop)Query cancellation mode on connection drop
+
+Specify how the query should behave when the HTTP connection to Firebolt is dropped, such as when the UI window is closed. For this, you can choose between 3 different modes:
+
+- `NONE`: The query will not be canceled on connection drop
+- `ALL` : The query will be canceled on connection drop
+- `TYPE_DEPENDENT`: Only queries without side effects will be canceled, such as `SELECT`.
+
+The default is `TYPE_DEPENDENT`.
+
+### [](#syntax-4)Syntax
+
+```
+SET cancel_query_on_connection_drop = <mode>
+```
+
+### [](#example-4)Example
+
+The following code example demonstrates how to control query cancellation behavior when a connection drops using `none`, `all`, and `type_dependent` modes for `SET cancel_query_on_connection_drop`:
+
+```
+SET cancel_query_on_connection_drop = none;
+INSERT INTO X [...]
+SELECT * FROM X; 
+
+SET cancel_query_on_connection_drop = all;
+INSERT INTO X [...]
+SELECT * FROM X;  
+
+SET cancel_query_on_connection_drop = type_dependent;
+INSERT INTO X [...] 
+SELECT * FROM X;  
+```
+
+## [](#query-labelingtagging)Query labeling/tagging
+
+Use this option to label your query with a custom text. This simplifies query cancellation and retrieving the query status from system tables.
+
+### [](#syntax-5)Syntax
+
+```
+SET query_label = '<text>'
+```
+
+### [](#example-5)Example
+
+The following code example assigns a query label to a query using `SET query_label`, allowing you to track it in `information_schema`, `engine_running_queries`, and `information_schema.engine_query_history`. It then demonstrates how to retrieve the `QUERY_ID` for the labeled query and cancel it using `CANCEL QUERY`:
+
+```
+SET query_label = 'Hello Firebolt';
+SELECT * FROM X;  
+
+SET query_label = '';
+
+SELECT query_id, * FROM information_schema.engine_running_queries WHERE query_label = 'Hello Firebolt'
+SELECT query_id, * FROM information_schema.engine_query_history WHERE query_label = 'Hello Firebolt'
+
+CANCEL QUERY WHERE query_id = '<retrieved query_id>'
+```
+
+## [](#multi-cluster-engine-warmup)Multi-cluster engine warmup
+
+Use this option to distribute queries across all clusters of an engine, simplifying the process of initializing cached data to a consistent state across all clusters after a `START ENGINE` or `ALTER ENGINE` operation.
+
+Warmup queries complete after they have run on all clusters of the engine. The queries return an empty result if they succeed on all clusters. If the query fails on any cluster, it returns an error. If multiple errors occur, only one error is returned.
+
+### [](#syntax-6)Syntax
+
+```
+SET warmup = true;
+```
+
+### [](#example-6)Example
+
+The following code example activates the warmup mode so that the query runs on `production_table` using all clusters of an engine, and returns an empty result upon success:
+
+```
+USE ENGINE multi_cluster_engine;
+SET warmup = true;
+SELECT checksum(*) FROM production_table;
+SET warmup = false;
+```
+
+## [](#result-cache)Result cache
+
+Set `enable_result_cache` to `FALSE` to disable the use of Firebolt’s [result cache](/Overview/queries/understand-query-performance-subresult.html), which is set to `TRUE` by default. Disabling result cashing can be useful for benchmarking query performance. When `enable_result_cache` is disabled, resubmitting the same query will recompute the results rather than retrieving them from cache.
+
+### [](#syntax-7)Syntax
+
+```
+SET enable_result_cache = [true|false];
+```
+
+### [](#example-7)Example
+
+The following code example disables the result cache so that no previously cached results are used, and no new cache entries are written:
+
+```
+SET enable_result_cache = false;
+SELECT checksum(*) FROM production_table;
+```
+
+## [](#subresult-cache)Subresult cache
+
+Firebolt implements [advanced cross-query optimization](/Overview/queries/understand-query-performance-subresult.html) that allows SQL queries to reuse intermediate query execution states from previous requests. Subresult caching operates at a semantic level, which allows Firebolt to understand and optimize queries based on the meaning and context of the data rather than solely based on their syntax or structure. This capability allows Firebolt to optimize across different query patterns for improved efficiency.
+
+Set `enable_subresult_cache` to `FALSE` to disable Firebolt’s subresult caching, which is set to `TRUE` by default.
+
+Disabling subresult caching is generally **not recommended**, as it can negatively impact query performance, especially for complex workloads. For most benchmarking scenarios, disable the result cache instead, as described in the previous [Result cache](#result-cache) section. This approach affects only the final result caching while preserving the benefits of subresult optimizations.
+
+### [](#syntax-8)Syntax
+
+```
+SET enable_subresult_cache = [true|false];
+```
+
+### [](#example-8)Example
+
+The following code example disables the subresult cache so no previously cached subresult is used and no new cache entries are written by this query:
+
+```
+SET enable_subresult_cache = false;
+SELECT count(*) FROM fact_table INNER JOIN dim_table ON (a = b);
+```
+
+Setting `enable_subresult_cache` to `FALSE` disables the use of all [cached subresults](/Overview/queries/understand-query-performance-subresult.html). In particular, it deactivates two caching mechanisms that normally speed up query runtimes: the use of the `MaybeCache` operator, which includes the full result cache, and the hash-table cache used by the `Join` operator.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference.md b/cmd/docs-scrapper/fireboltdocs/sql_reference.md
new file mode 100644
index 0000000..54a2315
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference.md
@@ -0,0 +1,12 @@
+# [](#sql-reference)SQL reference
+
+Reference SQL syntax for functions and commands, as well as available data type and operators. Check available views for observing metadata.
+
+* * *
+
+- [Data types](/sql_reference/data-types.html)
+- [Information schema](/sql_reference/information-schema/)
+- [Operators](/sql_reference/operators.html)
+- [Functions glossary](/sql_reference/functions-reference/functions-glossary.html)
+- [SQL commands](/sql_reference/commands/)
+- [SQL functions](/sql_reference/functions-reference/functions-reference.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_bytea_data_type.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_bytea_data_type.md
new file mode 100644
index 0000000..63d3c06
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_bytea_data_type.md
@@ -0,0 +1,130 @@
+# [](#bytea-data-type)BYTEA data type
+
+This topic describes the Firebolt implementation of the `BYTEA` data type.
+
+Not all functions support the `BYTEA` data type currently. For more information, see [BYTEA functions](/sql_reference/functions-reference/bytea/)
+
+- [Overview](#overview)
+  
+  - [Type conversions](#type-conversions)
+  - [Comparison operator](#comparison-operator)
+  - [Literal string interpretation](#literal-string-interpretation)
+  - [Output format](#output-format)
+  - [Importing `BYTEA` from external source](#importing-bytea-from-external-source)
+
+## [](#overview)Overview
+
+The `BYTEA` data type is a variable length binary string data type, commonly used to store binary data, like images, other multimedia files, or raw bytes of information. A binary string is a sequence of bytes - unlike `TEXT`, there is no character set. The `BYTEA` data type is nullable.
+
+### [](#type-conversions)Type conversions
+
+The `BYTEA` type can be cast to and from the `TEXT` data type. A cast from `BYTEA` to `TEXT` will interpret the binary string to a hexadecimal representation with `\x` as a prefix. For example `SELECT 'a'::BYTEA::TEXT` returns `\x61`.
+
+Cast from `TEXT` to `BYTEA` supports two formats, **hex** and **escaped**:
+
+**Hex**  
+Using hex format, the `TEXT` type data must start with `\x`. Characters `\n`, `\t`, `\r` and ‘ ‘ are ignored if they are not in sequence of two characters representing one byte. Each character must be in one of the following ranges: `a-f`, `A-F`, `0-9`.  
+Characters must be in pairs. For example, `\x aa` is a valid hex format, but `\xa a` is invalid.
+
+**Escape**  
+Using escape format, an escaped backslash becomes just a single backslash: `\\` -&gt; `\`. One backslash must be followed by 3 numbers representing octal value (base 8) in range of `000-377`. For example, `a \375`
+
+In addition to casting, the [ENCODE](/sql_reference/functions-reference/bytea/encode.html) and [DECODE](/sql_reference/functions-reference/bytea/decode.html) functions can be used to represent `TEXT` as `BYTEA` and vice versa, but will behave slightly differently. For example, `SELECT ENCODE('1'::BYTEA, 'HEX');` returns `31`, while `SELECT CAST('1'::BYTEA as TEXT);` returns `\x31`, both of type `TEXT`.
+
+### [](#comparison-operator)Comparison operator
+
+The `BYTEA` comparison operator will work as lexicographical comparison but with bytes. Two empty `BYTEA` type expressions are equal. If two `BYTEA` type expressions have equivalent bytes and are of the same length, then they are equal. In a greater than (&gt;) or less than (&lt;) comparison, two `BYTEA` type expressions are compared byte by byte, and the first mismatching byte defines which is greater or less than the other.
+
+**Examples:**
+
+`SELECT '\xa3'::BYTEA > '\xa2'::BYTEA;` returns `TRUE`.
+
+`SELECT '\xa3'::BYTEA = '\xa300'::BYTEA;` returns `FALSE`.
+
+`SELECT '\xa3'::BYTEA < '\xa300'::BYTEA;` returns `TRUE`.
+
+### [](#literal-string-interpretation)Literal string interpretation
+
+Literal strings will be interpreted according to the setting [`standard_conforming_strings`,](/Reference/system-settings.html#enable-parsing-for-literal-strings) which controls whether strings are parsed with or without escaping. Similar to [CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/cast.html) from `TEXT` to `BYTEA`, the two text formats hex and escape are supported.
+
+**Examples:**
+
+```
+SET standard_conforming_strings = false;
+SELECT '\x3132'::BYTEA; -> '\x313332'
+SELECT '\x31   32  '::BYTEA; -> '\x3120202033322020'
+SELECT 'a b\230a'::BYTEA; -> '\x61206232333061'
+
+set standard_conforming_strings = true;
+SELECT '\x3132'::BYTEA; -> '\x3132'
+SELECT '\x31   32  '::BYTEA; -> '\x3132'
+SELECT 'a b\230a'::BYTEA; -> '\x6120629861'
+```
+
+### [](#output-format)Output format
+
+The output format for `BYTEA` is the hexadecimal representation of the bytes in lower case prefixed by `\x` (Note: in JSON `\` is escaped).
+
+**Example:**
+
+```
+SELECT 'a'::BYTEA;
+```
+
+**Returns:**
+
+```
+{
+    "data":
+    [
+        ["\\x61"]
+    ]
+}
+```
+
+### [](#importing-bytea-from-external-source)Importing `BYTEA` from external source
+
+The input format for importing binary data from an external source depends on the external file format.
+
+**For ORC or PARQUET files:** For a specific field type without annotation (UTF-8 for example): BYTE\_ARRAY (binary), bytes will be imported exactly as they are in the source. All the other types will be imported to the corresponding datatype (for example, BYTE\_ARRAY with UTF-8 annotation will be imported to `TEXT` data type) and then cast to type `BYTEA`.
+
+**For CSV, TSV, or JSON files:** The input data are read exactly as they are in the source, and then cast to data type `BYTEA`.
+
+JSON files must be UTF-8 encoded; however this is not required for CSV and TSV files. In the case that these files are not UTF-8 encoded, field values must not start with `\x` - data starting with the characters `\x` will throw an error on ingest. Any data not starting with the characters `\x` will be copied as bytes to the column of data type `BYTEA`.
+
+**CSV File Example:**
+
+*file*
+
+```csv
+'row1'
+'a�a'
+'\xaabf'
+15
+'15'
+```
+
+**SQL**
+
+```
+CREATE EXTERNAL TABLE ex_table
+(
+    column1 BYTEA
+) URL = 's3://...'
+  OBJECT_PATTERN = '...'
+  TYPE = (CSV);
+
+SELECT * FROM ex_table;
+```
+
+**Returns:**
+
+```table
+| column1    |
+| ---------- |
+| \x726f7731 |
+| \x61ff61   |
+| \xaabf     |
+| \x3135     |
+| \x3135     |
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands.md
new file mode 100644
index 0000000..fff1652
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands.md
@@ -0,0 +1,91 @@
+# [](#sql-commands)SQL commands
+
+Use the alphabetical list in the navigation pane to find the syntax for commands that you already know.
+
+Use the functional list below to find commands for a specific task area that you’re working in.
+
+- [Queries](#queries)  
+  Analyze data with `SELECT`. Tune and optimize query performance with other commands.
+- [Data management](#data-management)  
+  Move data between your data lake and Firebolt and between Firebolt resources.
+- [Data definition](#data-definition)  
+  Data definition language. Create, alter, drop, and otherwise manage objects like databases, tables, and views in your Firebolt account.
+- [Engines](#engines)  
+  Start, stop, and manage Firebolt engines.
+- [Metadata](#metadata)  
+  Query the Firebolt information schema for metadata related to its objects and resources.
+- [Access control](#access-control)  
+  Access control language. Create, alter and drop, and otherwise manage users, logins, service accounts and roles.
+
+## [](#queries)Queries
+
+- [EXPLAIN](/sql_reference/commands/queries/explain.html)
+- [RECOMMEND DDL](/sql_reference/commands/queries/recommend_ddl.html)
+- [SELECT](/sql_reference/commands/queries/select.html)
+
+## [](#data-management)Data management
+
+- [COPY FROM](/sql_reference/commands/data-management/copy-from.html)
+- [COPY TO](/sql_reference/commands/data-management/copy-to.html)
+- [DELETE](/sql_reference/commands/data-management/delete.html)
+- [INSERT](/sql_reference/commands/data-management/insert.html)
+- [TRUNCATE TABLE](/sql_reference/commands/data-management/truncate-table.html)
+- [UPDATE](/sql_reference/commands/data-management/update.html)
+- [VACUUM](/sql_reference/commands/data-management/vacuum.html)
+
+## [](#data-definition)Data definition
+
+- [ALTER ACCOUNT](/sql_reference/commands/data-definition/alter-account.html)
+- [ALTER DATABASE](/sql_reference/commands/data-definition/alter-database.html)
+- [ALTER TABLE](/sql_reference/commands/data-definition/alter-table.html)
+- [CREATE ACCOUNT](/sql_reference/commands/data-definition/create-account.html)
+- [CREATE AGGREGATING INDEX](/sql_reference/commands/data-definition/create-aggregating-index.html)
+- [CREATE DATABASE](/sql_reference/commands/data-definition/create-database.html)
+- [CREATE EXTERNAL TABLE](/sql_reference/commands/data-definition/create-external-table.html)
+- [CREATE FACT or DIMENSION TABLE](/sql_reference/commands/data-definition/create-fact-dimension-table.html)
+- [CREATE VIEW](/sql_reference/commands/data-definition/create-view.html)
+- [DROP ACCOUNT](/sql_reference/commands/data-definition/drop-account.html)
+- [DROP DATABASE](/sql_reference/commands/data-definition/drop-database.html)
+- [DROP INDEX](/sql_reference/commands/data-definition/drop-index.html)
+- [DROP TABLE](/sql_reference/commands/data-definition/drop-table.html)
+- [DROP VIEW](/sql_reference/commands/data-definition/drop-view.html)
+- [USE DATABASE](/sql_reference/commands/data-definition/use-database.html)
+
+## [](#engines)Engines
+
+- [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html)
+- [CREATE ENGINE](/sql_reference/commands/engines/create-engine.html)
+- [DROP ENGINE](/sql_reference/commands/engines/drop-engine.html)
+- [START ENGINE](/sql_reference/commands/engines/start-engine.html)
+- [STOP ENGINE](/sql_reference/commands/engines/stop-engine.html)
+- [USE ENGINE](/sql_reference/commands/engines/use-engine.html)
+
+## [](#metadata)Metadata
+
+- [DESCRIBE](/sql_reference/commands/metadata/describe.html)
+- [SHOW CACHE](/sql_reference/commands/metadata/show-cache.html)
+- [SHOW CATALOGS](/sql_reference/commands/metadata/show-catalogs.html)
+- [SHOW COLUMNS](/sql_reference/commands/metadata/show-columns.html)
+- [SHOW ENGINES](/sql_reference/commands/metadata/show-engines.html)
+- [SHOW INDEXES](/sql_reference/commands/metadata/show-indexes.html)
+- [SHOW TABLES](/sql_reference/commands/metadata/show-tables.html)
+- [SHOW VIEWS](/sql_reference/commands/metadata/show-views.html)
+
+## [](#access-control)Access control
+
+- [ALTER LOGIN](/sql_reference/commands/access-control/alter-login.html)
+- [ALTER NETWORK POLICY](/sql_reference/commands/access-control/alter-network-policy.html)
+- [ALTER SERVICE ACCOUNT](/sql_reference/commands/access-control/alter-service-account.html)
+- [ALTER USER](/sql_reference/commands/access-control/alter-user.html)
+- [CREATE LOGIN](/sql_reference/commands/access-control/create-login.html)
+- [CREATE NETWORK POLICY](/sql_reference/commands/access-control/create-network-policy.html)
+- [CREATE ROLE](/sql_reference/commands/access-control/create-role.html)
+- [CREATE SERVICE ACCOUNT](/sql_reference/commands/access-control/create-service-account.html)
+- [CREATE USER](/sql_reference/commands/access-control/create-user.html)
+- [DROP LOGIN](/sql_reference/commands/access-control/drop-login.html)
+- [DROP NETWORK POLICY](/sql_reference/commands/access-control/drop-network-policy.html)
+- [DROP ROLE](/sql_reference/commands/access-control/drop-role.html)
+- [DROP SERVICE ACCOUNT](/sql_reference/commands/access-control/drop-service-account.html)
+- [DROP USER](/sql_reference/commands/access-control/drop-user.html)
+- [GRANT](/sql_reference/commands/access-control/grant.html)
+- [REVOKE](/sql_reference/commands/access-control/revoke.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control.md
new file mode 100644
index 0000000..bbae0dd
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control.md
@@ -0,0 +1,21 @@
+## [](#access-control)Access control
+
+* * *
+
+- [ALTER LOGIN](/sql_reference/commands/access-control/alter-login.html)
+- [ALTER NETWORK POLICY](/sql_reference/commands/access-control/alter-network-policy.html)
+- [ALTER ROLE](/sql_reference/commands/access-control/alter-role.html)
+- [ALTER SERVICE ACCOUNT](/sql_reference/commands/access-control/alter-service-account.html)
+- [ALTER USER](/sql_reference/commands/access-control/alter-user.html)
+- [CREATE LOGIN](/sql_reference/commands/access-control/create-login.html)
+- [CREATE NETWORK POLICY](/sql_reference/commands/access-control/create-network-policy.html)
+- [CREATE ROLE](/sql_reference/commands/access-control/create-role.html)
+- [CREATE SERVICE ACCOUNT](/sql_reference/commands/access-control/create-service-account.html)
+- [CREATE USER](/sql_reference/commands/access-control/create-user.html)
+- [DROP LOGIN](/sql_reference/commands/access-control/drop-login.html)
+- [DROP NETWORK POLICY](/sql_reference/commands/access-control/drop-network-policy.html)
+- [DROP ROLE](/sql_reference/commands/access-control/drop-role.html)
+- [DROP SERVICE ACCOUNT](/sql_reference/commands/access-control/drop-service-account.html)
+- [DROP USER](/sql_reference/commands/access-control/drop-user.html)
+- [GRANT](/sql_reference/commands/access-control/grant.html)
+- [REVOKE](/sql_reference/commands/access-control/revoke.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_login.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_login.md
new file mode 100644
index 0000000..912b93e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_login.md
@@ -0,0 +1,44 @@
+# [](#alter-login)ALTER LOGIN
+
+Updates the configuration of the specified login.
+
+For more information, see [Managing logins](/Guides/managing-your-organization/managing-logins.html).
+
+## [](#syntax)Syntax
+
+```
+ALTER LOGIN <login_name> SET 
+      [ IS_PASSWORD_ENABLED = { TRUE | FALSE } ]
+      [ IS_MFA_ENABLED = { TRUE | FALSE } ]
+      [ NETWORK_POLICY = <network_policy_name> | DEFAULT ]
+      [ IS_ORGANIZATION_ADMIN = { TRUE | FALSE } ]
+      [ IS_ENABLED = { TRUE | FALSE } ]
+      [ FIRST_NAME = <first_name> ]
+      [ LAST_NAME = <last_name> ] 
+```
+
+or
+
+```
+ALTER LOGIN <login_name> RENAME TO <new_login_name>;
+```
+
+A login that was provisioned via SSO cannot be renamed.
+
+## [](#parameters)Parameters
+
+Parameter Description `<login_name>` The name of the login in the form of an email address. The login must be unique within the organization. `IS_PASSWORD_ENABLED` A `BOOLEAN` value specifying if login with password is enabled. By default this is `TRUE` and passwords can be used to log in. `IS_MFA_ENABLED` A `BOOLEAN` value specifying if the login has multi-factor authentication (MFA) enabled. By default this value is `FALSE`. If set to `TRUE`, an enrollment email will be sent to the `<login_name>`. `<network_policy_name>` An optional parameter to define the network policy to link to the created login. Specifying `DEFAULT` will detach any linked network policy. `IS_ORGANIZATION_ADMIN` A `BOOLEAN` value specifying if the login is an organization admin. By default this value is `FALSE`. `IS_ENABLED` A `BOOLEAN` value specifying whether authentication with this login should be possible. Disable login if you want to prevent access to the system without dropping it. `<first_name>`, `<last_name>` The first and last name of the user to use the login. If the parameter is included, these values cannot be empty. `<new_login_name>` The new name of the login in the form of an email address. The login must be unique within the organization. Note: if the login was provisioned via SSO, it cannot be renamed.
+
+## [](#example)Example
+
+The following command will rename the “alexs@acme.com” login to “alexspotter@acme.com”.
+
+```
+ALTER LOGIN "alexs@acme.com" RENAME TO "alexspotter@acme.com";
+```
+
+This command will link the network policy “my\_network\_policy” to the “alexs@acme.com” login.
+
+```
+ALTER LOGIN "alexs@acme.com" SET NETWORK_POLICY = "my_network_policy";
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_network_policy.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_network_policy.md
new file mode 100644
index 0000000..a02bd4d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_network_policy.md
@@ -0,0 +1,52 @@
+# [](#alter-network-policy)ALTER NETWORK POLICY
+
+Updates the configuration of the existing network policy by specifying its name, a list of internet protocol (IP) addresses to allow or block, and an optional description.
+
+For more information, see [Network policies](/Guides/security/network-policies.html).
+
+## [](#syntax)Syntax
+
+```
+ALTER NETWORK POLICY [ IF EXISTS ] <network_policy_name>
+    SET [ ALLOWED_IP_LIST = ( '<allowed_ip>', '<allowed_ip>' ... ) ]
+        [ BLOCKED_IP_LIST = ( '<blocked_ip>', '<blocked_ip>' ... ) ]
+        [ DESCRIPTION = '<description>' ]
+
+ALTER NETWORK POLICY [ IF EXISTS ] <network_policy_name>
+    ADD [ ALLOWED_IP_LIST = ( '<allowed_ip>', '<allowed_ip>' ... ) ]
+        [ BLOCKED_IP_LIST = ( '<blocked_ip>', '<blocked_ip>' ... ) ]
+
+ALTER NETWORK POLICY [ IF EXISTS ] <network_policy_name>
+    REMOVE [ BLOCKED_IP_LIST = ( '<blocked_ip>', '<blocked_ip>' ... ) ]
+           [ BLOCKED_IP_LIST = ( '<blocked_ip>', '<blocked_ip>' ... ) ]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<network_policy_name>` The name of the network policy to edit. `<allowed_ip>` A comma-separated and quoted list of IP addresses to **allow** in the specified network policy. `<blocked_ip>` A comma-separated and quoted list of IP addresses to **block** in the specified network policy. `<description>` (Optional) A description for the specified network policy.
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example modifies the existing network policy ‘my\_network\_policy’ by replacing its allowed and blocked IP lists with specified values and an updating its description:
+
+```
+ALTER NETWORK POLICY my_network_policy SET ALLOWED_IP_LIST = ('4.5.6.7', '2.4.5.7') BLOCKED_IP_LIST = ('6.7.8.9') DESCRIPTION = 'updated network policy'
+```
+
+**Example**
+
+The following code example adds an IP address `192.168.5.1` to the allowed list of the existing network policy `my_network_policy`:
+
+```
+ALTER NETWORK POLICY my_network_policy ADD ALLOWED_IP_LIST = ('192.168.5.1');
+```
+
+**Example**
+
+The following code example removes the IP address `6.7.8.9` from the blocked list of the network policy `my_network_policy`:
+
+```
+ALTER NETWORK POLICY my_network_policy REMOVE BLOCKED_IP_LIST = ('6.7.8.9');
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_role.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_role.md
new file mode 100644
index 0000000..f90060a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_role.md
@@ -0,0 +1,17 @@
+# [](#alter-role)ALTER ROLE
+
+Updates the specified role.
+
+## [](#alter-role-owner-to)ALTER ROLE OWNER TO
+
+Change the owner of a role.
+
+### [](#syntax)Syntax
+
+```
+ALTER ROLE <role> OWNER TO <user>
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<role>` Name of the role to change the owner of. `<user>` The new owner of the role.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_service_account.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_service_account.md
new file mode 100644
index 0000000..097248b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_service_account.md
@@ -0,0 +1,49 @@
+# [](#alter-service-account)ALTER SERVICE ACCOUNT
+
+Updates the configuration of the specified service account.
+
+For more information, see [Service accounts](/Guides/managing-your-organization/service-accounts.html).
+
+## [](#syntax)Syntax
+
+```
+ALTER SERVICE ACCOUNT <service_account_name> SET 
+      [ NETWORK_POLICY = <network_policy_name> | DEFAULT ] 
+      [ DESCRIPTION = <description> | DEFAULT ]
+      [ IS_ORGANIZATION_ADMIN = { TRUE | FALSE } ]
+      [ CONNECTION_PREFERENCE = { PUBLIC_ONLY | PRIVATE_ONLY | PREFER_PUBLIC | PREFER_PRIVATE | DEFAULT } ]
+      [ IS_ENABLED = { TRUE | FALSE } ]
+```
+
+or
+
+```
+ALTER SERVICE ACCOUNT <service_account_name> RENAME TO <new_name>;
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<service_account_name>` The name of the service account to edit. `<description>` An optional description for the service account. `<network_policy_name>` An optional parameter to define the network policy to link to the edited service account. Specifying `DEFAULT` will detach any linked network policy. `IS_ORGANIZATION_ADMIN` A `BOOLEAN` value specifying if the service account is an organization admin. By default, this value is `FALSE`. `IS_ENABLED` A `BOOLEAN` value specifying whether authentication with this service account should be possible. Disable the service account to prevent access without dropping it. `CONNECTION_PREFERENCE` Defines how the service account connects to Firebolt. The default value is `PREFER_PUBLIC` if not specified. See **Connection preferences** for details. `<new_name>` The new name of the service account. Must start with a letter and may contain only alphanumeric, digit, or underscore (\_) characters.
+
+### [](#connection-preferences)Connection Preferences
+
+The `CONNECTION_PREFERENCE` parameter determines how a [service account](/Guides/managing-your-organization/service-accounts.html) accesses Firebolt:
+
+- **`PUBLIC_ONLY`** : Allows access only through public APIs.
+- **`PRIVATE_ONLY`** : Allows access only through AWS PrivateLink.
+- **`PREFER_PUBLIC`** (Default): Prefers public APIs but can use AWS PrivateLink if needed.
+- **`PREFER_PRIVATE`** : Prefers AWS PrivateLink but can use public APIs if needed.
+
+## [](#example)Example
+
+The following code example renames the service account `sa1` to `serviceaccount1`:
+
+```
+ALTER SERVICE ACCOUNT "sa1" RENAME TO "serviceaccount1";
+```
+
+The following code example assigns the network policy `my_network_policy` to the `serviceaccount1` service account:
+
+```
+ALTER SERVICE ACCOUNT "serviceaccount1" SET NETWORK_POLICY = "my_network_policy";
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_user.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_user.md
new file mode 100644
index 0000000..2d31a56
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_alter_user.md
@@ -0,0 +1,59 @@
+# [](#alter-user)ALTER USER
+
+Updates the configuration of the specified user.
+
+For more information, see [Managing users](/Guides/managing-your-organization/managing-users.html).
+
+Users can modify most of their own account settings without requiring [RBAC](/Overview/Security/Role-Based%20Access%20Control/#role-based-access-control-rbac) permissions, except when altering [LOGIN](/Guides/managing-your-organization/managing-logins.html) configurations or a [SERVICE ACCOUNT](/Guides/managing-your-organization/service-accounts.html).
+
+## [](#alter-user-set)ALTER USER SET
+
+### [](#syntax)Syntax
+
+```
+ALTER USER <user_name> SET
+	[ LOGIN = <login_name> | DEFAULT ]
+        [ SERVICE_ACCOUNT = <service_account_name> | DEFAULT ]
+        [ DEFAULT_DATABASE = <database_name> | DEFAULT ]
+	[ DEFAULT_ENGINE = <engine_name> | DEFAULT ];
+```
+
+or
+
+```
+ALTER USER <user_name> RENAME TO <new_user_name>;
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<user_name>` The name of the user, may contain non-alpha-numeric characters such as exclamation points (!), percent signs (%), dots (.), underscores (\_), dashes (-), and asterisks (\*). Strings containing non-alphanumeric characters must be enclosed in single or double quotes. For more information about the full set of naming rules, see the [object identifiers guide](/Reference/object-identifiers.html#user-names). `<new_user_name>` The new name of the user, used with the `RENAME TO` option. The new user name can be any string, and can also contain spaces and non-alpha-numeric characters such as exclamation points (!), percent signs (%), at signs(@), dot signs (.), underscore signs (\_), minus signs (-), and asterisks (\*). If the string contains spaces or non-alphanumeric characters, it must be enclosed in single or double quotes. `<login_name>` An optional, case-insensitive parameter to specify the name of the login to link the user with, used with the `SET` option. This cannot be used in conjunction with the `SERVICE_ACCOUNT` parameter - a user can be linked to a login OR a service account but not both. `DEFAULT` disassociates the user from its login. The user will become unusable before it’s re-associated with some login or service account. `<service_account_name>` An optional parameter to specify the name of the service account to link the user with, used with the `SET` option. This cannot be used in conjunction with the `LOGIN` parameter - a user can be linked to a login OR a service account but not both. `DEFAULT` disassociates the user from its service account. The user will become unusable before it’s re-associated with some login or service account. `<database_name>` An optional parameter to define a default database for the user (for future purposes). Used with the `SET` option. `<engine_name>` An optional parameter to define a default engine for the user (for future purposes).Used with the `SET` option.
+
+### [](#example)Example
+
+The following command will rename the “alex” account to “alexs”.
+
+```
+ALTER USER "alex" RENAME TO "alexs";
+```
+
+This command will link the user “alex” to the “alexs@acme.com” login.
+
+```
+ALTER USER alex SET LOGIN="alexs@acme.com";
+```
+
+## [](#alter-user-owner-to)ALTER USER OWNER TO
+
+Change the owner of a user. The current owner of a user can be viewed in the `information_schema.users` view on `user_owner` column.
+
+Check [ownership](/Guides/security/ownership.html) page for more info.
+
+### [](#syntax-1)Syntax
+
+```
+ALTER USER <user_name> OWNER TO <user>
+```
+
+### [](#parameters-1)Parameters
+
+Parameter Description `<user_name>` The name of the user to change the owner of. `<user>` The new owner of the user.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_login.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_login.md
new file mode 100644
index 0000000..a1572d3
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_login.md
@@ -0,0 +1,29 @@
+# [](#create-login)CREATE LOGIN
+
+Creates a new login.
+
+For more information, see [Managing logins](/Guides/managing-your-organization/managing-logins.html).
+
+## [](#syntax)Syntax
+
+```
+CREATE LOGIN [ IF NOT EXISTS ] <login_name> 
+	   WITH [ IS_PASSWORD_ENABLED = { TRUE | FALSE }]
+            [ IS_MFA_ENABLED = { TRUE | FALSE }]
+            [ NETWORK_POLICY = <network_policy_name>]
+            [ IS_ORGANIZATION_ADMIN = { TRUE | FALSE }]
+	        FIRST_NAME = <first_name>,
+	        LAST_NAME = <last_name> 
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<login_name>` The name of the login in the form of an email address. The login must be unique within the organization. `IS_PASSWORD_ENABLED` A `BOOLEAN` value specifying if login with password is enabled. By default this is `TRUE` and passwords can be used to log in. `IS_MFA_ENABLED` A `BOOLEAN` value specifying if the login has multi-factor authentication (MFA) enabled. By default this value is `FALSE`. If set to `TRUE`, an enrollment email will be sent to the `<login_name>`. `<network_policy_name>` An optional parameter to define the network policy to link to the created login. `IS_ORGANIZATION_ADMIN` A `BOOLEAN` value specifying if the login is an organization admin. By default this value is `FALSE`. `<first_name>`, `<last_name>` The first and last name of the user that will use the created login.
+
+## [](#example)Example
+
+The following command will create an account in the US East (N. Virginia) region.
+
+```
+CREATE LOGIN "alexs@acme.com" WITH FIRST_NAME = 'Alex' LAST_NAME = 'Summers';
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_network_policy.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_network_policy.md
new file mode 100644
index 0000000..8f4af42
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_network_policy.md
@@ -0,0 +1,26 @@
+# [](#create-network-policy)CREATE NETWORK POLICY
+
+Creates a new network policy.
+
+For more information, see [Network policies](/Guides/security/network-policies.html).
+
+## [](#syntax)Syntax
+
+```
+CREATE NETWORK POLICY [IF NOT EXISTS] <network_policy_name>
+WITH ALLOWED_IP_LIST = ( '<allowed_ip1>', '<allowed_ip2>', ... )
+[ BLOCKED_IP_LIST = ( '<blocked_ip1>', '<blocked_ip2>', ... ) ]
+[ DESCRIPTION = '<description>' ]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<network_policy_name>` The name of the network policy. Must start with a letter, and may contain only alphanumeric and underscore(\_) characters. `<allowed_ip>` The comma-separated and quoted list of IP addresses to allow in the created network policy. `<blocked_ip>` An optional comma-separated and quoted list of IP addresses to block in the created network policy. `<description>` An optional description for the created network policy.
+
+## [](#example)Example
+
+The following command will create a network policy that allows IPs ‘4.5.6.1’ and ‘2.4.5.1’ and blocks the IP address ‘6.7.8.1’, with a description:
+
+```
+CREATE NETWORK POLICY my_network_policy WITH ALLOWED_IP_LIST = ('4.5.6.1', '2.4.5.1') DESCRIPTION = 'my new network policy'
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_role.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_role.md
new file mode 100644
index 0000000..b6ef59f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_role.md
@@ -0,0 +1,33 @@
+# [](#create-role)CREATE ROLE
+
+Creates a new role.
+
+For more information, see [Role-based access control](/Guides/security/rbac.html).
+
+## [](#syntax)Syntax
+
+```
+CREATE ROLE [ IF NOT EXISTS ] <role_name>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<role_name>` The name of the role.
+
+## [](#example)Example
+
+The following command will create a role “user\_role”
+
+```
+CREATE ROLE user_role;
+```
+
+## [](#example-2)Example 2
+
+The following command will create a role “user\_role\_2”
+
+```
+CREATE ROLE IF NOT EXISTS my_role_2
+```
+
+If “my\_role\_2” exists, no error message is thrown.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_service_account.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_service_account.md
new file mode 100644
index 0000000..99c1529
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_service_account.md
@@ -0,0 +1,38 @@
+# [](#create-service-account)CREATE SERVICE ACCOUNT
+
+Creates a new service account.
+
+For more information, see [Service accounts](/Guides/managing-your-organization/service-accounts.html).
+
+## [](#syntax)Syntax
+
+```
+CREATE SERVICE ACCOUNT [ IF NOT EXISTS ] <service_account_name> 
+    [ WITH
+    [ DESCRIPTION = <description> ] 
+    [ NETWORK_POLICY = <network_policy_name> ]
+    [ IS_ORGANIZATION_ADMIN = { TRUE|FALSE } ]
+    [ CONNECTION_PREFERENCE = { PUBLIC_ONLY | PRIVATE_ONLY | PREFER_PUBLIC | PREFER_PRIVATE | DEFAULT } ]
+    ]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<service_account_name>` The name of the service account. Must start with a letter and may contain only alphanumeric, digit, or underscore (\_) characters. `<description>` An optional description for the service account. `<network_policy_name>` An optional parameter to define the network policy to link to the created service account. `IS_ORGANIZATION_ADMIN` A `BOOLEAN` value specifying if the login is an organization admin. By default, this value is `FALSE`. `CONNECTION_PREFERENCE` Defines how the service account connects to Firebolt. The default value is `PREFER_PUBLIC` if not specified. See **Connection preferences** for details.
+
+### [](#connection-preferences)Connection preferences
+
+The `CONNECTION_PREFERENCE` parameter determines how a [service account](/Guides/managing-your-organization/service-accounts.html) accesses Firebolt:
+
+- **`PUBLIC_ONLY`** : Allows access only through public APIs.
+- **`PRIVATE_ONLY`** : Allows access only through AWS PrivateLink.
+- **`PREFER_PUBLIC`** (Default): Prefers public APIs but can use AWS PrivateLink if needed.
+- **`PREFER_PRIVATE`** : Prefers AWS PrivateLink but can use public APIs if needed.
+
+## [](#example)Example
+
+The following code example creates a service account `sa1` linked to the `my_network_policy` network policy:
+
+```
+CREATE SERVICE ACCOUNT "sa1" WITH NETWORK_POLICY = my_network_policy
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_user.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_user.md
new file mode 100644
index 0000000..f8d67c1
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_create_user.md
@@ -0,0 +1,29 @@
+# [](#create-user)CREATE USER
+
+Creates a new user in Firebolt.
+
+For more information, see [Managing users and roles](/Guides/managing-your-organization/managing-users.html).
+
+## [](#syntax)Syntax
+
+```
+CREATE USER [ IF NOT EXISTS ] <user_name>  
+[ WITH 
+[ LOGIN = <login_name> | SERVICE_ACCOUNT = <service_account> ]
+[ DEFAULT_DATABASE = <database_name> ]
+[ DEFAULT_ENGINE = <engine_name> ]
+[ ROLE = <role_name>[,...<role_name>] ]
+]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<user_name>` The name of the user, may contain non-alpha-numeric characters such as exclamation points (!), percent signs (%), dots (.), underscores (\_), dashes (-), and asterisks (\*). Strings containing non-alphanumeric characters must be enclosed in single or double quotes. For more information about the full set of naming rules, see the [object identifiers guide](/Reference/object-identifiers.html#user-names). `<login>` (Optional) Specifies the name of the login to link the user with. This cannot be used in conjunction with the `SERVICE_ACCOUNT` parameter because a user can be linked to either a login OR a service account but not both. `<service_account>` (Optional) Specifies the name of the service account to link the user with. The `<service_account>` parameter cannot be used in conjunction with the `LOGIN_NAME` parameter because a user can be linked to a login OR a service account but not both. `<database_name>` (Optional) Defines the default database for the user. `<engine_name>` (Optional) Defines the default engine for the user. `<role_name>[, ...<role_name>]` (Optional) Defines a role for the user. Additional roles can be granted after the user is created. When assigning multiple roles, enclose the list of roles in parentheses. If no role is specified, the user is not granted any roles.
+
+## [](#example)Example
+
+The following code example creates a user named `alex`, links it to the login `alexs@acme.com`, and assigns it the roles of `analyst` and `data_engineer`:
+
+```
+CREATE USER alex WITH LOGIN= "alexs@acme.com" ROLE= (analyst, data_engineer);
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_login.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_login.md
new file mode 100644
index 0000000..4cb1413
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_login.md
@@ -0,0 +1,25 @@
+# [](#drop-login)DROP LOGIN
+
+Deletes an account.
+
+For more information, see [Managing logins](/Guides/managing-your-organization/managing-logins.html).
+
+## [](#syntax)Syntax
+
+```
+DROP LOGIN [ IF EXISTS ] <login_name>;
+```
+
+If the login is linked to a user, it can not be dropped. In order to drop a login linked to a user, the link must be reset `alter user foo set login="new-login@acme.com"|DEFAULT` or the user dropped.
+
+## [](#parameters)Parameters
+
+Parameter Description `<login_name>` The name of the login to delete.
+
+## [](#example)Example
+
+The following command will delete the “alexs@acme.com” login.
+
+```
+DROP LOGIN "alexs@acme.com";
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_network_policy.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_network_policy.md
new file mode 100644
index 0000000..104c2fc
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_network_policy.md
@@ -0,0 +1,25 @@
+# [](#drop-network-policy)DROP NETWORK POLICY
+
+Deletes a network policy.
+
+For more information, see [Network policies](/Guides/security/network-policies.html).
+
+## [](#syntax)Syntax
+
+```
+DROP NETWORK POLICY <network_policy_name> [ RESTRICT | CASCADE ]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<network_policy_name>` The name of the network policy to delete. `RESTRICT` or `CASCADE` An optional parameter to specify deletion mode.  
+RESTRICT mode prevents dropping the network policy if there is any login, service account or organization linked. RESTRICT mode is used by default.  
+CASCADE mode automatically drops the network policy and all its links to other objects.
+
+## [](#example)Example
+
+The following command will delete “my\_network\_policy”.
+
+```
+DROP NETWORK POLICY my_network_policy [ RESTRICT | CASCADE ]
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_role.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_role.md
new file mode 100644
index 0000000..8cf36b9
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_role.md
@@ -0,0 +1,35 @@
+# [](#drop-role)DROP ROLE
+
+Deletes a role. Note that role cannot be dropped if there are permissions granted to the role, in this case error message will be displayed and you need manually to drop permissions granted to the role and retry.
+
+For more information, see [Role-based access control](/Guides/security/rbac.html).
+
+A role cannot be dropped if there are permissions granted to the role. In this case, an error message will be displayed, and you need to manually drop the permissions granted to the role and retry.
+
+## [](#syntax)Syntax
+
+```
+DROP ROLE [ IF EXISTS ] <role_name>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<role_name>` The name of the role.
+
+## [](#example)Example
+
+The following command will delete the role “user\_role”
+
+```
+DROP ROLE user_role;
+```
+
+### [](#example-2)Example 2
+
+The following command will delete the role “my\_role\_2”
+
+```
+DROP ROLE IF EXISTS my_role_2
+```
+
+If “my\_role\_2” does not exist, no error message is thrown.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_service_account.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_service_account.md
new file mode 100644
index 0000000..ffaef32
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_service_account.md
@@ -0,0 +1,25 @@
+# [](#drop-service-account)DROP SERVICE ACCOUNT
+
+Deletes a service account.
+
+For more information, see [Service accounts](/Guides/managing-your-organization/service-accounts.html).
+
+## [](#syntax)Syntax
+
+```
+DROP SERVICE ACCOUNT <service_account_name>;
+```
+
+If the service account is linked to a user, it can not be dropped. In order to drop a service account linked to a user, the link must be reset `alter user foo set service_account=new_service_account|DEFAULT` or the user dropped.
+
+## [](#parameters)Parameters
+
+Parameter Description `<service_account_name>` The name of the service account to delete.
+
+## [](#example)Example
+
+The following command will delete the “sa1” service account.
+
+```
+DROP SERVICE ACCOUNT "sa1";
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_user.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_user.md
new file mode 100644
index 0000000..dcd0438
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_drop_user.md
@@ -0,0 +1,27 @@
+# [](#drop-user)DROP USER
+
+Deletes a user.
+
+For more information, see [Managing users](/Guides/managing-your-organization/managing-users.html).
+
+A user cannot be dropped if it owns objects. In this case, an error message will be displayed, and you need to manually drop the objects, or transfer ownership.
+
+for more information, see [Ownership](/Guides/security/ownership.html).
+
+## [](#syntax)Syntax
+
+```
+DROP USER [ IF EXISTS ] <user_name> ;
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<user_name>` The name of the user to delete. If the user name contains spaces or non-alphanumeric characters, it must be enclosed in single or double quotes.
+
+## [](#example)Example
+
+The following command will delete the “alex” user.
+
+```
+DROP USER alex;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_grant.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_grant.md
new file mode 100644
index 0000000..0df2966
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_grant.md
@@ -0,0 +1,103 @@
+# [](#grant)GRANT
+
+Grants permission or assignment to a role. `GRANT` can also be used to assign a role to another role or a user.
+
+For more information, see [Role-based access control](/Overview/Security/Role-Based%20Access%20Control/role-management/).
+
+## [](#grant-privilege)GRANT PRIVILEGE
+
+Grants a permission to a role.
+
+Only an account\_admin or a role owner can grant a permission to a role. To grant a permission, you must first have that permission granted to you.
+
+### [](#syntax)Syntax
+
+```
+GRANT <permission> ON <object_type> <object_name> [IN <object_type> <object_name>] TO <role_name>
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<permission>` The name of the permission to grant to a role. Available permissions vary depending on the object that they apply to. For a full list, see [Permissions](/Overview/Security/Role-Based%20Access%20Control/role-management/). `<object_type>` The type of object to grant permissions on. `<object_name>` The name of the object to grant permissions on. `<role_name>` The name of the role to grant the permission to.
+
+### [](#examples)Examples
+
+**Grant `USAGE` on a single database**
+
+The following code example grants the `USAGE` privilege on the `db` database to the role `user_role`, allowing it to access the database:
+
+```
+GRANT USAGE ON DATABASE db TO user_role;
+```
+
+**Grant `USAGE` on all databases within an account**
+
+The following code example grants the `USAGE` privilege on all databases in the `dev` account to the role `user_role`, allowing access to them:
+
+```
+GRANT USAGE ANY DATABASE ON ACCOUNT dev TO user_role;
+```
+
+**Grant access to a databse, schema, and a specific table**
+
+The following code example grants the role `user_role` access to the `db` database, the `public` schema within the `db` database, and permission to read data from the `my_table` table in the `public` schema:
+
+```
+GRANT USAGE ON DATABASE db TO user_role;
+GRANT USAGE ON SCHEMA public IN DATABASE db TO user_role;
+USE DATABASE db;
+GRANT SELECT ON TABLE my_table IN SCHEMA public TO user_role;
+```
+
+**Grant access to a database, schema, and all operations on a specific table**
+
+The following code example grants the role `user_role` access to the `db` database, the `public` schema within the `db` database, and all permissions on the `my_table` table in the `public` schema:
+
+```
+GRANT USAGE ON DATABASE db TO user_role;
+GRANT USAGE ON SCHEMA public IN DATABASE db TO user_role;
+USE DATABASE db;
+GRANT ALL ON TABLE my_table IN SCHEMA public TO user_role;
+```
+
+**Grant access to all existing and future tables or views in a schema**
+
+The following code example grants `user_role` access to the `db` database, the `public` schema within the `db` database, and permission to query all existing and future tables or views in the `public` schema:
+
+```
+GRANT USAGE ON DATABASE db TO user_role;
+GRANT USAGE ON SCHEMA public IN DATABASE db TO user_role;
+GRANT SELECT ANY ON SCHEMA public IN DATABASE db TO user_role;
+```
+
+## [](#grant-role)GRANT ROLE
+
+Grants a role to either a user or another role, allowing the recipient to inherit the permissions associated with the granted role.
+
+### [](#syntax-1)Syntax
+
+```
+GRANT ROLE <role_name> TO { USER <user_name> | ROLE <role_name_2> }
+```
+
+### [](#parameters-1)Parameters
+
+Parameter Description `<role_name>` The name of the role to grant. `<user_name>` The name of the user to grant `<role_name>` to. `<role_name_2>` The name of the role to assign the role to.
+
+### [](#examples-1)Examples
+
+**Grant a role to another role**
+
+The following code example assigns the `role_name` role to `role_name_2`, allowing `role_name_2` to inherit all the permissions granted to `role_name`:
+
+```
+GRANT ROLE role_name TO ROLE role_name_2;
+```
+
+**Grant a role to a user**
+
+The following code example assigns the `role_name` role to `user_name`, allowing the user to inherit all the permissions granted to `role_name`:
+
+```
+GRANT ROLE role_name TO USER user_name;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_revoke.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_revoke.md
new file mode 100644
index 0000000..8650ea0
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_access_control_revoke.md
@@ -0,0 +1,96 @@
+# [](#revoke)REVOKE
+
+Revokes permissions from a role. `REVOKE` can also be used to revoke a role from another role or a user.
+
+For more information, see [Role-based access control](/Guides/security/rbac.html).
+
+## [](#revoke-privilege)REVOKE PRIVILEGE
+
+Revokes a permission from a role.
+
+Only account\_admin or a role owner can revoke a permission to a role.
+
+### [](#syntax)Syntax
+
+```
+REVOKE <permission> ON <object_type> <object_name> [IN <object_type> <object_name>] FROM <role_name>
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<permission>` The name of the permission to revoke from a role. Permissions that can be revoked vary depending on the object that they apply to. For a full list, see [Permissions](/Overview/Security/Role-Based%20Access%20Control/). `<object_type>` The type of the object to revoke permissions from. `<object_name>` The name of the object to revoke permissions from. `<role_name>` The name of the role from which the permission will be revoked.
+
+### [](#examples)Examples
+
+**Revoke `MODIFY` permission on a database**
+
+The following code example revokes the `MODIFY` permission on the `db` database from the role `user_role`, preventing it from making changes to the database:
+
+```
+REVOKE MODIFY ON DATABASE db FROM user_role;
+```
+
+**Revoke all permissions on a database**
+
+The following code example revokes the all permissions on the `db` database from the role `user_role`, preventing all operations on it:
+
+```
+REVOKE ALL ON DATABASE db FROM user_role;
+```
+
+**Revoke `USAGE` permissions on all databases in an account**
+
+The following code example revokes `USAGE` permissions on all databases in the `dev` account from the role `user_role`, preventing it from accessing metadata or using those databases:
+
+```
+REVOKE USAGE ANY DATABASE ON ACCOUNT dev FROM user_role;
+```
+
+**Revoke `SELECT` permission on a specific table**
+
+The following code example sets the active database to `db` and revokes `user_role`’s permission to read data from the `my_table` table in the `public` schema.:
+
+```
+USE DATABASE db;
+REVOKE SELECT ON TABLE my_table IN SCHEMA public TO user_role;
+```
+
+**Revoke `SELECT` permission on all tables in a schema**
+
+The following code revokes `user_role`’s permission to read data from all existing and future tables in the `public` schema of the `db` database:
+
+```
+REVOKE SELECT ANY ON SCHEMA public  IN DATABASE db TO user_role;
+```
+
+## [](#revoke-role)REVOKE ROLE
+
+Revokes a role from a user or from another role.
+
+### [](#syntax-1)Syntax
+
+```
+REVOKE ROLE <role_name> FROM { USER <user_name> | ROLE <role_name_2> }
+```
+
+## [](#parameters-1)Parameters
+
+Parameter Description `<role_name>` The name of the role to revoke. `<user_name>` The name of the user from which to revoke the `<role_name>` role. `<role_name_2>` The name of the role from which to revoke the role.
+
+### [](#examples-1)Examples
+
+**Revoke a role from another role**
+
+The following code example removes the `role_name` role from `role_name_2`, revoking access to permissions granted to `role_name`:
+
+```
+REVOKE ROLE role_name FROM ROLE role_name_2;
+```
+
+**Revoke a role from a user**
+
+The following command revokes role `role_name` from user `user_name`, removing the user’s access to the permissions granted to `role_name`:
+
+```
+REVOKE ROLE role_name FROM USER user_name;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition.md
new file mode 100644
index 0000000..df412c2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition.md
@@ -0,0 +1,26 @@
+## [](#data-definition)Data definition
+
+* * *
+
+- [ALTER ACCOUNT](/sql_reference/commands/data-definition/alter-account.html)
+- [ALTER DATABASE](/sql_reference/commands/data-definition/alter-database.html)
+- [ALTER ORGANIZATION](/sql_reference/commands/data-definition/alter-organization.html)
+- [ALTER SCHEMA](/sql_reference/commands/data-definition/alter-schema.html)
+- [ALTER TABLE](/sql_reference/commands/data-definition/alter-table.html)
+- [ALTER VIEW](/sql_reference/commands/data-definition/alter-view.html)
+- [CREATE ACCOUNT](/sql_reference/commands/data-definition/create-account.html)
+- [CREATE AGGREGATING INDEX](/sql_reference/commands/data-definition/create-aggregating-index.html)
+- [CREATE DATABASE](/sql_reference/commands/data-definition/create-database.html)
+- [CREATE EXTERNAL TABLE](/sql_reference/commands/data-definition/create-external-table.html)
+- [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html)
+- [CREATE TABLE](/sql_reference/commands/data-definition/create-fact-dimension-table.html)
+- [CREATE TABLE AS SELECT (CTAS)](/sql_reference/commands/data-definition/create-fact-dimension-table-as-select.html)
+- [CREATE TABLE CLONE](/sql_reference/commands/data-definition/create-table-clone.html)
+- [CREATE VIEW](/sql_reference/commands/data-definition/create-view.html)
+- [DROP ACCOUNT](/sql_reference/commands/data-definition/drop-account.html)
+- [DROP DATABASE](/sql_reference/commands/data-definition/drop-database.html)
+- [DROP INDEX](/sql_reference/commands/data-definition/drop-index.html)
+- [DROP LOCATION](/sql_reference/commands/data-definition/drop-location.html)
+- [DROP TABLE](/sql_reference/commands/data-definition/drop-table.html)
+- [DROP VIEW](/sql_reference/commands/data-definition/drop-view.html)
+- [USE DATABASE](/sql_reference/commands/data-definition/use-database.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_account.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_account.md
new file mode 100644
index 0000000..1e60ea2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_account.md
@@ -0,0 +1,23 @@
+# [](#alter-account)ALTER ACCOUNT
+
+Updates the configuration of the specified database `<database_name>`.
+
+For more information, see [Managing accounts](/Guides/managing-your-organization/managing-accounts.html).
+
+## [](#syntax)Syntax
+
+```
+ALTER ACCOUNT <account_name> RENAME TO <new_account_name>;
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<account_name>` The name of the account to be altered. `<new_account_name>` The new name for the account. The account name must start and end with an alphabetic character and cannot contain spaces or special characters except for hyphens (-).
+
+## [](#example)Example
+
+The following command will rename the “dev” account to “staging”.
+
+```
+ALTER ACCOUNT dev RENAME TO staging;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_database.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_database.md
new file mode 100644
index 0000000..e775633
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_database.md
@@ -0,0 +1,40 @@
+# [](#alter-database)ALTER DATABASE
+
+Updates the configuration of the specified database.
+
+## [](#alter-database-description)ALTER DATABASE DESCRIPTION
+
+### [](#syntax)Syntax
+
+```
+ALTER DATABASE <database_name> WITH
+    [DESCRIPTION = <description>]
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<database_name>` The name of the database to be altered. `<description>` The description of the database.
+
+### [](#example)Example
+
+The following example alters a description of the database:
+
+```
+ALTER DATABASE my_database WITH DESCRIPTION = 'Database for query management';
+```
+
+## [](#alter-database-owner-to)ALTER DATABASE OWNER TO
+
+Change the owner of a database. The current owner of a database can be viewed in the [information\_schema.catalogs](/sql_reference/information-schema/catalogs.html) view on `catalog_owner` column.
+
+check [ownership](/Guides/security/ownership.html) page for more info.
+
+### [](#syntax-1)Syntax
+
+```
+ALTER DATABASE <database_name> OWNER TO <user>
+```
+
+### [](#parameters-1)Parameters
+
+Parameter Description `<database_name>` The name of the database to change the owner of. `<user>` The new owner of the database.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_organization.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_organization.md
new file mode 100644
index 0000000..3aadd0b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_organization.md
@@ -0,0 +1,42 @@
+# [](#alter-organization)ALTER ORGANIZATION
+
+Updates the specified organization to manage Single Sign-On configuration.
+
+For more information, see [Configure SSO](/Guides/security/sso/).
+
+## [](#syntax)Syntax
+
+```
+ALTER ORGANIZATION SET 
+  [ SSO = '{
+      “signOnUrl”: “<signOnUrl>”,
+      “signOutUrl”: “<signOutUrl>”, 
+      “issuer”: “<issuer>”,
+      “provider”: “<idp>”,
+      “label”: “<label>”,
+      “fieldMapping”: “<field_mapping>”,
+      “certificate”: “<certficate>”,
+  }' ]
+  [ NETWORK_POLICY = [ DEFAULT | <network_policy_name> ]
+  ;
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<signOnUrl>` The sign-on URL, provided by the SAML identity provider, to which Firebolt sends the SAML requests. The URL is IdP-specific and is determined by the identity provider during configuration. `<signOutUrl>` Optional. The sign-out URL, provided by the application owner, to be used when the user signs out of the application. `<issuer>` A unique value generated by the SAML identity provider specifying the issuer name. `<idp>` The provider’s name - for example: “Okta”. Possible values include: `Okta`, `Onelogin`, `Salesforce`, `PingFederate`, or `Custom`. Use `Custom` label if you are using a SAML 2.0-compliant service or application as your IdP. Once the provider has been selected, it can’t be changed, but you can [delete the SSO configuration](/Guides/security/sso/custom-sso.html#delete-sso). `<label>` The label to use for the SSO login button. If not provided, the IdP field value is used. `<field_mapping>` Optional. Mapping to your identity provider’s first and last name in key-value pairs. Mapping is required for Firebolt to fill in the login’s given and last names the first time the user logs in using SSO. If this field remains empty when a login that represents the user is being created, the login’s first and last name fields will contain “NA”. Those fields can be updated later by running the [ALTER LOGIN](/sql_reference/commands/access-control/alter-login.html) command. `<certificate>` The certificate to verify the communication between the identity provider and Firebolt. `<network_policy_name>` An optional parameter to define the network policy to link to the organization. Specifying `DEFAULT` will detach any linked network policy.
+
+## [](#example)Example
+
+The following command will configure SSO using the Okta identity provider. For more examples for other IdPs, see [Configure your identity provider](/Guides/security/sso/).
+
+```
+ALTER ORGANIZATION SET SSO = '{
+  “signOnUrl”: “https://abc.okta.com/app/okta_firebolt_app_id/sso/saml”,
+  “signOutUrl”: “https://myapp.exampleco.com/saml/logout”, 
+  “issuer”: “issuer”,
+  “provider”: “Okta”, 
+  “label”: “Okta”,
+  “fieldMapping”: “mapping”,
+  “certificate”: “XXXXXXXXXXXXXXXX”,
+}';
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_schema.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_schema.md
new file mode 100644
index 0000000..61fb39d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_schema.md
@@ -0,0 +1,20 @@
+# [](#alter-schema)ALTER SCHEMA
+
+Updates the specified SCHEMA.
+
+## [](#alter-schema-owner-to)ALTER SCHEMA OWNER TO
+
+Change the owner of a schema.  
+The current owner of a view can be viewed in the `information_schema.schemata` view on `schema_owner` column.
+
+check [ownership](/Guides/security/ownership.html) page for more info.
+
+### [](#syntax)Syntax
+
+```
+ALTER SCHEMA <schema> OWNER TO <user>
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<schema>` Name of the schema to change the owner of. `<user>` The new owner of the view.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_table.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_table.md
new file mode 100644
index 0000000..7aa4986
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_table.md
@@ -0,0 +1,87 @@
+# [](#alter-table)ALTER TABLE
+
+Updates the specified table.
+
+## [](#alter-table-add-column)ALTER TABLE ADD COLUMN
+
+Adds a column to an existing table.
+
+### [](#syntax)Syntax
+
+```
+ALTER TABLE <table> ADD COLUMN [IF NOT EXISTS] <column_name> <column_type> [NULL | NOT NULL] [DEFAULT <expression>]
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<table>` Name of the table to which to add the column. `<column_name>` An identifier that specifies the name of the column that will be added to the table. `<column_type>` Specifies the data type for the column. `IF NOT EXISTS` If specified, this clause prevents an error message that would occur if the column already exists in the table.
+
+### [](#column-constraints--default-expression)Column constraints &amp; default expression
+
+`DEFAULT <expression>` Determines the value that will be used for the column when this column is omitted in an `INSERT` statement. It also determines the value that is used for the rows that were inserted before the column was added. `NULL` | `NOT NULL` Determines if the column may or may not contain `NULL`s.
+
+### [](#limitations)Limitations
+
+The query can only be executed under the following conditions:
+
+- Only for managed tables created on Firebolt version 4.10 or higher (external tables are not supported).
+- The table must not have any dependent views.
+- The default expression must contain only literals or functions `CURRENT_DATE()`, `LOCALTIMESTAMP()`, `CURRENT_TIMESTAMP()`, and `NOW()`.
+
+## [](#alter-table-drop-partition)ALTER TABLE DROP PARTITION
+
+Use to delete a partition from a fact or dimension table.
+
+Dropping a partition deletes the partition and the data stored in that partition.
+
+### [](#syntax-1)Syntax
+
+```
+ALTER TABLE <table> DROP PARTITION <value1>[,...<value2]
+```
+
+### [](#parameters-1)Parameters
+
+Parameter Description `<table>` Name of the table from which to drop the partition. `<value1>[,...<value2>]` An ordered set of one or more values corresponding to the partition key definition. This specifies the partition to drop. When dropping partitions with composite keys (more than one key value), specify all key values in the same order as they were defined. Only partitions with values that match the entire composite key are dropped.
+
+### [](#examples)Examples
+
+See the examples in [Working with partitions](/Overview/indexes/using-indexes.html#partitions-in-tables).
+
+## [](#alter-table-owner-to)ALTER TABLE OWNER TO
+
+Change the owner of a table. The current owner of a table can be viewed in the `information_schema.tables` view on `table_owner` column.
+
+check [ownership](/Guides/security/ownership.html) page for more info.
+
+### [](#syntax-2)Syntax
+
+```
+ALTER TABLE <table> OWNER TO <user>
+```
+
+### [](#parameters-2)Parameters
+
+Parameter Description `<table>` Name of the table to change the owner of. `<user>` The new owner of the table.
+
+## [](#alter-table-rename-to)ALTER TABLE RENAME TO
+
+Renames a table.
+
+### [](#syntax-3)Syntax
+
+```
+ALTER TABLE [IF EXISTS] <table_name> RENAME TO <new_table_name>
+```
+
+### [](#parameters-3)Parameters
+
+Parameter Description `<table_name>` The name of the table to rename. `<new_table_name>` The new name of the table.
+
+### [](#limitations-1)Limitations
+
+The query can only be executed under the following conditions:
+
+- Only for managed tables created on Firebolt version 4.10 or higher (external tables are not supported).
+- The table must not have any dependent views.
+- Renaming tables across schemas and databases is not supported. Consider using [CREATE TABLE CLONE](/sql_reference/commands/data-definition/create-table-clone.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_view.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_view.md
new file mode 100644
index 0000000..0f9111f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_alter_view.md
@@ -0,0 +1,19 @@
+# [](#alter-view)ALTER VIEW
+
+Updates the specified VIEW.
+
+## [](#alter-view-owner-to)ALTER VIEW OWNER TO
+
+Change the owner of a view. The current owner of a view can be viewed in the `information_schema.views` view on `view_owner` column.
+
+check [ownership](/Guides/security/ownership.html) page for more info.
+
+### [](#syntax)Syntax
+
+```
+ALTER VIEW <view> OWNER TO <user>
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<view>` Name of the view to change the owner of. `<user>` The new owner of the view.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_account.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_account.md
new file mode 100644
index 0000000..e79483c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_account.md
@@ -0,0 +1,26 @@
+# [](#create-account)CREATE ACCOUNT
+
+Creates a new account.
+
+For more information, see [Managing accounts](/Guides/managing-your-organization/managing-accounts.html).
+
+Organizations can have 20 accounts per organization and you can use `CREATE ACCOUNT` 25 times. If you have a need for additional account creations beyond this limit, contact [Firebolt Support](/Reference/help-menu.html) for assistance. Our team can provide guidance and, if appropriate, adjust your account settings to accommodate your needs.
+
+## [](#syntax)Syntax
+
+```
+CREATE ACCOUNT [IF NOT EXISTS] <account_name>
+[ WITH REGION = <region> ]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<account_name>` The name of the account, must start and end with an alphabetic character and cannot contain spaces or special characters except for hyphens (-). `<region>` The region in which the account is configured. Choose the same region as the Amazon S3 bucket that contains data you ingest. See [Available AWS Regions](/Reference/available-regions.html) If not specified, `us-east-1` US East (N. Virginia) is the default.
+
+## [](#example)Example
+
+The following command will create an account in the US East (N. Virginia) region.
+
+```
+CREATE ACCOUNT dev WITH REGION = “us-east-1”
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_aggregating_index.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_aggregating_index.md
new file mode 100644
index 0000000..26f7c9d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_aggregating_index.md
@@ -0,0 +1,186 @@
+# [](#create-aggregating-index)CREATE AGGREGATING INDEX
+
+## [](#overview)Overview
+
+Aggregating indexes in Firebolt help speed up query performance by precomputing and storing frequent aggregations, reducing the need for expensive runtime calculations. Use aggregating indexes for queries that involve [aggregate functions](/sql_reference/functions-reference/aggregation/) including `GROUP BY`, `SUM`, and `AVG`. Instead of scanning a full table, queries use aggregating indexes to retrieve pre-aggregated results, leading to faster response times. These indexes update automatically when the underlying table changes, ensuring that queries using them run efficiently without manual intervention, and are most beneficial when querying large tables with precomputable aggregations.
+
+## [](#syntax)Syntax
+
+```
+CREATE AGGREGATING INDEX <index_name> ON <table_name> (
+  <key_expression>[,...<key_expressionN>],
+  <aggregation>[,...<aggregationN>]
+);
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<index_name>` A unique name for the aggregating index. `<table_name>` The name of the table on which the index is created. `<key_expressions>` One or more expressions that will be used for filtering or as aggregation dimensions in queries. `<aggregations>` [Aggregation functions](/sql_reference/functions-reference/aggregation/) including `SUM`, `COUNT`, `AVG`, applied to table column expressions.
+
+Firebolt automatically maintains the aggregating index when the table is updated, ensuring it stays optimized for queries.
+
+## [](#examples)Examples
+
+The following examples show use cases for the following:
+
+- [Create a simple aggregating index](#create-a-simple-aggregating-index)
+- [Create a complex aggregating index](#create-a-complex-aggregating-index)
+- [Compute AVG with multiple filters](#compute-avg-with-multiple-filters)
+- [Filter by a calculated column](#filter-by-a-calculated-column)
+
+### [](#create-a-simple-aggregating-index)Create a simple aggregating index
+
+You can optimize a frequently run query that counts distinct values, sums the `amount` for products, and groups by `product_name`, as shown in the following code example:
+
+```
+SELECT
+  product_name,
+  COUNT(DISTINCT source),
+  SUM(amount)
+FROM
+  my_table
+WHERE
+  origin_country = 'USA'
+GROUP BY
+  product_name;
+```
+
+To optimize the previous query, create an aggregating index on `my_table` to precompute aggregations for `COUNT(DISTINCT source)` and `SUM(AMOUNT)`, grouped by `origin_country` and `product_name` as follows:
+
+```
+CREATE AGGREGATING INDEX my_table_agg_idx1 ON my_table (
+  origin_country,
+  product_name,
+  COUNT(DISTINCT source),
+  SUM(amount)
+);
+```
+
+The aggregating index in the previous code example precomputes and stores aggregated values for `COUNT(DISTINCT source)` and `SUM(amount)`, reducing computation at query time.
+
+In order to use the aggregating index, **a query must group by all indexed columns**. In the previous code example, you must include `origin_country` as a filter expression because aggregating indexes store grouped data hierarchically based on the first column listed. If you don’t include the first grouping column, the entire table is scanned, reducing performance benefits. Filtering on `product_name` is optional because all `product_name` values are already grouped under each `origin_country`. If filtering on `origin_country` is not always required, you can define an index on another column. For example, the following code example creates an aggregating index on `product_name`:
+
+```
+CREATE AGGREGATING INDEX my_table_agg_idx2 ON my_table (
+  product_name,
+  COUNT(DISTINCT source),
+  SUM(amount)
+);
+```
+
+Then, you can use the aggregating index in a query as follows:
+
+```
+SELECT product_name, COUNT(DISTINCT source), SUM(amount)
+FROM my_table
+GROUP BY product_name;
+```
+
+### [](#create-a-complex-aggregating-index)Create a complex aggregating index
+
+The following code example groups products by name and replaces names longer than 100 characters with ‘Other.’ Then, it counts distinct brands approximately and filters records where `origin_country` is ‘USA’ and `amount` exceeds `100`:
+
+```
+SELECT
+  CASE WHEN LENGTH(product_name) < 100 THEN product_name ELSE 'Other' END AS product_name,
+  APPROX_COUNT_DISTINCT(brand)
+FROM
+  my_table
+WHERE
+  origin_country = 'USA' AND amount > 100
+GROUP BY
+  product_name;
+```
+
+To optimize the previous query, create an aggregating index on `my_table` that precomputes `APPROX_COUNT_DISTINCT(brand)`, grouped by `origin_country`, `amount`, and `product_name` as follows:
+
+```
+CREATE AGGREGATING INDEX my_table_agg_idx2 ON my_table (
+  origin_country,
+  amount,
+  product_name,
+  APPROX_COUNT_DISTINCT(brand)
+);
+```
+
+In order to use the aggregating index, **a query must group by all indexed columns in the index**. In the previous code example, you must include `origin_country` and `amount` as filter expressions because aggregating indexes store grouped data hierarchically based on the first columns listed. If you don’t include the first grouping column, the entire table is scanned, reducing performance benefits. The second grouping column `amount` is necessary to efficiently filter down results. Without both groupings, Firebolt cannot sufficiently narrow the dataset efficiently.
+
+## [](#compute-avg-with-multiple-filters)Compute `AVG` with multiple filters
+
+The following aggregating index precomputes `AVG(price)` and `COUNT(product_id)`, grouped by `category`, `region` and `price`, allowing efficient filtering and retrieval of aggregates:
+
+```
+CREATE AGGREGATING INDEX avg_sales_per_category ON sales_data (
+  category,
+  region,
+  price,
+  AVG(price),
+  COUNT(product_id)
+);
+```
+
+The following query retrieves the precomputed `AVG(price)` and `COUNT(product_id)` while filtering on `region` and `price`:
+
+```
+SELECT category, AVG(price), COUNT(product_id)
+FROM sales_data
+WHERE region = 'North America' AND price > 100
+GROUP BY category, region, price;
+```
+
+The previous code example utilizes the `avg_sales_per_category` aggregating index without requiring an explicit reference to it because Firebolt’s query optimizer automatically applies an aggregating index when a query’s `GROUP BY` structure matches the index’s grouping structure. If the query optimizer finds a matching structure, it retrieves the precomputed values instead of scanning and computing the raw data.
+
+### [](#filter-by-a-calculated-column)Filter by a calculated column
+
+The following aggregating index precomputes `SUM(order_value)` and `COUNT(order_id)`, grouped by `customer_segment` and `ROUND(order_value, 2)`, allowing efficient filtering on the rounded `order_value`:
+
+```
+CREATE AGGREGATING INDEX revenue_index ON orders (
+  customer_segment,
+  ROUND(order_value, 2),
+  SUM(order_value),
+  COUNT(order_id)
+);
+```
+
+The following code example retrieves precomputed aggregates while filtering on the rounded `order_value`:
+
+```
+SELECT customer_segment, SUM(order_value), COUNT(order_id)
+FROM orders
+WHERE ROUND(order_value, 2) > 100
+GROUP BY customer_segment, ROUND(order_value, 2);
+```
+
+The previous code example fully utilizes the aggregating index because it groups by all indexed columns: `customer_segment`, `ROUND(order_value, 2)`, allowing the use of the precomputed index instead of computing rounding at query time.
+
+## [](#how-to-check-if-a-query-is-applying-an-aggregating-index)How to check if a query is applying an aggregating index
+
+You can use [EXPLAIN](/sql_reference/commands/queries/explain.html) to check if Firebolt is applying an aggregating index as shown in the following code example:
+
+```
+EXPLAIN
+SELECT product_name, COUNT(DISTINCT source), SUM(amount)
+FROM my_table
+WHERE origin_country = 'USA'
+GROUP BY product_name;
+```
+
+If the aggregating index is being used, the query execution plan will show output as follows: `Aggregating Index: my_table_agg_idx1`
+
+If the aggregating index is not used, ensure that the query filters on the first grouping column.
+
+## [](#best-practices)Best practices
+
+- **Always include query filter expressions** – Queries should filter on indexed columns to ensure the aggregating indexes are applied efficiently.
+- **Prioritize low-cardinality columns** – Place columns with fewer unique values first to improve pruning efficiency.
+- **Match aggregations to queries** – Ensure the index includes all measures used in `GROUP BY` queries for optimal performance.
+
+By following these guidelines, you can use aggregating indexes to significantly speed up queries.
+
+## [](#limitations)Limitations
+
+- Because the index structure is precomputed, aggregating indexes are not suitable for queries that frequently change `GROUP BY` structures.
+- Aggregating indexes do not optimize queries that filter on columns that are not part of the grouping structure unless additional indexing strategies are applied.
+- Inserts and updates may be slower because of index maintenance, so avoid over-indexing to save storage space. Additionally, large updates can temporarily impact query performance.
+- Aggregating indexes are not beneficial for transactional workloads that require frequent row-level updates.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_database.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_database.md
new file mode 100644
index 0000000..05a41a7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_database.md
@@ -0,0 +1,27 @@
+# [](#create-database)CREATE DATABASE
+
+Creates a new database.
+
+Each account supports up to 100 databases. If you need more, contact Firebolt’s support team at [support@firebolt.io](mailto:support@firebolt.io).
+
+## [](#syntax)Syntax
+
+```
+CREATE DATABASE [IF NOT EXISTS] <database_name>
+[ WITH 
+[ DESCRIPTION = <description> ]
+]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<database_name>` The name of the database. `DESCRIPTION = 'description'` (Optional) The database’s description, which can contain up to 64 characters.
+
+## [](#example)Example
+
+The following code example creates a database named `my_db` with an optional description, `Testing database`:
+
+```
+CREATE DATABASE IF NOT EXISTS my_db
+WITH DESCRIPTION = 'Testing database'
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_external_table.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_external_table.md
new file mode 100644
index 0000000..039959c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_external_table.md
@@ -0,0 +1,327 @@
+# [](#create-external-table)CREATE EXTERNAL TABLE
+
+Creates an external table. External tables serve as connectors to your external data sources. External tables contain no data within Firebolt other than metadata virtual columns that are automatically populated with metadata. For more information, see [Working with external tables](/Guides/loading-data/working-with-external-tables.html). Data that you ingest must be in an Amazon S3 bucket in the same AWS Region as the Firebolt database.
+
+- [Using location objects](#using-location-objects)
+- [Common `LOCATION` errors](#common-location-errors)
+- [PARTITION](#partition)
+- [Credentials](#credentials)
+  
+  - [Syntax–authenticating using an access key and secret](#syntaxauthenticating-using-an-access-key-and-secret)
+- [OBJECT\_PATTERN](#object_pattern)
+- [TYPE](#type)
+  
+  - [CSV Types](#csv-types)
+  - [JSON Types](#json-types)
+  - [Other Types](#other-types)
+- [COMPRESSION](#compression)
+
+## [](#syntax)Syntax
+
+```
+-- Using location object (recommended)
+CREATE EXTERNAL TABLE [IF NOT EXISTS] <table>
+(
+    <column_name> <column_type>[ PARTITION('<regex>')]
+    [, <column_name2> <column_type2> [PARTITION('<regex>')]]
+    [,...<column_name2> <column_type2> [PARTITION('<regex>')]]
+)
+LOCATION = <location_name>
+OBJECT_PATTERN = '<object_pattern>'
+TYPE = ( <type> )
+[ <type_option> ]
+[ COMPRESSION = <compression_type> ]
+|
+-- Using static credentials
+CREATE EXTERNAL TABLE [IF NOT EXISTS] <table>
+(
+    <column_name> <column_type>[ PARTITION('<regex>')]
+    [, <column_name2> <column_type2> [PARTITION('<regex>')]]
+    [,...<column_name2> <column_type2> [PARTITION('<regex>')]]
+)
+[ CREDENTIALS = { AWS_ACCESS_KEY_ID = '<aws_access_key_id>' AWS_SECRET_ACCESS_KEY = '<aws_secret_access_key>' [ AWS_SESSION_TOKEN = '<aws_session_token>' ] | AWS_ROLE_ARN = '<aws_role_arn>' [ AWS_ROLE_EXTERNAL_ID = '<aws_role_external_id>' ] } ]
+URL = 's3://<bucket_name>[/<folder>][/...]/'
+OBJECT_PATTERN = '<object_pattern>'
+TYPE = ( <type> )
+[ <type_option> ]
+[ COMPRESSION = <compression_type> ]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table>` An identifier that specifies the name of the external table. This name should be unique within the database. For identifier usage and syntax, see [Object identifiers](/Reference/object-identifiers.html). `<column_name>` An identifier that specifies the name of the column. This name should be unique within the table.  
+**Note:** If column names are using mixed case, wrap your column name definitions in double quotes (`"`); otherwise they will be translated to lower case and will not match the mixed case Parquet schema. `<column_type>` Specifies the data type for the column. `PARTITION` An optional keyword. When specified, allows you to use a regular expression `<regex>` to extract a value from the file prefix to be stored as the column value. For more information, see [PARTITION](#partition). `LOCATION` The name of a location object that contains the Amazon S3 URL and credentials. This is the recommended approach for specifying the source. See ([CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html)) for details. The location must exist and you must have appropriate permissions to use it. `CREDENTIALS` Specifies the AWS credentials with permission to access the Amazon S3 location specified using `URL`. For more information, see [CREDENTIALS](#credentials). `URL` The path to an Amazon S3 URL where the source files are located. For example, `s3://my_bucket/my_folder/`. `OBJECT_PATTERN` Specifies the file naming pattern that Firebolt ingests when using this table. For more information, see [OBJECT\_PATTERN](#object_pattern). `TYPE` Specifies the file type Firebolt expects to ingest given the `OBJECT_PATTERN`. If a file referenced using `OBJECT_PATTERN` does not conform to the specified `TYPE`, an error occurs. For more information, see [TYPE](#type). `<type_option>` Allows configuration for ingesting different CSV file formats. Type option can be set at this top level, or as an option in the `TYPE` parameter. `COMPRESSION` See [COMPRESSION](#compression).
+
+### [](#using-location-objects)Using location objects
+
+Firebolt recommends using location objects as a secure, centralized way to manage Amazon S3 credentials and URLs.
+
+Use location objects for:
+
+- Centralized credential management.
+- Eliminating the exposure of credentials in queries.
+- Enabling role-based access control.
+- Simplified maintenance and updates.
+
+**Example**
+
+The following code example creates `my_external_table` in that loads data from Parquet files matching the \*.parquet pattern in `my_data_location`:
+
+```
+CREATE EXTERNAL TABLE my_external_table
+(
+    c_id INTEGER,
+    c_name TEXT
+)
+LOCATION = my_data_location
+OBJECT_PATTERN = '*.parquet'
+TYPE = (PARQUET);
+```
+
+For detailed information, see [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html).
+
+### [](#common-location-errors)Common `LOCATION` errors
+
+- Providing the location name as a string literal instead of an identifier results in an error, as shown in the following code example:
+  
+  ```
+  CREATE EXTERNAL TABLE et_1 (x INT NOT NULL, y TEXT NOT NULL) 
+  LOCATION = 'location_1'  -- Error: Parameter LOCATION must be of type IDENTIFIER
+  OBJECT_PATTERN = 'simple.csv' 
+  TYPE = CSV;
+  ```
+- If the specified location doesn’t exist or you lack permission to use it, an error occurs, as shown in the following code example:
+  
+  ```
+  CREATE EXTERNAL TABLE et_2 (x INT NOT NULL, y TEXT NOT NULL) 
+  LOCATION = nonexistent_location  -- Error: location 'nonexistent_location' does not exist or not authorized
+  OBJECT_PATTERN = 'simple.csv' 
+  TYPE = CSV;
+  ```
+
+### [](#partition)PARTITION
+
+In some applications, such as Hive partitioning, files use a folder naming convention to identify which partition their data belongs to. The `PARTITION` keyword allows you to specify a regular expression, `<regex>`, to extract a portion of the file path and store it in the specified column when Firebolt uses the external table to ingest partitioned data.
+
+Using `PARTITION` in this way is one method of extracting partition data from file paths. Another method is to use the table metadata column, `$source_file_name`, during the `INSERT` operation.
+
+#### [](#guidelines-for-creating-the-regex)Guidelines for creating the regex
+
+- The regular expression is matched against the object prefix, not including the `s3://<bucket_name>/` portion of the prefix.
+- You can specify as many `PARTITION` columns as you need, each extracting a different portion of the object prefix.
+- For each `PARTITION` column, you must specify a [re2 regular expression](https://github.com/google/re2/wiki/Syntax) that contains a capturing group, which determines the column value.
+- When `<column_type>` is `DATE`, Firebolt requires up to three capturing groups that must be in the order of year, month, and day.
+- When `<column_type>` is `TIMESTAMP`, Firebolt requires up to six capturing groups that must be in the order of year, month, day, hour, minute, second.
+- Firebolt tries to convert the captured string to the specified `<column_type>`. If the type conversion fails, the ingest will error out.
+
+In most cases, the easiest way to build a regular expression is as follows:
+
+1. Count the number of folders in the path, not including the bucket name.
+2. Concatenate the string `[^/]+/` according to the number of folders.
+3. Prefix the regex with an additional `[^/]+` for the file name.
+4. Wrap the `[^/]+` in the right folder with a capturing group parenthesis, such as `([^/]+).`
+
+For more information, see [Match groups](https://regexone.com/lesson/capturing_groups) on the RegexOne website. To test your regular expressions, online tools such as [regex101](https://regex101.com) are available.
+
+#### [](#exampleextract-hive-compatible-partitions)Example–extract Hive-compatible partitions
+
+The example below demonstrates a `CREATE EXTERNAL TABLE` statement that creates the table `my_ext_table`. This table is used to ingest all files with a `*.parquet` file extension in any sub-folder of the Amazon S3 bucket `s3://my_bucket`.
+
+Consider an example where folders and files in the bucket have the following consistent pattern, which is common for Hive partitions:
+
+```
+s3://my_bucket/c_type=xyz/year=2018/month=01/part-00001.parquet
+s3://my_bucket/c_type=xyz/year=2018/month=01/part-00002.parquet
+s3://my_bucket/c_type=abc/year=2018/month=01/part-00001.parquet
+s3://my_bucket/c_type=abc/year=2018/month=01/part-00002.parquet
+[...]
+```
+
+In the example `CREATE EXTERNAL TABLE` statement below, the `PARTITION` keyword in the column definition for `c_type` specifies a regular expression. This expression extracts the portion of the Amazon S3 path name that correspond to the `xyz` or `abc` within `c_type=xyz` or `c_type=abc`.
+
+```
+CREATE EXTERNAL TABLE my_ext_table (
+  c_id    INTEGER,
+  c_name  TEXT,
+  c_type  TEXT PARTITION('[^/]+/c_type=([^/]+)/[^/]+/[^/]+')
+)
+CREDENTIALS = (AWS_ACCESS_KEY_ID = 'AKIAIOSFODNN7EXAMPLE' AWS_SECRET_ACCESS_KEY = 'wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY')
+URL = 's3://my_bucket/'
+OBJECT_PATTERN= '*.parquet'
+TYPE = (PARQUET)
+```
+
+When Firebolt ingests the data from a Parquet file stored in that path, the `c_type` column for each row contains the extracted portion of the path. For the files listed above, the extraction results in the following values. `c_id` and `c_name` are values stored within the respective Parquet files, while `c_type` are values extracted from the file path.
+
+c\_id c\_name c\_type 1ef4302294 Njimba xyz 8b98470659 Yuang xyz 98734hkk89 Cole xyz 38cjodjlo8 Blanda xyz 448dfgkl12 Harris abc j987rr3233 Espinoza abc
+
+### [](#credentials)Credentials
+
+The credentials for accessing your data on AWS Amazon S3 using access key &amp; secret.
+
+#### [](#syntaxauthenticating-using-an-access-key-and-secret)Syntax–authenticating using an access key and secret
+
+```
+CREDENTIALS = (AWS_ACCESS_KEY_ID = '<aws_access_key_id>' AWS_SECRET_ACCESS_KEY = '<aws_secret_access_key>' [ AWS_SESSION_TOKEN = '<aws_session_token>' ] )
+```
+
+## [](#parameters-1)Parameters
+
+Parameters Description Data type `AWS_ACCESS_KEY_ID` The AWS access key ID. `TEXT` `AWS_SECRET_ACCESS_KEY` The AWS secret access key. `TEXT` `AWS_SESSION_TOKEN` The AWS session token. `TEXT` `AWS_ROLE_ARN` The AWS role ARN (Amazon Resource Name). `TEXT` `AWS_ROLE_EXTERNAL_ID` The AWS role external id. `TEXT`
+
+In case you don’t have the access key and secret to access your Amazon S3 bucket, read more [here](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys) on how to obtain them.
+
+### [](#object_pattern)OBJECT\_PATTERN
+
+An external table enables reading some (or all) files from an Amazon S3 bucket that you have read access to. The Amazon S3 bucket that you reference must be in the same AWS Region as the Firebolt database.
+
+The`OBJECT_PATTERN` parameter identifies which files represent the data for the external table.`OBJECT_PATTERN` is a glob that selects files within the `URL` or `LOCATION`.
+
+#### [](#syntax-1)Syntax
+
+```
+OBJECT_PATTERN = '<object_pattern>'
+```
+
+## [](#parameters-2)Parameters
+
+Parameters Description Data type `OBJECT_PATTERN` Specify the data pattern to be found in your data source. For example, \*.parquet indicates that all parquet files should be found. `TEXT`
+
+The following wildcards are supported:
+
+- `'*'` matches any sequence of characters
+- `'?'` matches any single character
+- `[SET]` matches any single character in the specified set
+- `[!SET]` matches any character, not in the specified set.
+
+#### [](#example)Example
+
+In the following layout of objects in a bucket, the data is partitioned according to client type, year, and month, with multiple parquet files in each partition. The examples demonstrate how choosing both URL and OBJECT\_PATTERN impacts the objects that are retrieved from Amazon S3.
+
+```
+s3://bucket/c_type=xyz/year=2018/month=01/part-00001.parquet
+s3://bucket/c_type=xyz/year=2018/month=01/part-00002.parquet
+...
+s3://bucket/c_type=xyz/year=2018/month=12/part-00001.parquet
+s3://bucket/c_type=xyz/year=2018/month=12/part-00002.parquet
+...
+s3://bucket/c_type=xyz/year=2019/month=01/part-00001.parquet
+s3://bucket/c_type=xyz/year=2019/month=01/part-00002.parquet
+...
+s3://bucket/c_type=xyz/year=2020/month=01/part-00001.parquet
+s3://bucket/c_type=xyz/year=2020/month=01/part-00002.parquet
+...
+s3://bucket/c_type=abc/year=2018/month=01/part-00001.parquet
+s3://bucket/c_type=abc/year=2018/month=01/part-00002.parquet
+...
+```
+
+Following are some common use cases for URL and object pattern combinations:
+
+Use cases Syntax Get all files for file type xyz *URL = ‘s3://bucket/c\_type=xyz/’*  
+*OBJECT\_PATTERN = ‘\*’*
+
+*URL = ‘s3://bucket/’*  
+*OBJECT\_PATTERN = ‘c\_type=xyz/\*’* Get one specific file: `c_type=xyz/year=2018/month=01/part-00001.parquet` \*URL = ‘s3://bucket/c\_type=xyz/year=2018/month=01/’  
+OBJECT\_PATTERN = ‘part-00001.parquet’ Get all parquet files for type xyz *URL = ‘s3://bucket/c\_type=xyz/’*  
+*OBJECT\_PATTERN = ‘\*.parquet’*
+
+### [](#type)TYPE
+
+Specifies the type of the files in Amazon S3. The following types and type options are supported.
+
+#### [](#csv-types)CSV Types
+
+```
+TYPE = (CSV [ <type_option> ])
+```
+
+or
+
+```
+TYPE = (CSV)
+[ <type_option> ]
+```
+
+The following type options allow configuration for ingesting different CSV file formats.
+
+- `[ALLOW_DOUBLE_QUOTES = {TRUE|FALSE}]`  
+  `[ALLOW_SINGLE_QUOTES = {TRUE|FALSE}]`  
+  With `ALLOW_DOUBLE_QUOTES = TRUE` or `ALLOW_SINGLE_QUOTES = TRUE` you define that unescaped double or single quotes in CSV input file will not cause an error to be generated on ingest. By default `ALLOW_DOUBLE_QUOTES` and `ALLOW_SINGLE_QUOTES` are set to `TRUE`.
+- `[ALLOW_COLUMN_MISMATCH = {TRUE|FALSE}]`  
+  With `ALLOW_COLUMN_MISMATCH = TRUE` the number of delimited columns in a CSV input file can be fewer than the number of columns in the corresponding table. By default, `ALLOW_COLUMN_MISMATCH` is set to `FALSE`, and an error is generated if the number of columns is fewer than the number of columns defined in the external table. If set to `TRUE`, and an input file record contains fewer columns than defined in the external table, the non-matching columns in the table are loaded with `NULL` values.
+- `[ALLOW_UNKNOWN_FIELDS = {TRUE|FALSE}]`  
+  With `ALLOW_UNKNOWN_FIELDS = TRUE` the number of delimited columns in a CSV input file can be more than the number of columns in the corresponding table. By default, `ALLOW_UNKNOWN_FIELDS` is set to `FALSE`, and an error is generated if the number of columns is more than the number of columns defined in the external table. If set to `TRUE`, and an input file record contains more columns than defined in the external table, the non-matching columns in the table are ignored.
+- `[ESCAPE_CHARACTER = {‘<character>’|NONE}`  
+  With `ESCAPE_CHARACTER = '<character>'` you can define which character is used to escape, to change interpretations from the original. By default, the `ESCAPE_CHARACTER` value is set to `\`. If, for example, you want to use `"` as a value and not as delimiter for string, you can escape like `\"`, with the default escape character.
+- `[FIELD_DELIMITER = '<field_delimeter>']`  
+  With `FIELD_DELIMITER = '<field_delimeter>'`, you can define a custom field delimiter to separate fields for ingest. By default, the `FIELD_DELIMITER` is set as `,`.
+- `[NEW_LINE_CHARACTER = '<new_line_character>']`  
+  With `NEW_LINE_CHARACTER = '<new_line_character>'`, you can define a custom new line delimiter to separate entries for ingest. By default, the `NEW_LINE_CHARACTER` is set as the end of line character `\n`, but also supports other end of line conventions, such as `\r\n`, `\n\r`, and `\r`, as well as multi-character delimiters, such as `#*~`.
+- `[NULL_STRING = '<null_string>']`  
+  With `NULL_STRING = '<null_string>'` you can define which set of characters is interpreted as `NULL`. By default, the `NULL_STRING` value is set to `\\N`.
+- `[SKIP_BLANK_LINES {TRUE|FALSE}]`  
+  With `SKIP_BLANK_LINES = TRUE` any blank lines encountered in the CSV input file will be skipped. By default, `SKIP_BLANK_LINES` is set to `FALSE`, and an error is generated if blank lines are enountered on ingest.
+- `[SKIP_HEADER_ROWS = {TRUE|FALSE}]`  
+  With `SKIP_HEADER_ROWS = TRUE`, Firebolt assumes that the first row in each file read from Amazon S3 is a header row and skips it when ingesting data. When set to `FALSE`, which is the default if not specified, Firebolt ingests the first row as data.
+
+#### [](#json-types)JSON Types
+
+- `TYPE = (JSON [PARSE_AS_TEXT = {TRUE|FALSE}])`  
+  With `TYPE = (JSON PARSE_AS_TEXT = TRUE)`, Firebolt ingests each JSON object literal in its entirety into a single column of type `TEXT`. With `TYPE = (JSON PARSE_AS_TEXT = FALSE)`, Firebolt expects each key in a JSON object literal to map to a column in the table definition. During ingestion, Firebolt inserts the key’s value into the corresponding column.
+
+#### [](#other-types)Other Types
+
+- `TYPE = (ORC)`
+- `TYPE = (PARQUET)`
+- `TYPE = (AVRO)`
+- `TYPE = (TSV)`
+
+All type options for CSV above, except for `FIELD_DELIMITER`, are also supported for the TSV file type.
+
+#### [](#example-1)Example
+
+Creating an external table that reads parquet files from Amazon S3 is being done with the following statement:
+
+```
+CREATE EXTERNAL TABLE my_external_table
+(
+    c_id INTEGER,
+    c_name TEXT
+)
+CREDENTIALS = (AWS_ACCESS_KEY_ID = '****' AWS_SECRET_ACCESS_KEY = '****')
+URL = 's3://bucket/'
+OBJECT_PATTERN= '*.parquet'
+TYPE = (PARQUET)
+```
+
+### [](#compression)COMPRESSION
+
+Specifies the compression type of the files matching the specified `OBJECT_PATTERN` in Amazon S3.
+
+#### [](#syntax-2)Syntax
+
+```
+[COMPRESSION = <compression_type>]
+```
+
+#### [](#parameters-3)Parameters
+
+Parameters Description `<compression_type>` Specifies the compression type of files. `GZIP` is supported.
+
+#### [](#example-2)Example
+
+The example below creates an external table to ingest CSV files from Amazon S3 that are compressed using gzip. The credentials for an IAM user with access to the bucket are provided.
+
+```
+CREATE EXTERNAL TABLE my_external_table
+(
+    c_id INTEGER,
+    c_name TEXT
+)
+CREDENTIALS = (AWS_ACCESS_KEY_ID = 'AKIAIOSFODNN7EXAMPLE' AWS_SECRET_ACCESS_KEY = 'wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY')
+URL = 's3://mybucket/'
+OBJECT_PATTERN= '*.csv.gz'
+TYPE = (CSV)
+COMPRESSION = GZIP
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_fact_dimension_table.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_fact_dimension_table.md
new file mode 100644
index 0000000..021f4d6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_fact_dimension_table.md
@@ -0,0 +1,129 @@
+# [](#create-table)CREATE TABLE
+
+Creates a new table in the current database.
+
+- [CREATE TABLE](#create-table)
+  
+  - [Column constraints and the default expression](#column-constraints-and-the-default-expression)
+    
+    - [Example: Creating a table with `NULL` and `NOT NULL` values](#example-creating-a-table-with-null-and-not-null-values)
+    - [PRIMARY INDEX](#primary-index)
+    - [PARTITION BY](#partition-by)
+    - [Table type](#table-type)
+  - [Related functions](#related-functions)
+
+## [](#syntax)Syntax
+
+```
+CREATE [FACT|DIMENSION] TABLE [IF NOT EXISTS] <table_name>
+(
+    <column_name> <column_type> [constraints]
+    [, <column_name> <column_type> [constraints]
+    [, ...n]]
+)
+[PRIMARY INDEX <column_name>[, <column_name>[, ...k]]]
+[PARTITION BY <column_name>[, <column_name>[, ...m]]]
+[WITH ( <storage_parameter> = <storage_parameter_value>[, <storage_parameter> = <storage_parameter_value>[, ...p]] ) ]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table_name>` An identifier that specifies the name of the table. This name should be unique within the database. `<column_name>` An identifier that specifies the name of the column. This name should be unique within the table. `<column_type>` Specifies the data type for the column. `<storage_parameter>` The name of a [storage parameter](#storage-parameters) for controlling behaviors related to storage and indexes. `<storage_parameter_value>` The value assigned to a `<storage_parameter>`.
+
+All identifiers are case-insensitive unless enclosed in double-quotes. For more information, see [Object identifiers](/Reference/object-identifiers.html).
+
+## [](#column-constraints-and-the-default-expression)Column constraints and the default expression
+
+Firebolt supports the following column constraints:
+
+```
+<column_name> <column_type> [NULL | NOT NULL] [DEFAULT <expression>]
+```
+
+Constraint Description Default value `DEFAULT <expression>` Determines the default value used when no value is provided, instead of inserting a `NULL` value.   `NULL` | `NOT NULL` Determines if the column may or may not contain `NULL` values. `NOT NULL`
+
+Nullable columns cannot be used in Firebolt primary or aggregating indexes. Additionally, only literals and the following functions are supported in default expressions: [CURRENT\_DATE](/sql_reference/functions-reference/date-and-time/current-date.html), [LOCALTIMESTAMP](/sql_reference/functions-reference/date-and-time/localtimestamp.html), [CURRENT\_TIMESTAMP](/sql_reference/functions-reference/date-and-time/current-timestamptz.html), and NOW, the alias for CURRENT\_TIMESTAMP.
+
+### [](#example-creating-a-table-with-null-and-not-null-values)Example: Creating a table with `NULL` and `NOT NULL` values
+
+The following example illustrates different use cases for column definitions and `INSERT` statements:
+
+- An **Explicit** `NULL` insert – a direct insertion of a `NULL` value into a particular column.
+- An **Implicit** `NULL` insert – an `INSERT` statement with missing values for a particular column.
+
+The following example creates a fact table `t1` with five columns, specifying if each column can contain `NULL` values, their default values, and a primary index on `col2`:
+
+```
+CREATE FACT TABLE t1
+(
+    col1 INTEGER  NULL,
+    col2 INTEGER  NOT NULL,
+    col3 INTEGER  NULL DEFAULT 1,
+    col4 INTEGER  NOT NULL DEFAULT 1,
+    col5 TEXT
+)
+PRIMARY INDEX col2;
+```
+
+After creating a table, you can manipulate the values using different `INSERT` statements, as shown in the following examples:
+
+INSERT statement Results and explanation `INSERT INTO t1 VALUES (1,1,1,1,1)` This code example inserts `1` into each column. `INSERT INTO t1 VALUES (NULL,1,1,1,1)` This code example explicitly inserts a `NULL` value into `col1`. Because `col1` can contain `NULL` values, this operation is successful. `INSERT INTO t1 (col2,col3,col4,col5) VALUES (1,1,1,1)` This code example shows both explicit and implicit `INSERT` statements. Because `col1` has no value specified, and lacks a default expression, it is implicitly set to `NULL`. `INSERT INTO t1 VALUES (1,NULL,1,1,1)`
+
+`INSERT INTO t1 (col1,col3,col4,col5) VALUES (1,1,1,1)` This code example shows how a **null mismatch** error is generated. Because `col2` is defined as `NOT NULL` with no default expression, both `INSERT` statements implicitly try to insert `NULL` values into `col2`, and generate “null mismatch” events. `INSERT INTO t1 VALUES (1,1,NULL,1,1)` This code example explicitly inserts a `NULL` value into `col3`. Because `col3` is defined as `NULL DEFAULT 1`, the operation is successful. `INSERT INTO t1 (col1,col2,col4,col5) VALUES (1,1,1,1)` By not specifying a value for `col3`, this code example implicitly inserts the default value `1` into `col3`, which is defined as `NULL DEFAULT 1`. `INSERT INTO t1 VALUES (1,1,1,NULL,1)` This code example shows how another **null mismatch** error is generated. Because `col4` is defined as `NOT NULL DEFAULT 1`, the explicit insertion of a `NULL` value violates the `NOT NULL` constraint, and results in a null mismatch event. `INSERT INTO t1 (col1,col2,col3,col5) VALUES (1,1,1,1)` This code example shows how omitting a value in an implicit insert invokes the default value `1` for `col4`. `INSERT INTO t1 VALUES (1,1,1,1,NULL)`
+
+`INSERT INTO t1 (col1,col2,col3,col4) VALUES (1,1,1,1)` This code example shows how explicit and implicit inserts cause a **null mismatch** error. Because `col5` was neither defined with a default expression nor allowed to contain `NULL` values, Firebolt treats `col5` as `NOT NULL DEFAULT NULL`. Both `INSERT` statements attempt to insert a `NULL` value into a `NOT NULL TEXT` column, invoking in a null mismatch event.
+
+### [](#primary-index)PRIMARY INDEX
+
+The `PRIMARY INDEX` is an optional sparse index that sorts and organizes data based on the indexed field as it is ingested, without affecting data scan performance. For more information, see [Primary index](/Overview/indexes/primary-index.html).
+
+#### [](#syntax-1)Syntax
+
+```
+PRIMARY INDEX <column_name>[, <column_name>[, ...n]]
+```
+
+The following table describes the primary index parameters:
+
+Parameter. Description Mandatory? `<column_name>` Specifies the name of the column in the Firebolt table which composes the index. At least one column is required. Y
+
+### [](#partition-by)PARTITION BY
+
+The `PARTITION BY` clause defines one or more columns that determine how the table is divided into physical parts. These columns serve as the partition key and cannot allow `NULL` values. When multiple columns are used as the partition key, the combination of all of these columns define the partition boundaries.
+
+```
+PARTITION BY <column_name>[, <column_name>[, ...n]]
+```
+
+The following subset of SQL functions can be used in `PARTITION BY` expressions:
+
+- [TO\_YYYYMM](/sql_reference/functions-reference/date-and-time/to-yyyymm.html)
+- [TO\_YYYYMMDD](/sql_reference/functions-reference/date-and-time/to-yyyymmdd.html)
+- [EXTRACT](/sql_reference/functions-reference/date-and-time/extract.html)`(year|month|day|hour from <column_name>)`
+- [DATE\_TRUNC](/sql_reference/functions-reference/date-and-time/date-trunc.html)
+
+For more information, see [Working with partitions](/Overview/indexes/using-indexes.html#partitions-in-tables).
+
+### [](#table-type)Table type
+
+Firebolt supports two types of [tables](/Overview/indexes/using-indexes.html#tables):
+
+- `FACT` table - the data is distributed across all nodes of the engine.
+- `DIMENSION` table - the entire table is replicated in every node of the engine.
+
+The [CREATE TABLE](/sql_reference/commands/data-definition/create-fact-dimension-table.html) command defaults to a `FACT` table. `DIMENSION` tables are ideal for relatively small tables, up to tens of gigabytes, that are used in joins with `FACT` tables.
+
+## [](#storage-parameters)Storage Parameters
+
+Storage parameters are specified in the optional `WITH (...)` clause as comma separated `<storage_parameter> = <storage_parameter_value>` assignments.
+
+Storage Parameter Description `<index_granularity>` The maximum number of rows in each granule. `<storage_parameter_value>` must be a power of 2 between 128 and 8192. The default value is 8192. For more information, see [Index granularity](/Overview/indexes/primary-index.html#advanced-option-index-granularity).
+
+All identifiers are case-insensitive unless enclosed in double-quotes. For more information, see [Object identifiers](/Reference/object-identifiers.html).
+
+## [](#related-functions)Related functions
+
+Firebolt also supports the following related functions:
+
+- [CREATE TABLE AS SELECT (CTAS)](/sql_reference/commands/data-definition/create-fact-dimension-table-as-select.html) – - Creates a table and loads data into it based on a `SELECT` query.
+- [CREATE TABLE CLONE](/sql_reference/commands/data-definition/) – Creates a table that is a copy of an existing table in the database.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_fact_dimension_table_as_select.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_fact_dimension_table_as_select.md
new file mode 100644
index 0000000..2e8b094
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_fact_dimension_table_as_select.md
@@ -0,0 +1,32 @@
+# [](#create-fact-or-dimension-tableas-select)CREATE FACT or DIMENSION TABLE…AS SELECT
+
+Creates a table and loads data into it based on the [SELECT](/sql_reference/commands/queries/select.html) query. The table column names and types are automatically inferred based on the output columns of the [SELECT](/sql_reference/commands/queries/select.html). When specifying explicit column names, those override the column names inferred from `SELECT`.
+
+## [](#syntax)Syntax
+
+Fact table:
+
+```
+CREATE FACT TABLE [IF NOT EXISTS] <table_name>
+[(<column_name>[, ...n] )]
+PRIMARY INDEX <column_name>[, <column_name>[, ...n]]
+[PARTITION BY <column_name>[, <column_name>[, ...n]]]
+AS <select_query>
+```
+
+Dimension table:
+
+```
+CREATE DIMENSION TABLE [IF NOT EXISTS] <table_name>
+[(<column_name>[, ...n] )]
+[PRIMARY INDEX <column_name>[, <column_name>[, ...n]]]
+AS <select_query>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table_name>` An identifier that specifies the name of the external table. This name should be unique within the database. `<column_name>` An identifier that specifies the name of the column. This name should be unique within the table. `<select_query`&gt; Any valid select query.
+
+## [](#remarks)Remarks
+
+Unlike a traditional `CREATE` statement, the primary index and partition definition must come *before* the `AS` clause.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_location.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_location.md
new file mode 100644
index 0000000..fe7c1b9
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_location.md
@@ -0,0 +1,225 @@
+# [](#create-location)CREATE LOCATION
+
+Creates a new location object in your Firebolt account, which is a secure, reusable object that stores the connection details and credentials for external data sources, like Amazon S3. Instead of entering these details each time you run a query or create a table, you can use a location object.
+
+The location object stores the following:
+
+- The source type specification
+- Authentication credentials
+- The data source URL
+- Optional descriptive metadata
+
+This makes it easier to manage data access, keeps your credentials safe, and saves you from having to repeat the same information across multiple queries.
+
+You can use `LOCATION` to centralize credential storage with managed access with Role-Based Access Control ([RBAC](/Overview/Security/Role-Based%20Access%20Control/)) for `CREATE`, `MODIFY`, and `USAGE` permissions for different users, use a single location definition for multiple tables and queries, and control access to sensitive data. `LOCATION` is version control-friendly because no sensitive credentials are stored in source code.
+
+After you create a `LOCATION`, you can use the `information_schema.locations` view to see [details about all the locations](/sql_reference/information-schema/locations.html) in your account including source type, URL, description, owner and creation time.
+
+**Topics:**
+
+- [Syntax](#syntax)
+- [Parameters](#parameters)
+- [Specify credentials to access Amazon S3](#specify-credentials-to-access-amazon-s3)
+- [Permissions](#permissions)
+- [Examples](#examples)
+- [Notes](#notes)
+- [Error handling](#error-handling)
+- [Best practices](#best-practices)
+- [Limitations](#limitations)
+
+## [](#syntax)Syntax
+
+```
+CREATE [OR REPLACE] LOCATION [IF NOT EXISTS] <location_name> WITH
+  SOURCE = <source_type>
+  CREDENTIALS = { AWS_ACCESS_KEY_ID = '<aws_access_key_id>' AWS_SECRET_ACCESS_KEY = '<aws_secret_access_key>' [ AWS_SESSION_TOKEN = '<aws_session_token>' ] | AWS_ROLE_ARN = '<aws_role_arn>' [ AWS_ROLE_EXTERNAL_ID = '<aws_role_external_id>' ] }
+  URL = '<url>'
+  [ DESCRIPTION = '<description>' ]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<location_name>` A unique identifier for the location within your account. `<source_type>` The external data source type. Currently, Firebolt only supports `AMAZON_S3`. `<credentials_options>` Authentication parameters specific to the source type. `<url>` The data source URL. For Amazon S3, use the following format: `s3://{bucket_name}/{path}` `<description>` Optional metadata describing the location’s purpose.
+
+## [](#specify-credentials-to-access-amazon-s3)Specify credentials to access Amazon S3
+
+You can use either access key-based or role-based credentials to authenticate to AWS. The parameters for both methods follow:
+
+Parameter Description Authentication type `AWS_ACCESS_KEY_ID` Your AWS access key ID key-based `AWS_SECRET_ACCESS_KEY` Your AWS secret access key key-based `AWS_SESSION_TOKEN` Optional temporary session token for temporary credentials key-based `AWS_ROLE_ARN` The ARN of the IAM role to assume role-based `AWS_ROLE_EXTERNAL_ID` Optional external ID for role assumption role-based
+
+## [](#permissions)Permissions
+
+`LOCATION` objects are managed using [RBAC](/Overview/Security/Role-Based%20Access%20Control/) with the following permission levels:
+
+Permission Description CREATE LOCATION Create a new location object. MODIFY LOCATION Modify existing location objects. MODIFY ANY LOCATION Modify any location object in the account. LIST LOCATION View location object details. LIST ANY LOCATION View any location object in the account. USAGE LOCATION Use a location object. USAGE ANY LOCATION Use any location object in the account.
+
+## [](#examples)Examples
+
+- [Authenticate using an access key](#authenticate-using-an-access-key)
+- [Authenticate using a role](#authenticate-using-a-role)
+- [Create a location with a description](#create-a-location-with-a-description)
+- [Create a location with an AWS session token](#create-a-location-with-an-aws-session-token)
+- [Create a location only if it doesn’t exist](#create-a-location-only-if-it-doesnt-exist)
+- [Replace a location if it already exists](#replace-a-location-if-it-already-exists)
+- [Use a location to load data into an external table](#use-a-location-to-load-data-into-an-external-table)
+- [Use a location to load data using COPY statements](#use-a-location-to-load-data-using-copy-statements)
+- [Use a location to load data with a TVF](#use-a-location-to-load-data-with-a-tvf)
+- [Alter a location](#alter-a-location)
+- [Delete a location](#delete-a-location)
+
+### [](#authenticate-using-an-access-key)Authenticate using an access key
+
+The following code example uses keys to authenticate to AWS:
+
+```
+CREATE LOCATION my_location WITH
+  SOURCE = 'AMAZON_S3'
+  CREDENTIALS = { AWS_ACCESS_KEY_ID = '1231' AWS_SECRET_ACCESS_KEY = '567' }
+  URL = 's3://my-bucket/path/to/data'
+```
+
+### [](#authenticate-using-a-role)Authenticate using a role
+
+The following code example use a role to authenticate to AWS:
+
+```
+CREATE LOCATION my_location WITH
+  SOURCE = 'AMAZON_S3'
+  CREDENTIALS = { AWS_ROLE_ARN = 'arn:aws:iam::123456789012:role/S3Access' }
+  URL = 's3://my-bucket/path/to/data'
+```
+
+### [](#create-a-location-with-a-description)Create a location with a description
+
+The following code example creates a location object named `my_location`, for an Amazon S3 data source with the specified URL and description:
+
+```
+CREATE LOCATION my_location WITH
+  SOURCE = 'AMAZON_S3'
+  CREDENTIALS = { AWS_ACCESS_KEY_ID = '1231' AWS_SECRET_ACCESS_KEY = '567' }
+  URL = 's3://my-bucket/path/to/data'
+  DESCRIPTION = 'Main data storage location'
+```
+
+### [](#create-a-location-with-an-aws-session-token)Create a location with an AWS session token
+
+The following code example creates a location object named `my_location`, for an Amazon S3 data source with the specified URL and AWS session token:
+
+```
+CREATE LOCATION my_location WITH
+  SOURCE = 'AMAZON_S3'
+  CREDENTIALS = { AWS_ACCESS_KEY_ID = '1231' AWS_SECRET_ACCESS_KEY = '567' AWS_SESSION_TOKEN = 'session-token' }
+  URL = 's3://my-bucket/path/to/data'
+```
+
+### [](#create-a-location-only-if-it-doesnt-exist)Create a location only if it doesn’t exist
+
+The following code example uses an access key to authenticate to AWS using a location only if it doesn’t already exist:
+
+```
+CREATE LOCATION IF NOT EXISTS my_location WITH
+  SOURCE = 'AMAZON_S3'
+  CREDENTIALS = { AWS_ACCESS_KEY_ID = '1231' AWS_SECRET_ACCESS_KEY = '567' }
+  URL = 's3://my-bucket/path/to/data'
+```
+
+### [](#replace-a-location-if-it-already-exists)Replace a location if it already exists
+
+The following code example uses an access key to authenticate to AWS replacing a previous location if it already exists:
+
+```
+CREATE OR REPLACE LOCATION my_location WITH
+  SOURCE = 'AMAZON_S3'
+  CREDENTIALS = { AWS_ACCESS_KEY_ID = '1231' AWS_SECRET_ACCESS_KEY = '567' }
+  URL = 's3://my-bucket/path/to/data'
+```
+
+### [](#use-a-location-to-load-data-into-an-external-table)Use a location to load data into an external table
+
+The following code example creates an external table `my_ext_table` that uses a previously created location `my_location` to load Parquet data files matching the \*.parquet pattern from Amazon S3:
+
+```
+CREATE EXTERNAL TABLE my_ext_table (
+  c_id    INT,
+  c_name  TEXT
+)
+LOCATION = my_location
+OBJECT_PATTERN = '*.parquet'
+TYPE = PARQUET
+```
+
+For more information about using locations in external tables, see [CREATE EXTERNAL TABLE](/sql_reference/commands/data-definition/create-external-table.html).
+
+### [](#use-a-location-to-load-data-using-copy-statements)Use a location to load data using COPY statements
+
+The following code example uses `COPY FROM` to load Parquet data files matching the \*.parquet pattern from `my_location` into `my_table`:
+
+```
+COPY INTO my_table
+FROM my_location
+WITH
+  OBJECT_PATTERN = '*.parquet'
+  TYPE = PARQUET
+```
+
+For more information, see [COPY TO](/sql_reference/commands/data-management/copy-to.html) and [COPY FROM](/sql_reference/commands/data-management/copy-from.html).
+
+### [](#use-a-location-to-load-data-with-a-tvf)Use a `LOCATION` to load data with a TVF
+
+You can use `LOCATION` to load data using table-valued functions (TVFs) such as [READ\_CSV](/sql_reference/functions-reference/table-valued/read_csv.html), [READ\_PARQUET](/sql_reference/functions-reference/table-valued/read_parquet.html), and [LIST\_OBJECTS](/sql_reference/functions-reference/table-valued/list-objects.html).
+
+The following code example uses `READ_CSV` to query data from a CSV file stored in `my_location`, using the first row as headers for column names:
+
+```
+SELECT * FROM READ_CSV(
+  location => my_location,
+  header => TRUE
+)
+```
+
+### [](#alter-a-location)Alter a location
+
+Firebolt does not yet support altering a location that has been created. This feature will be available in a future release.
+
+### [](#delete-a-location)Delete a location
+
+You can use [DROP LOCATION](/sql_reference/commands/data-definition/drop-location.html) to remove a location from your Firebolt account.
+
+The following code example deletes a `LOCATION` from your Firbolt account:
+
+```
+DROP LOCATION [IF EXISTS] <location_name> [WITH FORCE]
+```
+
+{: .note} Deleting a location will affect all objects that depend on the `LOCATION` that you are dropping.
+
+## [](#notes)Notes
+
+- The `IF NOT EXISTS` and `OR REPLACE` clauses cannot be used together
+- All identifiers are case-insensitive unless enclosed in double-quotes
+- The `SOURCE` parameter is required. Currently, the only supported source is ‘AMAZON\_S3’
+- The `URL` parameter is required and must be a valid S3 URL
+- For more information about object identifiers, see [Object identifiers](/Reference/object-identifiers.html)
+
+## [](#error-handling)Error Handling
+
+The system uses secure error handling for location objects:
+
+- Generic error messages ensure security by not exposing sensitive information.
+- Detailed error information is only available to users with the necessary permissions.
+- Users without the required permissions are provided with instructions to contact an administrator.
+
+## [](#best-practices)Best Practices
+
+1. Use location objects instead of embedding credentials directly in queries or table definitions.
+2. Regularly rotate credentials stored in location objects.
+3. Follow the principle of least privilege when assigning permissions.
+4. Use clear and descriptive names and descriptions for location objects.
+5. Keep a record of dependencies before removing any location objects.
+
+## [](#limitations)Limitations
+
+- The `DROP CASCADE` functionality is not supported.
+- The source type cannot be modified for existing location objects.
+- Location objects cannot be used alongside inline credentials in the same statement.
+- Historical versions of credentials are not maintained.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_table_clone.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_table_clone.md
new file mode 100644
index 0000000..1433441
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_table_clone.md
@@ -0,0 +1,102 @@
+# [](#create-table-clone)CREATE TABLE CLONE
+
+Creates a table that is a copy of an existing table in the database.
+
+The `CREATE TABLE CLONE` operation is extremely fast and highly cost-efficient because it copies the table’s structure and references, without duplicating the actual data.
+
+The column names and data types of the cloned table are automatically inferred from the source table.
+
+Once the clone is created, the cloned table and the source table become independent. Any future changes to the data or schema of either table will not affect the other.
+
+## [](#source-table-indexes)Source Table Indexes
+
+The primary index and partition expressions are copied from the source table.
+
+By default, all aggregating indexes are implicitly cloned from the source table. This behavior can be modified using the `INCLUDING INDEXES` or `EXCLUDING INDEXES` options as follows:
+
+- **INCLUDING INDEXES:** Clones all aggregating indexes from the source table, or clone a partial list of indexes if one is provided.
+- **EXCLUDING INDEXES:** Clones the table without any of the aggregating indexes from the source table.
+
+The newly created aggregating indexes will either retain the original aggregating index’s name or include an enumerated suffix if that name already exists.
+
+## [](#syntax)Syntax
+
+```
+CREATE TABLE [IF NOT EXISTS] <target_table_name> CLONE <source_table_name> [{INCLUDING INDEXES [<index_name>,...] | EXCLUDING INDEXES}] 
+```
+
+**— OR —**
+
+```
+CREATE [OR REPLACE] TABLE <target_table_name> CLONE <source_table_name> [{INCLUDING INDEXES [<index_name>,...] | EXCLUDING INDEXES}] 
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `IF NOT EXISTS` By default, specifies that an existing table `<target_table_name>` will not be replaced with the new table schema definition. This clause prevents an error message that would otherwise occur, making it useful for scripted and programmatic implementations. `OR REPLACE` Specifies that an existing `<target_table_name>` will be replaced with the new table definition. `<target_table_name>` An identifier that specifies the name of the table. This name should be unique within the target database. `<source_table_name>` An identifier that specifies the name of the source table to clone. The source table must exist within the source database. `<index_name>` An aggregating index to clone from the source table, the index must exist and be associated with the source table.
+
+### [](#examples)Examples
+
+The following code creates a table with two aggregating indexes, which will serve as the base table for the upcoming example use cases:
+
+```
+CREATE TABLE sales_data (
+    sale_id INTEGER,
+    sale_date DATE,
+    product_quantity INTEGER,
+    customer_quantity INTEGER
+);
+CREATE AGGREGATING INDEX product_idx ON sales_data (COUNT(product_quantity));
+CREATE AGGREGATING INDEX customer_idx ON sales_data (COUNT(customer_quantity));
+```
+
+**Example**
+
+The following code example creates an exact copy of the existing `sales_data` table, including its structure and data:
+
+```
+CREATE TABLE cloned_sales_data CLONE sales_data;
+```
+
+**Example**
+
+The following code example creates an exact copy of the `sales_data` table excluding any of its aggregating indexes:
+
+```
+CREATE TABLE cloned_sales_data CLONE sales_data EXCLUDING INDEXES;
+```
+
+**Example**
+
+The following code example creates a copy of the `sales_data` table and includes only the specified only index `product_idx`:
+
+```
+CREATE TABLE cloned_sales_data CLONE sales_data INCLUDING INDEXES product_idx;
+```
+
+**Example**
+
+The following code example creates a copy of the `sales_data` table and includes all associated indexes:
+
+```
+CREATE TABLE cloned_sales_data CLONE sales_data INCLUDING INDEXES;
+```
+
+# [](#clone-a-table-across-databases)CLONE A TABLE ACROSS DATABASES
+
+You can clone a table from one database to another using a three-part identifier for either the source or target table.
+
+When cloning across databases, you can keep the original table name as long as it does not already exist in the target database.
+
+**Example**
+
+The following code example creates an exact copy of the existing `sales_data` table from the `staging` database in the `prod` database:
+
+```
+CREATE TABLE prod.public.sales_data CLONE staging.public.sales_data;
+```
+
+### [](#limitations)Limitations
+
+- You can only use `CREATE TABLE CLONE` to clone Firebolt-managed tables. External tables and views are not supported.
+- `CREATE TABLE CLONE` is only supported for cloning tables created on Firebolt version 4.10 or higher.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_view.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_view.md
new file mode 100644
index 0000000..db2c0fb
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_create_view.md
@@ -0,0 +1,38 @@
+# [](#create-view)CREATE VIEW
+
+Creates a view, which is useful to filter, focus, and simplify a data set for querying. Views provide a level of abstraction that can make subqueries easier to write, especially for commonly referenced subsets of data.
+
+View results are not stored for future usage. Each time a query references a view, the view runs its `SELECT` query. For this reason, views do not provide a performance advantage. Consider using a materialized common table expression (CTE) as an alternative. For more information, see [Materialized common table expressions](/sql_reference/commands/queries/select.html#materialized-common-table-expressions).
+
+The optional `IF NOT EXISTS` and `OR REPLACE` clauses are mutually exclusive. They specify behavior if a view with the same name already exists. If neither clause is specified, an error occurs if a view with the same `<view_name>` already exists.
+
+## [](#syntax)Syntax
+
+```
+CREATE VIEW [IF NOT EXISTS] <view_name> [(<column_list>)]
+AS SELECT <select_statement>
+```
+
+**—OR—**
+
+```
+CREATE [OR REPLACE] VIEW <view_name> [(<column_list>)]
+AS SELECT <select_statement>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `IF NOT EXISTS` Specifies that an existing view with `<view_name>` will not be replaced with this view definition. This is the default behavior, but this clause suppresses the error message that would otherwise occur, which is useful for scripted and programmatic implementations. `OR REPLACE` Specifies that an existing view with `<view_name>` will be replaced with this view definition. `<view_name>` An identifier that specifies the name of the view. This name must be unique within the database. `<column_list>` An optional list of column names to be used for columns of the view. If not specified, the column names are deduced from the query. `<select_statement>` The select statement for creating the view.
+
+## [](#example)Example
+
+```
+CREATE VIEW fob_shipments
+AS SELECT   l_shipmode,
+            l_shipdate,
+            l_linestatus,
+            l_orderkey,
+FROM    lineitem
+WHERE   l_shipdate > 1990-01-01
+AND     l_shipmode = 'FOB';
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_account.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_account.md
new file mode 100644
index 0000000..71717ac
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_account.md
@@ -0,0 +1,28 @@
+# [](#drop-account)DROP ACCOUNT
+
+Deletes an account.
+
+For more information, see [Managing accounts](/Guides/managing-your-organization/managing-accounts.html).
+
+## [](#syntax)Syntax
+
+```
+DROP ACCOUNT [ IF EXISTS ] <account_name> [ RESTRICT | CASCADE ];
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<account_name>` The name of the account to delete. RESTRICT or CASCADE An optional parameter to specify deletion mode.  
+RESTRICT mode prevents dropping the account if there is any sub-object contained in the account.  
+By default, if the account contains no objects, it will just be dropped.  
+CASCADE mode automatically drops the account and all the sub-objects it contains (databases, engines, users, roles, etc.).
+
+All engines in your accounts must be in a stopped state before running the `DROP ACCOUNT … CASCADE` statement.
+
+## [](#example)Example
+
+The following command will delete the “dev” account.
+
+```
+DROP ACCOUNT dev
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_database.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_database.md
new file mode 100644
index 0000000..3f9d155
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_database.md
@@ -0,0 +1,15 @@
+# [](#drop-database)DROP DATABASE
+
+Deletes a database.
+
+## [](#syntax)Syntax
+
+Deletes the database and all of its tables and attached engines.
+
+`DROP DATABASE [IF EXISTS] <database_name>`
+
+## [](#parameters)Parameters
+
+## [](#parameters-1)Parameters
+
+Parameter Description `<database_name>` The name of the database to be deleted
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_index.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_index.md
new file mode 100644
index 0000000..c3d3306
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_index.md
@@ -0,0 +1,13 @@
+# [](#drop-index)DROP INDEX
+
+Deletes an index.
+
+## [](#syntax)Syntax
+
+```
+DROP AGGREGATING INDEX [IF EXISTS] <index_name>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<index_name>` The name of the index to be deleted.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_location.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_location.md
new file mode 100644
index 0000000..5403fda
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_location.md
@@ -0,0 +1,97 @@
+# [](#drop-location)DROP LOCATION
+
+Removes a location object from your Firebolt account. Be cautious when dropping a location that is referenced by external tables, as it may impact dependent objects.
+
+**Topics:**
+
+- [Syntax](#syntax)
+- [Parameters](#parameters)
+- [Examples](#examples)
+- [Error handling](#error-handling)
+- [Best practices](#best-practices)
+- [Notes](#notes)
+
+## [](#syntax)Syntax
+
+```
+DROP LOCATION [IF EXISTS] <location_name> [WITH FORCE]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<location_name>` The identifier of the location to remove. `IF EXISTS` A parameter that suppresses the error if the location doesn’t exist. `WITH FORCE` Forces the removal of the location even if it has dependent external tables. **Warning**: This option invalidates all dependent external tables.
+
+## [](#examples)Examples
+
+**Drop a location**
+
+The following code example removes a `LOCATION` object from your Firebolt account:
+
+```
+DROP LOCATION my_location
+```
+
+**Drop IF EXISTS**
+
+The following code example removes a `LOCATION` object from your Firebolt account if it exists:
+
+```
+DROP LOCATION IF EXISTS my_location
+```
+
+**Drop with FORCE Option**
+
+If you attempt to drop a location that is referenced by an external table, the drop operation fails by default. You can do either of the following:
+
+1. **Safe Approach**: Drop all dependent external tables before dropping the location.
+2. **Force Approach**: Use the `WITH FORCE` option to drop the location immediately regardless of dependencies.
+
+If you choose `WITH FORCE`, the following apply:
+
+- The location is deleted regardless of existing dependencies.
+- All external tables that reference the removed location become invalid.
+- Queries on any invalid tables will result in an error.
+- You must manually clean up the invalid external tables after using `WITH FORCE`.
+
+The following code example deletes a `LOCATION` object from your Firebolt account without considering its dependencies:
+
+```
+DROP LOCATION my_location WITH FORCE
+```
+
+## [](#error-handling)Error handling
+
+The following table lists the types of errors that may occur during location removal:
+
+Error Type Cause Resolution **Location Not Found or Unauthorized** The specified location does not exist or you lack permission to access it. Use `IF EXISTS` to handle non-existent locations without error. **Dependent Objects Exist** The location is referenced by one or more external tables. Drop the dependent tables first or use `WITH FORCE` to bypass dependency checks. **Invalid External Table** Attempting to query an external table after its location was removed using `WITH FORCE`. Drop the invalid external table.
+
+## [](#best-practices)Best Practices
+
+When dropping a location, consider the following:
+
+1. **Before Dropping**
+   
+   - Use `IF EXISTS` to handle non-existent locations gracefully.
+   - Ensure no active queries are using the location.
+   - Check for dependent external tables.
+
+To identify external tables that depend on this location, execute the following query.
+
+```
+SELECT * FROM information_schema.tables WHERE location_name = 'my_location_name'
+```
+
+1. **Using WITH FORCE**
+   
+   - Use only when necessary.
+   - Clean up invalid external tables immediately.
+   - Document the reason for using this option.
+2. **After Dropping**
+   
+   - Verify all dependent objects are handled.
+   - Update any scripts or documentation referencing the location.
+
+## [](#notes)Notes
+
+- All identifiers are case-insensitive unless enclosed in double-quotes
+- For more information about object identifiers, see [Object identifiers](/Reference/object-identifiers.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_table.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_table.md
new file mode 100644
index 0000000..8dd0722
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_table.md
@@ -0,0 +1,13 @@
+# [](#drop-table)DROP TABLE
+
+Deletes a table.
+
+## [](#syntax)Syntax
+
+```
+DROP TABLE [IF EXISTS] <table_name> [CASCADE]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table_name>` The name of the table to be deleted. For external tables, the definition is removed from Firebolt but not from the source. `CASCADE` When specified, causes all dependent database objects such as views and aggregating indexes to be dropped also.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_view.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_view.md
new file mode 100644
index 0000000..46bc0a1
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_drop_view.md
@@ -0,0 +1,13 @@
+# [](#drop-view)DROP VIEW
+
+Deletes a view.
+
+## [](#syntax)Syntax
+
+```
+DROP VIEW [IF EXISTS] <view_name> [CASCADE]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<view_name>` The name of the view to be deleted. `CASCADE` When specified, causes all dependent database objects such as views and aggregating indexes to be dropped also.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_use_database.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_use_database.md
new file mode 100644
index 0000000..7e26fd6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_definition_use_database.md
@@ -0,0 +1,46 @@
+# [](#use-database)USE DATABASE
+
+The `USE DATABASE` statement in allows users to specify the database context for their queries within a session. This statement is crucial for operations within Firebolt where users interact with multiple databases, ensuring queries are executed against the intended database without the need to fully qualify object names in their SQL statements.
+
+## [](#syntax)Syntax
+
+```
+USE [DATABASE] <database_name>;
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `DATABASE` This is an optional keyword. `<database_name>` The target database for session context. Essential for directing queries to the correct database without specifying the database name in each query. The database name must adhere to identifier rules supported by Firebolt, allowing for quoted or unquoted identifiers. An error is thrown if the database does not exist or the user lacks the necessary permissions.
+
+While `USE DATABASE` is designed to set the context at a session level, it plays a crucial role in the resolution of unqualified object names. All subsequent queries in the session resolve unqualified single-part names (like table or function names) based on the set database context, unless explicitly overridden by using fully qualified names or other USE statements is encountered.
+
+## [](#example)Example
+
+The following demonstrates setting the current database context to ‘sales’ database.
+
+```
+USE sales; -- Sets the current database context to 'sales'
+SELECT * FROM public.revenue; -- Executes against 'sales.public.revenue'
+```
+
+The following example demonstrat switching between databases within a single session
+
+```
+USE database sales; -- Context set to 'sales'
+USE marketing; -- Context switched to 'marketing'
+SELECT * FROM campaigns; -- Accesses 'campaigns' tables in  'marketing' database using one part name.
+SELECT * FROM sales.public.revenue; -- Accesses 'sales.public.revenue' using fully qualified name, despite current context being 'marketing'
+```
+
+## [](#faqs)FAQs
+
+1. What is the purpose of the `USE DATABASE` command? The `USE DATABASE` command sets the current database context for the session, ensuring that all subsequent queries operate within the specified database unless another `USE` command changes the context.
+2. How does the `USE DATABASE` command affect the resolution of unqualified object names in queries? Once the `USE DATABASE` command is executed, all unqualified single-part names or two-part names, such as table or function names, in subsequent queries are resolved based on the set database context, simplifying queries by not requiring full names.
+3. Can I access objects in different databases without changing the session’s database context after using `USE DATABASE`? Yes, you can access objects in different databases by using fully qualified names (including the database name and schema name) in your queries, which allows you to bypass the current session’s database context.
+4. What happens if I use another `USE DATABASE` command within the same session? Executing another `USE DATABASE` command changes the session’s database context to the new database specified, affecting the resolution of unqualified object names in all subsequent queries.
+5. How do I ensure my query targets the correct database and object if I have used the `USE DATABASE` command? To target a specific database and object, you can use fully qualified names in your queries regardless of the current session’s database context, or ensure the `USE DATABASE` command has set the desired database before executing unqualified queries.
+6. Can I use `USE DATABASE` within a transaction? Yes, but it will only affect the database context for the duration of the transaction.
+
+## [](#common-pitfalls)Common Pitfalls:
+
+• Forgetting to switch back to the original database context after temporary changes can lead to unintended query executions against the wrong database.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management.md
new file mode 100644
index 0000000..84a8e72
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management.md
@@ -0,0 +1,11 @@
+## [](#data-management)Data management
+
+* * *
+
+- [COPY FROM](/sql_reference/commands/data-management/copy-from.html)
+- [COPY TO](/sql_reference/commands/data-management/copy-to.html)
+- [DELETE](/sql_reference/commands/data-management/delete.html)
+- [INSERT](/sql_reference/commands/data-management/insert.html)
+- [TRUNCATE TABLE](/sql_reference/commands/data-management/truncate-table.html)
+- [UPDATE](/sql_reference/commands/data-management/update.html)
+- [VACUUM](/sql_reference/commands/data-management/vacuum.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_copy_from.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_copy_from.md
new file mode 100644
index 0000000..849827c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_copy_from.md
@@ -0,0 +1,530 @@
+# [](#copy-from)COPY FROM
+
+Loads data from an AWS S3 bucket into Firebolt. Use `COPY FROM` to load data from external sources, such as from Amazon S3, into Firebolt tables. `COPY FROM` supports various data loading workflows, including schema discovery, metadata filtering, and parallel processing, offering flexibility for different use cases. This page provides an overview of the `COPY FROM` syntax, parameters, and best practices.
+
+## [](#table-of-contents)Table of contents
+
+- [Syntax](#syntax)
+- [Parameters](#parameters)
+- [Best practice](#best-practice)
+- [Examples](#examples)
+  
+  **Data loading and filtering examples:**
+  
+  - [COPY FROM with LOCATION](#copy-from-with-location)
+  - [Filter by metadata during loading](#filter-by-metadata-during-loading)
+  - [Use LOCATION to copy data](#use-location-to-copy-data)
+  - [Load multiple directories with LOCATION](#load-multiple-directories-with-location)
+  - [Load multiple files and directories in parallel](#load-multiple-files-and-directories-in-parallel)
+  
+  **Schema management examples:**
+  
+  - [Automatic schema discovery](#automatic-schema-discovery)
+  - [Use PATTERN to insert data into an existing table](#use-pattern-to-insert-data-into-an-existing-table)
+  - [Load metadata into a table](#load-metadata-into-a-table)
+  - [Column mapping](#column-mapping)
+  - [Allow column name mismatch](#allow-column-name-mismatch)
+  
+  **Troubleshooting:**
+  
+  - [Error handling](#error-handling)
+
+## [](#syntax)Syntax
+
+```
+-- Using location object (recommended)
+COPY
+[INTO] <table_name> [ <column_mapping> ] 
+FROM location_name
+[ LIMIT <count> ]
+[ OFFSET <start> ]
+[ WITH <options> ]
+[ WHERE <condition> ]
+|
+-- Using static credentials
+COPY
+[INTO] <table_name> [ <column_mapping> ] 
+FROM '<url>'
+[ LIMIT <count> ]
+[ OFFSET <start> ]
+[ WITH <options> ]
+[ WHERE <condition> ]
+
+<column_mapping>:
+    ( <column_name> [DEFAULT <default_value>] [ { $c<source_column_index> | <source_column_name> } ] [, ...] )
+
+<options>:
+    [ CREDENTIALS = ( <credentials> ) ] 
+    [ PATTERN = <glob_pattern> ]
+    [ TYPE = { **AUTO** | CSV | TSV | PARQUET } ]
+    [ AUTO_CREATE = { **TRUE** | FALSE } ]
+    [ ALLOW_COLUMN_MISMATCH = { **TRUE** | FALSE } ]
+    [ ERROR_FILE = <directoryLocation> ]
+    [ ERROR_FILE_CREDENTIALS = <credentials> ]
+    [ MAX_ERRORS_PER_FILE = { integer | '<percentage>' } ]
+    [ CASE_SENSITIVE_COLUMN_MAPPING = { TRUE | **FALSE** } ]
+    [ <csv_options> ]
+
+<credentials>:
+    { AWS_ACCESS_KEY_ID = '<aws_access_key_id>' AWS_SECRET_ACCESS_KEY = '<aws_secret_access_key>' [ AWS_SESSION_TOKEN = '<aws_session_token>' ]
+    | AWS_ROLE_ARN = '<aws_role_arn>' [ AWS_ROLE_EXTERNAL_ID = '<aws_role_external_id>' ] }
+
+<csv_options>:
+    [ HEADER = { **FALSE** | TRUE  } ]
+    [ DELIMITER = 'character' ]
+    [ NEWLINE = 'string' ]
+    [ QUOTE = { **DOUBLE_QUOTE** | 'character' |  SINGLE_QUOTE } ]
+    [ ESCAPE = 'character' ]
+    [ NULL_STRING = 'string' ]
+    [ EMPTY_FIELD_AS_NULL = { **TRUE** | FALSE } ]
+    [ SKIP_BLANK_LINES = { **FALSE** | TRUE } ]
+    [ DATE_FORMAT = <date_format> ]
+    [ TIMESTAMP_FORMAT = <timestamp_format> ]
+
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table_name>` The name of the target table. `<column_mapping>` This feature is only available if the target table already exists. You can use `column_mapping` to specify the mapping between the source and target schema. Select a column in the source file to map to the target file using either the name of the column or its index. `<column_name>` The name of a target column in a table. If `<source_column_index/name>` is not specified, source columns will be automatically mapped to target columns based on name. `<default_value>` A replacement value for any `NULL` value generated by mapping the source to the target. This data type of `default_value` must be compatible with the data type of the target column. `<source_column_index>` The index position of the column in the source data to be mapped. If you are specifying multiple source files, `source_column_index` specifies the index for all source files. The index starts at `1`, and can be as large as `2^64-1`, which allows for a very large number of columns. If you prefix the index inside a command or query, precede the column index with a `$c` string. For example, prefix the index as shown in the following `COPY FROM` statement: `CREATE TABLE t(a text, b text); COPY INTO t(a $c1, b $c2) FROM 's3://my_bucket/my_folder/my_file';`. `<source_column_name>` The name of the column in the source data to be mapped. If you are specifying multiple source files, `source_column_name` specifies the column name for all source files. `location_name` The name of a location object that contains the S3 URL and credentials. This is the recommended approach for specifying the source. See [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html) for details. `<url>` The path to an S3 URL where the source files are located. For example, `s3://my_bucket/my_folder/`. If the URL ends with a forward slash (`/`), it’s interpreted as a folder; otherwise, it’s treated as a single file. `<directoryLocation>` The Amazon S3 path to a directory. `CREDENTIALS` The Amazon S3 credentials for accessing the specified `<url>`. For more information, see [CREDENTIALS](/sql_reference/commands/data-definition/create-external-table.html#credentials). `PATTERN` A string that represents a [glob pattern](https://en.wikipedia.org/wiki/Glob_%28programming%29) used to match filenames or other strings. `TYPE` The file type that Firebolt should expect when loading files identified by `PATTERN`. If `TYPE` is unspecified, Firebolt automatically detects the file type using the file’s suffix. If a file matched by `PATTERN` does not match the specified `TYPE`, Firebolt will generate an error. The default value is `AUTO`. `AUTO_CREATE` Specify whether Firebolt should automatically create a table if it doesn’t already exist. If `AUTO_CREATE` is set to `FALSE`, Firebolt will generate an error if the target table is missing. If the target table already exists, `AUTO_CREATE` is ignored. The default setting is `TRUE`, allowing automatic table creation. `ALLOW_COLUMN_MISMATCH` Set to `FALSE` to specify that all required columns must appear in the source file. If `ALLOW_COLUMN_MISMATCH` is set to `FALSE`, all required columns must be present in the source file. Required columns are those listed in `<column_mapping>` by name or index. If no column mapping is provided, the target table’s columns are required. Missing required columns will cause row-based errors for CSV or TSV files, and file-based errors for Parquet files. When `ALLOW_COLUMN_MISMATCH` is set to `TRUE`, any missing columns in the source file are filled with `NULL` values. `ERROR_FILE` The Amazon S3 `URL` where error files will be written. No error files are created by default or if the specified path doesn’t exist. If `ERROR_FILE` is specified, a subdirectory is created based on the time of load submission in the format: `YearMonthDay-HourMinuteSecond + QueryID`, such as: `20220330-173205`). For CSV files, this directory will contain a `rejected_rows.csv` file containing erroneous data rows, and an `error_reasons.csv` file, containing the reasons that the errors were generated. Because Parquet doesn’t produce row-based error files, on error, only an `error_reasons.csv` file is generated. `ERROR_FILE_CREDENTIALS` The Amazon S3 credentials required to write an error file to an Amazon S3 URL. For more information, see [CREDENTIALS](/sql_reference/commands/data-definition/create-external-table.html#credentials). `MAX_ERRORS_PER_FILE` Specify the maximum number of rows that can be rejected per file. `MAX_ERRORS_PER_FILE` can be an integer or percentage in the format “integer%”, such as `100%`. The only valid percentage options are `0%` and `100%`. If you specify an integer value, the `COPY FROM` job will load the job until it encounters the number of errors specified, and then stop the loading job. For example, if you specify `3`, then `COPY FROM` will load data until it encounters `3` errors, and then end the job with an error. If the threshold is exceeded, `COPY FROM` job will stop and return an error. By default, no errors are allowed. If `MAX_ERRORS_PER_FILE` is set to `100%`, then all errors are allowed. `CASE_SENSITIVE_COLUMN_MAPPING` Specify if column names should be case-sensitive when mapping from source to target tables. When set to `TRUE`, mapping between source and target columns is case-sensitive, and `COPY FROM` will fail or populate columns with `NULL` values when there is a case mismatch. You can use [QUOTED\_IDENTIFERS](/Reference/object-identifiers.html#quoted-identifiers) as an alternative when requiring case-sensitive behavior. When set to the default `FALSE` value, and if no target table exists, it is created with lowercase column identifiers if the source file’s column identifiers have capital, lowercase, or a combination of the two. When set to the default `FALSE` value, and the table already exists, `CASE_SENSITIVE_COLUMN_MAPPING` is ignored, and data will load from source to target.
+
+### [](#parameters-for-csv-files)Parameters for CSV files
+
+Parameter Description `HEADER` Specify if the file contains a header line containing the column names. If `HEADER` is `TRUE`, the first line will be interpreted to contain column names. The default value is `FALSE`. `DELIMITER` Specify the character used to separate fields. The default delimiter is a comma (`,`). `NEWLINE` Specify the character used to delimit rows. The default newline character is `\n`. If `NEWLINE` is `\n`, then `\r`, `\r\n`, and `\n\r` are also treated as newline characters. Custom characters are allowed only if the target table already exists. `QUOTE` Specify the character used for quoting fields. The default quote character is `DOUBLE_QUOTE`. You can specify either `SINGLE_QUOTE` or `DOUBLE_QUOTE`. You can also specify the single quote literal character (`'`) or the double quote literal character(`"`). `ESCAPE` Specify the character used to escape special characters. The default escape character is the quote (`'`) character. `NULL_STRING` Specify the string used to represent `NULL` values. The default null string is an empty string, which means that no specific null string is defined. `EMPTY_FIELD_AS_NULL` Specify whether empty fields should be interpreted as `NULL` values. The default value is `TRUE`. `SKIP_BLANK_LINES` Specify whether to ignore blank lines. If `SKIP_BLANK_LINES` is `TRUE`, then `COPY FROM` will ignore blank lines. The default value is `FALSE`. `DATE_FORMAT` Specify the date format for parsing text into date columns. This format will apply to all columns loaded as date columns. For supported formats, see [TO\_DATE](/sql_reference/functions-reference/date-and-time/to-date.html). `TIMESTAMP_FORMAT` Specify the timestamp format for parsing text into timestamp columns. The format will apply to all columns loaded as timestamp columns. For supported formats, see [TO\_TIMESTAMP](/sql_reference/functions-reference/date-and-time/to-timestamp.html).
+
+## [](#best-practice)Best practice
+
+Firebolt recommends using a `LOCATION` object to specify credentials.
+
+Location objects provide a secure, centralized way to manage Amazon S3 credentials and URLs. `LOCATION` objects let you specify credentials with the following:
+
+- Centralized credential management.
+- Reduced exposure of credentials in queries.
+- Role-based access control.
+- Simplified maintenance and updates.
+
+For detailed information, see [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html).
+
+## [](#examples)Examples
+
+### [](#copy-from-with-location)COPY FROM with LOCATION
+
+The following code example copies data from files matching the \*.parquet pattern in the specified my\_location into `my_table`:
+
+```
+COPY my_table 
+FROM my_location
+WITH PATTERN = '*.parquet';
+```
+
+### [](#filter-by-metadata-during-loading)Filter by metadata during loading
+
+When loading data into tables, you can filter data using the following options:
+
+1. `LIMIT`: Restricts the number of rows loaded, which can be useful to preview or create sample datasets.
+2. `OFFSET`: Skips a specified number of rows in the final result set before ingestion. The `OFFSET` clause in `COPY FROM` behaves the same way as the `OFFSET` clause in `SELECT` queries behaves.
+   
+   - `COPY FROM` currently does not support the `ORDER BY` clause. Thus, using `OFFSET` may result in different outcomes every time you run the command.
+   - Both `LIMIT` and `OFFSET` apply to the entire result set, not to individual files.
+3. `WHERE`: Filters data based on source file metadata, as follows:
+   
+   - $source\_file\_name - The full path of the source file in an Amazon S3 bucket, without the name of the bucket. For example, if your bucket is: `s3://my_bucket/xyz/year=2018/month=01/part-00001.parquet`, then `$source_file_name` is `xyz/year=2018/month=01/part-00001.parquet`.
+   - $source\_file\_timestamp - The timestamp in UTC, to the second when the source file was last modified in an Amazon S3 bucket.
+   - $source\_file\_size - The size in bytes of the source file.
+   - $source\_file\_etag - The [ETag](https://docs.aws.amazon.com/AmazonS3/latest/API/API_Object.html#API_Object_Contents) of the file, often used for version control.
+
+In the following code example, `COPY FROM` first reads all the files in the specified directory that were modified in the last three years. Then, it applies the offset and limit clause. As long as all source files modified in the last three years have at least 100 rows combined, the result set will have exactly 50 rows.
+
+```
+COPY tournament_results
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/rankings/TournamentID=1/'
+LIMIT 50 OFFSET 50
+WHERE $source_file_timestamp > NOW() - interval '3 YEARS';
+```
+
+The previous code example returns a table containing 50 rows of data that was modified in the last three years.
+
+**Recommended best practice**
+
+The following code example builds on the previous example by using a `LOCATION` to store credentials to authenticate:
+
+```
+COPY tournament_results
+FROM my_tournament_location
+LIMIT 50 OFFSET 50
+WHERE $source_file_timestamp > NOW() - interval '3 YEARS';
+```
+
+### [](#use-location-to-copy-data)Use LOCATION to copy data
+
+The following code example creates a table and uses a `LOCATION` object to copy Parquet files that match the specified pattern into it:
+
+```
+-- Create a table
+CREATE TABLE levels (
+    LevelID INT,
+    Name TEXT
+);
+
+-- Copy data using location object
+COPY INTO levels
+FROM my_game_data_location
+WITH 
+    PATTERN = 'levels/*.parquet'
+    TYPE = PARQUET;
+```
+
+### [](#load-multiple-directories-with-location)Load multiple directories with LOCATION
+
+The following code example copies data from Parquet files matching a pattern in `my_tournaments_location` to the `tournament_results` table:
+
+```
+COPY tournament_results FROM my_tournaments_location
+WITH 
+    PATTERN = 'tournaments/*/data/*.parquet'
+    TYPE = PARQUET;
+```
+
+### [](#load-multiple-files-and-directories-in-parallel)Load multiple files and directories in parallel
+
+You can use `COPY FROM` to read multiple sources and from multiple directories into a single table, simultaneously. The following code example reads any file ending in `.parquet` from multiple directories into `table_from_multiple_directories`.
+
+```
+COPY table_from_multiple_directories FROM 
+    's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/playstats/TournamentID=1/',
+    's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/playstats/TournamentID=10/',
+    's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/playstats/TournamentID=100/'
+WITH pattern='*.parquet';
+```
+
+The following code example reads two CSV files into `table_from_multiple_files`:
+
+```
+COPY table_from_multiple_files FROM 
+    's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv',
+    's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/tournaments.csv'
+WITH HEADER=TRUE;
+```
+
+In the previous example, there are two CSV files in the `firebolt_sample_dataset` folder: `levels.csv` and `tournaments.csv`. These files have a different schema. `COPY FROM` reads these files into a single table, and infers the schema from the first file. Any column mismatches are filled with `NULL` values.
+
+### [](#automatic-schema-discovery)Automatic schema discovery
+
+You can use the automatic schema discovery feature in `COPY FROM` to handle even very large data sources instead of manually defining it. The following apply:
+
+- **Parquet files** - Firebolt automatically reads metadata in Parquet files to create corresponding target tables.
+- **CSV files** - Firebolt infers column types based on the data content itself, which can streamline the initial data loading process significantly. Use `WITH HEADER=TRUE` if your CSV file contains column names in the first line.
+
+Automatic schema discovery operates on a “best effort” basis, and attempts to balance accuracy with practical usability, but it may not always be error-free.
+
+The following query reads `levels.csv`, a sample dataset from the fictional [Ultra Fast Gaming Inc](https://help.firebolt.io/t/ultra-fast-gaming-firebolt-sample-dataset/250). The example implicitly uses automatic schema creation with `AUTO_CREATE=TRUE`, which defaults to `TRUE`, and also triggers automatic table creation:
+
+```
+COPY automatic_schema_table 
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH HEADER=TRUE;
+```
+
+Use the following example code to display the table contents, ordered by the fourth column, followed by the fifth column:
+
+```
+SELECT * FROM automatic_schema_table ORDER BY 4,5;
+```
+
+### [](#use-pattern-to-insert-data-into-an-existing-table)Use PATTERN to insert data into an existing table
+
+You can use the `PATTERN` feature, which uses [regular expressions](https://en.wikipedia.org/wiki/Glob_%28programming%29), to select several files that match the specified pattern to populate a target table. The following example uses the `*.csv` pattern to read all files ending in `.csv` into the `pattern_target` table:
+
+```
+COPY pattern_target FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/'
+WITH TYPE=CSV HEADER=TRUE PATTERN='*.csv';
+```
+
+In the previous example, there are two CSV files in the `firebolt_sample_dataset` folder: `levels.csv` and `tournaments.csv`. These files have a different schema. `COPY FROM` reads these files into a single table, and infers the schema from the first file. Any column mismatches are filled with `NULL` values.
+
+### [](#load-metadata-into-a-table)Load metadata into a table
+
+You can load metadata information about your source file into your table so that you can track the source name, timestamp, size, and etag information for each row. You can use the following metadata columns:
+
+- $source\_file\_name - The full path of the source file in an Amazon S3 bucket, without the name of the bucket. For example, if your bucket is: `s3://my_bucket/xyz/year=2018/month=01/part-00001.parquet`, then `$source_file_name` is `xyz/year=2018/month=01/part-00001.parquet`.
+- $source\_file\_timestamp - The timestamp in UTC, to the second when the source file was last modified in an Amazon S3 bucket.
+- $source\_file\_size - The size in bytes of the source file.
+- $source\_file\_etag - The [ETag](https://docs.aws.amazon.com/AmazonS3/latest/API/API_Object.html#API_Object_Contents) of the file, often used for version control.
+
+The following code creates the `levels` table, and populates it with information from the `LevelID` column and the timestamp from the source data:
+
+```
+CREATE TABLE levels ("LevelID" TEXT NOT NULL, date_of_creation TIMESTAMP);
+COPY INTO levels("LevelID", date_of_creation $source_file_timestamp)
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv' WITH HEADER=TRUE;
+```
+
+The following code example displays the contents of `levels`:
+
+```
+SELECT * FROM levels;
+```
+
+The first three rows of the sample output follow:
+
+LevelID (TEXT) date\_of\_creation (TIMESTAMP) 1 2023-02-27 10:06:52 2 2023-02-27 10:06:52 3 2023-02-27 10:06:52
+
+### [](#column-mapping)Column mapping
+
+When loading data into a target table, you can manually map source and target schemas by [column name](#mapping-by-column-name) or [index position](#mapping-by-index-position). Column mapping ensures that data from the source file is correctly inserted into the appropriate columns in the target table.
+
+##### [](#handling-case-sensitivity)Handling case sensitivity
+
+By default, column mapping in Firebolt is **case-insensitive**, meaning column names in the `COPY FROM` statement are matched without quotes and are treated as lowercase. The [`CASE_SENSITIVE_COLUMN_MAPPING`](#parameters) parameter is ignored, and data loads into the table regardless of case differences. If you need to enforce case-sensitive column mapping, set the `CASE_SENSITIVE_COLUMN_MAPPING` parameter to `TRUE`. When enabled, column names must match exactly, including case, and `COPY FROM` will either fail or populate columns with `NULL` values if there is a case mismatch. You can also use quoted identifiers to preserve case-sensitive behavior.
+
+##### [](#mapping-by-column-name)Mapping by column name
+
+Before mapping schemas and ingesting data, you must first create a target table. You can explicitly map source columns to target table columns by matching column names.  
+The following code example creates a table and maps columns by name:
+
+```
+CREATE TABLE column_mapping_by_name (
+    LevelID INT,
+    Name TEXT
+);
+
+COPY INTO column_mapping_by_name
+(
+   LevelID,
+   Name
+)
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH HEADER = TRUE;
+```
+
+This approach allows the column order to differ between the source file and target table, as long as the column names in the `COPY FROM` statement match exactly with the source file.
+
+##### [](#mapping-by-index-position)Mapping by index position
+
+Instead of mapping by column name, you can reference column positions in the source file using `$cN` notation, where `N` represents the column index starting from one.  
+The following code example maps the first column in the source file to the `id` column in the target table and the fourth column to `name`:
+
+```
+CREATE TABLE column_mapping_positional (
+    id INT,
+    name TEXT
+);
+
+COPY INTO column_mapping_positional
+(
+   id $c1,
+   name $c4
+)
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH HEADER = TRUE
+```
+
+This method is useful when column names do not match or when working with files that lack headers.
+
+##### [](#mapping-source-columns-and-metadata)Mapping source columns and metadata
+
+You can also map both source columns and metadata columns to store additional details about the ingested data. Metadata columns provide useful information such as file creation date, size, and last modified timestamp.  
+The following code example maps source file columns by name and includes metadata:
+
+```
+CREATE TABLE levels (
+  "LevelID"          TEXT NOT NULL,
+  "NumberOfLaps"     INT,
+  "SceneDetails"     TEXT,
+  date_of_creation   TIMESTAMP,
+  file_name          TEXT,
+  file_last_modified TIMESTAMP,
+  file_size          BIGINT
+);
+
+COPY INTO levels (
+  "LevelID",
+  "NumberOfLaps",
+  "SceneDetails",
+  date_of_creation   $source_file_timestamp,
+  file_name          $source_file_name,
+  file_last_modified $source_file_timestamp,
+  file_size          $source_file_size
+)
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH HEADER=TRUE;
+```
+
+In the previous example:
+
+- Standard columns such as `LevelID`, `NumberofLaps`, and `SceneDetails` are mapped by name.
+- Metadata columns such as `date_of_creation`, `file_name`, `file_last_modified`, and `file_size` capture file-level information from the source file. This approach is particularly useful for auditing, tracking data lineage, or managing incremental loads.
+
+Note that if a required column in the mapping is missing from the source file, the load will fail unless `ALLOW_COLUMN_MISMATCH` is enabled. For cases where column names may change or be missing in the source file, see the following section [`ALLOW_COLUMN_MISMATCH`](#allow-column-name-mismatch).
+
+### [](#allow-column-name-mismatch)Allow column name mismatch
+
+If you specify a column mapping during data loading, `COPY FROM` treats the columns listed in the `<column_mapping>` as required. If no column mapping is specified, the columns in the target table are considered required. To allow the data to continue loading when some required columns are missing from the source file, you can use `ALLOW_COLUMN_MISMATCH`, which is enabled by default.
+
+For example, if you create a table with `LevelID2` and `Name` columns and attempt to load data from the `levels.csv` dataset, which lacks a `LevelID2` column, `COPY FROM` will populate the `Name` column as specified and fill the `LevelID2` column with `NULL` values. This allows flexible handling of missing data without raising errors, as shown in the following code example:
+
+```
+CREATE TABLE col_mismatch ("LevelID2" int, "Name" text);
+COPY col_mismatch
+  FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH HEADER=TRUE MAX_ERRORS_PER_FILE='0%';
+```
+
+### [](#error-handling)Error handling
+
+The following sections show you how to handle errors for both CSV and Parquet files.
+
+#### [](#row-based-errors-in-csv)Row-based errors in CSV
+
+`COPY FROM` generates a row-based error when there’s a mismatch between source and target table columns. In the following example, the `col_mismatch_csv` table includes a `LevelID2` column defined as `NOT NULL`, that does not exist in the source `levels.csv` table:
+
+```
+CREATE TABLE col_mismatch_csv ("LevelID2" int NOT NULL);
+
+COPY col_mismatch_csv FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH HEADER=TRUE MAX_ERRORS_PER_FILE='0%';
+```
+
+In the previous code example, when `COPY FROM` does not see the same column name in the target table `col_mismatch_csv`, it tries to fill the column with `NULL` values. Because `LevelID2` is defined with a constraint that it cannot have `NULL` values, the query generates the following error: `ERROR: The INSERT INTO statement failed because it tried to insert a NULL into the column LevelID2, which is NOT NULL. Please specify a value or redefine the column's logical constraints.` and stops loading into the table.
+
+##### [](#allow-all-row-based-errors-in-csv)Allow all row-based errors in CSV
+
+The previous code example uses `MAX_ERRORS_PER_FILE='0%'`, which causes the loading job to fail if there is a single error. You can change this behavior to allow errors. The following code example allows all errors, and the load job completes even if no data loads into the target table:
+
+```
+CREATE TABLE table_all_errors ("LevelID2" int NOT NULL);
+
+COPY table_all_errors FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH HEADER=TRUE MAX_ERRORS_PER_FILE='100%';
+```
+
+##### [](#column-data-type-mismatch-in-csv)Column data type mismatch in CSV
+
+If you try to load data into a column in an existing table that has a different data type than the source data, `COPY FROM` will attempt to cast the data into the specified data type. If the cast fails, `COPY FROM` generates an error. To demonstrate this error, the following example intentionally creates a table that defines the `LevelID` column incorrectly as an integer, instead of as text, and then attempts to copy data into it:
+
+```
+CREATE TABLE col_mismatch_type_csv ("Name" int);
+
+COPY col_mismatch_type_csv("Name" name)
+  FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH TYPE=CSV HEADER=TRUE;
+```
+
+The previous code example generates the following error: `Line 1, Column 8: Unable to cast text 'Thunderbolt Circuit' to integer`.
+
+In the previous code example, the query generates an error because the default value for `MAX_ERRORS_PER_FILE` is `0`. You can set `MAX_ERRORS_PER_FILE` to `100%` to allow all errors, as shown in the following section.
+
+#### [](#allow-all-errors-and-write-them-to-file)Allow all errors, and write them to file
+
+You can also allow all errors, so that the loading job continues until it has attempted to load all rows in your dataset. Firebolt can write these errors to an Amazon S3 bucket as CSV files. If your specified S3 bucket requires access credentials, you must specify them so that Firebolt can write the files on your behalf. Data rows that load without error are ingested in row order. A loading job that specifies writing error files will write files with the following syntax to your Amazon S3 bucket:
+
+- `error_reasons.csv` - An error file that contains all the reasons that a row generated an error, and also file-based errors.
+- `rejected_rows.csv` - An error file that contains all the rejected rows in row order.
+
+Producing an error while reading Parquet files doesn’t generate row-based error files. On error, only a `error_reasons.csv` file is generated.
+
+The previous files will have an order appended to the name such as `error_reasons_1.csv`.
+
+The following code example allows all errors, provides credentials, and writes two error files to an Amazon S3 bucket:
+
+```
+CREATE TABLE table_write_errors(TournamentID INT, Name INT);
+
+COPY table_write_errors(TournamentID TournamentId, Name Name) FROM 's3://firebolt-publishing-public/help_center_assets/tournaments.csv'
+WITH ERROR_FILE_CREDENTIALS = (
+    AWS_ACCESS_KEY_ID = 'YOUR_AWS_ACCESS_KEY_ID'
+    AWS_SECRET_ACCESS_KEY = 'YOUR_AWS_SECRET_ACCESS_KEY'
+)
+MAX_ERRORS_PER_FILE='100%' HEADER=TRUE ERROR_FILE='s3://bucket_name/error_directory/';
+```
+
+To provide your credentials in the previous example, do the following:
+
+- Replace the `<aws_access_key_id>` with an AWS access key ID that is associated with an AWS user or AWS role. The AWS access key ID is a 20-character string such as `AKIAIOSFODNN7EXAMPLE`.
+- Replace the `<aws_secret_access_key>` with an AWS secret access key associated with an AWS user or IAM role associated with the AWS access key ID. The AWS secret access key is a 40-character string such as `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`.
+
+#### [](#read-errors-from-file)Read errors from file
+
+The previous `COPY FROM` example shows how to create two error files, one that describes the error reasons and one that contains the rows that had errors. This example shows how to load and view the contents of these files.
+
+The following code example reads all files that begin with `error_reasons` and end with `.csv` into an `error_reasons` table:
+
+```
+COPY error_reasons FROM 's3://bucket_name/error_directory/' 
+WITH PATTERN='*error_reasons*.csv' HEADER=TRUE;
+```
+
+The following code returns the contents of the `error_reasons` table:
+
+```
+SELECT * FROM error_reasons ORDER BY source_line_num LIMIT 1;
+```
+
+The following output shows an example of the contents of the `error_reasons` table:
+
+file\_name (TEXT) source\_line\_num (BIGINT) error\_message (TEXT) help\_center\_assets/tournaments.csv 1 Error while casting
+
+The following code reads all files that begin with `rejected_rows` and ends with `.csv` into a rejected\_rows table:
+
+```
+COPY rejected_rows FROM 's3://bucket_name/error_directory/'
+WITH PATTERN='*rejected_rows*.csv' HEADER=FALSE;
+```
+
+Use `SELECT` to view the contents of a file. The following code returns the contents of the `rejected_rows` table:
+
+```
+SELECT * FROM rejected_rows ORDER BY f0 LIMIT 1;
+```
+
+The following output shows the contents of the `rejected_rows` table after running the previous `SELECT` statement:
+
+f0 (TEXT) f1 (TEXT) f2 (TEXT) f3 (TEXT) f4 (TEXT) f5 (TEXT) f6 (TEXT) 1 The Snow Park Grand Prix 1 20903 2021-05-28 20:40:54 2021-05-29 04:51:43 …
+
+#### [](#column-mapping-and-default-values)Column mapping and default values
+
+You can map a specific source column to a target column, and specify a default value to replace any `NULL` values generated during mapping.
+
+The following code example maps the `LevelID` column from the `levels.csv` sample dataset, into a column `LevelID_team_A` in a `target_default_mapping` table. It also maps a non-existent `Country` column in the `levels.csv` dataset, into `LevelsID_team_B`:
+
+```
+CREATE TABLE target_default_mapping ("LevelID_team_A" text, "LevelID_team_B" text);
+COPY target_default_mapping("LevelID_team_A", "LevelID", "LevelID_team_B" default 50 "Country")
+  FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH HEADER=TRUE;
+```
+
+In the previous example, all rows under `LevelsID_team_B` will contain the value `50`.
+
+#### [](#type-mismatch-errors)Type mismatch errors
+
+If you read a column from a source file into a table with an incompatible data type, the mapping generates a casting error. A loading job that specifies writing error files will write files starting with the following prefixes to a specified Amazon S3 bucket:
+
+- `error_reasons` - An error file that contains all the reasons that a row generated an error, and also file-based errors.
+- `rejected_rows` - An error file that contains all the rejected rows in row order.
+
+The following code uses the Firebolt sample `players` dataset which has a column `PlayerID` with a data type of `INTEGER`, and attempts to read it into an existing column with a `DATE` data type:
+
+```
+CREATE TABLE IF NOT EXISTS
+ players (
+   PlayerID DATE,
+   Nickname TEXT,
+   Email TEXT);
+
+COPY players FROM 's3://firebolt-sample-datasets-public-us-east-1/gaming/parquet/players/'
+WITH TYPE=PARQUET MAX_ERRORS_PER_FILE='100%'
+ERROR_FILE='s3://bucket_name/parquet_error_directory/';
+```
+
+Use the following sample code to view a table that contains the contents of all error files that contain `error_reasons`:
+
+```
+COPY error_reasons FROM 's3://bucket_name/parquet_error_directory/'
+WITH PATTERN='*error_reasons*' HEADER=TRUE;
+
+SELECT * FROM error_reasons;
+```
+
+file\_name (TEXT) source\_line\_num (BIGINT) error\_message (TEXT) gaming/parquet/players/11afd184-d2d4-4471-b23c-a14f4c0945a2\_1\_0\_0.snappy.parquet 0 Can not assignment cast column playerid from type integer null to type date null
+
+The type mismatch error in this example creates a file-based error, which is an error that affects the entire file during processing. This query only produces a file-based error and does not produce the `rejected_rows` error file.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_copy_to.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_copy_to.md
new file mode 100644
index 0000000..fe025cb
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_copy_to.md
@@ -0,0 +1,240 @@
+# [](#copy-to)COPY TO
+
+Copies exports or unloads the results of a `SELECT` query to an Amazon S3 source in the file format that you specify. You can specify the output file format, compression type, and other options to control how the data is written, such as file name conventions and whether to overwrite existing files. Use `COPY TO` for backing up query results or integrating Firebolt with other data processing tools.
+
+- [Syntax](#syntax)
+- [Parameters](#parameters)
+- [Credentials](#credentials)
+  
+  - [Credentials for Amazon S3](#credentials-for-amazon-s3)
+  - [Least privileged permissions](#least-privileged-permissions)
+- [Using Location Objects](#using-location-objects)
+  
+  - [Example with Location Object](#example-with-location-object)
+- [Examples](#examples)
+  
+  - [COPY TO with location object](#copy-to-with-location-object)
+  - [COPY TO with defaults and role ARN](#copy-to-with-defaults-and-role-arn)
+  - [COPY TO with single file and AWS access keys](#copy-to-with-single-file-and-aws-access-keys)
+  - [COPY TO with custom file name prefix and ARN with external ID](#copy-to-with-custom-file-name-prefix-and-arn-with-external-id)
+  - [COPY TO with custom file name and overwrite set to TRUE](#copy-to-with-custom-file-name-and-overwrite-set-to-true)
+
+## [](#syntax)Syntax
+
+```
+COPY (<select_query>)
+  TO <location_name>
+[ TYPE = CSV | TSV | JSON | PARQUET ]
+[ COMPRESSION = GZIP | SNAPPY | NONE ]
+[ INCLUDE_QUERY_ID_IN_FILE_NAME = TRUE | FALSE ]
+[ FILE_NAME_PREFIX = <file_string> ]
+[ SINGLE_FILE = FALSE | TRUE ]
+[ MAX_FILE_SIZE = <bytes> ]
+[ OVERWRITE_EXISTING_FILES = FALSE | TRUE ]
+[ HEADER = TRUE | FALSE ]
+|
+COPY (<select_query>)
+  TO '<url>'
+  CREDENTIALS = { AWS_ACCESS_KEY_ID = '<aws_access_key_id>' AWS_SECRET_ACCESS_KEY = '<aws_secret_access_key>' [ AWS_SESSION_TOKEN = '<aws_session_token>' ] | AWS_ROLE_ARN = '<aws_role_arn>' [ AWS_ROLE_EXTERNAL_ID = '<aws_role_external_id>' ] }
+[ TYPE = CSV | TSV | JSON | PARQUET ]
+[ COMPRESSION = GZIP | SNAPPY | NONE ]
+[ INCLUDE_QUERY_ID_IN_FILE_NAME = TRUE | FALSE ]
+[ FILE_NAME_PREFIX = <file_string> ]
+[ SINGLE_FILE = FALSE | TRUE ]
+[ MAX_FILE_SIZE = <bytes> ]
+[ OVERWRITE_EXISTING_FILES = FALSE | TRUE ]
+[ HEADER = TRUE | FALSE ]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<select_query>` Any valid `SELECT` statement. `<location_name>` The name of a location object that contains the Amazon S3 URL and credentials. This is the recommended approach for specifying the destination. See [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html) for more information. `<URL>` The path to an Amazon S3 URL where the query result file or files are saved. For example, `s3://my_bucket/my_folder`. `CREDENTIALS` The Amazon S3 credentials for accessing the specified `<s3_url>`. For more information, see [CREDENTIALS](#credentials). `TYPE` Specifies the file type to save to Amazon S3. If omitted, `CSV` is the default. `COMPRESSION` Specifies the compression algorithm to use for the output files. If omitted, defaults to GZIP. If `NONE` is specified, exported files are not compressed. For `TYPE=PARQUET`, `COMPRESSION` can be set to `NONE`, the default `GZIP`, or `SNAPPY`. Each output file is written in Parquet format, using the specified algorithm to compress each column according to the Parquet specification. This kind of compression is internal to the Parquet file. For `TYPE=CSV`, `TSV`, or `JSON`, `COMPRESSION` can be set to `NONE` or the default `GZIP`. With `GZIP`, the file is first created in the specified format and then compressed into a GZIP file. `INCLUDE_QUERY_ID_IN_FILE_NAME` Specifies whether a query ID is included in the file name. Each time the statement runs, Firebolt generates a new query ID. If omitted, defaults to `TRUE`, and Firebolt saves file names using the pattern `<query_id>.[type].gz`, for example, `123ABCXY2.csv.gz`. This allows Firebolt to generate unique file names by default. If `FALSE`, and `FILE_NAME_PREFIX` is not specified, files are exported with a generic `output` file name, for example, `output.csv.gz`. `FILE_NAME_PREFIX` Specifies an optional string to use in the file name. If `FILE_NAME_PREFIX` is omitted and `INCLUDE_QUERY_ID_IN_FILE_NAME` is `TRUE`, the exported file name is in the pattern `<query_id><file_string>.<type>.gz`. If `FILE_NAME_PREFIX` is specified and `INCLUDE_QUERY_ID_IN_FILE_NAME` is set to `FALSE`, the specified string replaces `output` and the file is in the pattern `<file_string>.<type>.gz`. `SINGLE_FILE` Specifies whether the export should be a single file or multiple files. If omitted, the default is `FALSE`, and the export is split based on the `MAX_FILE_SIZE` value. Exported files are appended with `_<n>` incrementally to indicate the position in series, starting with `0`. For example, the first file in a series might be named `123ABCXY2_0.parquet.gz`. If `TRUE`, only a single file is written. If set to `TRUE` and the file exceeds `MAX_FILE_SIZE`, an error occurs. `MAX_FILE_SIZE` Specifies the max file size in bytes. If omitted, the default value is 16,000,000 bytes (about 16 MB). The maximum file size that can be specified is 5,368,709,120 bytes (5 GB). `OVERWRITE_EXISTING_FILES` Specifies whether exported files should overwrite existing files of the same name in the specified Amazon S3 URL. If omitted, defaults to `FALSE`, and files of the same name are not overwritten. `HEADER` Specifies whether CSV files should contain a header line containing the column names. If omitted, defaults to `TRUE`. Must be omitted for TSV, JSON, or Parquet files.
+
+## [](#credentials)Credentials
+
+Firebolt needs permissions to write query results to the specified Amazon S3 URL. You can specify IAM credentials using the AWS access keys, and the specified credentials must be associated with a user with permissions to write objects to the bucket.
+
+### [](#credentials-for-amazon-s3)Credentials for Amazon S3
+
+Specify access key credentials using the syntax shown below.
+
+```
+  CREDENTIALS = { AWS_ACCESS_KEY_ID = '<aws_access_key_id>' AWS_SECRET_ACCESS_KEY = '<aws_secret_access_key>' [ AWS_SESSION_TOKEN = '<aws_session_token>' ] | AWS_ROLE_ARN = '<aws_role_arn>' [ AWS_ROLE_EXTERNAL_ID = '<aws_role_external_id>' ] }
+```
+
+For Amazon S3 locations, you can use either access key-based authentication or role-based authentication:
+
+Parameter Description `AWS_ACCESS_KEY_ID` Your AWS access key ID `AWS_SECRET_ACCESS_KEY` Your AWS secret access key `AWS_SESSION_TOKEN` Optional temporary session token for temporary credentials `AWS_ROLE_ARN` The ARN of the IAM role to assume `AWS_ROLE_EXTERNAL_ID` Optional external ID for role assumption
+
+For more information on how to create access keys, see [Creating Access Key and Secret ID](/Guides/loading-data/creating-access-keys-aws.html).
+
+### [](#least-privileged-permissions)Least privileged permissions
+
+The example AWS IAM policy statement below demonstrates the minimum actions that must be allowed for Firebolt to write query files to an example Amazon S3 URL. A permissions policy that allows at least these actions for the `<s3_url>` that you specify in the `COPY TO` statement must be attached to the user or role specified in the `CREDENTIALS` clause.
+
+```
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "s3:Get*",
+                "s3:List*",
+                "s3:PutObject",
+                "s3:DeleteObject"
+            ],
+            "Resource": [
+                "arn:aws:s3:::my_s3_bucket",
+                "arn:aws:s3:::my_s3_bucket/*"
+            ]
+        }
+    ]
+}
+```
+
+## [](#using-location-objects)Using Location Objects
+
+Location objects provide a secure and reusable way to specify Amazon S3 destinations for your data exports. This is the recommended approach as it:
+
+- Centralizes credential management
+- Eliminates the need to specify credentials in each COPY statement
+- Provides better security through role-based access control
+- Simplifies maintenance and updates
+
+For more information about location objects, see [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html).
+
+### [](#example-with-location-object)Example with Location Object
+
+```
+COPY (SELECT * FROM test_table)
+  TO my_export_location
+  TYPE = JSON
+  COMPRESSION = NONE
+  SINGLE_FILE = TRUE
+  FILE_NAME_PREFIX = 'latest-export'
+  MAX_FILE_SIZE = 5000000000
+  OVERWRITE_EXISTING_FILES = TRUE;
+```
+
+The location object `my_export_location` contains the Amazon S3 URL and credentials, making the statement cleaner and more secure.
+
+## [](#examples)Examples
+
+- [COPY TO with location object](#copy-to-with-location-object)
+- [COPY TO with defaults and role ARN](#copy-to-with-defaults-and-role-arn)
+- [COPY TO with single file and AWS access keys](#copy-to-with-single-file-and-aws-access-keys)
+- [COPY TO with custom file name prefix and ARN with external ID](#copy-to-with-custom-file-name-prefix-and-arn-with-external-id)
+- [COPY TO with custom file name and overwrite set to TRUE](#copy-to-with-custom-file-name-and-overwrite-set-to-true)
+
+### [](#copy-to-with-location-object)COPY TO with location object
+
+This example demonstrates the recommended approach using a location object. The location object contains the Amazon S3 URL and credentials, making the statement more secure and maintainable.
+
+```
+COPY (SELECT * FROM test_table)
+  TO my_export_location
+  TYPE = JSON
+  COMPRESSION = NONE
+  SINGLE_FILE = TRUE
+  FILE_NAME_PREFIX = 'latest-export'
+  MAX_FILE_SIZE = 5000000000
+  OVERWRITE_EXISTING_FILES = TRUE;
+```
+
+Firebolt writes a single file as shown below.
+
+```
+s3://my_bucket/exports/
+  latest-export.json
+```
+
+### [](#copy-to-with-defaults-and-role-arn)COPY TO with defaults and role ARN
+
+The example below shows a `COPY TO` statement with minimal parameters that specifies an `AWS_ROLE_ARN`. Because `TYPE` is omitted, the file or files will be written in CSV format, and because `COMPRESSION` is omitted, they are compressed using GZIP (`*.csv.gz`).
+
+```
+COPY (SELECT * FROM test_table)
+  TO 's3://my-bucket/path/to/data'
+  CREDENTIALS = (AWS_ROLE_ARN='arn:aws:iam::123456789012:role/my-firebolt-role');
+```
+
+Firebolt assigns the query ID `16B903C4206098FD` to the query at runtime. The compressed output is 40 MB, exceeding the default of 16 MB, so Firebolt writes 4 files as shown below.
+
+```
+s3://my_bucket/my_fb_queries/
+  16B903C4206098FD_0.csv.gz
+  16B903C4206098FD_1.csv.gz
+  16B903C4206098FD_2.csv.gz
+  16B903C4206098FD_3.csv.gz
+```
+
+### [](#copy-to-with-single-file-and-aws-access-keys)COPY TO with single file and AWS access keys
+
+The example below exports a single, uncompressed JSON file with the same name as the query ID. If the file to be written exceeds the specified `MAX_FILE_SIZE` (5 GB), an error occurs. AWS access keys are specified for credentials.
+
+```
+COPY (SELECT * FROM test_table)
+  TO 's3://my-bucket/path/to/data'
+  TYPE=JSON
+  COMPRESSION=NONE
+  CREDENTIALS=(AWS_ACCESS_KEY_ID='AKIAIOSFODNN7EXAMPLE' AWS_SECRET_ACCESS_KEY='wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY')
+  INCLUDE_QUERY_ID_IN_FILE_NAME=TRUE
+  SINGLE_FILE=TRUE
+  MAX_FILE_SIZE=5000000000;
+```
+
+Firebolt writes a single file as shown below.
+
+```
+s3://my_bucket/my_fb_queries/
+  16B90E96716236D0.json
+```
+
+### [](#copy-to-with-custom-file-name-prefix-and-arn-with-external-id)COPY TO with custom file name prefix and ARN with external ID
+
+In the example below, because `FILE_NAME_PREFIX` parameter is specified, Firebolt adds a string to the query ID to form file names. The IAM role specified for `CREDENTIALS` also has an external ID configured in AWS, so the ID is specified.
+
+```
+COPY (SELECT * FROM test_table)
+  TO 's3://my-bucket/path/to/data'
+  TYPE=JSON
+  COMPRESSION=NONE
+  CREDENTIALS = (AWS_ROLE_ARN='arn:aws:iam::123456789012:role/my-firebolt-role' AWS_ROLE_EXTERNAL_ID='99291')
+  FILE_NAME_PREFIX='_query_result';
+```
+
+Firebolt assigns the query an id of `16B90E96716236D6` at runtime and writes files as shown below.
+
+```
+s3://my_bucket/my_fb_queries/
+  16B90E96716236D6_query_result_0.json
+  16B90E96716236D6_query_result_1.json
+  16B90E96716236D6_query_result_2.json
+  16B90E96716236D6_query_result_3.json
+  16B90E96716236D6_query_result_4.json
+```
+
+### [](#copy-to-with-custom-file-name-and-overwrite-set-to-true)COPY TO with custom file name and overwrite set to TRUE
+
+In the example below, `INCLUDE_QUERY_ID_IN_FILE_NAME` is set to `FALSE` and a `FILE_NAME_PREFIX` is specified. In this case, Firebolt writes files using only the specified `FILE_NAME_PREFIX` as the file name. In addition, `SINGLE_FILE` and `OVERWRITE_EXISTING_FILES` are set to `TRUE` so that the Amazon S3 URL always contains a single file with the latest query results.
+
+```
+COPY (SELECT * FROM test_table)
+  TO 's3://my_bucket/my_fb_query'
+  TYPE=JSON
+  COMPRESSION=NONE
+  CREDENTIALS=(AWS_ROLE_ARN = 'arn:aws:iam::123456789012:role/my-firebolt-role')
+  INCLUDE_QUERY_ID_IN_FILE_NAME=FALSE
+  SINGLE_FILE=TRUE
+  FILE_NAME_PREFIX='latest-fb-query-result'
+  MAX_FILE_SIZE=5000000000
+  OVERWRITE_EXISTING_FILES=TRUE;
+```
+
+Firebolt writes a single file as shown below.
+
+```
+s3://my_bucket/my_fb-query/
+  latest-fb-query-result.json
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_delete.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_delete.md
new file mode 100644
index 0000000..b98fd43
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_delete.md
@@ -0,0 +1,57 @@
+# [](#delete)DELETE
+
+Deletes rows from the specified table.
+
+## [](#syntax)Syntax
+
+```
+DELETE FROM <table> [[AS] <alias>] [USING <from_item>] WHERE <condition>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table>` The table to delete rows from. `<from_item>` A table expression allowing columns from other tables to appear in the `WHERE` condition. This uses the same syntax as the `FROM` clause of a `SELECT` statement; for example, an alias for the table name can be specified. Do not repeat the target table as a `from_item` unless you wish to set up a self-join (in which case it must appear with an alias in the `from_item`). `<condition>` A Boolean expression. Only rows for which this expression returns `true` will be deleted. Condition can have subqueries doing semi-join with other table(s).
+
+The `DELETE FROM <table>` without `<expression>` will delete *all* rows from the table. It is equivalent to a [TRUNCATE TABLE](/sql_reference/commands/data-management/truncate-table.html) statement.
+
+## [](#remarks)Remarks
+
+Deleted rows are marked for deletion, but are not automatically cleaned up. You can monitor fragmentation in [information\_schema.tables](/sql_reference/information-schema/tables.html) to understand how many rows are marked for deletion out of total rows; fragmentation = (rows marked for deletion / total rows). Total row count in `information_schema.tables` excludes the number of rows marked for deletion. Query performance is not materially impacted by delete marks.
+
+To mitigate fragmentation, use the [VACUUM](/sql_reference/commands/data-management/vacuum.html) command to manually clean up deleted rows.
+
+## [](#example)Example
+
+The following example deletes entries from the `products` table where the `quantity` is less than `10`:
+
+```
+DELETE FROM products WHERE quantity < 10
+```
+
+Table before:
+
+product quantity wand 9 broomstick 21 robe 1 quidditch gloves 10 cauldron 16 quill 100
+
+Table after:
+
+product quantity broomstick 21 quidditch gloves 10 cauldron 16 quill 100
+
+### [](#example-specifying-other-tables-in-the-using-clause)Example specifying other tables in the USING clause
+
+This example deletes all the products from stores that went out of business.
+
+```
+DELETE FROM products USING suppliers WHERE products.product = suppliers.product AND suppliers.store = 'Ollivanders'
+```
+
+Table `products` before:
+
+product quantity wand 9 broomstick 21 robe 1 quidditch gloves 10 cauldron 16 quill 100
+
+Table `suppliers` before:
+
+product store wand Ollivanders broomstick Quality Quidditch Supplies robe Madam Malkin’s quidditch gloves Quality Quidditch Supplies cauldron Apothecary quill Amanuensis Quills
+
+Table `products` after:
+
+product quantity broomstick 21 robe 1 quidditch gloves 10 cauldron 16 quill 100
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_insert.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_insert.md
new file mode 100644
index 0000000..291e7ba
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_insert.md
@@ -0,0 +1,45 @@
+# [](#insert)INSERT
+
+Inserts one or more values into a specified table. Specifying column names is optional.
+
+- [Syntax](#syntax)
+- [Example](#example)
+
+## [](#syntax)Syntax
+
+```
+INSERT INTO <table> [(<column1>[, <column2>][, ...])]
+{ <expression> | VALUES ([<value1>[, <value2>][, ...]) }
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table>` The target table where values are to be inserted. `(<column1>[, <column2>][, ...])]` A list of column names from `<table_name>` for the insertion. If not defined, the columns are deduced from the `<select_statement>`. `<expression>`  
+–OR–  
+`VALUES ([<value1>[, <value2>][, ...])]` You can specify either a [`SELECT` query](/sql_reference/commands/queries/select.html) that determines values to or an explicit list of `VALUES` to insert.
+
+## [](#example)Example
+
+First, create a table populated with student information as follows:
+
+```
+CREATE TABLE students (
+    id INT,
+    full_name TEXT,
+    dob DATE,
+    gender TEXT)
+```
+
+Next, use `INSERT` to add two rows into the `students` table as follows:
+
+```
+INSERT INTO students VALUES
+    (1, 'Harry Potter', DATE '1980-07-31', 'M'),
+    (2, 'Hermione Granger', DATE '1979-09-19', 'F')
+```
+
+You can also add another row with only some of the columns populated. The missing `dob` column for date of birth does not have default value, so Firebolt sets it to `NULL`.
+
+```
+INSERT INTO students (id, full_name, gender) VALUES (3, 'Ron Weasley', 'M')
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_truncate_table.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_truncate_table.md
new file mode 100644
index 0000000..cb1b7ef
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_truncate_table.md
@@ -0,0 +1,44 @@
+# [](#truncate-table)TRUNCATE TABLE
+
+Removes all rows from a table.
+
+## [](#syntax)Syntax
+
+```
+TRUNCATE TABLE <table_name> 
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table_name>` The name of the table to be truncated.
+
+### [](#example)Example
+
+```
+TRUNCATE TABLE product;
+```
+
+Table before
+
+```
+product
++------------+--------+
+| name       | price  |
++---------------------+
+| wand       |    125 |
+| broomstick |    270 |
+| bludger    |      0 |
+| robe       |     80 |
+| cauldron   |     25 |
+| quaffle    |      0 |
++------------+--------+
+```
+
+Table after
+
+```
+product
++------------+--------+
+| name       | price  |
++---------------------+
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_update.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_update.md
new file mode 100644
index 0000000..9115856
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_update.md
@@ -0,0 +1,73 @@
+# [](#update)UPDATE
+
+Updates rows in the specified table.
+
+## [](#syntax)Syntax
+
+```
+UPDATE <table> [ [ AS ] <alias> ] SET <column1> = <expression1> [, <column2> = <expression2> ...] [ FROM from_item [, ...] ] WHERE <condition>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table>` The table name to update rows in. `<column>` The name of the column to be updated. `<expression>` An expression which computes a new value to populate the column. The expression can reference any column from the row being updated. `<from_item>` A table expression allowing columns from other tables to appear in the `WHERE` condition and update expressions. This uses the same syntax as the `FROM` clause of a `SELECT` statement; for example, an alias for the table name can be specified. Do not repeat the target table as a `from_item` unless you intend a self-join (in which case it must appear with an alias in the `from_item`). `<condition>` A Boolean expression. Only rows for which this expression returns `true` will be updated. Condition can have subqueries doing semi-join with other table(s).
+
+## [](#remarks)Remarks
+
+Updated rows are marked for deletion, but are not automatically cleaned up. You can monitor fragmentation in `information_schema.tables` to understand how many rows are marked for deletion out of total rows; fragmentation = (rows marked for deletion / total rows). Total row count in `information_schema.tables` excludes the number of rows marked for deletion. Query performance is not materially impacted by delete marks.
+
+To mitigate fragmentation, use the [VACUUM](/sql_reference/commands/data-management/vacuum.html) command to manually clean up deleted rows.
+
+When a `FROM` clause is present, what essentially happens is that the target table is joined to the tables mentioned in the `from_item` list, and each output row of the join represents an update operation for the target table. When using `FROM` the join must produce at most one output row for each row to be modified. In other words, a target row shouldn’t join to more than one row from the other table(s).
+
+### [](#example-with-where)Example with WHERE
+
+The following example restocks `product` for which `quantity` is less than `10`:
+
+```
+UPDATE product SET quantity = quantity + 10 WHERE quantity < 10
+```
+
+Table before:
+
+name price quantity wand 120 9 robe 80 1 broomstick 270 21 cauldron 20 16 quill 5 100
+
+Table after:
+
+name price quantity wand 120 19 robe 80 11 broomstick 270 21 cauldron 20 16 quill 5 100
+
+### [](#example-updating-multiple-columns)Example updating multiple columns
+
+This example applies a discount and updates the quantity of a specific product.
+
+```
+UPDATE product SET price = 15, quantity = 100 WHERE name = 'cauldron'
+```
+
+Table before:
+
+name price quantity wand 120 9 broomstick 270 21 robe 80 1 cauldron 20 16 quill 5 100
+
+Table after:
+
+name price quantity wand 120 9 broomstick 270 21 robe 80 1 cauldron 15 100 quill 5 100
+
+### [](#example-updating-with-from)Example updating with FROM
+
+This example updates available stock count.
+
+```
+UPDATE product AS p SET quantity = p.quantity - s.amount FROM sales AS s WHERE p.name = s.name
+```
+
+Table `product` before:
+
+name price quantity wand 120 9 broomstick 270 21 robe 80 1 cauldron 20 16 quill 5 100
+
+Table `sales` before:
+
+name amount wand 5 broomstick 3 quill 20
+
+Table `products` after:
+
+name price quantity wand 120 4 broomstick 270 18 robe 80 1 cauldron 20 16 quill 5 80
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_vacuum.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_vacuum.md
new file mode 100644
index 0000000..9e2c611
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_data_management_vacuum.md
@@ -0,0 +1,111 @@
+# [](#vacuum)VACUUM
+
+Optimizes tablets for query performance.
+
+`VACUUM` improves query efficiency by restructuring tablets for optimal performance. DML operations such as [DELETE](/sql_reference/commands/data-management/delete.html), [UPDATE](/sql_reference/commands/data-management/update.html), [INSERT](/sql_reference/commands/data-management/insert.html), and [COPY FROM](/sql_reference/commands/data-management/copy-from.html) might create tablets that are not optimally sized. Suboptimal tablets occur because DML efficiently utilizes resources in proportion to the cardinality of the data being inserted. In addition to standard SQL operations, tuples that are deleted by an update are not always physically removed from their table; they remain present until a `VACUUM` is finished operating. In other words, tablets are not necessarily optimal for running queries; therefore, it’s necessary to run `VACUUM` periodically, especially on frequently updated tables.
+
+Any engine that processes a DML operation automatically assesses the health of tables’ data layout and runs the `VACUUM` command when necessary to maintain the underlying table health. The fragmentation ratio—the ratio of rows marked for deletion to the total number of rows—can be monitored using the `information_schema.tables view`. You can also run `VACUUM` manually using the syntax and options described below.
+
+## [](#syntax)Syntax
+
+```
+VACUUM [ (option_name = option_value) ] <table|aggregating index>
+```
+
+Where `<table|aggregating index>` is the name of the table or aggregating index to be optimized.
+
+## [](#options)Options
+
+Option name Option value and description `INDEXES` `FULL` — (Default) Specifies whether to apply optimizations to both the table and all its aggregating indexes.  
+`INCREMENTAL` — Similar to `FULL`, but will apply incremental optimizations to aggregating indexes, instead of complete reevaluation.  
+`NONE` — Optimizes only the table. `MAX_CONCURRENCY` `<Number>` — The maximum number of concurrent jobs to use during optimization.
+
+## [](#examples)Examples
+
+**Optimize a table and its aggregating indexes**
+
+Optimizing a table along with its aggregating indexes ensures that both the data and aggregating indexes remain efficient, reducing query latency and improving overall performance.  
+The following code example optimizes the `games` table and all its aggregating indexes:
+
+```
+VACUUM games;
+```
+
+The example above performs a complete rebuild of related aggregating indexes. Alternatively, you can specify to apply incremental optimization, which still improves index layout while using fewer resources, though it may not achieve optimal layout:
+
+```
+VACUUM (INDEXES = INCREMENTAL) games;
+```
+
+**Optimize a table without its indexes**
+
+If you need to optimize a table without including its aggregating indexes to reduce resource usage, or retain efficient indexes, you can optimize only the table to prevent unnecessary computations.  
+The following code example optimizes the `players` table without updating its aggregating indexes:
+
+```
+VACUUM (INDEXES = NONE) players;
+```
+
+Optimize table named `players`, using a single concurrent stream.
+
+```
+VACUUM (MAX_CONCURRENCY = 1) players;
+```
+
+### [](#usage-notes)Usage Notes
+
+The following are considerations for running the `VACUUM` command:
+
+- **What happens during VACUUM**  
+  `VACUUM` analyzes the tablets, selects the ones that are too small or have too many deleted rows, and produces new versions that are optimized for query execution for both tablets and Aggregate Indexes.  
+  `VACUUM` runs as a non-blocking process, alongside other user-initiated operations. Consequently, some changes performed by `VACUUM` may conflict with mutations run by the user. If `VACUUM` and a user mutation modify the same data, the first committed operation takes precedence; see [Transactions and concurrency](/Overview/data-management.html#transactions-and-concurrency) for more details. This means that applications that run mutations in parallel with `VACUUM` should gracefully handle transaction conflicts. It also means that benefits of the `VACUUM` may be diminished by a mutation that committed data first.
+- **Space and performance considerations**  
+  Users must be aware that `VACUUM` consumes both compute and storage resources.  
+  `VACUUM` can consume a considerable amount of compute resources depending on the table size, number of tablets, and number of mutations in the table.  
+  `VACUUM` parallelizes its work into multiple concurrent streams, based on the number of CPU cores. While this can be beneficial for the speed of the operation, each stream consumes memory and CPU resources. Use the `MAX_CONCURRENCY` option to limit the number of concurrent streams.  
+  `VACUUM` produces optimized versions of the data, while leaving behind older versions subject to the garbage collection (GC) process. These older tablets will continue to consume storage space until the GC process completes the clean-up.  
+  If users would like to have precise control over `VACUUM`, it may be preferable to run on a dedicated engine that could be sized and run just for `VACUUM` operations. With `VACUUM` running on a dedicated engine, it would not conflict with other queries’ execution and cache resources, and would provide operational separation from other scenarios.  
+  `VACUUM` may introduce a performance penalty as the newly created optimized tablets need to be synchronized with other engines operating on the same table(s).
+- **Automatic scheduling**  
+  You can enable automatic scheduling of processes such as `VACUUM` by integrating with external tools. Please see section [Integrate with Firebolt](/Guides/integrations/integrations.html) for more detail on our current support for these tools.
+
+### [](#example-with-measuring-the-performance-impact-of-vacuum)Example with measuring the performance impact of VACUUM
+
+Over time, operations such as `INSERT`, `DELETE`, and `UPDATE` can create suboptimal tablets that decrease query performance. The `VACUUM` command restructures these tablets by removing deleted rows and optimizing storage, leading to faster queries.
+
+This example demonstrates the impact of `VACUUM` by:
+
+1. Creating a large table with 10 million rows.
+2. Deleting 90% of the rows, leaving behind fragmented data.
+3. Running a query before and after `VACUUM` to compare run times.
+
+The following code example loads data from a CSV file in an Amazon S3 bucket into the `tutorial_vacuum` table with headers:
+
+```
+COPY tutorial_vacuum
+FROM 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv'
+WITH HEADER=TRUE;
+
+INSERT INTO tutorial_vacuum
+SELECT a.* FROM tutorial_vacuum a, GENERATE_SERIES(1, 1000000); -- This may run a couple of minutes
+```
+
+Script above loads 10 rows from S3 csv file; after that it inserts into the same table the cross product of the 10 inserted rows with 1 million integers. Next, the following code example deletes all rows from the `tutorial_vacuum` table where the `LevelID` value is greater than 1, resulting in about 900,000 deleted rows:
+
+```
+DELETE FROM tutorial_vacuum WHERE "LevelID" > 1;
+```
+
+The following code example runs a query computing checksum of the entire `tutorial_vacuum` table before and after performing `VACUUM`, allowing a comparison of query performance and efficiency improvements after optimization.
+
+```
+SELECT hash_agg(*) FROM tutorial_vacuum;
+VACUUM tutorial_vacuum;
+SELECT hash_agg(*) FROM tutorial_vacuum;
+```
+
+In the previous code example, the first `SELECT` is run on data with many deleted rows, while the second runs after `VACUUM`, benefiting from it. The following query history shows the performance benefit of the `VACUUM` operation:
+
+NO STATEMENT STATUS DURATION 1 `SELECT hash_agg(*) FROM tutorial_vacuum;` Success 4.43 s 2 `VACUUM tutorial_vacuum;` Success 17.53 s 3 `SELECT hash_agg(*) FROM tutorial_vacuum;` Success 0.82 s
+
+Note that the initial `SELECT` query ran for over 4 seconds, while the identical `SELECT` query ran for under a second, after running `VACUUM`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines.md
new file mode 100644
index 0000000..2bd5cd0
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines.md
@@ -0,0 +1,14 @@
+## [](#engine-commands)Engine commands
+
+Engine commands allow you to create, modify, start, stop, and manage Firebolt engines. Engines are compute resources that process queries and handle data ingestion. These commands help control engine availability, configuration, and resource allocation based on workload needs.
+
+Use the following to manage Firebolt engines:
+
+- [ALTER ENGINE](/sql_reference/commands/engines/alter-engine.html) – Modify an existing engine’s configuration, such as node type, cluster count, or concurrency settings.
+- [CREATE ENGINE](/sql_reference/commands/engines/create-engine.html) – Define and provision a new Firebolt engine with specific compute resources.
+- [DROP ENGINE](/sql_reference/commands/engines/drop-engine.html) – Remove an existing engine.
+- [START ENGINE](/sql_reference/commands/engines/start-engine.html) – Activate an engine to make it available for running queries.
+- [STOP ENGINE](/sql_reference/commands/engines/stop-engine.html) – Shut down an engine to free up resources when not in use.
+- [USE ENGINE](/sql_reference/commands/engines/use-engine.html) – Set an active engine for running queries in the current session.
+
+Each command provides fine-grained control over compute resources, ensuring that queries run efficiently while managing costs. Select a command from the list for syntax and usage details.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_alter_engine.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_alter_engine.md
new file mode 100644
index 0000000..ceed222
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_alter_engine.md
@@ -0,0 +1,106 @@
+# [](#alter-engine)ALTER ENGINE
+
+Modify the configuration of an existing Firebolt engine.
+
+## [](#alter-engine-set)ALTER ENGINE SET
+
+Updates the configuration of the specified engine.
+
+### [](#syntax)Syntax
+
+```
+ALTER ENGINE <engine_name> SET
+    [AUTO_START = <true/false>]
+    [AUTO_STOP = <minutes>]
+    [DEFAULT_DATABASE = <database_name>]
+    [CLUSTERS = <clusters>]
+    [MIN_CLUSTERS = <clusters>]
+    [MAX_CLUSTERS = <clusters>]
+    [NODES = <nodes>]
+    [TYPE = <type>]
+    [FAMILY = <family>]
+```
+
+### [](#options)Options
+
+Parameter Description `<engine_name>` The name of the engine to be altered. `AUTO_START = <true/false>` When set to `TRUE`, sending a query to a stopped engine will automatically start the engine before processing the query. `AUTO_STOP = <minutes>` Specifies the number of minutes after which an engine automatically stops. Setting `minutes` to `0` disables `AUTO_STOP`. `DEFAULT_DATABASE = <database_name>` Specifies the default database that an engine will attempt to use when processing queries that require a database. To remove the default database, set `DEFAULT_DATABASE=default`. `CLUSTERS = <clusters>` Specifies the number of clusters in an engine. Each cluster is a group of nodes, and all clusters within an engine are identical in terms of node type and number of nodes. `MIN_CLUSTERS = <clusters>` Specifies a minimum number of clusters in an engine. If `MIN_CLUSTERS` is different from `MAX_CLUSTERS`, the engine will automatically change the number of clusters depending on load. If not specified, `1` is used as default. `MAX_CLUSTERS = <clusters>` Specifies a maximum number of clusters in an engine. If `MIN_CLUSTERS` is different from `MAX_CLUSTERS`, the engine will automatically change the number of clusters depending on load. If not specified, `1` is used as default. `NODES = <nodes>` Specifies the number of nodes in each cluster within an engine. You can specify any integer between `1` to `128`, inclusive. `TYPE =<type>` Specifies the node type for the engine. You can choose `S`, `M`, `L`, or `XL`. `FAMILY =<family>` Defines the family of node used in the engine. Options include `STORAGE_OPTIMIZED` (alias `SO`) or `COMPUTE_OPTIMIZED` (alias `CO`).
+
+**Limitations:**
+
+- Each engine is limited to a maximum of two clusters.
+- Each cluster can have up to ten nodes.
+- The total number of nodes across all clusters cannot exceed 15.
+- When scaling a running engine either vertically or horizontally, new queries will be directed to the new cluster. Queries running on the original clusters will continue until completion. The clusters will wait up to 24 hours for these queries to finish, after which any unfinished queries may be stopped.
+- Only small and medium engines are available for use right away.
+
+If you would like to remove the following limitations, reach out to Firebolt support at [support@firebolt.io](mailto:support@firebolt.io) to do the following:
+
+- Use a large or extra-large engine.
+- Use more than ten nodes per cluster.
+- Use more than 15 nodes across all clusters.
+
+## [](#examples)Examples
+
+### [](#scale-out-an-engine)Scale out an engine
+
+The following code example scales out, or increases the number of nodes, in an engine by setting the engine’s `NODES` to `3`:
+
+```
+ALTER ENGINE my_engine SET NODES = 3;
+```
+
+### [](#scale-up-an-engine)Scale up an engine
+
+The following code example scales up an engine by increasing its capacity from small (`S`) to large (`L`) by setting the engine’s `TYPE` parameter to `L`:
+
+```
+ALTER ENGINE my_engine SET TYPE = "L";
+```
+
+### [](#scale-up-and-out-an-engine)Scale up and out an engine
+
+The following code example both scales up and scales out an engine by increasing node capacity and the number of nodes:
+
+```
+ALTER ENGINE my_engine SET TYPE = "L" NODES = 5;
+```
+
+If you need to use a large or extra-large engine, reach out to [support@firebolt.io](mailto:support@firebolt.io).
+
+### [](#enable-concurrency-auto-scaling)Enable concurrency auto-scaling
+
+The following code example adjusts the maximum number of engine clusters to enable concurrency auto-scaling:
+
+```
+ALTER ENGINE my_engine SET MAX_CLUSTERS = 2;
+```
+
+## [](#alter-engine-rename-to)ALTER ENGINE RENAME TO
+
+Renames an engine.
+
+### [](#syntax-1)Syntax
+
+```
+ALTER ENGINE <engine_name> RENAME TO <new_engine_name>
+```
+
+### [](#parameters)Parameters
+
+Parameter Description `<engine_name>` The name of the engine to rename. `<new_engine_name>` The new name of the engine.
+
+## [](#alter-engine-owner-to)ALTER ENGINE OWNER TO
+
+Changes the owner of an engine. You can view the current owner in the the `engine_owner` column of the `information_schema.engines` view.
+
+For more information, see [ownership](/Guides/security/ownership.html).
+
+### [](#syntax-2)Syntax
+
+```
+ALTER ENGINE <engine_name> OWNER TO <user>
+```
+
+### [](#parameters-1)Parameters
+
+Parameter Description `<engine_name>` The name of the engine to change the owner of. `<user>` The new owner of the engine.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_create_engine.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_create_engine.md
new file mode 100644
index 0000000..c693b19
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_create_engine.md
@@ -0,0 +1,107 @@
+# [](#create-engine)CREATE ENGINE
+
+Creates an engine, which serves as a compute cluster for running queries and processing data.
+
+## [](#syntax)Syntax
+
+```
+CREATE ENGINE [IF NOT EXISTS] <engine_name>
+[WITH 
+    [AUTO_START = <true/false>]
+    [AUTO_STOP = <minutes>]
+    [DEFAULT_DATABASE = <database_name>]
+    [INITIALLY_STOPPED = <true/false>]
+    [START_IMMEDIATELY = <true/false>]
+    [CLUSTERS = <clusters>]
+    [MIN_CLUSTERS = <clusters>]
+    [MAX_CLUSTERS = <clusters>]
+    [NODES = <nodes>]
+    [TYPE = <type>]
+    [FAMILY = <family>]]
+```
+
+## [](#options)Options
+
+Parameter Description `<engine_name>` The name of the engine to be created. `AUTO_START = <true/false>` When `true`, sending a query to a stopped engine will start the engine before processing the query.
+
+If not specified, `true` will be used as default. `AUTO_STOP = <minutes>` The amount of idle time (in minutes) after which the engine automatically stops.  
+Setting the minutes to `0` indicates that `AUTO_STOP` is disabled.
+
+If not specified, `20` is used as default. `DEFAULT_DATABASE = <database_name>` The database an engine will attempt to use by default when dealing with queries that require a database.
+
+If not specified, `NULL` is used as default. `INITIALLY_STOPPED = <true/false>` When `false`, the newly created engine will be started as part of the `CREATE ENGINE` command.  
+Cannot be used with `START_IMMEDIATELY`.
+
+If not specified, `false` is used as default. `START_IMMEDIATELY = <true/false>` When `true`, the newly created engine will be started as part of the `CREATE ENGINE` command.  
+Cannot be used with `INITIALLY_STOPPED`.
+
+If not specified, `true` is used as default. `CLUSTERS = <clusters>` Specifies the number of clusters in an engine. Each cluster is a group of nodes, and all clusters within an engine are identical in terms of node type and number of nodes.
+
+If not specified, `1` is used as default. `MIN_CLUSTERS = <clusters>` Specifies a minimum number of clusters in an engine. If `MIN_CLUSTERS` is different from `MAX_CLUSTERS`, the engine will automatically change the number of clusters depending on load.
+
+If not specified, `1` is used as default. `MAX_CLUSTERS = <clusters>` Specifies a maximum number of clusters in an engine. If `MIN_CLUSTERS` is different from `MAX_CLUSTERS`, the engine will automatically change the number of clusters depending on load.
+
+If not specified, `1` is used as default. `NODES = <nodes>` Indicates the number of nodes in each cluster within an engine. This number can range from `1` to `128`.
+
+If not specified, `2` is used as default. `TYPE =<type>` Defines the type of node used in the engine. Options include `S`, `M`, `L`, or `XL`
+
+If not specified, `M` is used as default. `FAMILY =<family>` Defines the family of node used in the engine. Options include `STORAGE_OPTIMIZED` (alias `SO`) or `COMPUTE_OPTIMIZED` (alias `CO`)
+
+If not specified, `STORAGE_OPTIMIZED` is used as default.
+
+**Limitations:**
+
+- The number of clusters per engine is limited to two.
+- The number of nodes per cluster is limited to ten.
+- The total number of nodes x clusters cannot exceed 15.
+- Only small and medium engines are available for use right away.
+
+If you would like to remove the above limitations or use a large or extra-large engine, reach out to Firebolt Support at [support@firebolt.io](mailto:support@firebolt.io).
+
+## [](#examples)Examples
+
+### [](#create-a-basic-engine)Create a basic engine
+
+The following example creates an engine with one cluster, using node type ‘S’ and 1 nodes per cluster :
+
+```
+CREATE ENGINE my_engine;
+```
+
+### [](#create-an-engine-with-multiple-nodes)Create an engine with multiple nodes
+
+The following example creates an engine with one cluster, using node type ‘S’ and 5 nodes per cluster :
+
+```
+CREATE ENGINE my_engine
+WITH TYPE="S" NODES = 5 CLUSTERS = 1;
+```
+
+### [](#create-an-engine-with-delayed-start)Create an engine with delayed start
+
+The following example creates an engine with one cluster, using node type ‘M’ and 3 nodes per cluster. The engine will not be automatically started after creation because `INITIALLY_STOPPED` is set to true.
+
+```
+CREATE ENGINE my_engine
+WITH TYPE="M" NODES=3 INITIALLY_STOPPED=true;
+```
+
+### [](#create-an-engine-with-auto-stop)Create an engine with auto-stop
+
+The following example creates an engine with one cluster, using node type ‘L’ in the compute-optimized family with 2 nodes per cluster. The engine will be automatically stopped after 10 minutes of idle time because `AUTO_STOP` is set to 10.
+
+```
+CREATE ENGINE my_engine
+WITH TYPE="L" FAMILY="COMPUTE_OPTIMIZED" NODES=2 AUTO_STOP=10;
+```
+
+If you need to use a large or extra-large engine, reach out to [support@firebolt.io](mailto:support@firebolt.io).
+
+### [](#create-an-engine-with-concurrency-auto-scaling)Create an engine with concurrency auto-scaling
+
+The following example creates an engine that automatic concurrency scaling. The engine adjusts the number of clusters based on workload demand, maintaining between one and two clusters.
+
+```
+CREATE ENGINE my_engine
+WITH MIN_CLUSTERS=1 MAX_CLUSTERS=2;
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_drop_engine.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_drop_engine.md
new file mode 100644
index 0000000..33363b5
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_drop_engine.md
@@ -0,0 +1,21 @@
+# [](#drop-engine)DROP ENGINE
+
+Deletes an engine.
+
+## [](#syntax)Syntax
+
+```
+DROP ENGINE [IF EXISTS] <engine_name>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<engine_name>` The name of the engine to be deleted.
+
+## [](#example)Example
+
+The following example drops my\_engine:
+
+```
+DROP ENGINE my_engine
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_start_engine.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_start_engine.md
new file mode 100644
index 0000000..dfdac80
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_start_engine.md
@@ -0,0 +1,21 @@
+# [](#start-engine)START ENGINE
+
+Starts a stopped engine.
+
+## [](#syntax)Syntax
+
+```
+START ENGINE <engine_name>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<engine_name>` The name of the engine to be started.
+
+## [](#example)Example
+
+The following example starts my\_engine:
+
+```
+START ENGINE my_engine
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_stop_engine.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_stop_engine.md
new file mode 100644
index 0000000..e548fbd
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_stop_engine.md
@@ -0,0 +1,40 @@
+# [](#stop-engine)STOP ENGINE
+
+Stops a running engine.
+
+## [](#syntax)Syntax
+
+```
+STOP ENGINE [IF EXISTS] <engine_name>
+[WITH 
+    [TERMINATE = <true/false>]]
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<engine_name>` The name of the engine to be stopped. `<TERMINATE>` When `false`, the engine will wait for running queries to finish before stopping.  
+When `true`, the engine will stop without waiting for running queries to complete.
+
+If not specified, `false` is used as default.
+
+**Limitations:**
+
+- When `TERMINATE=false` (default), the engine will wait for up to 24 hours for running queries to finish before stopping. After 24 hours, the engine will finish shutting down. Any queries still running may not run to completion.
+
+If you would like to remove any of these limitations, reach out to Firebolt Support.
+
+## [](#example-1)Example 1
+
+The following example waits for queries on my\_engine to finish before stopping:
+
+```
+STOP ENGINE my_engine
+```
+
+## [](#example-2)Example 2
+
+The following example stops my\_engine without waiting for running queries to finish:
+
+```
+STOP ENGINE my_engine WITH TERMINATE=true
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_use_engine.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_use_engine.md
new file mode 100644
index 0000000..06717ca
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_engines_use_engine.md
@@ -0,0 +1,33 @@
+# [](#use-engine)USE ENGINE
+
+Changes the client to direct queries against the specified engine.
+
+The client can be updated to direct queries against the system engine by using `system` for the `engine_name`.
+
+Changing the engine used by the client will reset the user’s session.
+
+## [](#syntax)Syntax
+
+```
+USE ENGINE <engine_name>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<engine_name>` The name of the engine to be used.
+
+## [](#example-1)Example 1
+
+The following example changes the client to use my\_engine:
+
+```
+USE ENGINE my_engine
+```
+
+## [](#example-2)Example 2
+
+The following example changes the client to use system:
+
+```
+USE ENGINE system
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata.md
new file mode 100644
index 0000000..23649ba
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata.md
@@ -0,0 +1,12 @@
+## [](#metadata-commands)Metadata commands
+
+* * *
+
+- [DESCRIBE](/sql_reference/commands/metadata/describe.html)
+- [SHOW CACHE](/sql_reference/commands/metadata/show-cache.html)
+- [SHOW CATALOGS](/sql_reference/commands/metadata/show-catalogs.html)
+- [SHOW COLUMNS](/sql_reference/commands/metadata/show-columns.html)
+- [SHOW ENGINES](/sql_reference/commands/metadata/show-engines.html)
+- [SHOW INDEXES](/sql_reference/commands/metadata/show-indexes.html)
+- [SHOW TABLES](/sql_reference/commands/metadata/show-tables.html)
+- [SHOW VIEWS](/sql_reference/commands/metadata/show-views.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_describe.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_describe.md
new file mode 100644
index 0000000..0bb8319
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_describe.md
@@ -0,0 +1,25 @@
+# [](#describe)DESCRIBE
+
+Lists all columns and data types for the table. Once the results are displayed, you can also export them to CSV or JSON.
+
+## [](#syntax)Syntax
+
+```
+DESCRIBE <table_name>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table_name>` The name of the table to be described.
+
+## [](#example)Example
+
+The following lists all columns and data types for the table named `players`:
+
+```
+DESCRIBE prices
+```
+
+**Returns:**
+
+table\_name column\_name data\_type nullable players agecategory TEXT 0 players email INTEGER 0 players nickname TEXT 0
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_cache.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_cache.md
new file mode 100644
index 0000000..4b6d089
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_cache.md
@@ -0,0 +1,23 @@
+# [](#show-cache)SHOW CACHE
+
+Returns the current SSD usage for the engine queried. `SHOW CACHE` returns values at the engine level, rather than by each node.
+
+## [](#syntax)Syntax
+
+```
+SHOW CACHE;
+```
+
+The results of `SHOW CACHE` are formatted as follows:
+
+`<ssd_used>/<ssd_available> GB (<percent_utilization>%)`
+
+## [](#components)Components
+
+Component Description `<ssd_used>` The amount of storage currently used on your engine. This data includes storage that Firebolt reserves for internal usage. `<ssd_available>` The amount of available storage on your engine. `<percent_utilization>` The percent of used storage as compared to available storage.
+
+## [](#example)Example
+
+When the `SHOW CACHE` command is run, the usage displays as a result:
+
+ssd\_usage 3.82/73.28 GB (5.22%)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_catalogs.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_catalogs.md
new file mode 100644
index 0000000..b812479
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_catalogs.md
@@ -0,0 +1,25 @@
+# [](#show-catalogs)SHOW CATALOGS
+
+Returns a table with a row for each catalog (i.e., database) defined in the current Firebolt account, with columns containing information as listed below.
+
+## [](#syntax)Syntax
+
+```
+SHOW CATALOGS;
+```
+
+## [](#returns)Returns
+
+The returned table has the following columns.
+
+Column name Data Type Description catalog\_name TEXT The name of the catalog. catalog\_owner TEXT Current owner of the catalog. Default owner is the user who created the catalog created TIMESTAMPTZ Time the catalog was created (UTC) last\_altered TIMESTAMPTZ The date and time that the database was last modified (UTC) last\_altered\_by TEXT User/principal who edited the catalog ddl TEXT Complete DDL of the database. description TEXT User provided description of the database
+
+## [](#example)Example
+
+The following example shows information about CATALOGS in the account:
+
+```
+SHOW CATALOGS;
+```
+
+catalog\_name catalog\_owner created last\_altered last\_altered\_by ddl description AdTechDB\_v4 firebolt-demo 2024-09-03 11:48:31.683328+00 2024-09-03 11:48:31.683328+00 firebolt-demo CREATE DATABAE AdTechDB\_v4 () WITH DESCRIPTION='DB for AdTech' DB for AdTech
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_columns.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_columns.md
new file mode 100644
index 0000000..21017d6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_columns.md
@@ -0,0 +1,23 @@
+# [](#show-columns)SHOW COLUMNS
+
+Lists columns and their properties for a specified table. Returns `<table_name>`, `<column_name>`, `<data_type>`, and `nullable` (`TRUE` if nullable, `FALSE` if not) for each column.
+
+## [](#syntax)Syntax
+
+```
+SHOW COLUMNS <table>;
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table>` The name of the table to be analyzed.
+
+## [](#example)Example
+
+The following example highlights all of the columns from the `tournaments` table:
+
+```
+SHOW COLUMNS tournaments;
+```
+
+table\_name column\_name data\_type nullable tournaments enddatetime TIMESTAMP FALSE tournaments gameid INTEGER FALSE tournaments name TEXT FALSE tournaments rulesdefinition TEXT FALSE tournaments SOURCE\_FILE\_NAME TEXT FALSE tournaments SOURCE\_FILE\_TIMESTAMP TIMESTAMP FALSE tournaments startdatetime TIMESTAMP FALSE tournaments totalprizedollars INTEGER FALSE tournaments tournamentid INTEGER FALSE
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_engines.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_engines.md
new file mode 100644
index 0000000..4cf5ff6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_engines.md
@@ -0,0 +1,17 @@
+# [](#show-engines)SHOW ENGINES
+
+Returns a table with a row for each Firebolt engine defined in the current Firebolt account, with columns containing information about each engine as listed below.
+
+## [](#syntax)Syntax
+
+```
+SHOW ENGINES;
+```
+
+## [](#returns)Returns
+
+The returned table has the following columns.
+
+Column name Data Type Description engine\_name TEXT The name of the engine. engine\_owner TEXT (5) Name of the user who created the engine. type TEXT The specification of nodes comprising the engine. clusters INT Collection of nodes, where each node is of a certain type. All the clusters in an engine have the same type and same number of nodes. nodes INT The number of nodes for each cluster in an engine. Can be an integer ranging from `1` to `128`. status TEXT The engine status. For more information, see [Viewing and understanding engine status](/Overview/engine-fundamentals.html#viewing-and-understanding-engine-status) auto\_stop INT The amount of idle time (in minutes) after which the engine automatically stops. url TEXT Engine endpoint. version TEXT The engine version. initially\_stopped BOOLEAN If `false`, engine was started as part of the `CREATE ENGINE` command. default\_database TEXT The database an engine will attempt to use by default when dealing with queries that require a database.
+
+If not specified, `NULL` is used as default. created TIMESTAMPTZ Creation time of the engine. last\_altered\_by TEXT Name of the last user who edited the engine. last\_altered TIMESTAMPTZ Last modified time of the engine. fbu\_rate INT Hourly FBU consumption rate of running engines based on engine topology at the time the view is invoked by the user.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_indexes.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_indexes.md
new file mode 100644
index 0000000..bb3b178
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_indexes.md
@@ -0,0 +1,25 @@
+# [](#show-indexes)SHOW INDEXES
+
+Returns a table with a row for each Firebolt index defined in the current database, with columns containing information about each index as listed below.
+
+## [](#syntax)Syntax
+
+```
+SHOW INDEXES;
+```
+
+## [](#returns)Returns
+
+The returned table has the following columns.
+
+Column name Data Type Description index\_name TEXT The name of the index. table\_name TEXT The name of the table associated with the index. type TEXT One of `primary` or `aggregating`. expression ARRAY (TEXT) An ordered array of the expression in SQL that defined the index. size\_compressed DOUBLE PRECISION The size of the index in bytes. size\_uncompressed DOUBLE PRECISION The uncompressed size of the index in bytes. compression\_ratio DOUBLE PRECISION The compression ratio (`<size_uncompressed>`/`<size_compressed>`). number\_of\_segments INTEGER The number of segments comprising the table.
+
+## [](#example)Example
+
+The following example returns information about indexes in the database queried:
+
+```
+SHOW INDEXES;
+```
+
+index\_name table\_name type expression size\_compressed size\_uncompressed compression\_ratio number\_of\_tablets players\_join\_idx players join \[“playerid”,”nickname”,”email”,”agecategory”] 819.98 KiB 819.98 KiB 1 0
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_tables.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_tables.md
new file mode 100644
index 0000000..a90b0f2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_tables.md
@@ -0,0 +1,25 @@
+# [](#show-tables)SHOW TABLES
+
+Returns a table with a row for each table in the current database, with columns containing information for each table as listed below.
+
+## [](#syntax)Syntax
+
+```
+SHOW TABLES;
+```
+
+## [](#returns)Returns
+
+The returned table has the following columns.
+
+Column name Data Type Description table\_name TEXT The name of the table. state TEXT The current table state. table\_type TEXT One of `FACT`, `DIMENSION`, or `EXTERNAL`. column\_count INTEGER The number of columns in the table. primary\_index TEXT An ordered array of the column names comprising the primary index definition, if applicable. schema TEXT The text of the SQL statement that created the table. number\_of\_rows INTEGER The number of rows in the table. size DOUBLE PRECISION The compressed size of the table. size\_uncompressed DOUBLE PRECISION The uncompressed size of the table. compression\_ratio DOUBLE PRECISION The compression ratio (`<size_uncompressed>`/`<size>`). number\_of\_tablets INTEGER The number of tablets comprising the table.
+
+## [](#example)Example
+
+The following example returns information about tables in the database queried:
+
+```
+SHOW TABLES;
+```
+
+table\_name state table\_type column\_count primary\_index schema number\_of\_rows size size\_uncompressed compression\_ratio number\_of\_tablets ex\_games Valid EXTERNAL 1 “CREATE EXTERNAL TABLE IF NOT EXISTS ““ex\_games”” (““src”” text NOT NULL) "”OBJECT\_PATTERN”” = ‘help\_center\_assets/firebolt\_sample\_dataset/games.json’ ““TYPE”” = (““JSON”” ““PARSE\_AS\_TEXT”” = ‘TRUE’) ““URL”” = ‘s3://firebolt-publishing-public/help\_center\_assets/firebolt\_sample\_dataset/’” 0 0.00 B 0.00 B 0 0
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_views.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_views.md
new file mode 100644
index 0000000..8dbdca0
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_metadata_show_views.md
@@ -0,0 +1,17 @@
+# [](#show-views)SHOW VIEWS
+
+Lists the views defined in the current database and the `CREATE VIEW` statement that defines each view.
+
+## [](#syntax)Syntax
+
+```
+SHOW VIEWS;
+```
+
+## [](#example)Example
+
+The following example displays the view name and view definition of a views in the database queried:
+
+**Returns**:
+
+view\_name schema v14 CREATE VIEW “v14” AS SELECT a.* FROM (SELECT 1 AS “x”) AS “a” INNER JOIN (SELECT 1 AS “x”) AS “b” USING(x) v15 CREATE VIEW IF NOT EXISTS “v15” AS SELECT * FROM “bf\_test\_t” WHERE ( “n” = 0 ) v16 CREATE VIEW “v16” AS WITH x7 AS (SELECT * FROM “oz\_x6” ) SELECT * FROM “x7”
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries.md
new file mode 100644
index 0000000..3c01ec7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries.md
@@ -0,0 +1,9 @@
+## [](#querying-and-query-optimization)Querying and query optimization
+
+* * *
+
+- [CANCEL QUERY](/sql_reference/commands/queries/cancel.html)
+- [EXPLAIN](/sql_reference/commands/queries/explain.html)
+- [RECOMMEND DDL](/sql_reference/commands/queries/recommend_ddl.html)
+- [SELECT](/sql_reference/commands/queries/select.html)
+- [SQL Pipe syntax](/sql_reference/commands/queries/pipe.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_cancel.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_cancel.md
new file mode 100644
index 0000000..a2358b8
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_cancel.md
@@ -0,0 +1,45 @@
+# [](#cancel-query)CANCEL QUERY
+
+The `CANCEL QUERY` statement is used to cancel a running query within the Firebolt engine. This statement provides a mechanism to terminate the execution of a specific query identified by its unique `query_id`. Using [query labels](/Reference/system-settings.html#query-labelingtagging) makes it easier to retrieve the query id of your query.
+
+## [](#syntax)Syntax
+
+```
+CANCEL QUERY WHERE query_id = '<query_id>';
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<query_id>` A unique identifier assigned to the query that needs to be canceled.
+
+## [](#example)Example
+
+```
+CANCEL QUERY WHERE query_id = '12345';
+```
+
+## [](#notes)Notes
+
+- The query\_id is typically obtained from the `information_schema.engine_running_queries` view.
+- When a query is canceled, it terminates the processes of that specific query. This action both frees up resources and prevents any further execution of the query.
+- This statement is designed for administrative use and may require appropriate privileges to execute. However, all users can cancel their own queries by default.
+
+## [](#example-use-case)Example Use Case
+
+Consider a scenario where there is a long-running query that needs to be canceled to free up system resources. The following statement can be used to obtain the query\_id:
+
+```
+SELECT status, duration_us, query_text, query_id FROM information_schema.engine_running_queries;
+```
+
+Suppose the long-running query is identified with query\_id ‘12345’:
+
+```
+CANCEL QUERY WHERE query_id = '12345';
+```
+
+This will initiate the cancellation process for the specified query\_id. While the query is not immediately removed from running\_queries, its status will be observed as `CANCELING` there. After the cancellation process is completed, the query will have the `CANCELED` status in the `information_schema.engine_query_history` view:
+
+```
+SELECT query_id, query_text FROM information_schema.engine_query_history WHERE status = 'CANCELED';
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_explain.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_explain.md
new file mode 100644
index 0000000..e48d0ca
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_explain.md
@@ -0,0 +1,298 @@
+# [](#explain)EXPLAIN
+
+The `EXPLAIN` feature analyzes and displays how Firebolt’s query processing system runs your query. You can use this information to understand resource utilization, and identify opportunities to improve and optimize your query performance.
+
+If you specify the `ANALYZE` option for `EXPLAIN`, Firebolt also collects detailed metrics about each operator during query runtime, including the amount of time spent on the operator, and how much data it processes.
+
+## [](#syntax)Syntax
+
+```
+EXPLAIN [( <option_name> [<option_value>] [, ...] )] <select_statement>
+```
+
+Parameter Description `option_name` The name of an option. See below for a list of all available options. `option_value` The value of the option. If no value is specified, the default is `TRUE`. `<select_statement>` Any select statement.
+
+## [](#explain-options)Explain Options
+
+You can augment the output of `EXPLAIN` by specifying options. The following table lists all available options and their functionalities:
+
+Option Name Option Values Description `LOGICAL` `TRUE`, `FALSE` Returns the optimized logical query plan by default, unless otherwise specified. `PHYSICAL` `TRUE`, `FALSE` Returns an optimized physical query plan containing shuffle operators for queries on distributed engines, showing how work is distributed between nodes of an engine. `ANALYZE` `TRUE`, `FALSE` Returns an optimized physical query plan annotated with metrics from query execution. For more information about these metrics, see [Example with ANALYZE](#example-with-analyze). `ALL` `TRUE`, `FALSE` Returns all of the previous `LOGICAL`, `PHYSICAL`, and `ANALYZE` plans. Use the following sample syntax: `EXPLAIN (ALL) <select statement>`. `STATISTICS` `TRUE`, `FALSE` Returns an annotated query plan that includes estimates from Firebolt’s query optimizer. This option works with `LOGICAL`, `PHYSICAL`, `ANALYZE`, and `ALL`. Use the following sample syntax: `EXPLAIN (STATISTICS) <select statement>`.
+
+You may specify only one of the following options: `LOGICAL`, `PHYSICAL`, `ANALYZE`, and `ALL`. If you need to view several plans at once, use the `ALL` option.
+
+## [](#example)Example
+
+The following example shows how to generate an `EXPLAIN` statement for a `SELECT` query on a table named `lineitem`.
+
+```
+EXPLAIN
+SELECT
+	l_shipdate,
+	l_linestatus,
+	l_orderkey,
+	AVG(l_discount)
+FROM
+	lineitem
+WHERE
+	l_returnflag = 'N'
+	AND l_shipdate > '1996-01-01'
+GROUP BY
+	ALL
+ORDER BY
+	1,2,3,4;
+```
+
+**Returns:**
+
+```
+[0] [Projection] lineitem.l_shipdate, lineitem.l_linestatus, lineitem.l_orderkey, avgOrNull(lineitem.l_discount)
+ \_[1] [Sort] OrderBy: [lineitem.l_shipdate Ascending Last, lineitem.l_linestatus Ascending Last, lineitem.l_orderkey Ascending Last, avgOrNull(lineitem.l_discount) Ascending Last]
+    \_[2] [Aggregate] GroupBy: [lineitem.l_orderkey, lineitem.l_linestatus, lineitem.l_shipdate] Aggregates: [avgOrNull(lineitem.l_discount)]
+       \_[3] [Projection] lineitem.l_orderkey, lineitem.l_discount, lineitem.l_linestatus, lineitem.l_shipdate
+          \_[4] [Predicate] equals(lineitem.l_returnflag, 'N'), greater(lineitem.l_shipdate, toPGDate('1996-01-01'))
+             \_[5] [StoredTable] Name: 'lineitem', used 5/16 column(s) FACT
+```
+
+The `EXPLAIN` output shows the sequence of operations that Firebolt’s engine will use to run the query:
+
+1. Read the required columns from the `lineitem` table.
+2. Filter the `lineitem` table by the `WHERE` conditions.
+3. Remove the columns that are no longer required.
+4. Perform the aggregation as specified by the `GROUP BY` clause.
+5. Sort resulting rows in ascending order by all columns from the `ORDER BY` clause.
+6. Bring the columns into the order specified in the `SELECT` clause.
+
+## [](#example-with-analyze)Example with ANALYZE
+
+The following code example runs the same query as the previous example on a multi-node engine using the `(ALL)` option, which is the same as specifying `(ALL TRUE)` or `(LOGICAL, PHYSICAL, ANALYZE)`.
+
+```
+EXPLAIN (ALL)
+SELECT
+	l_shipdate,
+	l_linestatus,
+	l_orderkey,
+	AVG(l_discount)
+FROM
+	lineitem
+WHERE
+	l_returnflag = 'N'
+	AND l_shipdate > '1996-01-01'
+GROUP BY
+	ALL
+ORDER BY
+	1,2,3,4;
+```
+
+**Returns:**
+
+Disclaimer
+
+The format of this result is subject to change.
+
+The query in the previous example returns three columns `explain_logical`, `explain_physical`, and `explain_analyze`, as shown in the following sections.
+
+Each column can be toggled on or off using the corresponding options. For example, to display only `explain_logical` and `explain_analyze`, you can specify either `(LOGICAL, ANALYZE)` or `(ALL, PHYSICAL FALSE)`. With the `ANALYZE` option enabled, this query took 4.7 seconds to run. Without the `ANALYZE` option, the query does not run and should return the result almost immediately.
+
+### [](#explain-logical-output)`EXPLAIN (LOGICAL)` output
+
+```
+[0] [Projection] ref_2, ref_1, ref_0, ref_3
+|   [RowType]: date not null, text not null, bigint not null, double precision null
+ \_[1] [Sort] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last]
+   |   [RowType]: bigint not null, text not null, date not null, double precision null
+    \_[2] [Aggregate] GroupBy: [ref_0, ref_2, ref_3] Aggregates: [avg2(ref_1)]
+      |   [RowType]: bigint not null, text not null, date not null, double precision null
+       \_[3] [Projection] ref_0, ref_1, ref_3, ref_4
+         |   [RowType]: bigint not null, double precision not null, text not null, date not null
+          \_[4] [Filter] (ref_2 = 'N'), (ref_4 > DATE '1996-01-01')
+            |   [RowType]: bigint not null, double precision not null, text not null, text not null, date not null
+             \_[5] [StoredTable] Name: "lineitem", used 5/16 column(s) FACT, ref_0: "l_orderkey" ref_1: "l_discount" ref_2: "l_returnflag" ref_3: "l_linestatus" ref_4: "l_shipdate"
+                   [RowType]: bigint not null, double precision not null, text not null, text not null, date not null
+```
+
+The `explain_logical` column shows the optimized logical query plan of the `SELECT` statement, identical to the plan in [Example](#example). Additionally, it shows the output row type for each operator. The variable `ref_2` refers to the second input column from the operator below. For operators with multiple input operators such as the `Join` operator, input columns are concatenated. For example, if the first input produces three columns, and the second input produces four columns, the first input’s columns are labeled `ref_0` to `ref_2`, while the second input’s columns are labeled `ref_3` to `ref-6`.
+
+### [](#explain-physical-output)`EXPLAIN (PHYSICAL)` output
+
+```
+[0] [MaybeCache]
+|   [RowType]: date not null, text not null, bigint not null, double precision null
+ \_[1] [Projection] ref_2, ref_1, ref_0, ref_3
+   |   [RowType]: date not null, text not null, bigint not null, double precision null
+    \_[2] [SortMerge] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last]
+      |   [RowType]: bigint not null, text not null, date not null, double precision null
+       \_[3] [Shuffle] Gather
+         |   [RowType]: bigint not null, text not null, date not null, double precision null
+         |   [Affinity]: many nodes
+          \_[4] [Sort] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last]
+            |   [RowType]: bigint not null, text not null, date not null, double precision null
+             \_[5] [AggregateMerge] GroupBy: [ref_0, ref_1, ref_2] Aggregates: [avg2merge(ref_3)]
+               |   [RowType]: bigint not null, text not null, date not null, double precision null
+                \_[6] [Shuffle] Hash by [ref_0, ref_1, ref_2]
+                  |   [RowType]: bigint not null, text not null, date not null, aggregatefunction(avg2ornull, double precision not null) not null
+                  |   [Affinity]: many nodes
+                   \_[7] [AggregateState partial] GroupBy: [ref_0, ref_2, ref_3] Aggregates: [avg2(ref_1)]
+                     |   [RowType]: bigint not null, text not null, date not null, aggregatefunction(avg2ornull, double precision not null) not null
+                      \_[8] [Projection] ref_0, ref_1, ref_3, ref_4
+                        |   [RowType]: bigint not null, double precision not null, text not null, date not null
+                         \_[9] [Filter] (ref_2 = 'N'), (ref_4 > DATE '1996-01-01')
+                           |   [RowType]: bigint not null, double precision not null, text not null, text not null, date not null
+                            \_[10] [StoredTable] Name: "lineitem", used 5/16 column(s) FACT, ref_0: "l_orderkey" ref_1: "l_discount" ref_2: "l_returnflag" ref_3: "l_linestatus" ref_4: "l_shipdate"
+                                  [RowType]: bigint not null, double precision not null, text not null, text not null, date not null
+```
+
+The `explain_physical` column displays a detailed, optimized physical plan that includes Shuffle operators for distributed query execution, offering insights into how tasks are distributed across the engine’s nodes. A `Shuffle` operator redistributes data across engine nodes. For example, scans of `FACT` tables, like operator `[9] [StoredTable]` in the previous example, and the operators following it are automatically distributed across all nodes of an engine. A `Shuffle` operator of type `Hash` indicates that the workload of the following operators is distributed across all nodes, while a `Shuffle` operator of type `Gather` consolidates data onto a single node of the engine. In the previous example, only the operator `[1] [SortMerge]` runs on a single node, merging the sorted partial query results from all other nodes.
+
+The `MaybeCache` operator, at the top of the plan, caches its input in main memory on a best-effort basis for future runs of the same (sub-) query. It considers the entire plan leading to its input, as well as the state of the scanned tables. If the data in a table changes, the `MaybeCache` operator will know not to read an outdated cached entry. It may also skip caching large results or prioritize caching results that offer greater time savings. The `MaybeCache` operator may appear in different places of a plan, but in this query it caches the full query result. For more information about the `MaybeCache` operator, see [Subresult Reuse in Firebolt](/Overview/queries/understand-query-performance-subresult.html).
+
+### [](#explain-analyze-output)`EXPLAIN (ANALYZE)` output
+
+```
+[0] [MaybeCache]
+|   [RowType]: date not null, text not null, bigint not null, double precision null
+|   [Execution Metrics]: output cardinality = 270958684, thread time = 7ms, cpu time = 4ms
+ \_[1] [Projection] ref_2, ref_1, ref_0, ref_3
+   |   [RowType]: date not null, text not null, bigint not null, double precision null
+   |   [Execution Metrics]: Optimized out
+    \_[2] [SortMerge] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last]
+      |   [RowType]: bigint not null, text not null, date not null, double precision null
+      |   [Execution Metrics]: output cardinality = 270958684, thread time = 27932ms, cpu time = 27692ms
+       \_[3] [Shuffle] Gather
+         |   [RowType]: bigint not null, text not null, date not null, double precision null
+         |   [Affinity]: many nodes
+         |   [Execution Metrics]: output cardinality = 270958684, thread time = 1846ms, cpu time = 1779ms
+          \_[4] [Sort] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last]
+            |   [RowType]: bigint not null, text not null, date not null, double precision null
+            |   [Execution Metrics]: output cardinality = 270958684, thread time = 286199ms, cpu time = 285590ms
+             \_[5] [AggregateMerge] GroupBy: [ref_0, ref_1, ref_2] Aggregates: [avg2merge(ref_3)]
+               |   [RowType]: bigint not null, text not null, date not null, double precision null
+               |   [Execution Metrics]: output cardinality = 270958684, thread time = 90694ms, cpu time = 77308ms
+                \_[6] [Shuffle] Hash by [ref_0, ref_1, ref_2]
+                  |   [RowType]: bigint not null, text not null, date not null, aggregatefunction(avg2ornull, double precision not null) not null
+                  |   [Affinity]: many nodes
+                  |   [Execution Metrics]: output cardinality = 270958691, thread time = 27649ms, cpu time = 24247ms
+                   \_[7] [AggregateState partial] GroupBy: [ref_0, ref_2, ref_3] Aggregates: [avg2(ref_1)]
+                     |   [RowType]: bigint not null, text not null, date not null, aggregatefunction(avg2ornull, double precision not null) not null
+                     |   [Execution Metrics]: output cardinality = 270958691, thread time = 191561ms, cpu time = 184761ms
+                      \_[8] [Projection] ref_0, ref_1, ref_3, ref_4
+                        |   [RowType]: bigint not null, double precision not null, text not null, date not null
+                        |   [Execution Metrics]: Optimized out
+                         \_[9] [Filter] (ref_2 = 'N'), (ref_4 > DATE '1996-01-01')
+                           |   [RowType]: bigint not null, double precision not null, text not null, text not null, date not null
+                           |   [Execution Metrics]: output cardinality = 275468571, thread time = 3578ms, cpu time = 3566ms
+                            \_[10] [StoredTable] Name: "lineitem", used 5/16 column(s) FACT, ref_0: "l_orderkey" ref_1: "l_discount" ref_2: "l_returnflag" ref_3: "l_linestatus" ref_4: "l_shipdate"
+                                  [RowType]: bigint not null, double precision not null, text not null, text not null, date not null
+                                  [Execution Metrics]: output cardinality = 334006486, thread time = 29642ms, cpu time = 29608ms
+```
+
+The `explain_analyze` column contains the same query plan as the `explain_physical` column, but annotated with metrics collected during query execution. For each operator, it shows the number of rows it produced in `output_cardinality`, and how much time was spent on that operator in `thread_time` and `cpu_time`. The `thread_time` is the sum of the wall-clock time that threads spent working on the operator across all nodes, while `cpu_time` is the total time those threads were scheduled on a CPU core. A significantly smaller `cpu_time` compared to `thread_time` suggests that the operator is either waiting on input or output operations or that the engine is handling multiple queries simultaneously.
+
+#### [](#analyzing-the-metrics)Analyzing the Metrics
+
+In the previous example, the `cpu_time` is almost as high as the `thread_time` on the `StoredTable` node. This indicates that the data of the `lineitem` table was in the SSD cache. On a cold query run, where data must be retrieved from an Amazon S3 bucket, `thread_time` is considerably higher than `cpu_time` for the same operator:
+
+```
+[10] [StoredTable] Name: "lineitem", used 5/16 column(s) FACT, ref_0: "l_orderkey" ref_1: "l_discount" ref_2: "l_returnflag" ref_3: "l_linestatus" ref_4: "l_shipdate"
+    [RowType]: bigint not null, double precision not null, text not null, text not null, date not null
+    [Execution Metrics]: output cardinality = 334006486, thread time = 29642ms, cpu time = 29608ms
+```
+
+Additionally, a significant amount of time is devoted to sorting the query results:
+
+```
+[2] [SortMerge] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last]
+|   [RowType]: bigint not null, text not null, date not null, double precision null
+|   [Execution Metrics]: output cardinality = 270958684, thread time = 27932ms, cpu time = 27692ms
+ \_[3] [Shuffle] Gather
+   |   [RowType]: bigint not null, text not null, date not null, double precision null
+   |   [Affinity]: many nodes
+   |   [Execution Metrics]: output cardinality = 270958684, thread time = 1846ms, cpu time = 1779ms
+    \_[4] [Sort] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last]
+      |   [RowType]: bigint not null, text not null, date not null, double precision null
+      |   [Execution Metrics]: output cardinality = 270958684, thread time = 286199ms, cpu time = 285590ms
+```
+
+Removing the `ORDER BY` can considerably speed up query runtimes. In this case, the total query time is nearly halved, dropping from 1 minute and 19 seconds to 47.3 seconds. If only the initial results in the specified sorting order are needed, introducing a `LIMIT` operator can further enhance performance. Adding `LIMIT 10000` to the query produces the following output:
+
+```
+[2] [SortMerge] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last] Limit: [10000]
+|   [RowType]: bigint not null, text not null, date not null, double precision null
+|   [Execution Metrics]: output cardinality = 10000, thread time = 1ms, cpu time = 1ms
+ \_[3] [Shuffle] Gather
+   |   [RowType]: bigint not null, text not null, date not null, double precision null
+   |   [Affinity]: many nodes
+   |   [Execution Metrics]: output cardinality = 20000, thread time = 0ms, cpu time = 0ms
+    \_[4] [Sort] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last] Limit: [10000]
+      |   [RowType]: bigint not null, text not null, date not null, double precision null
+      |   [Execution Metrics]: output cardinality = 20000, thread time = 6403ms, cpu time = 6372ms
+       \_[5] [AggregateMerge] GroupBy: [ref_0, ref_1, ref_2] Aggregates: [avg2merge(ref_3)]
+         |   [RowType]: bigint not null, text not null, date not null, double precision null
+         |   [Execution Metrics]: output cardinality = 270958684, thread time = 83213ms, cpu time = 74525ms
+```
+
+The time spent in the `Sort` operator is significantly reduced, nearly by an order of magnitude. The `Sort` operator takes the `LIMIT` clause directly into account and emits only the required minimum number of rows. This reduces the overall query time from 1 minute and 19 seconds to 40.3 seconds, which is an even greater improvement than removing the `ORDER BY` clause, as less result data needs to be serialized for client return.
+
+A secondary benefit is that the result is now small enough to be cached by the `MaybeCache` operator. Running the query with `LIMIT 10000` again produces the following output:
+
+```
+[0] [MaybeCache]
+|   [RowType]: date not null, text not null, bigint not null, double precision null
+|   [Execution Metrics]: output cardinality = 10000, thread time = 0ms, cpu time = 0ms
+ \_[1] [Projection] ref_2, ref_1, ref_0, ref_3
+   |   [RowType]: date not null, text not null, bigint not null, double precision null
+   |   [Execution Metrics]: Optimized out
+    \_[2] [SortMerge] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last] Limit: [10000]
+      |   [RowType]: bigint not null, text not null, date not null, double precision null
+      |   [Execution Metrics]: Nothing was executed
+```
+
+## [](#example-with-statistics)Example with STATISTICS
+
+The following code example uses the `STATISTICS` option to display the logical and physical query plan for the `SELECT` statement, annotated with estimated statistics from Firebolt’s query optimizer:
+
+```
+EXPLAIN (STATISTICS)
+SELECT
+	l_shipdate,
+	l_linestatus,
+	l_orderkey,
+	AVG(l_discount)
+FROM
+	lineitem
+WHERE
+	l_returnflag = 'N'
+	AND l_shipdate > '1996-01-01'
+GROUP BY
+	ALL
+ORDER BY
+	1,2,3,4;
+```
+
+In the following output, each plan node includes a `[Logical Profile]`, which specifies the `source` of the estimation for that node, along with estimated row counts and, if available, distinct column counts:
+
+```
+explain TEXT
+[0] [Projection] ref_2, ref_1, ref_0, ref_3
+|   [RowType]: date null, text null, bigint null, numeric(38, 9) null
+|   [Logical Profile]: [est. #rows=6676, column profiles={}, source: estimated]
+ \_[1] [Sort] OrderBy: [ref_2 Ascending Last, ref_1 Ascending Last, ref_0 Ascending Last, ref_3 Ascending Last]
+   |   [RowType]: bigint null, text null, date null, numeric(38, 9) null
+   |   [Logical Profile]: [est. #rows=6676, column profiles={}, source: estimated]
+    \_[2] [Aggregate] GroupBy: [ref_0, ref_2, ref_3] Aggregates: [avg2(ref_1)]
+      |   [RowType]: bigint null, text null, date null, numeric(38, 9) null
+      |   [Logical Profile]: [est. #rows=6676, column profiles={[ref_3: #distinct=6676]}, source: estimated]
+       \_[3] [Projection] ref_0, ref_1, ref_3, ref_4
+         |   [RowType]: bigint null, numeric(38, 9) null, text null, date null
+         |   [Logical Profile]: [est. #rows=23489, column profiles={}, source: estimated]
+          \_[4] [Filter] (ref_2 = 'N'), (ref_4 > DATE '1996-01-01')
+            |   [RowType]: bigint null, numeric(38, 9) null, text null, text null, date null
+            |   [Logical Profile]: [est. #rows=23489, column profiles={[ref_2: #distinct=1]}, source: estimated]
+             \_[5] [StoredTable] Name: "lineitem", used 5/16 column(s) FACT, ref_0: "l_orderkey" ref_1: "l_discount" ref_2: "l_returnflag" ref_3: "l_linestatus" ref_4: "l_shipdate"
+                   [RowType]: bigint null, numeric(38, 9) null, text null, text null, date null
+                   [Logical Profile]: [est. #rows=6.59431e+08, column profiles={}, source: metadata]
+```
+
+The possible sources are as follows:
+
+**Source** **Description** `hardcoded` This node received hard-coded defaults because no additional information is available, a scenario that typically occurs only with external tables. `estimated` This node’s profile was computed from its child nodes’ profiles, based on assumptions about the data that may not always hold true. These assumptions can introduce inaccuracies, which may be further amplified. `metadata` This node’s profile was constructed from available metadata, ensuring that the information is either precise or highly accurate. `history` This node’s profile was obtained from a previously recorded run, and is accurate unless data has changed since the recording. `learned` This node’s profile was predicted using machine learning.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_pipe.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_pipe.md
new file mode 100644
index 0000000..a020d77
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_pipe.md
@@ -0,0 +1,240 @@
+# [](#sql-pipe-syntax)SQL Pipe syntax
+
+Firebolt supports SQL Pipe syntax, an alternative SQL syntax that uses the `|>` operator to chain query transformations step by step. SQL Pipe syntax supports the same functionality as standard SQL, but can improve readability by allowing queries to flow in a linear, top-to-bottom structure, which makes it easier to express, compose and understand queries. This syntax was first presented by Google in the research paper [SQL Has Problems. We Can Fix Them: Pipe Syntax In SQL](https://research.google/pubs/sql-has-problems-we-can-fix-them-pipe-syntax-in-sql/).
+
+SQL Pipe syntax has the following structure:
+
+- Each pipe operator consists of the pipe symbol, `|>`, an operator name, and arguments: `|> operator_name arguments`.
+- You can add pipe operators to the end of any valid query.
+- You can apply pipe operators in any order, and apply them as many times as needed.
+- Pipe syntax can be used anywhere that standard syntax is used including in queries, subqueries, and views.
+- You can combine pipe syntax with standard SQL syntax in the same query. For example, a parent query can use standard SQL while the subquery uses pipe syntax, or the other way around.
+
+For more information, see Google’s original research paper, [SQL Has Problems. We Can Fix Them: Pipe Syntax In SQL](https://research.google/pubs/sql-has-problems-we-can-fix-them-pipe-syntax-in-sql/).
+
+### [](#example)Example
+
+The following code example is taken from [Query 13 in the TPC-H benchmark suite](https://github.com/apache/impala/blob/master/testdata/workloads/tpch/queries/tpch-q13.test), a standard set of queries used to measure database performance. Query 13 specifically analyzes customer order patterns to identify how many customers fall into different order-count categories. In **standard SQL**, the following query counts how many customers have placed a certain number of orders, excluding special requests, and sorts the results by customer count and order count:
+
+```
+SELECT c_count, COUNT(*) AS custdist
+  FROM
+  (SELECT c_custkey, COUNT(o_orderkey) c_count
+    FROM customer
+    LEFT OUTER JOIN orders ON c_custkey = o_custkey
+                           AND o_comment NOT LIKE '%special%requests%'
+   GROUP BY c_custkey
+) AS c_orders
+GROUP BY c_count
+ORDER BY custdist DESC, c_count DESC;
+```
+
+The following query shows the previous query rewritten using pipe syntax:
+
+```
+FROM customer
+|> LEFT OUTER JOIN orders ON c_custkey = o_custkey
+|> WHERE o_comment NOT LIKE '%special%requests%'
+|> AGGREGATE COUNT(o_orderkey) AS c_count  GROUP BY c_custkey
+|> AGGREGATE COUNT(*)          AS custdist GROUP BY c_count
+|> ORDER BY custdist DESC, c_count DESC;
+```
+
+## [](#from-first)`FROM` first
+
+Firebolt supports [`FROM` first queries](/sql_reference/commands/queries/select.html#from-first), which are especially useful with pipe syntax, which builds queries in a step-by-step flow, with each step transforming the result of the previous one. Starting with the `FROM` clause defines the initial data source, allowing you to clearly chain joins, filters, and transformations. A pipe query typically starts with a `FROM` clause that references a table, view, subquery, join, or table-valued function.
+
+### [](#examples)Examples
+
+**Example**
+
+The following code example selects all data from the `levels` table:
+
+```
+FROM levels
+```
+
+**Example**
+
+The following code example generates a series of numbers from 1 to 5:
+
+```
+FROM generate_series(1,5);
+```
+
+## [](#pipe-operators)Pipe operators
+
+- [SELECT](#select-pipe-operator)
+- [EXTEND](#extend-pipe-operator)
+- [AS](#as-pipe-operator)
+- [WHERE](#where-pipe-operator)
+- [LIMIT](#limit-pipe-operator)
+- [AGGREGATE](#aggregate-pipe-operator)
+- [ORDER BY](#order-by-pipe-operator)
+- [JOIN](#join-pipe-operator)
+
+### [](#select-pipe-operator)`SELECT` pipe operator
+
+The `SELECT` pipe operator works similarly to the standard SQL `SELECT` statement, and is used to specify the columns or expressions you want in the result, including column references, scalar expressions, `*` wildcards, and clauses like `DISTINCT` or `EXCLUDE`. The `SELECT` pipe operator enables flexible data selection within the pipe query flow.
+
+#### [](#syntax)Syntax
+
+```
+|> SELECT [ ALL | DISTINCT ] <select_list>
+```
+
+The `<select_list>` in the `SELECT` pipe operator follows the same syntax as the [`SELECT` statement](/sql_reference/commands/queries/select.html#select-1) in standard SQL. Specifically, it can contain components including column references, scalar expressions, `*` wildcards, and the `EXCLUDE` clause.
+
+**Example**
+
+The following code example selects the `level`, `name`, `maxpoints`, and `pointsperlap` columns from the `levels` table and computes the number of laps by dividing `maxpoints` by `pointsperlap`:
+
+```
+FROM levels
+|> SELECT level, name, maxpoints, pointsperlap, maxpoints / pointsperlap AS number_of_laps
+```
+
+### [](#extend-pipe-operator)`EXTEND` pipe operator
+
+The `EXTEND` pipe operator adds new computed columns to query results while keeping the existing columns so that you can perform calculations or transformations on your data without losing any original columns. This is useful when you want to enrich your results with additional insights.
+
+#### [](#syntax-1)Syntax
+
+```
+|> EXTEND <expression> [AS <alias>] [, ...]
+```
+
+The `EXTEND` operator propagates all the columns from the input and adds computed columns, similar to the `SELECT *, <expression> [AS <alias>]` syntax in standard SQL. These computed columns can include scalar expressions or window functions defined using the format `|> EXTEND <expression> [AS <alias>] [, ...]`.
+
+**Example**
+
+The following code example adds two computed columns to the `levels` table: `number_of_laps`, calculated by dividing `maxpoint`s by `pointsperlap`, and `total_max_points`, which is the cumulative sum of `maxpoints` ordered by `level`:
+
+```
+FROM levels
+|> EXTEND 
+     maxpoints / pointsperlap AS number_of_laps,
+     SUM(maxpoints) OVER (ORDER BY level ASC) AS total_max_points
+```
+
+### [](#as-pipe-operator)`AS` pipe operator
+
+The `AS` pipe operator is used to rename tables or columns within a query, similar to the `AS` keyword in standard SQL. You can use it to assign aliases to tables or columns, and make your query more readable and simplify complex operations. The `AS` pipe operator can help clarify the intent of your query by giving meaningful names to columns or tables, improving its structure and understanding within the pipe query flow.
+
+#### [](#syntax-2)Syntax
+
+```
+|> AS <table_alias> | <table_alias>(<column1_alias>, ...)
+```
+
+**Example**
+
+The following code example generates a series of numbers from 1 to 5, aliases the result as `table(i)`, and selects the `i` column from the aliased table:
+
+```
+FROM generate_series(1,5)
+|> AS table(i)
+|> SELECT table.i
+```
+
+### [](#where-pipe-operator)`WHERE` pipe operator
+
+The `WHERE` pipe operator filters the input data based on a specified condition, similar to the [WHERE](/sql_reference/commands/queries/select.html#where) clause in standard SQL, and also replaces the `HAVING` clause in pipe syntax, allowing you to exclude rows that don’t meet the criteria.
+
+#### [](#syntax-3)Syntax
+
+```
+|> WHERE <condition>
+```
+
+**Example**
+
+The following code example filters the `levels` table to include only rows where the `leveltype` is `FastestLap`:
+
+```
+FROM levels
+|> WHERE leveltype = 'FastestLap'
+```
+
+### [](#limit-pipe-operator)`LIMIT` pipe operator
+
+The `LIMIT` pipe operator restricts the number of rows in the result set, similar to the [LIMIT clause](/sql_reference/commands/queries/select.html#limit) in standard SQL, and can optionally use `OFFSET` to skip a specified number of rows, useful for limiting large result sets, pagination, or testing smaller data subsets.
+
+#### [](#syntax-4)Syntax
+
+```
+|> LIMIT <count> [OFFSET <start>]
+```
+
+**Example**
+
+The following code example generates a series of numbers from 1 to 1000 and limits the result to the first 3 rows:
+
+```
+FROM generate_series(1,1000)
+|> LIMIT 3
+```
+
+### [](#aggregate-pipe-operator)`AGGREGATE` pipe operator
+
+You can use the `AGGREGATE` pipe operator to perform either **full table aggregation** or **aggregation across groups**, similar to using the [`GROUP BY`](/sql_reference/commands/queries/select.html#group-by) clause in standard SQL. Use this operator to apply aggregate functions like `SUM`, `AVG`, or `COUNT` to grouped data.
+
+Unlike SQL, where grouping expressions need to be repeated in both the `SELECT` and `GROUP BY` clauses, in pipe syntax, grouping expressions are listed only once in the `GROUP BY` clause and are automatically included in the output columns. The `AGGREGATE` operator’s output first includes the grouping expressions, followed by the aggregated expressions, using their assigned aliases as column names.
+
+#### [](#syntax-for-full-table-aggregation)Syntax for full table aggregation
+
+```
+|> AGGREGATE <aggregate_expression> [AS <alias>] [, ...]
+```
+
+#### [](#syntax-for-aggregation-with-grouping)Syntax for aggregation with grouping
+
+```
+|> AGGREGATE [<aggregate_expression> [AS <alias>] [, ...]] GROUP BY <grouping_expression> [, ...]
+```
+
+**Examples**
+
+The following code example calculates the total sum of `maxpoints` from the `levels` table without grouping:
+
+```
+FROM levels
+|> AGGREGATE SUM(maxpoints)
+```
+
+The following code example calculates the maximum `maxpoints` for each `leveltype` and returns the corresponding `level` for each maximum value, grouping the results by `leveltype`:
+
+```
+FROM levels
+|> AGGREGATE MAX_BY(level, maxpoints) level, MAX(maxpoints) maxpoints GROUP BY leveltype
+```
+
+### [](#order-by-pipe-operator)`ORDER BY` pipe operator
+
+Use the `ORDER BY` pipe operator to sort the input data based on one or more expressions, similar to the [`ORDER BY`](/sql_reference/commands/queries/select.html#order-by) clause in standard SQL to organize query results in a meaningful order. You can use `ORDER BY` to specify the sorting order with options for ascending (`ASC`) or descending (`DESC`) order, as well as the handling of `NULL` values with `NULLS FIRST` or `NULLS LAST`.
+
+#### [](#syntax-5)Syntax
+
+```
+|> ORDER BY <expression> [ ASC | DESC ] [ NULLS FIRST | NULLS LAST] [, ...]
+```
+
+**Example**
+
+The following code example sorts the `levels` table by `numberoflaps` in descending order and then selects the `level` and `numberoflaps` columns from the sorted result:
+
+```
+FROM levels
+|> ORDER BY numberoflaps DESC
+|> SELECT level, numberoflaps
+```
+
+### [](#join-pipe-operator)`JOIN` pipe operator
+
+Use the `JOIN` pipe operator to combine rows from two or more tables based on a related column and merge datasets in a query similar to the standard SQL [`JOIN`](/sql_reference/commands/queries/select.html#join) clause. You can perform different types of joins, such as `INNER`, `LEFT`, `RIGHT`, and `FULL`, to retrieve and merge data based on specific conditions.
+
+#### [](#syntax-6)Syntax
+
+```
+|> [ INNER | LEFT | RIGHT | FULL ] JOIN <join_table> ON <join_condition>
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_recommend_ddl.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_recommend_ddl.md
new file mode 100644
index 0000000..24fd63a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_recommend_ddl.md
@@ -0,0 +1,66 @@
+# [](#recommend-ddl)RECOMMEND DDL
+
+`CALL recommend_ddl` can help you optimize schema configurations to enhance query performance by early data pruning. The statement finds [primary indexes](/Overview/indexes/primary-index.html) (PIs) and [partition](/Overview/indexes/using-indexes.html#partitions-in-tables) recommendations for the specified table tailored to the given workload.
+
+## [](#syntax)Syntax
+
+```
+CALL recommend_ddl(<table_name>, (<select_statement>))
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<table_name>` The name of the table for which primary indexes and partition keys should be recommended. `<select_statement>` [SELECT](/sql_reference/commands/queries/select.html) statement that returns the workload that the DDL recommendation is based on. The `<select_statement>` must return exactly one column of type `TEXT`.
+
+## [](#example)Example
+
+The example below demonstrates retrieving schema recommendation using the `CALL recommend_ddl` statement for a table named `lineitem` tailored to the workload in the query history of the past week.
+
+```
+CALL recommend_ddl(lineitem, (SELECT query_text FROM information_schema.engine_query_history WHERE start_time > NOW() - INTERVAL '1 week'))
+```
+
+The `<select_statement>` returns exactly one column of type `TEXT` containing the SQL statements that the `CALL recommend_ddl` command should analyze.
+
+**Returns:**
+
+recommended\_partition\_key recommended\_primary\_index average\_pruning\_improvement analyzed\_queries DATE\_TRUNC(‘month’, l\_orderdate) l\_shipmode, l\_returnflag, l\_shipinstruct 0.42 393
+
+The `CALL recommend_ddl` results indicate that the amount of bytes scanned can be decreased by up to 42% by configuring `PRIMARY INDEX l_shipmode, l_returnflag, l_shipinstruct` and `PARTITION BY DATE_TRUNC('month', l_orderdate)`. The statement analyzed 393 queries that scanned the `lineitem` table and applied filters to any of the `lineitem` columns.
+
+## [](#quick-setup)Quick Setup
+
+The following steps will guide you to achieve great query performance within the first few minutes after joining Firebolt. First, create a table without any primary index and parition key configurations.
+
+```
+CREATE TABLE <table_name>(
+    ...
+);
+```
+
+Next, load a workload that you want to run on this table from S3 into Firebolt utilizing [COPY INTO]().
+
+```
+COPY INTO workload_table FROM 's3://bucket/workload/' with ... 
+```
+
+Now you can use the `CALL recommend_ddl` command to find primary index and parition key configurations.
+
+```
+CALL recommend_ddl(<table_name>, (select * from workload_table));
+```
+
+Finally, recreate the table with the recommended primary index and parition key configurations and ingest the data into this table.
+
+```
+DROP TABLE <table_name>;
+CREATE TABLE <table_name>(
+    ...
+)
+PRIMARY INDEX ...
+PARTITION BY ..;
+```
+
+## [](#under-the-hood)Under The Hood
+
+Primary index and partition key configurations are chosen to maximize pruning potential and thus reduce query runtime time. Columns with selective filters and low cardinality are suggested as primary index and partition key columns. Recommendations can be run on empty tables as well as on tables with production data. The more queries executed on a populated table, the better the recommendations become. If additionally the workload of a table changes over time, it can be beneficial to run the `CALL recommend_ddl` command periodically to check for better table configurations.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_select.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_select.md
new file mode 100644
index 0000000..b41ec75
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_commands_queries_select.md
@@ -0,0 +1,623 @@
+# [](#select)SELECT
+
+Retrieves specific data from one or more tables in a database based on certain criteria. If you run multiple `SELECT` queries in a single script, you must them with a semicolon (`;`). Firebolt also supports `CREATE TABLE...AS SELECT` (CTAS). For more information, see [CREATE TABLE…AS SELECT](/sql_reference/commands/data-definition/create-fact-dimension-table-as-select.html).
+
+- [Syntax](#syntax)
+- [SELECT](#select-1)
+  
+  - [SELECT expression](#select-expression)
+    
+    - [Example](#example)
+  - [SELECT wildcard](#select-wildcard)
+  - [SELECT DISTINCT](#select-distinct)
+  - [SELECT ALL](#select-all)
+- [WITH](#with)
+- [FROM](#from)
+  
+  - [`FROM` first](#from-first)
+- [JOIN](#join)
+- [UNNEST](#unnest)
+- [WHERE](#where)
+- [GROUP BY](#group-by)
+  
+  - [GROUP BY ALL](#group-by-all)
+- [HAVING](#having)
+- [UNION \[ALL\]](#union-all)
+- [ORDER BY](#order-by)
+- [LIMIT](#limit)
+- [OFFSET](#offset)
+
+## [](#syntax)Syntax
+
+```
+[ WITH <with_query> [, ...n] ]
+SELECT [ ALL | DISTINCT ] {<select_expr> [, ...]}
+    [ FROM <from_item> [, ...] ]
+    [ WHERE <condition> ]
+    [ GROUP BY [ <grouping_element> [, ...] | ALL ] ]
+    [ HAVING <condition> [, ...] ]
+    [ UNION [ ALL ] <select_expr> [ ...n]
+    [ ORDER BY <expression> [ ASC | DESC ] [ NULLS FIRST | NULLS LAST] [, ...] ]
+    [ LIMIT <count> ]
+    [ OFFSET <start> ]
+```
+
+## [](#select-1)SELECT
+
+```
+SELECT [ ALL | DISTINCT ] {<select_expression> [, ...]}
+```
+
+The `SELECT` list defines the columns that it returns. Each `<select_expression>` in the `SELECT` list can be either an individual expression or a wildcard.
+
+You cannot select **only** [partitioned](/Overview/indexes/using-indexes.html#partitions-in-tables) or [virtual columns](/Guides/loading-data/working-with-external-tables.html#using-metadata-virtual-columns). Selecting both partitioned or virtual columns together with regular columns is supported, but selecting only partitioned or virtual columns is not.
+
+### [](#select-expression)SELECT expression
+
+```
+<expression> [ AS <alias> ]
+```
+
+Expressions in the `SELECT` list return a single value and generate one output column. You can define the column name using an explicit alias with the `AS` clause, or, for expressions without explicit alias, the output column name is automatically generated. Expressions can reference any column from the `FROM` clause, but cannot reference other columns produced by the same `SELECT` list. The expressions can use scalar functions, aggregate functions, window functions or subqueries, as long as they return a single value.
+
+#### [](#example)Example
+
+The following code retrieves the `currentscore`, `currentspeed`, and the product of `currentlevel` and `playterid` as `score_information from the`playstats\` table:
+
+```
+SELECT currentscore, currentspeed, currentlevel * playterid AS score_information FROM playstats
+```
+
+### [](#select-wildcard)SELECT wildcard
+
+```
+[ <table_name>. ] * [ EXCLUDE { <column_name> | ( <column_name>, ... ) } ]
+```
+
+Wildcards are expanded into multiple output columns based on the following rules:
+
+- The wildcard symbol (`*`) expands to include all columns in the `FROM` clause.
+- `<table_name>.*` expands to include all columns specified in the `FROM` clause for the table named `<table_name>`
+- `EXCLUDE` defines columns which are removed from the previous expansion.
+
+### [](#select-distinct)SELECT DISTINCT
+
+The `SELECT DISTINCT` statement removes duplicate rows.
+
+### [](#select-all)SELECT ALL
+
+The `SELECT ALL` statement returns all rows. `SELECT ALL` is the default behavior.
+
+## [](#with)WITH
+
+The `WITH` clause refactors subqueries so that you can define them once and reference them within the main query. This simplifies the hierarchy of the main query, enabling you to avoid using multiple nested sub-queries.
+
+In order to reference the data from the `WITH` clause, a name must be specified for it. This name is then treated as a temporary relation table during query execution.
+
+The primary query and the queries included in the `WITH` clause are all run at the same time; `WITH` queries are evaluated only once every time the main query runs, even if the clause is referred to by the main query more than once.
+
+### [](#materialized-common-table-expressions)Materialized common table expressions
+
+The query hint `MATERIALIZED` or `NOT MATERIALIZED` controls whether common table expressions (CTEs) produce an internal results table that is cached in engine RAM (`MATERIALIZED`) or calculated each time the sub-query runs. `NOT MATERIALIZED` is the default. `MATERIALIZED` must be specified explicitly.
+
+Materialized results can be accessed more quickly in some circumstances. By using the proper materialization hint, you can control when a CTE gets materialized and improve query performance. We recommend the `MATERIALIZED` hint to improve query performance in the following circumstances:
+
+- The CTE is reused at the main query level more than once.
+- The CTE is computationally expensive, producing a relatively small number of rows.
+- The CTE calculation is independent of the main query, and no external optimizations from the main table are needed for it to be fast.
+- The materialized CTE fits into the nodes’ RAM.
+
+### [](#syntax-1)Syntax
+
+```
+WITH <subquery_table_name> AS [ MATERIALIZED| NOT MATERIALIZED ] <subquery>
+```
+
+Component Description `<subquery_table_name>` A unique name for a temporary table. `<subquery>` Any query statement.
+
+### [](#example-1)Example
+
+The following example retrieves all players who have subscribed to receive the game newsletter, having the results of the `WITH` query in the temporary table `nl_subscribers`.
+
+The results of the main query then list the `nickname` and `email` for those customers, sorted by nickname.
+
+```
+WITH nl_subscribers AS (
+	SELECT
+		*
+	FROM
+		players
+	WHERE
+		issubscribedtonewsletter=TRUE
+)
+SELECT
+	nickname,
+	email
+FROM
+	nl_subscribers
+ORDER BY
+	nickname
+```
+
+## [](#from)FROM
+
+Use the `FROM` clause to list the tables and any relevant join information and functions necessary for running the query.
+
+### [](#syntax-2)Syntax
+
+```
+FROM <from_item> [, ...n]
+```
+
+Component Description `<from_item>` Indicates the table or tables from which the data is to be retrieved.
+
+### [](#example-2)Example
+
+In the following example, the query retrieves all entries from the `players` table for which the `agecategory` value is “56+”.
+
+```
+SELECT
+	*
+FROM
+	players
+WHERE
+	agecategory='56+'
+```
+
+### [](#from-first)`FROM` first
+
+Firebolt allows using the `FROM` clause before the `SELECT` clause. The previous example can also be written as follows:
+
+```
+FROM players
+SELECT *
+WHERE agecategory='56+'
+```
+
+You can also omit the `SELECT` clause and use only the `FROM` clause in the query as shown in the following code example:
+
+```
+FROM players
+```
+
+The previous code example is equivalent to the following:
+
+```
+FROM players SELECT *
+```
+
+## [](#join)JOIN
+
+A `JOIN` operation combines rows from two data sources, such as tables or views, and creates a new table of combined rows that can be used in a query.
+
+`JOIN` operations can be used with an `ON` clause for conditional logic or a `USING` clause to specify columns to match.
+
+### [](#join-with-on-clause-syntax)JOIN with ON clause syntax
+
+```
+FROM <join_table1> [ INNER | LEFT | RIGHT | FULL ] JOIN <join_table2> ON <join_condition>
+```
+
+Parameters Description `<join_table1>` A table or view to be used in the join operation. `<join_table2>` A second table or view to be used in the join operation. `ON <join_condition>` One or more `BOOLEAN` comparison expressions that specify the logic to join two specified tables and which columns to compare. For example: `ON join_table1.column = join_table2.column`.
+
+### [](#join-with-using-clause-syntax)JOIN with USING clause syntax
+
+```
+FROM <join_table1> [ INNER | LEFT | RIGHT | FULL ] JOIN <join_table2> USING (column_list)
+```
+
+Component Description `<join_table1>` A table or view to be used in the join operation. `<join_table2>` A second table or view to be used in the join operation. `USING (column_list)` A list of one or more columns to compare for exact matching. `USING` is a shortcut to join tables that share the same column names. The specified columns are joined via a basic match condition. The match condition of `USING (column_list)` is equivalent to `ON join_table1.column = join_table2.column`
+
+### [](#join-types)JOIN types
+
+The type of `JOIN` operation specifies which rows are included between two specified tables. If unspecified, `JOIN` defaults to `INNER JOIN`.
+
+`JOIN` types include:
+
+`[INNER] JOIN` When used with an `ON` clause, `INNER JOIN` includes only rows that satisfy the `<join_condition>`. When used with a `USING` clause, `INNER JOIN` includes rows only if they have matching values for the specified columns in the `column_list`. `LEFT [OUTER] JOIN` Includes all rows from `<join_table1>` but excludes any rows from `<join_table2>` that don’t satisfy the `<join_condition>`. `LEFT JOIN` is equivalent to `LEFT OUTER JOIN`. `RIGHT [OUTER] JOIN` Includes all rows from `<join_table2>` but excludes any rows from `<join_table1>` that don’t satisfy the `<join_condition>`. `RIGHT JOIN` is equivalent to `RIGHT OUTER JOIN`. `FULL [OUTER] JOIN` Includes all rows from both tables matched where appropriate with the `<join_condition>`. `FULL JOIN` is equivalent to `FULL OUTER JOIN`. `CROSS JOIN` Includes every possible combination of rows from `<join_table1>` and `<join_table2>`. A `CROSS JOIN` does not use an `ON` or `USING` clause.
+
+### [](#examples)Examples
+
+The following `JOIN` examples use two tables, `level_one_players` and `level_two_players`. These tables are created and populated with data as follows.
+
+```
+CREATE DIMENSION TABLE level_one_players (
+    nickname TEXT,
+    currentscore INTEGER);
+
+INSERT INTO num_test VALUES
+    ('kennethpark', 11),
+    ('rileyjon', 50),
+    ('sabrina21', 90),
+    ('steven70', 50)
+
+CREATE DIMENSION TABLE level_two_players (
+    nickname TEXT,
+    currentscore INTEGER);
+
+INSERT INTO num_test2 VALUES
+    ('aaronbutler', 90),
+    ('esimpson', 56),
+    ('ruthgill', 85),
+    ('adrianachoi', 50)
+
+```
+
+The tables and their data are shown as follows:
+
+level\_one\_players.nickname level\_one\_players.currentscore level\_two\_players.nickname level\_two\_players.currentscore kennethpark 11 aaronbutler 90 rileyjon 50 esimpson 56 sabrina21 90 ruthgill 85 steven70 50 adrianachoi 50
+
+#### [](#inner-join-example)INNER JOIN example
+
+The `INNER JOIN` example below includes only the rows where the `nickname` and `currenscore` values match.
+
+```
+SELECT
+    *
+FROM
+    level_one_players
+INNER JOIN
+    level_two_players
+    USING (
+        nickname,
+        currentscore
+	);
+```
+
+The previous query is equivalent to the following:
+
+```
+SELECT
+    *
+FROM
+    level_one_players
+INNER JOIN
+    level_two_players
+        ON level_one_players.nickname = level_two_players.nickname
+        AND level_one_players.currentscore = level_two_players.score;
+```
+
+**Returns**
+
+level\_one\_players.nickname level\_one\_players.currentscore level\_two\_players.nickname level\_two\_players.currentscore lauradavis 90 lauradavis 90 hamiltonjorge 50 hamiltonjorge 50 adrian26 50 adrian26 50 leahbyrd 90 leahbyrd 90 rachelortiz 87 rachelortiz 87
+
+#### [](#left-outer-join-example)LEFT OUTER JOIN example
+
+The following `LEFT OUTER JOIN` example includes all `nickname` values from the `level_one_players` table. Any rows with no matching value in the `level_two_players` table return `NULL`.
+
+```
+SELECT
+    level_one_players.nickname,
+    level_two_players.nickname
+FROM level_one_players
+LEFT OUTER JOIN
+    level_two_players
+    USING (nickname);
+```
+
+**Returns**
+
+level\_one\_players.nickname level\_two\_players.nickname kennethpark kennethpark rileyjon rileyjon sabrina21 NULL steven70 steven70
+
+#### [](#right-outer-join-example)RIGHT OUTER JOIN example
+
+The following `RIGHT OUTER JOIN` example includes all `nickname` values from `level_two_players`. Any rows with no matching values in the `level_one_players` table return `NULL`.
+
+```
+SELECT
+    level_one_players.nickname,
+    level_two_players.nickname
+FROM
+    level_one_players
+RIGHT OUTER JOIN
+    level_two_players
+    USING (nickname);
+```
+
+**Returns**
+
+level\_one\_players.nickname level\_two\_players.nickname kennethpark kennethpark sabrina21 sabrina21 rileyjon rileyjon steven70 steven70 NULL aaronbutler NULL ruthgill NULL adrianachoi
+
+#### [](#full-outer-join-example)FULL OUTER JOIN example
+
+The following `FULL OUTER JOIN` example includes all values from `num_test` and `num_test2`. Any rows with no matching values return `NULL`.
+
+```
+SELECT
+    level_one_players.nickname,
+    level_two_players.nickname
+FROM
+    level_one_players
+FULL OUTER JOIN
+    level_two_players
+    USING (nickname);
+```
+
+**Returns**
+
+level\_one\_players.nickname level\_two\_players.nickname kennethpark kennethpark sabrina21 sabrina21 rileyjon rileyjon steven70 steven70 NULL aaronbutler NULL ruthgill NULL adrianachoi
+
+#### [](#cross-join-example)CROSS JOIN example
+
+A `CROSS JOIN` produces a table with every combination of row values in the specified columns.
+
+The following example uses two tables with player information, `beginner_player` and `intermediate_player`, each with a single `level` column. The tables contain the following data:
+
+beginner\_player.level intermediate\_player.level 1 4 2 5 3 6
+
+The following `CROSS JOIN` example produces a table of every possible pairing of these rows.
+
+```
+SELECT
+    beginner_player.level,
+    intermediate_player.level
+FROM
+    beginner_player
+CROSS JOIN
+    intermediate_player;
+```
+
+**Returns**
+
+beginner\_player.level intermediate\_player.letter 1 4 1 5 1 6 2 4 2 5 2 6 3 4 3 5 3 6
+
+## [](#unnest)UNNEST
+
+`UNNEST` is a table-valued function (TVF) that transforms an input row containing an array into a set of rows. The output table repeats rows of the input table for every element of the array. Every array element is attached to one of the output rows. If the input array is empty, the corresponding row is eliminated.
+
+### [](#syntax---from-clause)Syntax - FROM Clause
+
+Using TVFs such as `UNNEST` is permitted in `FROM` clauses as follows:
+
+```
+FROM <from_items>, UNNEST(<array_column> [,<array_column>...]) [[ AS ] <row_alias>]
+```
+
+Component Description Valid values and syntax `<from_items>` The tables containing the array columns that should be unnested.   `<array_column>` The array columns to unnest, which can be either an array literal or a reference to an array-typed column. Any valid array literal or column name. `<row_alias>` An alias for the result row, such as `r(x)`.  
+
+The previous query performs a lateral join onto the result of the `UNNEST` operation. However, the `LATERAL` keyword is optional.
+
+### [](#syntax---select-clause)Syntax - SELECT Clause
+
+When unnesting a single column, the TVF can also be invoked directly in the `SELECT` clause.
+
+```
+SELECT <select_list>, UNNEST(<array_column>) [[ AS ] <column_alias>]
+```
+
+Component Description Valid values and syntax `<select_list>` The regular select list of your SQL query.   `<array_column>` The array columns to unnest, which can be either an array literal or a reference to an array-typed column. Any valid array literal or column name. `<column_alias>` A column alias for the result column, such as `x`.  
+
+### [](#example-3)Example
+
+The example is based on the following table:
+
+```
+CREATE FACT TABLE players 
+(
+    player TEXT,
+    completed_levels ARRAY(INTEGER)
+) PRIMARY INDEX product;
+```
+
+Assume the table was populated and contains the following values:
+
+player completed\_levels kennethpark \[2,5] sabrina21 \[3,6,7] andres \[]
+
+The following query with `UNNEST`:
+
+```
+SELECT
+    player,
+    completed_levels,
+    completed
+FROM
+    players, UNNEST(completed_levels) as r(completed);
+```
+
+Returns the following result:
+
+player completed\_levels  completed kennethpark \[2,5] 2 kennethpark \[2,5] 5 sabrina21 \[3,6,7] 3 sabrina21 \[3,6,7] 6 sabrina21 \[3,6,7] 7
+
+The above query can be rewritten to invoke `UNNEST` in the `SELECT` clause:
+
+```
+SELECT
+    player,
+    completed_levels,
+    UNNEST(completed_levels) as completed
+FROM
+    players;
+```
+
+## [](#where)WHERE
+
+Use the `WHERE` clause to define conditions for the query in order to filter the query results. When included, the `WHERE` clause always follows the `FROM` clause as part of a command such as `SELECT`.
+
+### [](#syntax-3)Syntax
+
+```
+WHERE <condition>
+```
+
+Component Description Valid values and syntax `<condition>` Indicates the conditions of the query. Any valid `BOOLEAN` expression.
+
+### [](#example-4)Example
+
+In the following example, the query retrieves all entries from the `customers` table for which the `region` value is “EMEA”.
+
+```
+SELECT
+	*
+FROM
+	players
+WHERE
+	region = 'EMEA'
+```
+
+The following query retrieves users who registered after August 30, 2020 from the `players` table:
+
+```
+SELECT
+	playerid,
+	email,
+	nickname
+FROM
+	players
+WHERE
+	registeredon >= TO_DATE('2020-08-30');
+```
+
+The following query retrieves users who registered after August 30, 2020:
+
+```
+SELECT
+	playerid,
+	email,
+SELECT
+	playerid,
+	email,
+	nickname
+FROM
+	players
+WHERE
+	registeredon >= TO_DATE('2020-08-30')
+	AND user_id IN (
+		SELECT
+			playerid
+		FROM
+			players
+	)
+```
+
+## [](#group-by)GROUP BY
+
+The `GROUP BY` clause groups together input rows. Multiple input rows which have same values of expressions in the `GROUP BY` clause become a single row in the output. `GROUP BY` is typically used in conjunction with aggregate functions such as `SUM` and `MIN`. Query with `GROUP BY` clause and without aggregate functions is equivalent to `SELECT DISTINCT`.
+
+### [](#syntax-4)Syntax
+
+```
+GROUP BY [ <grouping_element> [, ...n] | ALL ]
+```
+
+### [](#example-5)Example
+
+In the following example, the retrieved results are grouped by the `nickname` column, and then by the `email` column.
+
+```
+SELECT
+	nickname,
+	email,
+	sum(agecategory)
+FROM
+	purchases
+GROUP BY
+	nickname,
+	email
+```
+
+If the expression in `GROUP BY` clause is exactly the same as in the `SELECT` list, then its position can be used instead.
+
+```
+SELECT
+	nickname,
+	email,
+	SUM(agecategory)
+FROM
+	players
+GROUP BY
+	1,
+	2
+```
+
+The `GROUP BY` clause must include all expressions in the `SELECT` list that do not use aggregate functions. It may include expressions which are not part of `SELECT` list.
+
+```
+SELECT SUM(agecategory) FROM players GROUP BY nickname
+```
+
+The following will cause an error, since `SELECT` list has an expression which is not an aggregate function, and it is not listed in `GROUP BY` clause.
+
+```
+SELECT nickname, email, SUM(agecategory) FROM players GROUP BY playerid
+```
+
+#### [](#group-by-all)GROUP BY ALL
+
+For the common case of `GROUP BY` clause repeating all the non-aggregate function expressions in the `SELECT` list, it is possible to use `GROUP BY ALL` syntax. It will automatically group by all non-aggregate functions expressions from the `SELECT` list.
+
+```
+SELECT
+	nickname,
+	email,
+	SUM(currentscore)
+FROM
+	players
+GROUP BY ALL
+```
+
+## [](#having)HAVING
+
+The `HAVING` clause is used in conjunction with the `GROUP BY` clause, and is computed after computing the `GROUP BY` clause and aggregate functions. `HAVING` is used to further eliminate groups that don’t satisfy the `<condition>` by filtering the `GROUP BY` results.
+
+### [](#syntax-5)Syntax
+
+```
+HAVING <condition> [, ...n]
+```
+
+Component Description `<condition>` Indicates the boolean condition by which the results should be filtered.
+
+## [](#union-all)UNION \[ALL]
+
+The `UNION` operator combines the results of two or more `SELECT` statements into a single query.
+
+- `UNION` combines with duplicate elimination.
+- `UNION ALL` combines without duplicate elimination.
+
+When including multiple clauses, the same number of columns must be selected by all participating `SELECT` statements. Data types of all column parameters must be the same. Multiple clauses are processed left to right. Use parentheses to define an explicit order for processing.
+
+### [](#syntax-6)Syntax
+
+```
+<select_expression1> UNION [ALL] <select_expression2> [ ...n]
+```
+
+Component Description `<select_expression1>` A `SELECT`statement. `<select_expression2>` A second `SELECT` statement to be combined with the first.
+
+## [](#order-by)ORDER BY
+
+The `ORDER BY` clause sorts a result set by one or more output expressions. `ORDER BY` is evaluated as the last step after any `GROUP BY` or `HAVING` clause. `ASC` and `DESC` determine whether results are sorted in ascending or descending order. When the clause contains multiple expressions, the result set is sorted according to the first expression. Rows with the same values for the first expression are then sorted by the second expression, and this process continues for subsequent expressions.
+
+The `NULLS FIRST` and `NULLS LAST` options can be used to determine whether `NULL` values appear before or after non-`NULL` values in the sort order. By default, `NULL` values are considered greater than any non-`NULL` value. `NULLS FIRST` is the default for descending order, and `NULLS LAST` is the default for ascending order.
+
+### [](#syntax-7)Syntax
+
+```
+ORDER BY <expression> [ ASC | DESC ] [ NULLS FIRST | NULLS LAST] [, ...]
+```
+
+Component Description `<expression>` Each expression may specify output columns from `SELECT` or an ordinal number for an output column by position, starting at one. `[ ASC | DESC ]` Indicates whether the sort should be in ascending or descending order. `[ NULLS FIRST | NULLS LAST]` Indicates whether null values should be included at the beginning or end of the result. `NULLS FIRST` is the default for `DESC` order, and `NULLS LAST` otherwise.
+
+## [](#limit)LIMIT
+
+The `LIMIT` clause restricts the number of rows that are included in the result set.
+
+### [](#syntax-8)Syntax
+
+```
+LIMIT <count>
+```
+
+Component Description Valid values and syntax `<count>` Indicates the number of rows that should be returned. An integer.
+
+## [](#offset)OFFSET
+
+The `OFFSET` clause specifies a non-negative number of rows that are skipped before returning results from the query.
+
+### [](#syntax-9)Syntax
+
+```
+OFFSET <start>
+```
+
+Component Description Valid values and syntax `<start>` Indicates the number of rows that should be skipped. An integer.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_data_types.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_data_types.md
new file mode 100644
index 0000000..401377c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_data_types.md
@@ -0,0 +1,167 @@
+# [](#data-types)Data types
+
+This topic lists the data types available in Firebolt.
+
+Category Data Type Aliases Description Numeric [INTEGER](https://docs.firebolt.io/sql_reference/data-types.html#integer) INT, INT4 A four-byte signed integer. [BIGINT](https://docs.firebolt.io/sql_reference/data-types.html#bigint) LONG, INT8 An eight-byte signed integer. [NUMERIC](https://docs.firebolt.io/sql_reference/data-types.html#numeric-1) DECIMAL An exact numeral defined by a fixed precision and scale, with a default of \`38\` for precision and \`9\` for scale. [REAL](https://docs.firebolt.io/sql_reference/data-types.html#real) FLOAT4 A four-bye floating point number with six decimal digits of precision. [DOUBLE PRECISION](https://docs.firebolt.io/sql_reference/data-types.html#double-precision) DOUBLE, FLOAT, FLOAT8, FLOAT(p) An eight-byte floating point number with fifteen decimal digits of precision. Boolean [BOOLEAN](https://docs.firebolt.io/sql_reference/data-types.html#boolean-1) BOOL A logical boolean value of true or false. Composite [ARRAY](#array) An array that holds multiple values of the same data type. Date &amp; Timestamp [DATE](#date) A calendar date including the year, month, and day. [TIMESTAMP](#timestamp) A calendar date and time in Coordinated Universal Time (UTC), including the year, month, day, hour, minute, second, and microsecond. [TIMESTAMPTZ](#timestamptz) A calendar date and time in the local timezone, including year, month, day, hour, minute, second, and microsecond. String [TEXT](#text) A character string of variable length. Binary [BYTEA](#bytea) Binary data of variable length. Spatial [GEOGRAPHY](#geography) Geographic data, including points, LineStrings, Polygons and collections thereof.
+
+*For more information about converting a value with a given data type to another, see [Type Conversion](#type-conversion).*
+
+## [](#numeric)Numeric
+
+### [](#integer)INTEGER
+
+A whole number ranging from -2,147,483,648 to 2,147,483,647. `INTEGER` data types require 4 bytes of storage. Aliases: `INT`, `INT4`.
+
+### [](#bigint)BIGINT
+
+A whole number ranging from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. `BIGINT` data types require 8 bytes of storage. Aliases: `LONG`, `INT8`.
+
+### [](#numeric-1)NUMERIC
+
+A fixed-point numeric data type defined by its precision (total number of digits) and scale (number of digits to the right of the decimal point). For more information, see [NUMERIC data type](/sql_reference/numeric-data-type). Aliases: `DECIMAL`.
+
+### [](#real)REAL
+
+A floating-point number that has six decimal-digit precision. `REAL` data types require 4 bytes of storage. Aliases: `FLOAT4`.
+
+### [](#double-precision)DOUBLE PRECISION
+
+A floating-point number that has 15 decimal-digit precision. `DOUBLE` data types require 8 bytes. Aliases: `DOUBLE`, `FLOAT`, `FLOAT8`, `FLOAT(p)` where 25 &lt;= p &lt;= 53.
+
+## [](#boolean)Boolean
+
+### [](#boolean-1)BOOLEAN
+
+Represents boolean value of `TRUE` or `FALSE`. Aliases: `BOOL`
+
+## [](#composite)Composite
+
+### [](#array)ARRAY
+
+Represents an array of values. All elements of the array must have the same data type. Elements of the array can be of any supported data type including nested arrays (array with arrays).
+
+Array columns must be defined with the data type of the array elements, and optionally whether or not those elements are nullable. The following syntax options are supported:
+
+- `ARRAY(<data-type> [NULL | NOT NULL])`
+- `<data-type> ARRAY`
+- `<data-type>[]`
+
+For example, the following three queries will create tables with the same nullable `demo_array` column of `TEXT` elements:
+
+```
+  CREATE TABLE demo1 (
+  demo_array ARRAY(TEXT NULL) 
+  );
+  
+  CREATE TABLE demo2 (
+  demo_array TEXT[]
+  );
+
+  CREATE TABLE demo3 (
+  demo_array TEXT ARRAY 
+  );
+```
+
+You can also specify that an array be NOT NULL, but you must then use the `ARRAY(<data-type> NOT NULL)` syntax.
+
+You can access a specific array element with an array subscript expression: `array_value[index]`. The supplied index must be of type `INT` or `BIGINT`. An array of n elements starts with `array_value[1]` and ends with `array_value[n]`. Array subscript expressions:
+
+- raise an error if the subscript expression evaluates to a negative number or 0,
+- return NULL if the array is NULL, or if the subscript expression evaluates to NULL or an index larger than the size of the array,
+- return the specific element of the array for subscript expressions evaluating to a number in the range \[1, array\_size].
+
+#### [](#example)Example
+
+The following `CREATE TABLE` statement shows arrays of different element types and different nullabilities.
+
+```
+CREATE TABLE demo (
+  a_t ARRAY(TEXT NULL) NULL,
+  a_i ARRAY(INTEGER NULL) NOT NULL,
+  a_d ARRAY(DATE NOT NULL) NULL,
+  a_f ARRAY(REAL NOT NULL) NOT NULL,
+  a_a ARRAY(ARRAY(INTEGER NULL) NULL) NULL
+);
+```
+
+And the following `INSERT INTO` statement demonstrates examples of values for these arrays:
+
+```
+INSERT INTO demo VALUES
+  (
+    ['Hello', NULL, 'world'],
+    [1, 42, NULL],
+    [DATE '2000-01-01'],
+    [3.14, 2.71, 9.8],
+    [ [1, 2], [NULL], NULL]
+  ),
+  (
+    NULL,
+    [],
+    NULL,
+    [],
+    NULL
+  )
+```
+
+## [](#date-and-timestamp)Date and timestamp
+
+Type Size Min Max Resolution `DATE` 4 bytes `0001-01-01` `9999-12-31` 1 day `TIMESTAMP` 8 bytes `0001-01-01 00:00:00.000000` `9999-12-31 23:59:59.999999` 1 microsecond `TIMESTAMPTZ` 8 bytes `0001-01-01 00:00:00.000000 UTC` `9999-12-31 23:59:59.999999 UTC` 1 microsecond
+
+Dates are counted according to the [proleptic Gregorian calendar](https://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar). Each year consists of 365 days, with leap days added to February in leap years.
+
+### [](#date)DATE
+
+A year, month, and day calendar date independent of a time zone. For more information, see [DATE data type](/sql_reference/date-data-type.html).
+
+### [](#timestamp)TIMESTAMP
+
+A year, month, day, hour, minute, second, and microsecond timestamp independent of a time zone. For more information, see [TIMESTAMP data type](/sql_reference/timestampntz-data-type.html).
+
+### [](#timestamptz)TIMESTAMPTZ
+
+A year, month, day, hour, minute, second, and microsecond timestamp associated with a time zone. For more information, see [TIMESTAMPTZ data type](/sql_reference/timestamptz-data-type.html).
+
+## [](#string)String
+
+### [](#text)TEXT
+
+The `TEXT` type can be used to store character strings of any length using the UTF-8 encoding standard. Only the ASCII letters “A” through “Z” and “a” through “z” are classified as letters (e.g., `UPPER('aäuü')` returns `'AäUü'`). The sort order of two strings is determined using the collation `ucs_basic`, which sorts strings by Unicode code point (e.g., `'Ab' < 'ab'` is true as `A` (`U+0041`) is less than `a` (`U+0061`)). The character with code zero cannot be in a string.
+
+Regular string literals are enclosed in single quotes and don’t recognize escape sequences. Write two adjacent single quotes to include a single-quote character within a string literal (e.g., `'Leonard''s bicycle'`).
+
+Escape string literals are specified by writing the letter `E` (upper or lower case) before the opening single quote, e.g., `E'Firebolt 🔥\U0001F680'`. Use backslash escape sequences within an escape string literal to represent special byte values:
+
+Backslash escape sequence Interpretation `\b` backspace `\f` form feed `\n` newline `\r` carriage return `\t` tab `\o`, `\oo`, `\ooo` (o = 0–7) octal byte value (decimal value must be between 1 and 255) `\xh`, `\xhh` (h = 0–9, A–F) hexadecimal byte value `\uxxxx`, `\Uxxxxxxxx` (x = 0–9, A–F) 16 or 32-bit hexadecimal Unicode character value
+
+Any other character following a backslash is taken literally (e.g., write two backslashes `\\` to include one backslash character). The byte sequences you create must be valid UTF-8. For historic reasons, if you set the setting `standard_conforming_strings` to `false`, regular string literals will also recognize backslash escape sequences.
+
+## [](#binary)Binary
+
+### [](#bytea)BYTEA
+
+Represents variable size binary data. A binary string is a sequence of bytes - unlike TEXT, there is no character set. The BYTEA data type is nullable. For more information, see [BYTEA data type](/sql_reference/bytea-data-type.html).
+
+## [](#spatial)Spatial
+
+## [](#geography)GEOGRAPHY
+
+Represents geographic objects like points, LineStrings, Polygons, or collections thereof. For more information, see [GEOGRAPHY data type](geography-data-type).
+
+## [](#type-conversion)Type Conversion
+
+Values with a given data type can be converted to another data type. There are three contexts in which this happens:
+
+- *Explicit*: With an explicit invocation of the [CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/cast.html) function.
+- *Assignment*: Assigning values to a column of the target data type, as happens in the insert statement.
+- *Implicit*: Using a SQL function where none of the available signatures match the argument types. The planner inserts implicit casts.
+
+The following table lists which type conversions are supported and in which context.
+
+“Explicit”, “Assignment”, and “Implicit” indicate in which type conversion context the conversion operation can be invoked.
+
+- “Explicit” means only as an explicit cast (using [CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/cast.html) or :: syntax).
+- “Assignment” means implicitly in assignment to a target column, as well as explicitly.
+- “Implicit” means implicitly in expressions, as well as the other cases.
+
+From \\ To UNKNOWN INT BIGINT REAL DOUBLE TEXT BYTEA BOOLEAN NUMERIC ARRAY DATE TIMESTAMP TIMESTAMPTZ GEOGRAPHY **UNKNOWN**   Implicit Implicit Implicit Implicit Implicit Implicit Implicit Implicit Implicit Implicit Implicit Implicit Implicit **INT**     Implicit Implicit Implicit Assignm.   Explicit Implicit           **BIGINT**   Assignm.   Assignm. Implicit Assignm.   Explicit Implicit           **REAL**   Assignm. Assignm.   Implicit Assignm.   Explicit Assignm.           **DOUBLE**   Assignm. Assignm. Assignm.   Assignm.   Explicit Assignm.           **TEXT**   Assignm. Assignm. Assignm. Assignm.   Explicit Explicit Explicit Assignm. Assignm. Assignm. Assignm. Assignm. **BYTEA**           Explicit               Implicit **BOOLEAN**   Explicit       Assignm.                 **NUMERIC**   Assignm. Assignm. Explicit Implicit Assignm.     Explicit           **DATE**           Assignm.           Implicit Implicit   **TIMESTAMP**           Assignm.         Implicit   Implicit   **TIMESTAMPTZ**           Assignm.         Implicit Implicit     **GEOGRAPHY**           Assignm. Implicit
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_date_data_type.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_date_data_type.md
new file mode 100644
index 0000000..d29743d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_date_data_type.md
@@ -0,0 +1,95 @@
+# [](#date-data-type)DATE data type
+
+This topic describes the Firebolt implementation of the `DATE` data type.
+
+- [Overview](#overview)
+- [Literal string interpretation](#literal-string-interpretation)
+- [Functions and operators](#functions-and-operators)
+  
+  - [Type conversions](#type-conversions)
+  - [Comparison operators](#comparison-operators)
+  - [Arithmetic operators](#arithmetic-operators)
+- [Serialization and deserialization](#serialization-and-deserialization)
+
+## [](#overview)Overview
+
+Name Size Min Max Resolution `DATE` 4 bytes `0001-01-01` `9999-12-31` 1 day
+
+The `DATE` type represents a calendar date, independent of a time zone.
+
+## [](#literal-string-interpretation)Literal string interpretation
+
+`DATE` literals follow the ISO 8601 format: `YYYY-[M]M-[D]D`.
+
+- `YYYY`: Four-digit year (`0001` - `9999`)
+- `[M]M`: One or two digit month (`01` - `12`)
+- `[D]D`: One or two digit day (`01` - `31`)
+
+**Examples**
+
+```
+SELECT DATE '2023-02-13';
+SELECT '2023-02-13'::DATE;
+SELECT CAST('2023-6-03' AS DATE);
+SELECT DATE('2023-02-13');
+```
+
+## [](#functions-and-operators)Functions and operators
+
+### [](#type-conversions)Type conversions
+
+The `DATE` data type can be cast to and from types as follows:
+
+#### [](#to-date)To DATE
+
+From type Example Note `TEXT` `SELECT CAST(TEXT '2023-02-13' as DATE); --> 2023-02-13` Interprets the text according to the literal string format. `TIMESTAMP` `SELECT CAST(TIMESTAMP '2023-02-13 11:19:42' as DATE); --> 2023-02-13` Truncates the timestamp to the date. `TIMESTAMPTZ` `SELECT CAST(TIMESTAMPTZ '2023-02-13 Europe/Berlin' as DATE); --> 2023-02-13` Converts the timestamptz to local time in the time zone specified by the [session’s `timezone` setting](/Reference/system-settings.html#setting-the-time-zone), then truncates the timestamp to the date. This example assumes `SET timezone = 'UTC';`.
+
+#### [](#from-date)From DATE
+
+To type Example Note `TEXT` `SELECT CAST(DATE '2023-02-13' as TEXT); --> 2023-02-13` Converts the date to text in the format `YYYY-MM-DD`. `TIMESTAMP` `SELECT CAST(DATE '2023-02-13' as TIMESTAMP); --> 2023-02-1 00:00:00` Extends the date with `00:00:00`. `TIMESTAMPTZ` `SELECT CAST(DATE '2023-02-13' as TIMESTAMPTZ); --> 2023-02-13` Interprets the date as midnight in the time zone specified by the [session’s `timezone` setting](/Reference/system-settings.html#setting-the-time-zone). This example assumes `SET timezone = 'UTC';`.
+
+### [](#comparison-operators)Comparison operators
+
+Operator Description `DATE < DATE` Less than `DATE > DATE` Greater than `DATE <= DATE` Less than or equal to `DATE >= DATE` Greater than or equal to `DATE = DATE` Equal to `DATE <> DATE` Not equal to
+
+A `DATE` value is also comparable with a `TIMESTAMP` or `TIMESTAMPTZ` value:
+
+- The `DATE` value is cast to the `TIMESTAMP` type for comparison with a `TIMESTAMP` value.
+- The `DATE` value is cast to the `TIMESTAMPTZ` type for comparison with a `TIMESTAMPTZ` value.
+
+### [](#arithmetic-operators)Arithmetic operators
+
+The `+` operators described below come in commutative pairs:
+
+Operator Description Example `DATE + INTEGER -> DATE` Add a number of days to a date `SELECT DATE '2023-03-03' + 42; --> 2023-04-14` `DATE - INTEGER -> DATE` Subtract a number of days from a date `SELECT DATE '2023-03-03' - 42; --> 2023-01-20` `DATE - DATE -> INTEGER` Subtract dates, producing the number of elapsed days `SELECT DATE '2023-03-03' - DATE '1996-09-03'; --> 9677` `DATE + INTERVAL -> TIMESTAMP` Add an interval to a date `SELECT DATE '1996-09-03' + INTERVAL '42' YEAR; --> 2038-09-03 00:00:00` `DATE - INTERVAL -> TIMESTAMP` Subtract an interval from a date `SELECT DATE '2023-03-18' - INTERVAL '26 years 5 months 44 days 12 hours 41 minutes'; --> 1996-09-03 11:19:00`
+
+#### [](#interval-arithmetic)Interval arithmetic
+
+Arithmetic with intervals can be used to add or subtract a duration to or from a date. The result is of type `TIMESTAMP`.
+
+**Example**
+
+```
+SELECT DATE '1996-09-03' + INTERVAL '42' YEAR;  --> 2038-09-03 00:00:00
+SELECT DATE '2023-03-18' - INTERVAL '26 years 5 months 44 days 12 hours 41 minutes';  --> 1996-09-03 11:19:00
+```
+
+For more information, see [Arithmetic with intervals](/Reference/interval-arithmetic.html).
+
+## [](#serialization-and-deserialization)Serialization and deserialization
+
+### [](#text-csv-json)Text, CSV, JSON
+
+In the text, CSV, and JSON format, a `DATE` value is output as a `YYYY-MM-DD` string. Input is accepted in the literal format described above: `YYYY-[M]M-[D]D`.
+
+### [](#parquet)Parquet
+
+`DATE` maps to Parquet’s 32-bit signed integer `DATE` type, also representing the number of days before or after `1970-01-01`.
+
+### [](#avro)Avro
+
+`DATE` maps to Avro’s 32-bit signed integer `DATE` type, also representing the number of days before or after `1970-01-01`.
+
+### [](#orc)ORC
+
+`DATE` maps to ORC’s signed integer `DATE` type, also representing the number of days before or after `1970-01-01`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation.md
new file mode 100644
index 0000000..521c10f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation.md
@@ -0,0 +1,29 @@
+## [](#aggregation-functions)Aggregation functions
+
+* * *
+
+- [ANY\_VALUE](/sql_reference/functions-reference/aggregation/any_value.html)
+- [APPROX\_COUNT\_DISTINCT](/sql_reference/functions-reference/aggregation/approx-count-distinct.html)
+- [ARRAY\_AGG](/sql_reference/functions-reference/aggregation/array-agg.html)
+- [AVG](/sql_reference/functions-reference/aggregation/avg.html)
+- [BIT\_AND](/sql_reference/functions-reference/aggregation/bit_and.html)
+- [BIT\_OR](/sql_reference/functions-reference/aggregation/bit_or.html)
+- [BIT\_XOR](/sql_reference/functions-reference/aggregation/bit_xor.html)
+- [BOOL\_AND](/sql_reference/functions-reference/aggregation/bool_and.html)
+- [BOOL\_OR](/sql_reference/functions-reference/aggregation/bool_or.html)
+- [COUNT](/sql_reference/functions-reference/aggregation/count.html)
+- [HASH\_AGG](/sql_reference/functions-reference/aggregation/hash-agg.html)
+- [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html)
+- [HLL\_COUNT\_DISTINCT](/sql_reference/functions-reference/aggregation/hll-count-distinct.html)
+- [HLL\_COUNT\_MERGE](/sql_reference/functions-reference/aggregation/hll-count-merge.html)
+- [MAX](/sql_reference/functions-reference/aggregation/max.html)
+- [MAX\_BY](/sql_reference/functions-reference/aggregation/max-by.html)
+- [MEDIAN](/sql_reference/functions-reference/aggregation/median.html)
+- [MIN](/sql_reference/functions-reference/aggregation/min.html)
+- [MIN\_BY](/sql_reference/functions-reference/aggregation/min-by.html)
+- [PERCENTILE\_CONT](/sql_reference/functions-reference/aggregation/percentile-cont.html)
+- [STDDEV\_POP](/sql_reference/functions-reference/aggregation/stddev-pop.html)
+- [STDDEV\_SAMP](/sql_reference/functions-reference/aggregation/stddev-samp.html)
+- [SUM](/sql_reference/functions-reference/aggregation/sum.html)
+- [VAR\_POP](/sql_reference/functions-reference/aggregation/variance-pop.html)
+- [VAR\_SAMP](/sql_reference/functions-reference/aggregation/variance-samp.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_any_value.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_any_value.md
new file mode 100644
index 0000000..33cb4ea
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_any_value.md
@@ -0,0 +1,47 @@
+# [](#any_value)ANY\_VALUE
+
+Returns a single arbitrary value from the specified column.
+
+**Alias:** `ANY`
+
+## [](#syntax)Syntax
+
+```
+ANY_VALUE(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` Any expression Any
+
+This function ignores `NULL` inputs. It returns `NULL` only when all inputs are `NULL` or there are no inputs.
+
+## [](#return-type)Return Type
+
+Same as input type
+
+## [](#examples)Examples
+
+**Example**
+
+```
+SELECT
+	ANY_VALUE(nickname)
+FROM
+	UNNEST (ARRAY['kennethpark', NULL, 'sabrina21', 'ruthgill', 'steven70']) AS players(nickname);
+```
+
+**Returns**
+
+Any value of the `nickname` column, excluding `NULL`. The first time the query below runs, the nickname `kennethpark` might be returned. The second time the query runs, `sabrina21` or any other value, such as `ruthgill` or `steven70`, might be returned, but `NULL` will never be returned while non-`NULL` options exist.
+
+**Example**
+
+```
+SELECT ANY_VALUE(data) FROM UNNEST (ARRAY[NULL, NULL, NULL]) arr(data);
+SELECT ANY_VALUE(data) FROM UNNEST (ARRAY[1,2,3]) arr(data) WHERE false;
+```
+
+**Returns**
+
+`NULL` as no non-`NULL` values are available.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_approx_count_distinct.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_approx_count_distinct.md
new file mode 100644
index 0000000..bfeb410
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_approx_count_distinct.md
@@ -0,0 +1,77 @@
+# [](#approx_count_distinct)APPROX\_COUNT\_DISTINCT
+
+Counts the approximate number of unique values that are not NULL. Internally, `APPROX_COUNT_DISTINCT` uses HyperLogLog (HLL) sketches. Calling `APPROX_COUNT_DISTINCT` returns the same value as calling `HLL_COUNT_DISTINCT` with precision 17.
+
+## [](#syntax)Syntax
+
+```
+APPROX_COUNT_DISTINCT(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` Expression on which to approximate the distinct count Any type
+
+## [](#return-type)Return Type
+
+`BIGINT`
+
+## [](#example)Example
+
+When aggregating on few distinct values, `APPROX_COUNT_DISTINCT` has no estimation error and returns exact results:
+
+```
+SELECT
+    APPROX_COUNT_DISTINCT(number) as approximate,
+    COUNT(DISTINCT number) as exact
+FROM
+    generate_series(1, 1000) r(number);
+```
+
+**Returns**:
+
+approximate exact 1,000 1,000
+
+`NULL` values do not change the result of `APPROX_COUNT_DISTINCT`:
+
+```
+SELECT
+    APPROX_COUNT_DISTINCT(number) as approximate,
+    COUNT(DISTINCT number) as exact
+FROM
+    (SELECT * FROM generate_series(1, 1000)
+       UNION ALL
+     SELECT NULL) r(number);
+```
+
+**Returns**:
+
+approximate exact 1,000 1,000
+
+As the number of distinct values grows, the result becomes an approximation:
+
+```
+SELECT
+    APPROX_COUNT_DISTINCT(number) as approximate,
+    COUNT(DISTINCT number) as exact
+FROM
+    generate_series(1, 50000) r(number);
+```
+
+**Returns**:
+
+approximate exact 50,160 50,000
+
+`APPROX_COUNT_DISTINCT` also works for compound types:
+
+```
+SELECT 
+    APPROX_COUNT_DISTINCT(arr) as approximate,
+    COUNT(DISTINCT arr) as exact
+FROM 
+    unnest([[1, 2], [3, 4], NULL, [NULL], [1, NULL]]) r(arr)
+```
+
+**Returns**:
+
+approximate exact 4 4
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_array_agg.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_array_agg.md
new file mode 100644
index 0000000..08d496b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_array_agg.md
@@ -0,0 +1,53 @@
+# [](#array_agg)ARRAY\_AGG
+
+Concatenates input values, including `NULL` values, into an array.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_AGG(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input type `<expression>` Expression of any type to be accumulated into an array. Any
+
+## [](#return-type)Return Type
+
+`ARRAY` of the same type as the input data. If there is no input data, `ARRAY_AGG` returns `NULL`.
+
+## [](#example)Example
+
+For the following example, see the `player_information` table:
+
+nickname playerid stephen70 1 burchdenise 7 sabrina21 NULL
+
+The following code example code selects the columns in the `player_information` table and returns the values in two arrays, `nicknames` and `playerids`:
+
+```
+SELECT
+  ARRAY_AGG(nickname) AS nicknames,
+  ARRAY_AGG(playerid) AS playerids
+FROM
+	price_list;
+```
+
+**Returns**
+
+`{'stephen70', 'burchdenise', 'sabrina21'}, {1, 7, NULL}`
+
+The following code example shows that if a filter is added to the query which rejects all rows, `ARRAY_AGG` will return `NULL`:
+
+```
+SELECT
+  ARRAY_AGG(nickname) AS nicknames,
+  ARRAY_AGG(playerid) AS playerids
+FROM
+	price_list
+WHERE
+  playerid = 42;
+```
+
+**Returns**
+
+`NULL, NULL`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_avg.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_avg.md
new file mode 100644
index 0000000..70e44d9
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_avg.md
@@ -0,0 +1,46 @@
+# [](#avg)AVG
+
+Calculates the average of an expression.
+
+## [](#syntax)Syntax
+
+```
+AVG(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The expression used to calculate the average Any numeric type
+
+Valid values for the expression include column names or functions that return a column name (or columns) that contain numeric values.
+
+The `AVG()` aggregation function ignores rows with `NULL` values. For example, an `AVG` from 3 rows containing `1`, `2`, and `NULL` returns `1.5` because the `NULL` row is not counted. To calculate an average that includes `NULL`, use `SUM(COLUMN)/COUNT(*)`.
+
+## [](#return-types)Return Types
+
+- `NUMERIC` if the input is type `INTEGER`, `BIGINT` or `NUMERIC`
+- `DOUBLE PRECISION` if the input is type `REAL` or `DOUBLE PRECISION`
+
+## [](#precision-and-determinism)Precision and Determinism
+
+Applying `AVG` to REAL and DOUBLE PRECISION is subject to [floating point arithmetic accuracy limitations](https://en.wikipedia.org/wiki/Floating-point_arithmetic#Accuracy_problems) and its resulting error. This error may add up when aggregating multiple values.
+
+The order of operations while computing the aggregate is non-deterministic. This can lead to varying total floating point error when running a query multiple times. If this is not acceptable for your use-case, aggregate on [NUMERIC](/sql_reference/numeric-data-type) data instead.
+
+## [](#example)Example
+
+The example below uses the following table `LevelPoints`. This table includes the maximum points a player can score at each level of the game:
+
+levels maxpoints 1 50 2 100 3 150 4 200 5 250
+
+Use the query below to find the average of the `maxpoints` value.
+
+```
+SELECT 
+    AVG(maxpoints) AS AverageMaxPoints 
+FROM levels;
+```
+
+**Returns**:
+
+AverageMaxPoints 150
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_and.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_and.md
new file mode 100644
index 0000000..0db2f1c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_and.md
@@ -0,0 +1,64 @@
+# [](#bit_and)BIT\_AND
+
+Performs a bitwise `AND` operation on an integer expression, ignoring null input values. Bitwise `AND` compares two bits and returns `1` if both are `1`, and `0` otherwise.
+
+Numbers are represented in two’s complement, a binary method for signed integers as follows:
+
+- Positive numbers are represented in standard binary form, while negative numbers are derived by inverting the bits of their positive counterpart and adding `1`.
+- A leftmost bit of `0` indicates a positive number, while `1` indicates a negative number.
+
+## [](#syntax)Syntax
+
+```
+BIT_AND
+([ DISTINCT ] <expression>)
+```
+
+Note: `DISTINCT` has no effect on the function’s result.
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression used to compute the result. `INT`, `BIGINT`
+
+## [](#return-types)Return Types
+
+The `BIT_AND` function returns a result of either type `INT` or `BIGINT`, depending on the type of the input.
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example performs a bitwise `AND` operation across all integers ranging from `1` to `3`:
+
+```
+SELECT BIT_AND(a)
+FROM GENERATE_SERIES(1, 3) as a;
+```
+
+**Returns**
+
+The previous code example returns `0`. In a 4-bit system, the binary representation of integers from `1` to `3` is:
+
+- `1` `->` `0001`
+- `2` `->` `0010`
+- `3` `->` `0011`
+
+The bitwise `AND` function returns `0` because there is no bit position where all three integers have a `1`. The bitwise `AND` of `0001` and `0010` is `0000`, which equals `0`. The bitwise `AND` between `0000` and `0011` is `0000`, or `0`.
+
+**Example**
+
+The following code performs a bitwise `AND` operation across two rows in column `a` that contain the values `-1` and `3`, respectively:
+
+```
+SELECT BIT_AND(a)
+FROM UNNEST([-1,3]) as a;
+```
+
+**Returns**
+
+The previous code example returns `3`. In a 4-bit system, the binary representation of `-1` and `3` is:
+
+- `-1` `->` `1111`
+- `3` `->` `0011`
+
+The bitwise `AND` of `1111` and `0011` is `0011` because the last two positions have `1` in both values.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_or.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_or.md
new file mode 100644
index 0000000..8e302d2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_or.md
@@ -0,0 +1,65 @@
+# [](#bit_or)BIT\_OR
+
+Performs a bitwise `OR` operation on an integer expression, ignoring null input values. Bitwise `OR` compares two bits and returns `1` if either is `1`, and `0` otherwise.
+
+Numbers are represented in two’s complement, a binary method for signed integers, as follows:
+
+- Positive numbers are represented in standard binary form, while negative numbers are derived by inverting the bits of their positive counterpart and adding `1`.
+- A leftmost bit of `0` indicates a positive number, while `1` indicates a negative number.
+
+## [](#syntax)Syntax
+
+```
+BIT_OR
+([ DISTINCT ] <expression>)
+```
+
+Note: `DISTINCT` has no effect on the function’s result.
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression used to compute the result. `INT`, `BIGINT`
+
+## [](#return-types)Return Types
+
+The `BIT_OR` function returns a result of either type `INT` or `BIGINT`, depending on the type of the input.
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example performs a bitwise `OR` operation across a series of integers ranging from `1` to `3`:
+
+```
+SELECT BIT_OR(a)
+FROM GENERATE_SERIES(1, 3) as a;
+```
+
+**Returns**
+
+The previous code example returns `3`. In a 4-bit system, the binary representation of integers from `1` to `3` is:
+
+- `1` `->` `0001`
+- `2` `->` `0010`
+- `3` `->` `0011`
+
+The bitwise `OR` of `0001` and `0010` is `0011`, which equals `3`. The bitwise `OR` between `0011` and itself is `0011`, or `3`.
+
+**Example**
+
+The following code example performs a bitwise `OR` operation across a series of integers ranging from `-1` to `1`:
+
+```
+SELECT BIT_OR(a)
+FROM generate_series(-1, 1) as a;
+```
+
+**Returns**
+
+The previous code example returns `-1`. In a 4-bit system, the binary representation of integers from `-1` to `1` is:
+
+- `-1` `->` `1111`
+- `0` `->` `0000`
+- `1` `->` `0001`
+
+The bitwise `OR` of `1111` and any integer is `1111`, or `-1`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_xor.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_xor.md
new file mode 100644
index 0000000..f5ef510
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bit_xor.md
@@ -0,0 +1,102 @@
+# [](#bit_xor)BIT\_XOR
+
+Performs a bitwise `XOR` operation on an integer expression, ignoring null input values. Bitwise `XOR`, or exclusive `OR`, compares two bits and returns `1` if they are different, and `0` if they are the same.
+
+Numbers are represented in two’s complement, a binary method for signed integers as follows:
+
+- Positive numbers are represented in standard binary form, while negative numbers are derived by inverting the bits of their positive counterpart and adding `1`.
+- A leftmost bit of `0` indicates a positive number, while `1` indicates a negative number.
+
+## [](#syntax)Syntax
+
+```
+BIT_XOR
+([ DISTINCT ] <expression>)
+```
+
+Note: `DISTINCT` has no effect on the function’s result.
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression used to compute the result. `INT`, `BIGINT`
+
+## [](#return-types)Return Types
+
+The `BIT_XOR` function returns a result of either type `INT` or `BIGINT`, depending on the type of the input.
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example performs a bitwise `XOR` operation across three rows in column `a` that contain the values `1`, `2`, and `1`, respectively:
+
+```
+SELECT BIT_XOR(a)
+FROM UNNEST([1,2,1]) as a;
+```
+
+**Returns**
+
+The previous code example returns `2`. In a 4-bit system, the binary representation of `1`, and `2` are:
+
+- `1` `->` `0001`
+- `2` `->` `0010`
+
+The bitwise `XOR` of `0001` and `0010` from the first and second rows is `0011`, or `3`. The bitwise `XOR` between this result and the `1` in the third row is `0010`, or `2`, because the `XOR` of two identical numbers is `0`.
+
+**Example**
+
+The following code example uses `DISTINCT` to eliminate duplicate values from column `a`, and performs a bitwise `XOR` operation across two rows that contain the values `1` and `2`:
+
+```
+SELECT BIT_XOR(DISTINCT a)
+FROM UNNEST([1,2,1]) as a;
+```
+
+**Returns**
+
+The previous code example returns `3`. In a 4-bit system, the binary representation of `1` and `2` are:
+
+- `1` `->` `0001`
+- `2` `->` `0010`
+
+The bitwise `XOR` of `0001` and `0010` is `0011`, or `3`.
+
+**Example**
+
+The following code example performs a bitwise `XOR` operation across a series of integers ranging from `1` to `3`:
+
+```
+SELECT BIT_XOR(a)
+FROM generate_series(1, 3) as a;
+```
+
+**Returns**
+
+The previous code example returns `0`. In a 4-bit system, the binary representation of integers from `1` to `3` are:
+
+- `1` `->` `0001`
+- `2` `->` `0010`
+- `3` `->` `0011`
+
+The bitwise `XOR` of `0001` and `0010` is `0011`, which equals `3`. The bitwise `XOR` between `0011` and itself is `0000`, or `0`.
+
+**Example**
+
+The following code example performs a bitwise `XOR` operation across a series of integers ranging from `-1` to `2`:
+
+```
+SELECT BIT_XOR(a)
+FROM generate_series(-1, 2) as a;
+```
+
+**Returns**
+
+The previous code example returns `-4`. In a 4-bit system, the binary representation of integers from `-1` to `1` are:
+
+- `-1` `->` `1111`
+- `0` `->` `0000`
+- `1` `->` `0001`
+- `2` `->` `0010`
+
+The bitwise `XOR` of `1111` and `0000` is `1111`, which equals `-1`. The bitwise `XOR` between `1111` and `0001` is `1110`, or `-2`. The bitwise `XOR` between `1110` and `0010` is `1100`, which equals `-4`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bool_and.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bool_and.md
new file mode 100644
index 0000000..e903535
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bool_and.md
@@ -0,0 +1,34 @@
+# [](#bool_or)BOOL\_OR
+
+Returns true if all non NULL input value are true, otherwise false. If all input values are NULL values, returns NULL.
+
+## [](#syntax)Syntax
+
+```
+BOOL_AND(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The boolean expression used to calculate the result `BOOLEAN`
+
+## [](#return-types)Return Types
+
+`BOOLEAN`
+
+## [](#example)Example
+
+name totalprizedollars The Drift Championship 22,048 The Lost Track Showdown 5,336 The Acceleration Championship 19,274 The French Grand Prix 237 The Circuit Championship 9,739
+
+We want to check if all tournaments have prize money
+
+```
+SELECT
+	BOOL_ALL(totalprizeddollars IS NOT NULL AND totalprizeddollars > 0) as all_have_prizes 
+FROM
+	tournaments;
+```
+
+**Returns**
+
+`true`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bool_or.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bool_or.md
new file mode 100644
index 0000000..4037d50
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_bool_or.md
@@ -0,0 +1,34 @@
+# [](#bool_or)BOOL\_OR
+
+Returns true if any non NULL input value is true, otherwise false. If all input values are NULL values, returns NULL.
+
+## [](#syntax)Syntax
+
+```
+BOOL_OR(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The boolean expression used to calculate the result `BOOLEAN`
+
+## [](#return-types)Return Types
+
+`BOOLEAN`
+
+## [](#example)Example
+
+name totalprizedollars The Drift Championship 22,048 The Lost Track Showdown 5,336 The Acceleration Championship 19,274 The French Grand Prix 237 The Circuit Championship 9,739
+
+We want to see if any of the tournaments have prize value more than 20,000
+
+```
+SELECT
+	BOOL_OR(totalprizeddollars > 20000) as has_big_prize
+FROM
+	tournaments;
+```
+
+**Returns**
+
+`true`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_count.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_count.md
new file mode 100644
index 0000000..137d2fb
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_count.md
@@ -0,0 +1,77 @@
+# [](#count)COUNT
+
+Counts the number of rows or not NULL values.
+
+## [](#syntax)Syntax
+
+```
+COUNT([ DISTINCT ] <expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression to count Any
+
+Valid values for the input expression include column names or functions that return a column name. When `DISTINCT` is being used, only the unique number of rows with no `NULL` values are counted. `COUNT(*)` returns a total count of all rows in the table, while `COUNT(<column_name>)` returns a count of non-null rows in the specified `<column_name>`.
+
+> By default, `COUNT(DISTINCT)` returns exact results. If you do not require a precise result and want to have faster performance, consider using the APPROX\_COUNT\_DISTINCT function. See below for examples and considerations.
+
+## [](#return-type)Return Type
+
+`NUMERIC`
+
+## [](#example)Example
+
+For this example, see the following table `tournaments`:
+
+name totalprizedollars The Drifting Thunderdome 24768 The Lost Track Showdown 5336 The Acceleration Championship 19274 The Winter Wilderness Rally 21560 The Circuit Championship 9739 The Singapore Grand Prix 19274
+
+Doing a regular `COUNT` returns the total number of rows in the column. As the `tournaments` table contains 6 rows, this will be the returned value.
+
+```
+SELECT
+	COUNT(name)
+FROM
+	tournaments;
+```
+
+**Returns**
+
+`6`
+
+A `COUNT(DISTINCT)` function on the same column returns the number of unique rows. When applied to the `totalprizedollars` column, the value returned is `5`, as there is a repeated number in the column.
+
+```
+SELECT
+	COUNT(DISTINCT totalprizedollars)
+FROM
+	tournaments;
+```
+
+**Returns**
+
+`5`
+
+## [](#example-of-countdistinct-vs-approx_count_distinct)Example of COUNT(DISTINCT) vs. APPROX\_COUNT\_DISTINCT
+
+To understand the difference between `COUNT(DISTINCT pk)` with exact precision enabled and using default approximation, consider a table, `count_test` with 8,388,608 unique `pk` values. The `APPROX_COUNT_DISTINCT` function returns the same approximate results as the `COUNT(DISTINCT)` function with exact precision disabled, so we can see the difference between these methods with the following example.
+
+```
+SELECT
+	COUNT(DISTINCT pk) as count_distinct,
+	APPROX_COUNT_DISTINCT(pk) as approx_count
+FROM
+	count_test;
+```
+
+**Returns**
+
+Assuming 8,388,608 unique pk values, the previous code example returns the following:
+
+```
+' +----------------+--------------+
+' | count_distinct | approx_count |
+' +----------------+--------------+
+' |      8,388,608 |    8,427,387 |
+' +----------------+--------------+
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hash_agg.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hash_agg.md
new file mode 100644
index 0000000..5175cb5
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hash_agg.md
@@ -0,0 +1,59 @@
+# [](#hash_agg)HASH\_AGG
+
+Calculates a hash value over all rows on a list of arguments. When `*` is specified as an argument - calculates a hash aggregation over all columns in the input. Performing a hash aggregation operation is useful for warming up table data or to check if the same values exist in two different tables.
+
+**Alias:** `CHECKSUM`
+
+## [](#syntax)Syntax
+
+```
+HASH_AGG( <expression1> [, <expression2>] [, <expression3>] [, ...<expressionN>] )
+HASH_AGG(*)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` A column name for specific results for the `HASH_AGG` function to be applied to Any `<column>` name
+
+## [](#return-type)Return Type
+
+`BIGINT`
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example creates a new table `tournament_information`:
+
+```
+CREATE DIMENSION TABLE tournament_information (name TEXT, prizedollars DOUBLE PRECISION, tournamentid INTEGER);
+
+INSERT INTO
+	tournament_information
+VALUES
+	('The Snow Park Grand Prix', 20903, 1),
+	('The Acceleration Championsip', 19274, 2),
+	('The Acceleration Trials', 13877, 3)
+```
+
+**Example**
+
+The following code example calculates a hash aggregation based on all columns in the table `tournament_information`:
+
+```
+SELECT HASH_AGG(*) FROM tournament_information;
+```
+
+**Returns**
+
+`1,889,915,309,908,437,919`
+
+The next example calculates a hash aggregation based on columns `prizedollars` and `tournamentid` only.
+
+```
+SELECT HASH_AGG(prizedollars, tournamentid) FROM tournament_information;
+```
+
+**Returns**
+
+`3,058,600,455,882,068,351`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_build.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_build.md
new file mode 100644
index 0000000..68cb51f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_build.md
@@ -0,0 +1,68 @@
+# [](#hll_count_build)HLL\_COUNT\_BUILD
+
+Counts the approximate number of unique not NULL values, aggregating the values to HLL++ sketches represented as the [BYTEA data type](/sql_reference/bytea-data-type.html). Multiple sketches can be merged to a single sketch using the aggregate function [HLL\_COUNT\_MERGE](/sql_reference/functions-reference/aggregation/hll-count-merge.html). To estimate the final distinct count value, the scalar function [HLL\_COUNT\_ESTIMATE](/sql_reference/functions-reference/numeric/hll-count-estimate.html) can be used. `HLL_COUNT_BUILD` uses the HLL++ algorithm and allows you to control the set sketch size precision, similar to [HLL\_COUNT\_DISTINCT](/sql_reference/functions-reference/aggregation/hll-count-distinct.html).
+
+`HLL_COUNT_BUILD` requires less memory than exact count distinct aggregation, but also introduces statistical uncertainty. The default precision is 12, with a maximum of 20 set optionally.
+
+> Higher precision comes at a memory and performance cost.
+
+## [](#syntax)Syntax
+
+```
+HLL_COUNT_BUILD(<expression> [, <precision> ])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` Any column name or function that return a column name. Any type `<precision>` Optional literal integer value to set precision. If not included, the default precision is 12. Precision range: 12-20. `INTEGER`, `BIGINT`
+
+## [](#return-type)Return Type
+
+`BYTEA`
+
+## [](#example)Example
+
+```
+CREATE TABLE data_to_count AS
+SELECT *
+FROM generate_series(0, 10000000, 3) a;
+
+SELECT count(distinct a) AS accurate_count
+FROM data_to_count;
+```
+
+accurate\_count (BIGINT) 3333334
+
+```
+CREATE TABLE data_to_count2 AS
+SELECT *
+FROM generate_series(0, 10000000, 2) a;
+
+SELECT count(distinct a) AS accurate_count
+FROM data_to_count2;
+```
+
+accurate\_count (BIGINT) 5000001
+
+```
+CREATE TABLE sketch_of_data_to_count AS
+SELECT hll_count_build(a) a
+FROM data_to_count;
+
+INSERT INTO sketch_of_data_to_count
+SELECT hll_count_build(a)
+FROM data_to_count2;
+
+SELECT hll_count_estimate(a) AS hll_estimate, a AS sketch
+FROM sketch_of_data_to_count
+ORDER BY 1;
+```
+
+hll\_estimate (BIGINT) sketch (BYTEA) 3291008 \\x2f41676772656761746546…. 4948957 \\x2f41676772656761746546….
+
+```
+SELECT hll_count_estimate(hll_count_merge(a)) AS hll_estimate
+FROM sketch_of_data_to_count;
+```
+
+hll\_estimate (BIGINT) 6606880
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_distinct.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_distinct.md
new file mode 100644
index 0000000..bae378e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_distinct.md
@@ -0,0 +1,53 @@
+# [](#hll_count_distinct)HLL\_COUNT\_DISTINCT
+
+Counts the approximate number of unique or not NULL values, to the precision specified. `HLL_COUNT_DISTINCT` uses the HLL++ algorithm and allows you to control the sketch size set precision.
+
+`HLL_COUNT_DISTINCT` requires less memory than exact aggregation functions, but also introduces statistical uncertainty. The default precision is 12, with a maximum of 20.
+
+> Higher precision comes at a memory and performance cost.
+
+## [](#syntax)Syntax
+
+```
+HLL_COUNT_DISTINCT ( <expression> [, <precision> ] )
+```
+
+Parameter Description Supported input types `<expression>` Valid values for the expression include column names or functions that return a column name. Any type `<precision>` Optional integer value to set precision. If not included, the default precision is 12. Precision range: 12-20. `INTEGER`, `BIGINT`
+
+## [](#return-type)Return Type
+
+`BIGINT`
+
+> `APPROX_COUNT_DISTINCT(expression)` and `HLL_COUNT_DISTINCT(expression, 17)` return the same results, as `APPROX_COUNT_DISTINCT` uses the HLL algorithm with the default parameter to control the sketch size set to 17.
+
+## [](#return-type-1)Return Type
+
+`NUMERIC`
+
+## [](#example)Example
+
+To understand the difference between `COUNT(DISTINCT pk)` with exact precision enabled, `APPROX_COUNT_DISTNCT(pk)`, and `HLL_COUNT_DISTINCT(pk, <precision>)`, consider a table, `count_test` with 8,388,608 unique `pk` values.
+
+```
+SELECT
+	COUNT(DISTINCT pk) as count_distinct,
+	APPROX_COUNT_DISTINCT(pk) as approx_count
+	HLL_COUNT_DISTINCT(pk, 12) as hll12_count,
+	HLL_COUNT_DISTINCT(pk, 20) as hll20_count
+FROM
+	count_test;
+```
+
+**Returns**
+
+Assuming 8,388,608 unique pk values, the previous code example returns the following:
+
+```
+' +----------------+--------------+-------------+-------------+
+' | count_distinct | approx_count | hll12_count | hll20_count |
+' +----------------+--------------+-------------+-------------+
+' |      8,388,608 |    8,427,387 |   8,667,274 |   8,377,014 |
+' +----------------+--------------+-------------+-------------+
+```
+
+In the previous result, `approx_count` is using precision 17, `hll12_count` is using precision 12, and `hll20_count` is using precision 20, which is the most precise value.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_merge.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_merge.md
new file mode 100644
index 0000000..83bd71b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_hll_count_merge.md
@@ -0,0 +1,30 @@
+# [](#hll_count_merge)HLL\_COUNT\_MERGE
+
+Merges one or more HLL++ sketches that were previously built using the aggregate function [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html) into a new sketch.
+
+Each sketch must be built on the same type and the same precision. Attempts to merge sketches for different types or precisions results in an error. For example, you cannot merge a sketch built from `INTEGER` data with one built from `TEXT` data, or a sketch built with precision 13 and a sketch built with precision 14.
+
+## [](#syntax)Syntax
+
+```
+HLL_COUNT_MERGE(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` HLL++ sketch in a valid format, e.g. the output of the [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html) function. `BYTEA`
+
+## [](#return-type)Return Type
+
+`BYTEA`
+
+## [](#example)Example
+
+Following the [example](/sql_reference/functions-reference/aggregation/hll-count-build.html#example) in [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html):
+
+```
+SELECT hll_count_estimate(hll_count_merge(a)) AS hll_estimate, hll_count_merge(a) AS merged_sketch
+FROM sketch_of_data_to_count;
+```
+
+hll\_estimate BIGINT merged\_sketch BYTEA 6606880 \\x2f4167677265676174654675….
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_max.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_max.md
new file mode 100644
index 0000000..9e32191
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_max.md
@@ -0,0 +1,53 @@
+# [](#max)MAX
+
+Returns the maximum value in its argument. NULL values are ignored. If all inputs are NULL, `MAX` returns NULL.
+
+## [](#syntax)Syntax
+
+```
+MAX(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression whose maximum to determine Any type
+
+## [](#return-types)Return Types
+
+Same as input type
+
+## [](#examples)Examples
+
+**Example**
+
+This code example uses the following `tournaments` table:
+
+name totalprizedollars The Drifting Thunderdome 24,768 The Lost Track Showdown 5,336 The Acceleration Championship 19,274 The Winter Wilderness Rally 21,560 The Circuit Championship 9,739
+
+When used on the `totalprizedollars` column, `MAX` will return the highest value, as follows:
+
+```
+SELECT
+	MAX(totalprizedollars) as maxprize
+FROM
+	tournaments;
+```
+
+**Returns**
+
+`24,768`
+
+**Example**
+
+`MAX` can also work on text or array columns, in which case it returns the lexicographically largest value. In this example, the function assesses the `name` column in the `tournaments` table.
+
+```
+SELECT
+	MAX(name) as maxtournament
+FROM
+	tournaments;
+```
+
+**Returns**
+
+`The Winter Wilderness Rally`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_max_by.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_max_by.md
new file mode 100644
index 0000000..ef3d095
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_max_by.md
@@ -0,0 +1,68 @@
+# [](#max_by)MAX\_BY
+
+Returns the value of the first argument for the row that contains the maximum of the second argument. If the maximum of the second argument is not unique, an arbitrary non-NULL value of the first argument is returned from the set of rows that maximize the second argument. If the first argument is NULL for all rows maximizing the second argument, NULL is returned.
+
+## [](#syntax)Syntax
+
+```
+MAX_BY(<result>, <value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<result>` The column from which the value is returned Any type `<value>` The column that is maximized Any type
+
+## [](#return-types)Return Types
+
+Same as input type of
+
+## [](#examples)Examples
+
+**Example**
+
+This example uses the following table, `tournaments`:
+
+name totalprizedollars The Drifting Thunderdome 24,768 The Lost Track Showdown 5,336 The Acceleration Championship 19,274 The French Grand Prix 237 The Circuit Championship 9,739
+
+In the following code example, `MAX_BY` is used to find the name of the tournament with the highest total prize.
+
+```
+SELECT
+	MAX_BY(name, totalprizedollars) as maxprizetournament
+FROM
+	tournaments
+```
+
+**Returns:** `The Drifting Thunderdome`
+
+**Example**
+
+When multiple rows maximize the second argument, an arbitrary one is chosen, preferring non-NULL values of the first argument:
+
+```
+SELECT MAX_BY(key, value)
+FROM UNNEST(
+    ['a', NULL, 'c', 'd', 'e', NULL],
+    [10,  100,   1,  100, 100, NULL]
+) t(key, value)
+```
+
+**Returns**
+
+`'d'` or `'e'`, as rows 2, 4, and 5 maximize the second argument, but the first argument is NULL for row 2. Because non-NULL values of the first argument exist for the other rows, one of those values is returned. Which of them is non-deterministic, hence this query may return either `'d'` or `'e'`.
+
+**Example**
+
+However, if all rows maximizing the second argument are `NULL` in the first argument, `NULL` is returned:
+
+```
+SELECT MAX_BY(key, value)
+FROM UNNEST(
+    ['a', NULL, 'c', 'd', NULL, 'f'],
+    [10,  100,   1,   2,  100, NULL]
+) t(key, value)
+```
+
+**Returns**
+
+`NULL`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_median.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_median.md
new file mode 100644
index 0000000..e3019ab
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_median.md
@@ -0,0 +1,50 @@
+# [](#median)MEDIAN
+
+Returns the middle value in a given column. If number of values are even, `MEDIAN` returns the average of the two middle values.
+
+## [](#syntax)Syntax
+
+```
+MEDIAN(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The expression used to calculate the median value. `DOUBLE PRECISION`, `REAL`, `BIGINT`, `INT`
+
+## [](#return-type)Return Type
+
+`MEDIAN` returns a value of type `DOUBLE PRECISION`.
+
+- This function ignores `NULL` values.
+- If the input is empty, the function returns `NULL`.
+
+## [](#examples)Examples
+
+**Example**
+
+The following query uses `UNNEST` to convert an array \[1,2,5] into a column, calculates the median value, and returns it as `result`:
+
+```
+SELECT MEDIAN(a) as result FROM UNNEST(array[1,2,5]) as a;
+```
+
+**Returns**
+
+result (DOUBLE PRECISION) 2
+
+The previous code example returns the middle element as the median because the number of elements in the array is odd.
+
+**Example**
+
+The following query uses `UNNEST` to convert an array \[100, NULL, 1, 2, 5] into a column, calculates the median value, and returns it as `result`:
+
+```
+SELECT MEDIAN(a) as result FROM UNNEST(array[100,NULL,1,2,5]) as a;
+```
+
+**Returns**
+
+result (DOUBLE PRECISION) 3.5
+
+The previous code example returns the average of the two middle elements after sorting the values, because the number of non-`NULL` elements is even after ignoring `NULL` values. The average of the middle elements, `2` and `5`, is calculated as : `((2+5)/2)`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_min.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_min.md
new file mode 100644
index 0000000..0f398de
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_min.md
@@ -0,0 +1,51 @@
+# [](#min)MIN
+
+Returns the minimum value in its argument. `NULL` values are ignored. If all inputs are `NULL`, `MIN` returns NULL.
+
+## [](#syntax)Syntax
+
+```
+MIN(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression whose minimum to determine Any type
+
+## [](#return-types)Return Types
+
+Same as input type
+
+## [](#examples)Examples
+
+**Example**
+
+This code example uses the following `tournaments` table:
+
+name totalprizedollars The Drift Championship 22,048 The Lost Track Showdown 5,336 The Acceleration Championship 19,274 The French Grand Prix 237 The Circuit Championship 9,739
+
+When used on the `totalprizedollars` column, `MIN` will return the smallest value.
+
+```
+SELECT
+	MIN(totalprizedollars) as minprize
+FROM
+	tournaments;
+```
+
+**Returns**
+
+`237`
+
+`MIN` can also work on text or array columns, in which case it returns the lexicographically smallest value. In this example, the function assesses the `name` column in the `tournaments` table.
+
+```
+SELECT
+	MIN(name) as mintournament
+FROM
+	tournaments;
+```
+
+**Returns**
+
+`The Acceleration Championship`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_min_by.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_min_by.md
new file mode 100644
index 0000000..cda4b09
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_min_by.md
@@ -0,0 +1,68 @@
+# [](#min_by)MIN\_BY
+
+Returns the value of the first argument for the row that contains the minimum of the second argument. If the minimum of the second argument is not unique, an arbitrary non-NULL value of the first argument is returned from the set of rows that minimize the second argument. If the first argument is NULL for all rows minimizing the second argument, NULL is returned.
+
+## [](#syntax)Syntax
+
+```
+MIN_BY(<result>, <value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<result>` The column from which the value is returned Any type `<value>` The column that is minimized Any type
+
+## [](#return-types)Return Types
+
+Same as input type of
+
+## [](#example)Example
+
+This example uses the following table, `tournaments`:
+
+name totalprizedollars The Drift Championship 22,048 The Lost Track Showdown 5,336 The Acceleration Championship 19,274 The French Grand Prix 237 The Circuit Championship 9,739
+
+In the following code example, `MIN_BY` is used to find the name of the tournament with the lowest total prize:
+
+```
+SELECT
+	MIN_BY(name, totalprizedollars) as minprizetournament
+FROM
+	tournaments
+```
+
+**Returns:**
+
+The French Grand Prix\`
+
+**Example**
+
+When multiple rows minimize the second argument, an arbitrary one is chosen, preferring non-NULL values of the first argument:
+
+```
+SELECT MIN_BY(key, value)
+FROM UNNEST(
+    ['a', NULL, 'c', 'd', 'e', NULL],
+    [10,  1,    100,  1,   1,  NULL]
+) t(key, value)
+```
+
+**Returns**
+
+`'d'` or `'e'`, as rows 2, 4, and 5 minimize the second argument, but the first argument is NULL for row 2. Because non-NULL values of the first argument exist for the other rows, one of those values is returned. Which of them is non-deterministic, hence this query may return either `'d'` or `'e'`.
+
+**Example**
+
+However, if all rows minimizing the second argument are NULL in the first argument, NULL is returned:
+
+```
+SELECT MIN_BY(key, value)
+FROM UNNEST(
+    ['a', NULL, 'c', 'd', NULL, 'f'],
+    [10,  1,    100,  2,   1,  NULL]
+) t(key, value)
+```
+
+**Returns**
+
+`NULL`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_percentile_cont.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_percentile_cont.md
new file mode 100644
index 0000000..9282e44
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_percentile_cont.md
@@ -0,0 +1,91 @@
+# [](#percentile_cont)PERCENTILE\_CONT
+
+Returns the value at the position in an ordered list where a specified percentage falls. If the percentile value does not correspond to an exact data point in the dataset, `PERCENTILE_CONT` interpolates between the two closest values surrounding the specified percentile to estimate the result. The interpolation is based on the dataset’s ascending or descending order.
+
+For example, if you want to find the `40%` percentile on the ordered list `[10,20,30]`, position `1` corresponds to the value `10`, and position `2` corresponds to the value `20`. The position that corresponds to the specified percentile is calculated as `1` plus the percentile multiplied by (`n-1`), where `n` is the number of data points in the set. Then, the `40th` percentile corresponds to `1 + 0.40 * (3 - 1) = 1.8`, which falls between position `1` and `2`, or the values `10` and `20`. Because the desired percentile does not correspond to an exact data point, `PERCENTILE_CONT` interpolates an estimated value using the following formula:
+
+**Formula to interpolate values**
+
+```
+RN = 1 + <percentile> * (<number_of_values> - 1)
+CRN = CEILING(RN)
+FRN = FLOOR(RN)
+EXP_CRN = <sorted_expression>[CRN]
+EXP_FRN = <sorted_expression>[FRN]
+If RN is a whole number, RESULT = <ordered_set>[RN].
+If RN is not a whole number, RESULT = (CRN - RN) * EXP_FRN + (RN - FRN) * EXP_CRN.
+```
+
+**Formula definitions** In the previous formula for interpolation, the following apply:
+
+- `RN`: The row number of the exact position of a value within an ordered dataset.
+- `CRN`: The ceiling row number, which determines the upper row position for interpolation.
+- `FRN`: The floor row number, which determines the lower row position for interpolation.
+- `EXP_CRN`: The value from the sorted dataset that corresponds to the `CRN`, used as the **upper** bound in percentile calculations when interpolation is required.
+- `EXP_FRN`: The value from the sorted dataset that corresponds to the FRN, used as the **lower** bound in percentile calculations when interpolation is required.
+- `<sorted_expression>`: The ordered list of values derived from the input expression, arranged in ascending or descending order, used as the basis for percentile calculations.
+- `<number_of_values>`: The total count of values within the input expression, used to calculate the exact position of a specified percentile by multiplying the percentile (as a decimal) by (`number_of_values` − 1). This calculated position then identifies the two values in the sorted dataset used for interpolation.
+
+In the previous example, `PERCENTILE_CONT` estimates the value between `10` and `20` in the ordered list `[10,20,30]` to find the 40th percentile as follows:
+
+`result = (CRN - RN) * (EXP_FRN) + (RN - FRN) * EXP_CRN = (2 - 1.8) * 10 + (1.8 - 1) * 20 = 18`.
+
+In the previous example, the set `[10,20,30]` is in ascending order. If the set were in descending order as `[30,20,10]`, the `40th` percentile would correspond to:
+
+`result = (CRN - RN) * (EXP_FRN) + (RN - FRN) * EXP_CRN = (2 - 1.8) * 30 + (1.8 - 1) * 20 = 22`.
+
+## [](#syntax)Syntax
+
+```
+PERCENTILE_CONT
+( <percentile> ) WITHIN GROUP ( ORDER BY <expression> [ { ASC | DESC } ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<percentile>` The desired percentile position within the ordered dataset. `DOUBLE PRECISION`, `REAL` literal between 0.0 and 1.0 `<sorted_expression>` The expression used to calculate the percentile, which is sorted in ascending or descending order prior to calculation. `DOUBLE PRECISION`, `REAL`, `BIGINT`, `INT`
+
+## [](#return-types)Return Types
+
+`PERCENTILE_CONT` returns a value of type `DOUBLE PRECISION`.
+
+- This function ignores `NULL` values.
+- This function returns `NULL` if the input is either empty or contains only `NULL` values.
+
+## [](#examples)Examples
+
+These calculations use 1-based indexing, where the first element is at position `1`.
+
+**Example**
+
+The following code example calculates the 20th percentile of values from a generated series ranging from `0` to `5`, and returns it as `result`:
+
+```
+SELECT PERCENTILE_CONT(0.2) WITHIN GROUP (ORDER BY x) as result FROM GENERATE_SERIES(0, 5) as x;
+```
+
+**Returns**
+
+result (DOUBLE PRECISION) 1
+
+The previous code example calculates the 20th percentile from a series that contains the following six values: `0`, `1`, `2`, `3`, `4`, and `5`. The position for the 20th percentile is calculated as follows: `RN = 1 + 0.2 * (6 - 1) = 2`. Since the row number is a whole number, it corresponds directly to the value at position `2`, which is `EXP_RN = 1`, using one-based indexing.
+
+**Example**
+
+The following code example calculates the 20th percentile of values from a generated series ranging from `0` to `6`, interpolates the position, and returns it as `result`:
+
+```
+SELECT PERCENTILE_CONT(0.2) WITHIN GROUP (ORDER BY x) as result FROM GENERATE_SERIES(0, 6) as x;
+```
+
+**Returns**
+
+result (DOUBLE PRECISION) 1.2000000000000002
+
+The previous code example calculates the 20th percentile from a series that contains the following seven values: `0`, `1`, `2`, `3`, `4`, `5`, and `6`. The position for the 20th percentile is calculated as follows: `RN = 1 + 0.2 * (7 - 1) = 2.2`. Since `2.2` is not a whole number, `PERCENTILE_CONT` interpolates the position as follows:
+
+- The `CRN` is `CEILING(2.2) = 3`.
+- The `FRN` is `FLOOR(2.2) = 2`.
+- The `EXP_CRN` is the value at position `3` of the ordered set which is `2` using one-based indexing.
+- The `EXP_FRN` is the value at position `2` of the ordered set which is `1` using one-based indexing.
+- The result is `(CRN - RN) * EXP_FRN + (RN - FRN) * EXP_CRN` which is `(3 − 2.2) × 1 + (2.2 − 2) × 2 = 0.8 + 0.4 = 1.2`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_stddev_pop.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_stddev_pop.md
new file mode 100644
index 0000000..c341e3f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_stddev_pop.md
@@ -0,0 +1,41 @@
+# [](#stddev_pop)STDDEV\_POP
+
+Computes the population standard deviation of all non-`NULL` numeric values produced by an expression. The population standard deviation shows how spread out the values in a population are, by measuring the average distance of each value from the population’s mean. For information about the sample standard deviation, which estimates the spread of values across sample rather than the full population, see [STDDEV\_SAMP](/sql_reference/functions-reference/aggregation/stddev-samp.html).
+
+## [](#syntax)Syntax
+
+```
+STDDEV_POP(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An expression producing numeric values for which to calculate the population standard deviation. `REAL`, `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`STDDEV_POP` returns a result of type `DOUBLE PRECISION`.
+
+### [](#special-cases)Special cases
+
+- If there are no non-`NULL` input values, the result is `NULL`.
+- If the input contains an `Inf` or `NaN` value, the result will be `NaN`.
+
+## [](#example)Example
+
+The following code creates an `exams` table with a `grade` column of type `DOUBLE PRECISION`, and inserts five grade values into it:
+
+```
+CREATE TABLE exams (grade DOUBLE PRECISION);
+INSERT INTO exams VALUES (4.0), (3.7), (3.3), (2.7), (2.7);
+```
+
+The following code calculates the population standard deviation of the grade values from the `exams` table, rounds the result to three decimal places, and returns it as `stddev`:
+
+```
+SELECT ROUND(STDDEV_POP(grade), 3) as stddev from exams;
+```
+
+**Returns** The previous code returns the following result:
+
+stddev (DOUBLE PRECISION) 0.523
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_stddev_samp.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_stddev_samp.md
new file mode 100644
index 0000000..18f4a14
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_stddev_samp.md
@@ -0,0 +1,43 @@
+# [](#stddev_samp)STDDEV\_SAMP
+
+Computes the sample standard deviation of all non-`NULL` numeric values produced by an expression. The sample standard deviation measures how spread out values are in a sample by calculating the square root of the average of squared deviations from the sample mean, using a correction for sample size. For information about the population standard deviation, which estimates the spread of values in the full population, see [STDDEV\_POP](/sql_reference/functions-reference/aggregation/stddev-pop.html).
+
+**Alias**: `STDDEV`
+
+## [](#syntax)Syntax
+
+```
+{ STDDEV | STDDEV_SAMP }(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An expression producing numeric values for which to calculate the sample standard deviation. `REAL`, `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`STDDEV_SAMP` returns a result of type `DOUBLE PRECISION`.
+
+### [](#special-cases)Special cases
+
+- If there is at most one non-`NULL` input value, the result is `NULL`.
+- If the input contains an `Inf` or `NaN` value, the result will be `NaN`.
+
+## [](#example)Example
+
+The following code creates an `exams` table with a `grade` column of type `DOUBLE PRECISION`, and inserts five grade values into it:
+
+```
+CREATE TABLE exams (grade DOUBLE PRECISION);
+INSERT INTO exams VALUES (4.0), (3.7), (3.3), (2.7), (2.7);
+```
+
+The following code calculates the sample standard deviation of the grade values from the `exams` table, rounds the result to three decimal places, and returns it as `stddev`:
+
+```
+SELECT ROUND(STDDEV_SAMP(grade), 3) as stddev from exams;
+```
+
+**Returns** The previous code returns the following result:
+
+stddev (DOUBLE PRECISION) 0.585
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_sum.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_sum.md
new file mode 100644
index 0000000..2a1f541
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_sum.md
@@ -0,0 +1,59 @@
+# [](#sum)SUM
+
+Calculates the sum of an expression.
+
+## [](#syntax)Syntax
+
+```
+SUM ([ DISTINCT ] <value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The expression used to calculate the sum. Any numeric type
+
+Valid values for `<value>` include column names or expressions that evaluate to numeric values. When `DISTINCT` is being used, only the unique number of rows with no `NULL` values are summed.
+
+## [](#return-types)Return Types
+
+`NUMERIC`
+
+## [](#precision-and-determinism)Precision and Determinism
+
+Applying `SUM` to REAL and DOUBLE PRECISION is subject to [floating point arithmetic accuracy limitations](https://en.wikipedia.org/wiki/Floating-point_arithmetic#Accuracy_problems) and its resulting error. This error may add up when aggregating multiple values.
+
+The order of operations while computing the aggregate is non-deterministic. This can lead to varying total floating point error when running a query multiple times. If this is not acceptable for your use-case, aggregate on [NUMERIC](/sql_reference/numeric-data-type) data instead.
+
+## [](#examples)Examples
+
+**Example**
+
+This code example uses the following `tournaments` table:
+
+name totalprizedollars The Drifting Thunderdome 24,768 The Lost Track Showdown 5,336 The Acceleration Championship 19,274 The Winter Wilderness Rally 21,560 The Circuit Championship 9,739 The Singapore Grand Prix 19,274
+
+```
+SELECT
+	SUM(totalprizedollars)
+FROM
+	tournaments
+```
+
+**Returns**
+
+`99,951`
+
+**Example**
+
+For the following code example, since both the Singapore Grand Prix and The Acceleration Championship have the same total prize of `19,274`, only one of these values in this sum in included:
+
+```
+SELECT
+	SUM (DISTINCT totalprizedollars)
+FROM
+	tournaments
+```
+
+**Returns**
+
+`80,677`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_variance_pop.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_variance_pop.md
new file mode 100644
index 0000000..bb4ad9b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_variance_pop.md
@@ -0,0 +1,41 @@
+# [](#var_pop)VAR\_POP
+
+Computes the population variance of all non-`NULL` numeric values produced by an expression. The population variance measures the average of the squared differences from the population mean, indicating how spread out the values are within the entire population. For information about the sample variance, which measures how spread out the values are within a sample, see [VAR\_SAMP](/sql_reference/functions-reference/aggregation/variance-samp.html).
+
+## [](#syntax)Syntax
+
+```
+VAR_POP(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An expression producing numeric values for which to calculate the population variance. `REAL`, `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`VAR_POP` returns a result of type `DOUBLE PRECISION`.
+
+### [](#special-cases)Special cases
+
+- If there are no non-`NULL` input values, the result is `NULL`.
+- If the input contains an `Inf` or `NaN` value, the result will be `NaN`.
+
+## [](#example)Example
+
+The following code creates an `exams` table with a `grade` column of type `DOUBLE PRECISION`, and inserts five grade values into it:
+
+```
+CREATE TABLE exams (grade DOUBLE PRECISION);
+INSERT INTO exams VALUES (4.0), (3.7), (3.3), (2.7), (2.7);
+```
+
+The following code calculates the population variance of the grade values from the `exams` table, rounds the result to three decimal places, and returns it as `variance`:
+
+```
+SELECT ROUND(VAR_POP(grade), 3) as variance from exams;
+```
+
+**Returns** The previous code returns the following result:
+
+variance (DOUBLE PRECISION) 0.274
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_variance_samp.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_variance_samp.md
new file mode 100644
index 0000000..bed0447
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_aggregation_variance_samp.md
@@ -0,0 +1,43 @@
+# [](#var_samp)VAR\_SAMP
+
+Computes the sample variance of all non-`NULL` numeric values produced by an expression. The sample variance measures the average of the squared differences from the sample mean, indicating how spread out the values are within a sample. For information about the population variance, which measures how spread out the values are within the full population, see [VAR\_POP](/sql_reference/functions-reference/aggregation/variance-pop.html).
+
+**Alias**: `VARIANCE`
+
+## [](#syntax)Syntax
+
+```
+{ VARIANCE | VAR_SAMP }(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An expression producing numeric values for which to calculate the sample variance. `REAL`, `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`VAR_SAMP` returns a result of type `DOUBLE PRECISION`.
+
+### [](#special-cases)Special cases
+
+- If there is at most one non-`NULL` input value, the result is `NULL`.
+- If the input contains an `Inf` or `NaN` value, the result will be `NaN`.
+
+## [](#example)Example
+
+The following code creates an `exams` table with a `grade` column of type `DOUBLE PRECISION`, and inserts five grade values into it:
+
+```
+CREATE TABLE exams (grade DOUBLE PRECISION);
+INSERT INTO exams VALUES (4.0), (3.7), (3.3), (2.7), (2.7);
+```
+
+The following code calculates the sample variance of the grade values from the `exams` table, rounds the result to three decimal places, and returns it as `variance`:
+
+```
+SELECT ROUND(VAR_SAMP(grade), 3) as variance from exams;
+```
+
+**Returns** The previous code returns the following result:
+
+variance (DOUBLE PRECISION) 0.342
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array.md
new file mode 100644
index 0000000..69154d0
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array.md
@@ -0,0 +1,19 @@
+## [](#array-functions)Array functions
+
+* * *
+
+- [ARRAY\_CONCAT](/sql_reference/functions-reference/array/array-concat.html)
+- [ARRAY\_CONTAINS](/sql_reference/functions-reference/array/array-contains.html)
+- [ARRAY\_COUNT](/sql_reference/functions-reference/array/array-count.html)
+- [ARRAY\_COUNT\_DISTINCT](/sql_reference/functions-reference/array/array-count-distinct.html)
+- [ARRAY\_DISTINCT](/sql_reference/functions-reference/array/array-distinct.html)
+- [ARRAY\_FLATTEN](/sql_reference/functions-reference/array/flatten.html)
+- [ARRAY\_LENGTH](/sql_reference/functions-reference/array/array-length.html)
+- [ARRAY\_MAX](/sql_reference/functions-reference/array/array-max.html)
+- [ARRAY\_MIN](/sql_reference/functions-reference/array/array-min.html)
+- [ARRAY\_REVERSE](/sql_reference/functions-reference/array/array-reverse.html)
+- [ARRAY\_REVERSE\_SORT](/sql_reference/functions-reference/array/array-reverse-sort.html)
+- [ARRAY\_SORT](/sql_reference/functions-reference/array/array-sort.html)
+- [ARRAY\_SUM](/sql_reference/functions-reference/array/array-sum.html)
+- [ARRAY\_TO\_STRING](/sql_reference/functions-reference/array/array-to-string.html)
+- [INDEX\_OF](/sql_reference/functions-reference/array/index-of.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_concat.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_concat.md
new file mode 100644
index 0000000..6321c98
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_concat.md
@@ -0,0 +1,62 @@
+# [](#array_concat)ARRAY\_CONCAT
+
+**Alias:** `ARRAY_CAT`
+
+Combines one or more arrays that are passed as arguments.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_CONCAT(<array> [, ...n])
+```
+
+**—OR—**
+
+```
+<expression> || <expression>
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array> [, ...n]` The arrays to be combined. If only one array is given, an identical array is returned. `ARRAY`
+
+### [](#-operator)`||` operator
+
+Parameter Description Supported input types `<expression>` The expressions to be concatenated. `TEXT` / `ARRAY`, but at least one `ARRAY`
+
+To enable array concatenation, one parameter to the `||` operator must be of type `ARRAY`, while the other parameter can be a string whose value can be converted to the underlying type of the array parameter, or it can be an array of the same type.
+
+If one parameter to the `||` operator is `NULL`, the result will be the non-null parameter; if both parameters are `NULL`, the result will be `NULL`.
+
+The concatenation operator `||` can also be used for [string concatenation](/sql_reference/functions-reference/string/concat.html).
+
+## [](#return-type)Return Type
+
+`ARRAY` of the same type as the input arrays
+
+## [](#example)Example
+
+In the following example, two arrays are combined to show all of the levels in a particular game:
+
+```
+SELECT
+    ARRAY_CONCAT([ 1, 2, 3, 4 ], [ 5, 6, 7, 8, 9, 10 ]) AS levels;
+```
+
+**Returns**: `[1, 2, 3, 4, 5, 6, 7, 8, 9, 10]`
+
+The following example concatenates two integer arrays:
+
+```
+SELECT ARRAY[1,2] || ARRAY[3];
+```
+
+**Returns**: `[1, 2, 3]`
+
+The following example concatenates a string, whose value can be converted to integer, with an integer array:
+
+```
+SELECT '{2}' || ARRAY[1];
+```
+
+**Returns**: `[2, 1]`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_contains.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_contains.md
new file mode 100644
index 0000000..af10846
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_contains.md
@@ -0,0 +1,42 @@
+# [](#array_contains)ARRAY\_CONTAINS
+
+Returns `true` if a specified argument is present in the array, or `false` otherwise. Note that `ARRAY_CONTAINS` employs `IS NOT DISTINCT FROM` semantics when comparing values, i.e. `NULL` is considered equal to `NULL`.
+
+**Alias:** `CONTAINS`
+
+## [](#syntax)Syntax
+
+```
+ARRAY_CONTAINS(<array>, <value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array to be checked for the given element. `ARRAY` `<value>` The element to be searched for within the array Any type that can be converted to the element type of the array
+
+## [](#return-type)Return Type
+
+The `BOOLEAN` value `true` if the element to be searched is present in the array, or `false` otherwise.
+
+## [](#example)Example
+
+```
+SELECT
+	ARRAY_CONTAINS(['sabrina21', 'rileyjon', 'ywilson', 'danielle53', NULL], 'danielle53');
+```
+
+**Returns**: `true`, since `'danielle53'` is an element of the input array.
+
+```
+SELECT
+	ARRAY_CONTAINS(['sabrina21', 'rileyjon', 'ywilson', NULL] , 'danielle53');
+```
+
+**Returns**: `false`, since `'danielle53'` is not an element of the input array.
+
+```
+SELECT
+	ARRAY_CONTAINS(['sabrina21', 'rileyjon', 'ywilson', NULL] , NULL);
+```
+
+**Returns**: `true`, since `NULL` is an element of the input array.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_count.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_count.md
new file mode 100644
index 0000000..9b5e788
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_count.md
@@ -0,0 +1,37 @@
+# [](#array_count)ARRAY\_COUNT
+
+Counts the number of elements in an array for which `function(array[i])` evaluates to TRUE, if a function is provided. If `<function>` is not provided, counts the number of elements in the array that evaluate to TRUE, equivalent to using `x -> x`. To count the elements in an array without any conditions, use the [ARRAY\_LENGTH](/sql_reference/functions-reference/array/array-length.html) function instead.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_COUNT(<function>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<function>` Optional. A [Lambda function](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html#lambda-function-general-syntax) used to check elements in the array. If `<function>` is not provided, `x -> x` is used. Any Lambda function returning `BOOLEAN` `<array>` An array of elements Any `ARRAY` type if `<function>` is provided, else `ARRAY(BOOLEAN)`
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#examples)Examples
+
+The example below searches through the array for any elements that are greater than 3. Only one number that matches this criteria is found, so the function returns `1`
+
+```
+SELECT
+	ARRAY_COUNT(x -> x > 3, [ 1, 2, 3, 9, NULL ]) AS levels;
+```
+
+**Returns**: `1`
+
+In this example below, there is no `<function>` provided in the `ARRAY_COUNT` function. This means the function will count all of the elements in the array that evaluate to TRUE. Below, this is the case for all values except `FALSE` and `null`:
+
+```
+SELECT
+	ARRAY_COUNT([TRUE, FALSE, 2::BOOLEAN, 3 is not null, null is null, null]) AS levels;
+```
+
+**Returns**: `4`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_count_distinct.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_count_distinct.md
new file mode 100644
index 0000000..5b4a337
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_count_distinct.md
@@ -0,0 +1,25 @@
+# [](#array_count_distinct)ARRAY\_COUNT\_DISTINCT
+
+Returns the number of distinct (unique) elements in the array. As with `COUNT` and `COUNT(DISTINCT ...)` aggregations, `NULL` is not counted as a value if it occurs.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_COUNT_DISTINCT(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array of which to count the distinct elements. Any `ARRAY` type
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#example)Example
+
+```
+SELECT ARRAY_COUNT_DISTINCT([ 1, 2, 4, 5, 2, NULL, 5, 1 ]) AS res;
+```
+
+**Returns**: `4`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_distinct.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_distinct.md
new file mode 100644
index 0000000..0906d13
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_distinct.md
@@ -0,0 +1,28 @@
+# [](#array_distinct)ARRAY\_DISTINCT
+
+Returns an array containing only the *unique* elements of the given array. If the given array contains multiple identical members, the returned array will include only a single member of that value. NULL is considered a value like any other, meaning that if the array contains one or more NULLs, the returned array will contain NULL.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_DISTINCT(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array to be deduplicated `ARRAY`
+
+## [](#return-type)Return Type
+
+`ARRAY` of the same type as the input array
+
+## [](#example)Example
+
+In the following example, the unique levels of the game are returned in an array called `levels`:
+
+```
+SELECT
+	ARRAY_DISTINCT([ 1, 1, 2, 2, 3, 4, 1, NULL, 2, NULL ]) AS levels;
+```
+
+**Returns**: `[1,2,3,4,NULL]`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_length.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_length.md
new file mode 100644
index 0000000..0cae244
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_length.md
@@ -0,0 +1,35 @@
+# [](#array_length)ARRAY\_LENGTH
+
+Returns the length of the given array, i.e., how many elements it contains. Produces `NULL` for `NULL` arrays.
+
+**Alias:** [LENGTH](/sql_reference/functions-reference/string/length.html) (when used with an array argument)
+
+## [](#syntax)Syntax
+
+```
+ARRAY_LENGTH(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array whose length should be calculated `ARRAY`
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#example)Example
+
+```
+SELECT
+	ARRAY_LENGTH([ 1, 2, 3, 4 ]) AS levels;
+```
+
+**Returns**: `4`
+
+```
+SELECT
+	ARRAY_LENGTH([ [ 1, 2, 3 ], [ 4, 5, 6, 7 ]) AS levels;
+```
+
+**Returns**: `2`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_max.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_max.md
new file mode 100644
index 0000000..7b3846d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_max.md
@@ -0,0 +1,28 @@
+# [](#array_max)ARRAY\_MAX
+
+Returns the maximum element in an array.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_MAX(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array or array-type column to be checked `ARRAY`
+
+## [](#return-type)Return Type
+
+Same as the element type of the array.
+
+## [](#example)Example
+
+The following example calculates the maximum number in the `levels` array:
+
+```
+SELECT
+	ARRAY_MAX([ 1, 2, 3, 4 ]) AS levels;
+```
+
+**Returns**: `4`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_min.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_min.md
new file mode 100644
index 0000000..d1153e6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_min.md
@@ -0,0 +1,28 @@
+# [](#array_min)ARRAY\_MIN
+
+Returns the minimum element in an array.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_MIN(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array or array-type column to be checked `ARRAY`
+
+## [](#return-type)Return Type
+
+Same as the element type of the array.
+
+## [](#example)Example
+
+The following example calculates the minimum number in the `levels` array:
+
+```
+SELECT
+	ARRAY_MIN([ 1, 2, 3, 4 ]) AS levels;
+```
+
+**Returns**: `1`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_reverse.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_reverse.md
new file mode 100644
index 0000000..47e8522
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_reverse.md
@@ -0,0 +1,37 @@
+# [](#array_reverse)ARRAY\_REVERSE
+
+Returns an array of the same size and type as the original array, with the elements in reverse order. Nulls are retained.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_REVERSE(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array to be reversed `ARRAY` of any type
+
+## [](#return-type)Return Type
+
+`ARRAY` of the same type as the input array
+
+## [](#example)Example
+
+The following example returns the reverse of the input array:
+
+```
+SELECT
+	ARRAY_REVERSE([ 1, 2, 3, 6 ]);
+```
+
+**Returns**: `[6,3,2,1]`
+
+Only the outermost array is reversed for nested arrays:
+
+```
+SELECT
+	ARRAY_REVERSE([[1,2,3], [4,5], NULL, [7], [8,9]]);
+```
+
+**Returns**: `[[8,9], [7], NULL, [4,5], [1,2,3]]`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_reverse_sort.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_reverse_sort.md
new file mode 100644
index 0000000..c0262b9
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_reverse_sort.md
@@ -0,0 +1,37 @@
+# [](#array_reverse_sort)ARRAY\_REVERSE\_SORT
+
+Returns the elements of the input array in descending order.
+
+If the argument `<function>` is provided, the sorting order is determined by the result of applying `<function>` on each element of the array.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_REVERSE_SORT([<function>,] <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input type `<function>` An optional function to be used to determine the sort order. Any lambda function that takes the elements of `<array>` as input `<array>` The array to be sorted. Any array
+
+## [](#return-type)Return Type
+
+`ARRAY` of the same type as the input array
+
+## [](#example)Example
+
+```
+SELECT
+	ARRAY_REVERSE_SORT([ 4, 1, 3, 2 ]);
+```
+
+**Returns**: `[4,3,2,1]`
+
+In this example below, the modulus operator is used to calculate the remainder on any odd numbers. Therefore `ARRAY_REVERSE_SORT` puts the lower (even) numbers last in the results.
+
+```
+SELECT
+	ARRAY_REVERSE_SORT(x -> x % 2, [ 4, 1, 3, 2 ]);
+```
+
+**Returns**: `[1,3,4,2]`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_sort.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_sort.md
new file mode 100644
index 0000000..0500a3b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_sort.md
@@ -0,0 +1,37 @@
+# [](#array_sort)ARRAY\_SORT
+
+Returns the elements of the input array in ascending order.
+
+If the argument `<function>` is provided, the sorting order is determined by the result of applying `<function>` on each element of the array.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_SORT([<function>,] <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input type `<function>` An optional function to be used to determine the sort order. Any lambda function that takes the elements of `<array>` as input `<array>` The array to be sorted. Any array
+
+## [](#return-type)Return Type
+
+`ARRAY` of the same type as the input array
+
+## [](#example)Example
+
+```
+SELECT
+	ARRAY_SORT([ 4, 1, 3, 2 ]);
+```
+
+**Returns**: `[1,2,3,4]`
+
+In this example below, the modulus operator is used to calculate the remainder on any odd numbers. Therefore `ARRAY_SORT` puts the higher (odd) numbers last in the results.
+
+```
+SELECT
+	ARRAY_SORT(x -> x % 2, [ 4, 1, 3, 2 ]);
+```
+
+**Returns**: `[4,2,1,3]`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_sum.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_sum.md
new file mode 100644
index 0000000..ef3e43c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_sum.md
@@ -0,0 +1,26 @@
+# [](#array_sum)ARRAY\_SUM
+
+Returns the sum of elements of `<array>`.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_SUM(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array to be used to calculate the function. Any array of numeric types
+
+## [](#return-type)Return Type
+
+The return type is `BIGINT` if the element type of `<array>` is `INT` and `DOUBLE PRECISION` if the element type is `REAL`. Otherwise, it matches the element type.
+
+## [](#example)Example
+
+```
+SELECT
+	ARRAY_SUM([ 4, 1, 3, 2 ]) AS levels;
+```
+
+**Returns**: `10`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_to_string.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_to_string.md
new file mode 100644
index 0000000..4a74868
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_array_to_string.md
@@ -0,0 +1,48 @@
+# [](#array_to_string)ARRAY\_TO\_STRING
+
+Converts each array element to its text representation, and concatenates those using an optional delimiter. If no delimiter is provided, an empty string is used instead. `NULL` array elements are omitted.
+
+**Alias:** `ARRAY_JOIN`
+
+## [](#syntax)Syntax
+
+```
+ARRAY_TO_STRING(<array>[, <delimiter>])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` An array to be concatenated `ARRAY` `<delimiter>` The delimiter used for concatenating the array elements `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#example)Example
+
+In the example below, the three elements are concatenated with no delimiter.
+
+```
+SELECT
+	ARRAY_TO_STRING([ '1', '2', '3' ]) AS levels;
+```
+
+**Returns**: `123`
+
+In this example below, the levels are concatenated separated by a comma.
+
+```
+SELECT
+	ARRAY_TO_STRING([ '1', '2', '3' ], ',') AS levels;
+```
+
+**Returns**: `1,2,3`
+
+In this example below, the elements of a nested array containing a `NULL` are concatenated.
+
+```
+SELECT
+	ARRAY_TO_STRING([ [ 1, 2 ], [3, 4], [NULL, 5] ], ',') AS levels;
+```
+
+**Returns**: `1,2,3,4,5`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_flatten.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_flatten.md
new file mode 100644
index 0000000..96f01a2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_flatten.md
@@ -0,0 +1,33 @@
+# [](#array_flatten)ARRAY\_FLATTEN
+
+Converts an array of arrays into a flat array. For every element that is an array, this function extracts its elements into the new array. The resulting flattened array contains all the elements from all source arrays.
+
+The function:
+
+- Applies to one level of nested arrays.
+- Does not accept arrays that are already flat.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_FLATTEN(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array of arrays to be flattened Any `ARRAY` of `ARRAY` types
+
+## [](#return-type)Return Type
+
+`ARRAY` of the same type as the input array
+
+## [](#example)Example
+
+The following example flattens multiple arrays of level IDs:
+
+```
+SELECT
+	ARRAY_FLATTEN([ [ [ 1, 2 ] ], [ [ 2, 3 ], [ 3, 4 ] ] ])
+```
+
+**Returns**: `[ [ 1, 2 ], [ 2, 3 ], [ 3, 4 ] ]`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_index_of.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_index_of.md
new file mode 100644
index 0000000..977846e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_array_index_of.md
@@ -0,0 +1,28 @@
+# [](#index_of)INDEX\_OF
+
+Returns the index position of the first occurrence of the element in the array (or `0` if not found).
+
+## [](#syntax)Syntax
+
+```
+INDEX_OF(<array>, <value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array to be analyzed `ARRAY` `<value>` The element from the array that is to be matched Any integer that corresponds to an element in the array
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#example)Example
+
+The following example returns the index position of the 5 in the `levels` array:
+
+```
+SELECT
+	INDEX_OF([ 1, 3, 4, 5, 7 ], 5) AS levels;
+```
+
+**Returns**: `4`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea.md
new file mode 100644
index 0000000..d337aa2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea.md
@@ -0,0 +1,7 @@
+## [](#binary-functions)Binary functions
+
+* * *
+
+- [CONVERT\_FROM](/sql_reference/functions-reference/bytea/convert-from.html)
+- [DECODE](/sql_reference/functions-reference/bytea/decode.html)
+- [ENCODE](/sql_reference/functions-reference/bytea/encode.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_convert_from.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_convert_from.md
new file mode 100644
index 0000000..890e75b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_convert_from.md
@@ -0,0 +1,77 @@
+# [](#convert_from)CONVERT\_FROM
+
+Converts a binary string from a specified encoding to the `TEXT` data type, using the database’s encoding.
+
+## [](#syntax)Syntax
+
+```
+CONVERT_FROM
+(<bytes>, <src_encoding>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<bytes>` A sequence of bytes representing text in `<src_encoding>`. `BYTEA` `<src_encoding>` The encoding from which the src `<bytes>` are derived, which must be constant. The supported source encoding aligns with those supported in the [ICU library](https://icu.unicode.org/). `TEXT`
+
+## [](#return-type)Return Type
+
+`CONVERT_FROM` returns a value of type `TEXT`.
+
+## [](#errors)Errors
+
+If `<src_encoding>` is invalid, an error is thrown. If `<bytes>` are malformed according to `<src_encoding>`, the behavior is undefined and may result in replacement characters or errors, depending on the encoding. For example, in `UTF-8` encoding, malformed bytes are replaced with the � character.
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example uses `CONVERT_FROM` to convert the binary input `\x1212003100` of type `BYTEA` into a `TEXT` string using the `UTF-16` encoding. All results are displayed in `UTF-8` encoding:
+
+```
+SELECT CONVERT_FROM('\x1212003100'::BYTEA, 'utf16');
+```
+
+**Returns**
+
+The result, `ሒ1�` consists of:
+
+- `ሒ`, the `UTF-16` representation of `1212`.
+- `1`, the `UTF-16` representation of `0031`.
+- The replacement character `�`. Because `00` is a single byte, it does not form a valid `UTF-16` sequence.
+
+**Example**
+
+The following code example uses `CONVERT_FROM` to convert the binary input `\x31a031ffffffff` of type `BYTEA` into a `TEXT` string using the `windows-1252` encoding:
+
+```
+SELECT CONVERT_FROM('\x31a031ffffffff'::BYTEA, 'windows-1252');
+```
+
+**Returns**
+
+The result, `1 1ÿÿÿÿ`, consists of:
+
+- `1`, the windows-1252 representation of `31`.
+- ` `, the windows-1252 representation of the [non-breaking space character](https://en.wikipedia.org/wiki/Non-breaking_space) a0.
+- `ÿ`, the windows-1252 representation of `ff`.
+
+**Example**
+
+The following code example creates a table, which represents an external table, with a `BYTEA` column that represents text data in a custom encoding that is specified during data loading:
+
+```
+CREATE TABLE external_bytes_data (a bytea);
+INSERT INTO external_bytes_data VALUES ('\x1212003100');
+```
+
+**Example**
+
+The following code example converts the `BYTEA` column `col_bytea` into `TEXT` using the specified encoding `UTF-16`, and inserts it into `text_encoded_data` target table:
+
+```
+CREATE TABLE text_encoded_data (a text);
+INSERT INTO text_encoded_data SELECT CONVERT_FROM(a, 'UTF-16') FROM external_bytes_data;
+SELECT * FROM text_encoded_data;
+```
+
+In the previous code example, you can replace the `UTF-16` input encoding with another encoding supported by the [ICU library](https://icu.unicode.org/).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_decode.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_decode.md
new file mode 100644
index 0000000..c1d6cab
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_decode.md
@@ -0,0 +1,48 @@
+# [](#decode)DECODE
+
+Decode binary data from a SQL expression of type `TEXT`.
+
+## [](#syntax)Syntax
+
+```
+DECODE(<expression>, <format>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` A SQL expression of type `TEXT` `TEXT` `<format>` Format to use to decode binary data `HEX`, `ESCAPE`, `BASE64` (case insensitive)
+
+The `HEX` format represents each 4 bits of data as one hexadecimal digit, 0 through f, writing the higher-order digit of each byte first. The `DECODE` function accepts the a-f characters in either upper or lower case. An error is raised when `DECODE` is given invalid hex data — including when given an odd number of characters.
+
+The `ESCAPE` format converts zero bytes and bytes with the high bit set into octal escape sequences (\\nnn) and doubles backslashes. Other byte values are represented literally. The `DECODE` function will raise an error if a backslash is not followed by either a second backslash or three octal digits; it accepts other byte values unchanged.
+
+THE `BASE64` format, per [RFC 2045 Secion 6.8](https://www.rfc-editor.org/rfc/rfc2045#section-6.8), breaks encoded lines at 76 characters using a newline for end of line. The `DECODE` function ignores carriage-return, newline, space, and tab characters. Otherwise, an error is raised when `DECODE`is supplied invalid base64 data — including when trailing padding is incorrect.
+
+## [](#return-type)Return type
+
+`BYTEA`
+
+## [](#example)Example
+
+The following examples decode expressions from the `HEX`, `ESCAPE`, and `BASE64` format:
+
+```
+SELECT
+	DECODE('31323300343536', 'HEX');
+```
+
+**Returns**: `\x31323300343536`
+
+```
+SELECT
+	DECODE('123\000456', 'ESCAPE');
+```
+
+**Returns**: `\x31323300343536`
+
+```
+SELECT
+	DECODE('MTIzADQ1Ng==', 'BASE64');
+```
+
+**Returns**: `\x31323300343536`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_encode.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_encode.md
new file mode 100644
index 0000000..65f9b82
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_bytea_encode.md
@@ -0,0 +1,48 @@
+# [](#encode)ENCODE
+
+Encode binary data into a SQL expression of type `TEXT`.
+
+## [](#syntax)Syntax
+
+```
+ENCODE(<expression>, <format>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` A SQL expression of type `BYTEA` `BYTEA` `<format>` Format to use to encode binary data `HEX`, `ESCAPE`, `BASE64` (case insensitive)
+
+The `HEX` format represents each 4 bits of data as one hexadecimal digit, 0 through f, writing the higher-order digit of each byte first. The `ENCODE` function outputs the a-f hex digits in lower case. Because the smallest unit of data is 8 bits, there are always an even number of characters returned by `ENCODE`.
+
+The `ESCAPE` format converts zero bytes and bytes with the high bit set into octal escape sequences (\\nnn) and doubles backslashes. Other byte values are represented literally.
+
+THE `BASE64` format, per [RFC 2045 Secion 6.8](https://www.rfc-editor.org/rfc/rfc2045#section-6.8), breaks encoded lines at 76 characters using a newline for end of line.
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#example)Example
+
+The following examples encode binary expressions to the `ESCAPE`, `HEX`, and `BASE64` format:
+
+```
+SELECT
+	ENCODE('123\000456'::BYTEA, 'ESCAPE');
+```
+
+**Returns**: `123\000456`
+
+```
+SELECT
+	ENCODE('123\000456'::BYTEA, 'HEX');
+```
+
+**Returns**: `31323300343536`
+
+```
+SELECT
+	ENCODE('123\000456'::BYTEA, 'BASE64');
+```
+
+**Returns**: `MTIzADQ1Ng==`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous.md
new file mode 100644
index 0000000..b123474
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous.md
@@ -0,0 +1,17 @@
+## [](#conditional-and-miscellaneous-functions)Conditional and miscellaneous functions
+
+* * *
+
+- [CASE](/sql_reference/functions-reference/conditional-and-miscellaneous/case.html)
+- [CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/cast.html)
+- [CITY\_HASH](/sql_reference/functions-reference/conditional-and-miscellaneous/city-hash.html)
+- [COALESCE](/sql_reference/functions-reference/conditional-and-miscellaneous/coalesce.html)
+- [GREATEST](/sql_reference/functions-reference/conditional-and-miscellaneous/greatest.html)
+- [HASH](/sql_reference/functions-reference/conditional-and-miscellaneous/hash.html)
+- [IF](/sql_reference/functions-reference/conditional-and-miscellaneous/if.html)
+- [IFNULL](/sql_reference/functions-reference/conditional-and-miscellaneous/ifnull.html)
+- [LEAST](/sql_reference/functions-reference/conditional-and-miscellaneous/least.html)
+- [NULLIF](/sql_reference/functions-reference/conditional-and-miscellaneous/nullif.html)
+- [TRY\_CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/try-cast.html)
+- [TYPEOF](/sql_reference/functions-reference/conditional-and-miscellaneous/typeof.html)
+- [VERSION](/sql_reference/functions-reference/conditional-and-miscellaneous/version.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_case.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_case.md
new file mode 100644
index 0000000..a320dd2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_case.md
@@ -0,0 +1,51 @@
+# [](#case)CASE
+
+Conditional expression similar to if-then-else statements. If the result of the condition is true, then the value of the CASE expression is the result that follows the condition, and the remainder of the CASE expression is not processed. If the result is not true, any subsequent WHEN clauses (conditions) are evaluated in the same manner. If no WHEN condition is true, then the value of the case expression is the result specified in the ELSE clause. If the ELSE clause is omitted and no condition matches, the result is NULL.
+
+## [](#syntax)Syntax
+
+```
+CASE
+    WHEN <condition> THEN <result>
+    [ WHEN ...n ]
+    [ ELSE <result> ]
+END;
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<condition>` A condition can be defined for each `WHEN` clause. `BOOLEAN` `<result>` The result of the CASE expression when the preceding condition holds. Every `THEN` clause receives a single result. All results in a single `CASE` expression must share the same data type. Any
+
+## [](#return-type)Return type
+
+Same data type as `<result>`
+
+## [](#example)Example
+
+This example references a table `player_level` with the following columns and values:
+
+player current\_level kennethpark 3 esimpson 8 sabrina21 11 rileyjon 15 burchdenise 4
+
+The following example categorizes each player by level. If the level is higher than zero and less than 5 they are categorized as beginner. When the level is 6-12, they are categorized as intermediate, and when even higher, they are categorized as expert.
+
+```
+SELECT
+	player,
+	current_level,
+	CASE
+		WHEN current_level > 0 AND current_level <= 5 
+			THEN 'Beginner'
+		WHEN current_level > 5 AND current_level <= 12 
+			THEN 'Intermediate'
+		WHEN current_level > 12
+			THEN 'Expert'
+	END ranking
+FROM
+	player_level
+ORDER BY
+	player;
+```
+
+**Returns**:
+
+player current\_level ranking burchdenise 4 Beginner esimpson 8 Intermediate kennethpark 3 Beginner rileyjon 15 Expert sabrina21 11 Intermediate
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_cast.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_cast.md
new file mode 100644
index 0000000..0313e49
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_cast.md
@@ -0,0 +1,31 @@
+# [](#cast)CAST
+
+Converts data types into other data types based on specified parameters. If the conversion cannot be performed, `CAST` returns an error. To return a `NULL` value instead, use [TRY\_CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/try-cast.html).
+
+## [](#syntax)Syntax
+
+```
+CAST(<value> AS <type>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value to convert or an expression that results in a value to convert. Any `<type>` The target [data type](/sql_reference/data-types.html) (case-insensitive) Any
+
+## [](#return-types)Return Types
+
+Same data type as `<type>`
+
+## [](#example)Example
+
+The following example returns `1` as an integer:
+
+```
+SELECT CAST('1' AS INTEGER) as level;
+```
+
+**Returns**: `1`
+
+`CAST` can also be done by writing the format before the object, for example - `SELECT DATE '2022-01-01'` , `SELECT TIMESTAMP '2022-01-01 01:02:03'.`
+
+`CAST` can also be done by using the `::` operator. For more information, see [:: operator for CAST](/sql_reference/operators.html#-type-cast).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_city_hash.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_city_hash.md
new file mode 100644
index 0000000..710c0b8
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_city_hash.md
@@ -0,0 +1,31 @@
+# [](#city_hash)CITY\_HASH
+
+Takes one or more input parameters of any data type and returns a 64-bit non-cryptographic hash value. `CITY_HASH` uses the CityHash algorithm for string data types, implementation-specific algorithms for other data types, and the CityHash combinator to produce the resulting hash value. If any of the inputs is `NULL`, the result will be `NULL`. See [HASH](/sql_reference/functions-reference/conditional-and-miscellaneous/hash.html) if `NULL` values should not produce `NULL`.
+
+## [](#syntax)Syntax
+
+```
+CITY_HASH(<expression>, [, expression [,...]])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An expression that returns any data type that Firebolt supports. Any
+
+## [](#return-type)Return type
+
+`BIGINT`
+
+## [](#example)Example
+
+```
+SELECT CITY_HASH('esimpson', '08-25-2016')
+```
+
+**Returns:** `-6,509,667,128,195,191,394`
+
+```
+SELECT CITY_HASH(NULL, '08-25-2016')
+```
+
+**Returns:** `NULL`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_coalesce.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_coalesce.md
new file mode 100644
index 0000000..816385f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_coalesce.md
@@ -0,0 +1,27 @@
+# [](#coalesce)COALESCE
+
+Checks from left to right for the first non-NULL argument found for each entry parameter pair.
+
+## [](#syntax)Syntax
+
+```
+COALESCE(<expression> [,...])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression(s) to coalesce. Any
+
+## [](#return-types)Return Types
+
+Same as input type
+
+## [](#example)Example
+
+The following example returns the first non-NULL value provided, which is the username `esimpson`:
+
+```
+SELECT COALESCE(NULL, 'esimpson','sabrina21') AS nicknames;
+```
+
+**Returns:** `esimpson`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_greatest.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_greatest.md
new file mode 100644
index 0000000..4a3bb3c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_greatest.md
@@ -0,0 +1,25 @@
+# [](#greatest)GREATEST
+
+The GREATEST function selects the largest value from a list of any number of expressions. The expressions must all be convertible to a common data type, which will be the type of the result. NULL values in the argument list are ignored. The result will be NULL only if all the expressions evaluate to NULL.
+
+## [](#syntax)Syntax
+
+```
+GREATEST(<expression> [,...])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression(s) to select greatest value. Any
+
+## [](#return-types)Return Types
+
+Same as input type
+
+## [](#example)Example
+
+```
+SELECT GREATEST(NULL, 2^3, 3^2)
+```
+
+**Returns:** `9`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_hash.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_hash.md
new file mode 100644
index 0000000..10cf53a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_hash.md
@@ -0,0 +1,31 @@
+# [](#hash)HASH
+
+Takes one or more input parameters of any data type and returns a 64-bit non-cryptographic hash value. `HASH` uses the CityHash algorithm for string data types, implementation-specific algorithms for other data types, and the CityHash combinator to produce the resulting hash value. `NULL` values of any type get the same fixed value. See [CITY\_HASH](/sql_reference/functions-reference/conditional-and-miscellaneous/city-hash.html) if `NULL` values should produce `NULL`.
+
+## [](#syntax)Syntax
+
+```
+HASH(<expression>, [, expression [,...]])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An expression that returns any data type that Firebolt supports. Any
+
+## [](#return-type)Return type
+
+`BIGINT`
+
+## [](#example)Example
+
+```
+SELECT HASH('esimpson', '08-25-2016')
+```
+
+**Returns:** `-6,509,667,128,195,191,394`
+
+```
+SELECT HASH(NULL, '08-25-2016')
+```
+
+**Returns:** `7610523868633494549`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_if.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_if.md
new file mode 100644
index 0000000..8699d14
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_if.md
@@ -0,0 +1,34 @@
+# [](#if)IF
+
+Evaluates a condition and returns different results based on whether the condition is true or false. The `IF` function is a simplified alternative to the `CASE` expression for handling conditional logic.
+
+## [](#syntax)Syntax
+
+```
+IF(<condition>, <then>, <else>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<condition>` Condition that the function evaluates. `BOOLEAN`
+
+`<then>` Value returned when evaluates to \`true\`. Any
+
+`<else>` Value returned when evaluates to \`false\` or \`NULL\`. Must match the data type of . Any
+
+## [](#return-type)Return type
+
+The `IF` function returns the same data type as the and parameters.
+
+## [](#example)Example
+
+The following example uses the `IF` function to determine if the current day is a weekend or weekday:
+
+```
+SELECT IF(EXTRACT(DOW FROM CURRENT_DATE()) % 6 = 0, 'Weekend', 'Weekday')
+```
+
+The previous query returns:
+
+- `Weekend` when the current day is Saturday or Sunday.
+- `Weekday` for any other day.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_ifnull.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_ifnull.md
new file mode 100644
index 0000000..b21ba09
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_ifnull.md
@@ -0,0 +1,32 @@
+# [](#ifnull)IFNULL
+
+Compares two expressions. Returns `<expression1>` if it’s non-NULL, otherwise returns `<expression2>`.
+
+## [](#syntax)Syntax
+
+```
+IFNULL(<expression1>, <expression2>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression1>`, `<expression2>` Expressions that evaluate to any data type that Firebolt supports. Any
+
+## [](#return-types)Return Types
+
+Same as input type
+
+## [](#remarks)Remarks
+
+Use `ZEROIFNULL(<expression>)` as a synonym shorthand for `IFNULL(<expression>, 0)`. `IFNULL(a, b)` has the same behaviour as `COALESCE(a, b)`.
+
+## [](#example)Example
+
+The following truth table demonstrates values that `IFNULL` returns based on the values of two columns: `level` and `player_id`:
+
+```
+SELECT level, player_id, IFNULL(level, player_id), IFNULL(player_id, level)
+FROM players;
+```
+
+level player\_id IFNULL(level,player\_id) IFNULL(player\_id,level) 0 32 0 32 1 null 30 30 null 33 33 33 null null null null
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_least.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_least.md
new file mode 100644
index 0000000..f90791f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_least.md
@@ -0,0 +1,25 @@
+# [](#least)LEAST
+
+The LEAST function selects the smallest value from a list of any number of expressions. The expressions must all be convertible to a common data type, which will be the type of the result. NULL values in the argument list are ignored. The result will be NULL only if all the expressions evaluate to NULL.
+
+## [](#syntax)Syntax
+
+```
+LEAST(<expression> [,...])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression(s) to select smallest value. Any
+
+## [](#return-types)Return Types
+
+Same as input type
+
+## [](#example)Example
+
+```
+SELECT LEAST(NULL, 2^3, 3^2)
+```
+
+**Returns:** `8`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_nullif.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_nullif.md
new file mode 100644
index 0000000..e66bed2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_nullif.md
@@ -0,0 +1,45 @@
+# [](#nullif)NULLIF
+
+The `NULLIF` function compares the values of its parameters and returns `NULL` if they are equal. Otherwise, it returns the value of its first parameter. Therefore, `NULLIF` performs the inverse operation of the [COALESCE](/sql_reference/functions-reference/conditional-and-miscellaneous/coalesce.html) function.
+
+## [](#syntax)Syntax
+
+```
+NULLIF(<expression1>, <expression2>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression1>` Expression of any type that is comparable to the type of `<expression2>` Any `<expression2>` Expression of any type that is comparable to the type of `<expression1>` Any
+
+If `<expression1>` and `<expression2>` have different types, they will be promoted to their least common supertype for the purpose of comparison. The same type promotion rules as for the regular comparison operators (e.g. `=`) apply.
+
+## [](#return-types)Return Types
+
+If `<expression1>` and `<expression2>` have the same type, this will also be the return type of the `NULLIF` function. If `<expression1>` and `<expression2>` have different types, the return type will be the least common supertype to which they are promoted for comparison purposes.
+
+## [](#example)Example
+
+This example below highlights an instance where `NULL` would be returned from `NULLIF`:
+
+```
+NULLIF('(none)', '(none)')
+```
+
+**Returns**: The `TEXT` value `NULL`
+
+In the next example, `NULLIF` returns the value of `<expression1>` because it is not equal to the value of `<expression2>`:
+
+```
+NULLIF('Level 4', '(none)')
+```
+
+**Returns**: The `TEXT` value `'Level 4'`
+
+Finally, the following example illustrates type promotion if the parameters to `NULLIF` have different types:
+
+```
+NULLIF(3.14::REAL, 42::BIGINT)
+```
+
+**Returns**: The `DOUBLE` value `3.14`, since the least common supertype of `REAL` and `BIGINT` is `DOUBLE`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_try_cast.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_try_cast.md
new file mode 100644
index 0000000..67f38fd
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_try_cast.md
@@ -0,0 +1,29 @@
+# [](#try_cast)TRY\_CAST
+
+Converts data types into other data types based on the specified parameters. If the conversion cannot be performed, returns a NULL. To return an error message instead, use [CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/cast.html).
+
+TRY\_CAST replaces only execution errors with NULLs. However, during planning, impossible casts between two non-castable types still produce an error because the query is invalid.
+
+## [](#syntax)Syntax
+
+```
+TRY_CAST(<value> AS <type>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value to convert or an expression that results in a value to convert Any `<type>` The target [data type](/sql_reference/data-types.html) (case-insensitive) Any
+
+## [](#return-type)Return Type
+
+Returns `NULL` if the conversion cannot be performed. Otherwise, returns the data type of `<type>`.
+
+## [](#example)Example
+
+The following example attempts to cast the level input as an integer:
+
+```
+SELECT TRY_CAST('1' AS INTEGER) as level, TRY_CAST('level 2' AS INTEGER) as current_level;
+```
+
+**Returns**: `1, null`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_typeof.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_typeof.md
new file mode 100644
index 0000000..e0e841b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_typeof.md
@@ -0,0 +1,27 @@
+# [](#typeof)TYPEOF
+
+Returns the type of a given expression.
+
+## [](#syntax)Syntax
+
+```
+TYPEOF(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression to typeof. Any
+
+## [](#return-types)Return Types
+
+A text of the given expression data type.
+
+## [](#example)Example
+
+The following example returns the type of PI() function:
+
+```
+SELECT TYPEOF(RANDOM()) AS random_data_type;
+```
+
+**Returns:** `double precision`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_version.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_version.md
new file mode 100644
index 0000000..08a5f51
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_conditional_and_miscellaneous_version.md
@@ -0,0 +1,18 @@
+# [](#version)VERSION
+
+Returns the version number information for the Firebolt engine.
+
+## [](#syntax)Syntax
+
+```
+VERSION()
+```
+
+## [](#example)Example
+
+```
+SELECT
+    VERSION();
+```
+
+**Returns**: `3.11.0`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches.md
new file mode 100644
index 0000000..1ef640f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches.md
@@ -0,0 +1,13 @@
+## [](#apache-datasketches-functions)Apache DataSketches functions
+
+[Apache DataSketches](https://datasketches.apache.org/) is a robust library that provides a collection of advanced algorithms for data analysis. These algorithms are designed to work efficiently with large datasets and provide accurate results for various data analysis tasks. The following functions are part of the Apache Datasketches library and can be used in SQL queries to perform advanced data analysis tasks.
+
+### [](#distinct-counting-with-hyperloglog-sketches)Distinct Counting with HyperLogLog Sketches
+
+HyperLogLog (HLL) Sketches are a highly efficient probabilistic data structure used for cardinality estimation, which means they can quickly and accurately count the number of distinct elements in large datasets. The following functions are used to work with HLL sketches in SQL queries: [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html), [APACHE\_DATASKETCHES\_HLL\_MERGE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-merge.html), [APACHE\_DATASKETCHES\_HLL\_ESTIMATE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-estimate.html).
+
+* * *
+
+- [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html)
+- [APACHE\_DATASKETCHES\_HLL\_ESTIMATE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-estimate.html)
+- [APACHE\_DATASKETCHES\_HLL\_MERGE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-merge.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_build.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_build.md
new file mode 100644
index 0000000..68c5de1
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_build.md
@@ -0,0 +1,99 @@
+# [](#apache_datasketches_hll_build)APACHE\_DATASKETCHES\_HLL\_BUILD
+
+An aggregate function that creates a new [HyperLogLog sketch](https://datasketches.apache.org/docs/HLL/HLL.html). This sketch is compatible **only** with the [HyperLogLog sketch](https://datasketches.apache.org/docs/HLL/HLL.html) of the [Apache DataSketches](https://datasketches.apache.org/) library. HyperLogLog (HLL) sketches are a highly efficient probabilistic data structure used for cardinality estimation.
+
+The `APACHE_DATASKETCHES_HLL_BUILD` function is used to create a new HLL (HyperLogLog) sketch from a dataset. This is particularly useful for large datasets where exact counting is computationally expensive.
+
+Multiple sketches can be merged to a single sketch using the aggregate function [APACHE\_DATASKETCHES\_HLL\_MERGE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-merge.html). To estimate the final distinct count value from a sketch, the scalar function [APACHE\_DATASKETCHES\_HLL\_ESTIMATE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-estimate.html) can be used.
+
+`APACHE_DATASKETCHES_HLL_BUILD` requires less memory than exact count distinct aggregation, but also introduces statistical error. For more information see [Apache HyperLogLog sketch docs](https://datasketches.apache.org/docs/HLL/HLL.html).
+
+## [](#syntax)Syntax
+
+```
+APACHE_DATASKETCHES_HLL_BUILD
+(<expression> [,hll_precision => <hll_precision>] [, hll_type => <hll_type>] [, text_utf16_little_endian => <text_utf16_little_endian>])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` Any column name or function that return a column name. `INTEGER`, `BIGINT`, `REAL`, `DOUBLE`, `TEXT` `<hll_precision>` Optional. Literal integer value for precision. If not set explicitly, a precision of 12 is used. Range: 12-20. This value represents the log (2 based) of the size of the sketch. For more information see [Apache HyperLogLog sketch](https://datasketches.apache.org/docs/HLL/HLL.html). `INTEGER` `<hll_type>` Optional. Literal text value to set [hll type](https://datasketches.apache.org/docs/HLL/HLL.html). If not included, the default is ‘HLL\_4’. Valid values are: ‘HLL\_4’, ‘HLL\_6’, ‘HLL\_8’. These values represent different levels of compression of the final HLL array where 4, 6 and 8 refer to the number of bits each bucket of the HLL array is compressed down to. HLL\_4 is the most compressed variant but generally slightly slower than the other two, especially during merge operations. `TEXT` `<text_utf16_little_endian>` Optional. Literal boolean value to specify encoding of text if the `<expression>` is of `TEXT` datatype. By default set to `false` means UTF-8 encoding, if set to `true` it means UTF-16 little endian encoding. `BOOLEAN`
+
+## [](#return-type)Return Type
+
+`BYTEA`
+
+## [](#performance-considerations)Performance Considerations
+
+Using HLL sketches is efficient for large datasets, but the accuracy of the estimate can vary. It is recommended to understand the trade-offs between accuracy and performance when using this function. For more information, see [Apache DataSketches HLL Performance](https://datasketches.apache.org/docs/HLL/HllPerformance.html).
+
+## [](#compatibility-with-other-systems)Compatibility With Other Systems
+
+The created sketch is compatible with all the other systems that support the [HyperLogLog sketch](https://datasketches.apache.org/docs/HLL/HLL.html) of the [Apache DataSketches](https://datasketches.apache.org/) library. Few systems applies different encoding before inserting data to the sketch and after creating the sketch, so the sketches created by this function may be incompatible with them as is, but with encoding modification it should be compatible.
+
+#### [](#utf-16-little-endian-text-encoding)UTF-16 Little Endian Text Encoding
+
+Few vendors ([Imply](https://imply.io/)/[Druid](https://druid.apache.org/)) use UTF-16 Little Endian encoding for text data before inserting it into the sketch. In order to be compatible with them, we added this optional parameter. This transition to UTF-16 little endian encoding is done before hashing (sending the string to the DataSketches lib). For example the string ‘ab’ in UTF-8 encoded as ‘0x3132’. in UTF-16: ‘0x00310032’. in UTF-16LE: ‘0x31003200’.
+
+#### [](#sketch-blob-encoding)Sketch Blob Encoding
+
+Few vendors ([Imply](https://imply.io/)/[Druid](https://druid.apache.org/)) apply different encoding to the sketch blob after creating the sketch. In the Druid Database they apply base64 encoding to the sketch blob, in order to make this function sketch compatible with theirs, you can use the following querys:
+
+In order to export a sketch that is compatible with Druid, you can use the following query:
+
+```
+SELECT REPLACE(ENCODE(APACHE_DATASKETCHES_HLL_BUILD(...), 'base64'), e'\n', '+');
+```
+
+In order to import a sketch that is created with Druid, you can use the following query:
+
+```
+SELECT DECODE(<druid_sketch>, 'base64');
+```
+
+## [](#example)Example
+
+```
+CREATE TABLE data_to_count AS
+SELECT *
+FROM generate_series(0, 10000000, 3) a;
+
+SELECT count(distinct a) AS accurate_count
+FROM data_to_count;
+```
+
+accurate\_count (BIGINT) 3333334
+
+```
+CREATE TABLE data_to_count2 AS
+SELECT *
+FROM generate_series(0, 10000000, 2) a;
+
+SELECT count(distinct a) AS accurate_count
+FROM data_to_count2;
+```
+
+accurate\_count (BIGINT) 5000001
+
+```
+CREATE TABLE sketch_of_data_to_count AS
+SELECT APACHE_DATASKETCHES_HLL_BUILD(a) a
+FROM data_to_count;
+
+INSERT INTO sketch_of_data_to_count
+SELECT APACHE_DATASKETCHES_HLL_BUILD(a)
+FROM data_to_count2;
+
+SELECT APACHE_DATASKETCHES_HLL_ESTIMATE(a) AS estimate, a AS sketch
+FROM sketch_of_data_to_count
+ORDER BY 1;
+```
+
+estimate (BIGINT) sketch (BYTEA) 3333526 \\x0a0107120a180102…. 5001149 \\x0a0107120a180102….
+
+```
+SELECT APACHE_DATASKETCHES_HLL_ESTIMATE(APACHE_DATASKETCHES_HLL_MERGE(a)) AS estimate
+FROM sketch_of_data_to_count;
+```
+
+estimate (BIGINT) 6673219
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_estimate.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_estimate.md
new file mode 100644
index 0000000..6ed0156
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_estimate.md
@@ -0,0 +1,43 @@
+# [](#hll_count_estimate)HLL\_COUNT\_ESTIMATE
+
+A scalar function. Extracts a cardinality estimate of a single [Apache DataSketches HLL sketches](https://datasketches.apache.org/docs/HLL/HLL.html) that was previously built using the aggregate function [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html).
+
+The `APACHE_DATASKETCHES_HLL_ESTIMATE` function is used to estimate the cardinality (number of unique elements) of a dataset represented by an HLL (HyperLogLog) sketch. This is particularly useful for large datasets where exact counting is computationally expensive.
+
+## [](#syntax)Syntax
+
+```
+APACHE_DATASKETCHES_HLL_ESTIMATE
+(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An [Apache DataSketches HLL sketches](https://datasketches.apache.org/docs/HLL/HLL.html) in a valid format, e.g. the output of the [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html) function. `BYTEA`
+
+## [](#return-type)Return Type
+
+`BIGINT`
+
+## [](#error-handling)Error Handling
+
+If the input expression is not a valid [Apache DataSketches HLL sketches](https://datasketches.apache.org/docs/HLL/HLL.html), the function will raise an error. Ensure that the input is correctly formatted and generated by the [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html) function.
+
+## [](#example)Example
+
+Following the [example](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html#example) in [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html):
+
+```
+SELECT APACHE_DATASKETCHES_HLL_ESTIMATE(a) AS estimate
+FROM sketch_of_data_to_count
+ORDER BY 1;
+```
+
+estimate (BIGINT) 3333526 5001149
+
+```
+SELECT APACHE_DATASKETCHES_HLL_ESTIMATE(APACHE_DATASKETCHES_HLL_MERGE(a)) AS estimate
+FROM sketch_of_data_to_count;
+```
+
+hll\_estimate (BIGINT) 6673219
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_merge.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_merge.md
new file mode 100644
index 0000000..7d38514
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_datasketches_apache_datasketches_hll_merge.md
@@ -0,0 +1,38 @@
+# [](#apache_datasketches_hll_merge)APACHE\_DATASKETCHES\_HLL\_MERGE
+
+An aggregate function. Merges one or more [Apache DataSketches HLL sketches](https://datasketches.apache.org/docs/HLL/HLL.html) that were built using the aggregate function [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html) into a new sketch.
+
+In order to get correct results each sketch must be built on the same `<expression>` datatype. Attempts to merge sketches for different datatypes will **NOT** result in an error, and it’s the user responsibility to merge skeches with the same datatype only. For example, you can merge a sketch built from `INTEGER` data with one built from `TEXT` data but the estimated cardinality will be incorrect.
+
+If sketches are with different hll precision and hll type the merged sketch will be built with lowest precision and type of all inputs. For example, you can merge a sketch built with precision 13 and a sketch built with precision 14 and the result precision will be 13.
+
+## [](#syntax)Syntax
+
+```
+APACHE_DATASKETCHES_HLL_MERGE
+(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An [Apache DataSketches HLL sketches](https://datasketches.apache.org/docs/HLL/HLL.html) in a valid format, e.g. the output of the [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html) function. `BYTEA`
+
+## [](#return-type)Return Type
+
+`BYTEA`
+
+## [](#error-handling)Error Handling
+
+If the input expression is not a valid [Apache DataSketches HLL sketches](https://datasketches.apache.org/docs/HLL/HLL.html), the function will raise an error. Ensure that the input is correctly formatted and generated by the [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html) function.
+
+## [](#example)Example
+
+Following the [example](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html#example) in [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html):
+
+```
+SELECT APACHE_DATASKETCHES_HLL_ESTIMATE(APACHE_DATASKETCHES_HLL_MERGE(a)) AS estimate,
+       APACHE_DATASKETCHES_HLL_MERGE(a)                                   AS merged_sketch
+FROM sketch_of_data_to_count;
+```
+
+estimate BIGINT merged\_sketch BYTEA 6673219 \\x0a0107120018000a….
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time.md
new file mode 100644
index 0000000..f18db44
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time.md
@@ -0,0 +1,17 @@
+## [](#date-and-time-functions)Date and time functions
+
+* * *
+
+- [CURRENT\_DATE](/sql_reference/functions-reference/date-and-time/current-date.html)
+- [CURRENT\_TIMESTAMP](/sql_reference/functions-reference/date-and-time/current-timestamptz.html)
+- [DATE](/sql_reference/functions-reference/date-and-time/date.html)
+- [DATE\_ADD](/sql_reference/functions-reference/date-and-time/date-add.html)
+- [DATE\_DIFF](/sql_reference/functions-reference/date-and-time/date-diff.html)
+- [DATE\_TRUNC](/sql_reference/functions-reference/date-and-time/date-trunc.html)
+- [EXTRACT](/sql_reference/functions-reference/date-and-time/extract.html)
+- [LOCALTIMESTAMP](/sql_reference/functions-reference/date-and-time/localtimestamp.html)
+- [TO\_CHAR](/sql_reference/functions-reference/date-and-time/to-char.html)
+- [TO\_DATE](/sql_reference/functions-reference/date-and-time/to-date.html)
+- [TO\_TIMESTAMP](/sql_reference/functions-reference/date-and-time/to-timestamp.html)
+- [TO\_YYYYMM](/sql_reference/functions-reference/date-and-time/to-yyyymm.html)
+- [TO\_YYYYMMDD](/sql_reference/functions-reference/date-and-time/to-yyyymmdd.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_current_date.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_current_date.md
new file mode 100644
index 0000000..0469b92
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_current_date.md
@@ -0,0 +1,35 @@
+# [](#current_date)CURRENT\_DATE
+
+Returns the current local date in the time zone specified in the [session’s `time_zone` setting](/Reference/system-settings.html#setting-the-time-zone).
+
+## [](#syntax)Syntax
+
+The function can be called with or without parentheses:
+
+```
+CURRENT_DATE
+CURRENT_DATE()
+```
+
+## [](#return-type)Return Type
+
+`DATE`
+
+## [](#remarks)Remarks
+
+The function gets the current timestamp from the system, converts it to the time zone specified in the `time_zone` setting, and truncates it to a `DATE` value.
+
+## [](#example)Example
+
+The following example assumes that the current timestamp is `2023-03-03 23:59:00 UTC`. It displays the current date in the time zone `Europe/Berlin`.
+
+```
+SET time_zone = 'Europe/Berlin';
+SELECT CURRENT_DATE();
+```
+
+**Returns**
+
+`2023-03-04`
+
+Notice that the time zone conversion from `UTC` to `Europe/Berlin` causes the resulting date to be `2023-03-04` instead of `2023-03-03`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_current_timestamptz.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_current_timestamptz.md
new file mode 100644
index 0000000..22d6ff0
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_current_timestamptz.md
@@ -0,0 +1,34 @@
+# [](#current_timestamp)CURRENT\_TIMESTAMP
+
+Returns the current timestamp as a `TIMESTAMPTZ` value.
+
+**Alias:** `NOW`
+
+## [](#syntax)Syntax
+
+The function can be called with or without parentheses:
+
+```
+CURRENT_TIMESTAMP
+CURRENT_TIMESTAMP()
+```
+
+## [](#return-type)Return Type
+
+`TIMESTAMPTZ`
+
+## [](#remarks)Remarks
+
+The function gets the current timestamp from the system, and returns it as a `TIMESTAMPTZ` value.
+
+## [](#example)Example
+
+The following example assumes that the current Unix timestamp is `2023-03-03 14:42:31.123456 UTC`.
+
+```
+SET time_zone = 'Europe/Berlin';
+SELECT CURRENT_TIMESTAMP;  --> 2023-03-03 15:42:31.123456+01
+
+SET time_zone = 'America/New_York';
+SELECT CURRENT_TIMESTAMP;  --> 2023-03-03 09:42:31.123456-05
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date.md
new file mode 100644
index 0000000..7565e29
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date.md
@@ -0,0 +1,38 @@
+# [](#date)DATE
+
+Converts a `TIMESTAMP`, `TIMESTAMPTZ`, `DATE`, or `TEXT` value to a `DATE` value. If the conversion cannot be performed, the `DATE` function raises an error.
+
+## [](#syntax)Syntax
+
+```
+DATE(<expression>)
+```
+
+### [](#aliases)Aliases
+
+```
+CAST(<expression> AS DATE)
+<expression>::DATE
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<expression>` The expression that should be converted to a `DATE`.
+
+## [](#return-type)Return Type
+
+The `DATE` function returns a result of type `DATE`. If the conversion cannot be performed, the `DATE` function raises an error. For more information on conversion rules, check out the documentation of the [DATE data type](/sql_reference/date-data-type.html).
+
+## [](#example)Example
+
+The following code example converts the `TEXT` value `1990-01-01` to a `DATE` value representing that date:
+
+```
+SELECT DATE('1990-01-01');
+```
+
+**Returns**
+
+```
+1990-01-01
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_add.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_add.md
new file mode 100644
index 0000000..92e84ad
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_add.md
@@ -0,0 +1,19 @@
+# [](#date_add)DATE\_ADD
+
+Computes a new TIMESTAMP or TIMESTAMPTZ value by adding or subtracting a specified number of time units from a DATE, TIMESTAMP, or TIMESTAMPTZ value. It’s similar to [arithmetic with intervals](/Reference/interval-arithmetic.html), but it also allows using a column reference for the `<quantity>`.
+
+## [](#syntax)Syntax
+
+```
+DATE_ADD('<unit>', <quantity>, <expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<unit>` A TEXT literal specifying the time unit. Must be one of `microsecond`,`millisecond`,`second`,`minute`,`hour`,`day`,`week`,`month`,`quarter`,`year`,`decade`,`century`, or `millennium`. `<quantity>` An INT or BIGINT specifying how often the time unit should be added or subtracted to . `<expression>` An expression evaluating to type DATE, TIMESTAMP, or TIMESTAMPTZ.
+
+## [](#return-types)Return Types
+
+TIMESTAMP if `<expression>` has type DATE or TIMESTAMP. TIMESTAMPTZ if `<expression>` has type TIMESTAMPTZ.
+
+## [](#example)Example
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_diff.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_diff.md
new file mode 100644
index 0000000..bd3d447
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_diff.md
@@ -0,0 +1,27 @@
+# [](#date_diff)DATE\_DIFF
+
+Calculates the difference between `start_timestamp` and `end_timestamp` by the indicated unit.
+
+## [](#syntax)Syntax
+
+```
+DATE_DIFF('<unit>', <start_timestamp>, <end_timestamp>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<unit>` A TEXT literal specifying the time unit. Must be one of `microsecond`, `millisecond`, `second`, `minute`, `hour`, `day`, `week`, `month`, `quarter`, `year`, `decade`, `century`, or `millennium`. `<start_timestamp>` A value expression evaluating to a `TIMESTAMP` or `TIMESTAMPTZ` value. `<end_timestamp>` A value expression evaluating to a `TIMESTAMP` or `TIMESTAMPTZ` value.
+
+## [](#return-type)Return Type
+
+`BIGINT`
+
+## [](#example)Example
+
+```
+SELECT DATE_DIFF('day', '2024-01-01'::TIMESTAMP, '2024-04-15'::TIMESTAMP);
+```
+
+**Returns**
+
+105
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_trunc.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_trunc.md
new file mode 100644
index 0000000..119fc2b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_date_trunc.md
@@ -0,0 +1,47 @@
+# [](#date_trunc)DATE\_TRUNC
+
+Truncates a value (`<expression>`) of type `DATE`, `TIMESTAMP`, or `TIMESTAMPTZ` to the selected precision (`<time_unit>`).
+
+## [](#syntax)Syntax
+
+```
+DATE_TRUNC(<time_unit>, <expression> [, <time_zone> ])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<time_unit>` A TEXT literal with the time unit precision to truncate to. Must be one of `microsecond`, `millisecond`, `second`, `minute`, `hour`, `day`, `week`, `month`, `quarter`, `year`, `decade`, `century` or `millennium`. `<expression>` A value expression evaluating to the DATE, TIMESTAMP, or TIMESTAMPTZ value that should be truncated. `<time_zone>` An optional TEXT literal giving a time zone name.
+
+## [](#return-type)Return Type
+
+DATE if `<expression>` has type DATE, TIMESTAMP if `<expression>` has type TIMESTAMP, TIMESTAMPTZ if `<expression>` has type TIMESTAMPTZ.
+
+## [](#remarks)Remarks
+
+Truncation of TIMESTAMPTZ values is performed after conversion to local time in a particular time zone. For instance, truncation to ‘day’ produces a TIMESTAMPTZ that is midnight in that time zone. By default, the function uses the time zone specified in the session’s `time_zone` setting. Alternatively, if the optional `<time_zone>` argument is provided, the function uses that time zone.
+
+Firebolt raises an error if the optional `<time_zone>` argument is provided for an `<expression>` evaluating to DATE or TIMESTAMP. Firebolt also raises an error if one attempts to truncate a value expression of type DATE to `microsecond`, `millisecond`, `second`, `minute`, or `hour`.
+
+The `DATE_TRUNC` function can be used in the `PARTITION BY` clause of `CREATE TABLE` commands.
+
+```
+CREATE DIMENSION TABLE test (
+  d DATE,
+  t TIMESTAMP
+)
+PARTITION BY DATE_TRUNC('month', d), DATE_TRUNC('hour', t);
+```
+
+## [](#example)Example
+
+The following examples truncate `DATE` and `TIMESTAMP` values without timezones.
+
+You can also truncate `TIMESTAMPTZ` values.
+
+```
+SET time_zone = 'US/Pacific';
+-- Returns 1996-09-02 00:00:00-07
+SELECT DATE_TRUNC('week', TIMESTAMPTZ '1996-09-03 11:19:42.123 Europe/Berlin');  
+-- returns 1996-09-01 15:00:00-07
+SELECT DATE_TRUNC('week', TIMESTAMPTZ '1996-09-03 11:19:42.123 Europe/Berlin', 'Europe/Berlin');
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_extract.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_extract.md
new file mode 100644
index 0000000..26e6fd6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_extract.md
@@ -0,0 +1,40 @@
+# [](#extract)EXTRACT
+
+Retrieves the time unit, such as `year` or `hour`, from a `DATE`, `TIMESTAMP`, or `TIMESTAMPTZ` value.
+
+## [](#syntax)Syntax
+
+```
+EXTRACT(<time_unit> FROM <expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<time_unit>` The time unit to extract from the expression. `microseconds`, `milliseconds`, `second`, `minute`, `hour`, `day`, `week`, `month`, `quarter`, `year`, `decade`, `century`, `millennium` `<expression>` The expression from which the time unit is extracted. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ`
+
+`TIMESTAMPTZ` values are converted to local time according to the session’s `time_zone` setting before extracting the `time_unit`. The set of allowed `time_unit` values depends on the data type of `<expression>`. Furthermore, the return type depends on the `time_unit`.
+
+### [](#time-units)Time Units
+
+Unit Description Supported input types Return type Example `century` Extract the century. The first century starts on `0001-01-01` and ends on `0100-12-31`. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(century FROM TIMESTAMP '0100-12-31'); --> 1` `day` Extract the day (of the month) field. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(day FROM DATE '2001-02-16'); --> 16` `decade` Extract the year field divided by 10. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(decade FROM DATE '0009-12-31'); --> 0` `dow` Extract the day of the week as Sunday (0) to Saturday (6). `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(dow FROM DATE '2022-10-13'); --> 4` `doy` Extract the day of the year (1–365/366). `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(doy FROM DATE '1972-02-29'); --> 60` `epoch` For `TIMESTAMPTZ`, extract the number of seconds since `1970-01-01 00:00:00 UTC`. For `TIMESTAMP`, extract the number of seconds since `1970-01-01 00:00:00` independent of a time zone. `DATE` expressions are implicitly converted to `TIMESTAMP`. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `DECIMAL(38, 9)` `SELECT EXTRACT(epoch FROM TIMESTAMP '2001-02-16 20:38:40.12'); --> 982355920.120000000` `hour` Extract the hour field (0–23). `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(hour FROM TIMESTAMP '2001-02-16 20:38:40.12'); --> 20` `isodow` Extract the day of the week as Monday (1) to Sunday (7). `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(isodow FROM DATE '2022-10-13'); --> 4` `isoyear` Extract the ISO 8601 week-numbering year that the date falls in. Each ISO 8601 week-numbering year begins with the Monday of the week containing the 4th of January; so in early January or late December the ISO year may be different from the Gregorian year. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(isoyear FROM DATE '2006-01-01'); --> 2005` `microseconds` Extract the seconds field, including fractional parts, multiplied by 1,000,000. `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(microseconds FROM TIMESTAMP '2001-02-16 20:38:40.12'); --> 40120000` `millennium` Extract the millennium. The third millennium started on 2001-01-01. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(millennium FROM TIMESTAMP '1000-12-31 23:59:59.999999'); --> 1` `milliseconds` Extract the seconds field, including fractional parts, multiplied by 1,000. `TIMESTAMP`, `TIMESTAMPTZ` `DECIMAL(38, 9)` `SELECT EXTRACT(milliseconds FROM TIMESTAMP '2001-02-16 20:38:40.12'); --> 40120.000000000` `minute` Extract the minutes field (0–59). `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(minute FROM TIMESTAMP '1000-12-31 23:42:59'); --> 42` `month` Extract the number of the month within the year (1–12). `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(month FROM DATE '1000-12-31'); --> 12` `quarter` Extract the quarter of the year (1–4) that the date is in:  
+`[01, 03] -> 1`  
+`[04, 06] -> 2`  
+`[07, 09] -> 3`  
+`[10, 12] -> 4` `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(quarter FROM DATE '1000-10-31'); --> 4` `second` Extract the second’s field, including fractional parts. `TIMESTAMP`, `TIMESTAMPTZ` `DECIMAL(38, 9)` `SELECT EXTRACT(second FROM TIMESTAMP '2001-02-16 20:38:40.12'); --> 40.120000000` `timezone` Extract the time zone offset from UTC, measured in seconds, with a positive sign for zones east of Greenwich. `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(timezone FROM TIMESTAMPTZ '2022-11-29 13:58:23 Europe/Berlin'); --> -28800` (assumes set time zone is ‘US/Pacific’) `timezone_hour` Extract the hour component of the time zone offset. `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(timezone_hour FROM TIMESTAMPTZ '2022-11-29 13:58:23 Europe/Berlin'); --> -8` (assumes set time zone is ‘US/Pacific’) `timezone_minute` Extract the minute component of the time zone offset. `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(timezone_minute FROM TIMESTAMPTZ '2022-11-29 13:58:23 Europe/Berlin'); --> 0` (assumes set time zone is ‘US/Pacific’) `week` Extract the number of the ISO 8601 week-numbering week of the year. By definition, ISO weeks start on Mondays and the first week of a year contains January 4 of that year. It is possible for early-January dates to be part of the 52nd or 53rd week of the previous year, and for late-December dates to be part of the first week of the next year. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ`. `INTEGER` `SELECT EXTRACT(week FROM DATE '2005-01-01'); --> 53`  
+`SELECT EXTRACT(week from DATE '2006-01-01'); --> 52` `year` Extract the year field. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `INTEGER` `SELECT EXTRACT(year FROM TIMESTAMP '2001-02-16'); --> 2001`
+
+## [](#return-types)Return Types
+
+Depending on the requested time unit, either an integer or a decimal.
+
+## [](#remarks)Remarks
+
+The `EXTRACT` function can be used in the `PARTITION BY` clause of `CREATE TABLE` commands.
+
+```
+CREATE DIMENSION TABLE test (
+  d DATE,
+  t TIMESTAMP
+)
+PARTITION BY EXTRACT(month FROM d), EXTRACT(hour FROM t);
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_localtimestamp.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_localtimestamp.md
new file mode 100644
index 0000000..b1a729b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_localtimestamp.md
@@ -0,0 +1,32 @@
+# [](#localtimestamp)LOCALTIMESTAMP
+
+Returns the current local timestamp in the time zone specified in the session’s [`timezone` setting](/Reference/system-settings.html#setting-the-time-zone).
+
+## [](#syntax)Syntax
+
+The function can be called with or without parentheses:
+
+```
+LOCALTIMESTAMP
+LOCALTIMESTAMP()
+```
+
+## [](#return-type)Return Type
+
+`TIMESTAMP`
+
+## [](#remarks)Remarks
+
+The function gets the current timestamp from the system, converts it to the time zone specified in the `timezone` setting, and returns it as a `TIMESTAMP` value.
+
+## [](#example)Example
+
+The following example assumes that the current timestamp is `2023-03-03 14:42:31.123456 UTC`. Observe how it returns different `TIMESTAMP` values for different time zone settings:
+
+```
+SET timezone = 'Europe/Berlin';
+SELECT LOCALTIMESTAMP;  --> 2023-03-03 15:42:31.123456
+
+SET timezone = 'America/New_York';
+SELECT LOCALTIMESTAMP;  --> 2023-03-03 09:42:31.123456
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_char.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_char.md
new file mode 100644
index 0000000..9d1df91
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_char.md
@@ -0,0 +1,39 @@
+# [](#to_char)TO\_CHAR
+
+Converts a value of type `DATE`, `TIMESTAMP`, or `TIMESTAMPTZ` to a formatted string.
+
+## [](#syntax)Syntax
+
+```
+TO_CHAR(<expression>, '<format>')
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` A date or time expression to be converted to text. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ` `<format>` A string literal that specifies the format of the `<expression>` to convert. See below.
+
+Accepted `<format>` patterns include:
+
+Format option Description Example   `HH12` or `HH` Hour of day (01–12) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'hh12 HH'); --> '06 06'`   `HH24` Hour of day (00–23) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'HH24'); --> '18'`   `MI` Minute (00–59) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'MI'); --> '24'`   `SS` Second (00–59) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'SS'); --> '58'`   `SSSS` or `SSSSS` Seconds past midnight (0–86399) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'SSSS'); --> '41098'`   `MS` Millisecond (000–999) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'MS'); --> '085'`   `US` Microsecond (000000–999999) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'US'); --> '085109'`   `Y,YYY` Year (4 or more digits) with comma Y,YYY `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'Y,YYY'); --> '2,023'`   `YYYY` Year (4 or more digits) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'YYYY'); --> '2023'`   `YYY` Last 3 digits of year `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'YYY'); --> '023'`   `YY` Last 2 digits of year `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'YY'); --> '23'`   `Y` Last digit of year `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'Y'); --> '3'`   `IYYY` ISO 8601 week-numbering year (4 or more digits) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'IYYY'); --> '2023'`   `IYY` Last 3 digits of ISO 8601 week-numbering year `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'IYY'); --> '023'`   `IY` Last 2 digits of ISO 8601 `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'IY'); --> '23'`   `I` Last digit of ISO 8601 week-numbering year `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'I'); --> '3'`   `MM` Month number (01–12) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'MM'); --> '03'`   `DDD` Day of year (001–366) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'DDD'); --> '062'`   `DD` Day of month (01–31) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'DD'); --> '03'`   `D` Day of the week, Sunday (1) to Saturday (7) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'D'); --> '6'`   `ID` ISO 8601 day of the week, Monday (1) to Sunday (7) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'ID'); --> '5'`   `W` Week of month (1–5) (the first week starts on the first day of the month) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'W'); --> '1'`   `WW` Week number of year (1–53) (the first week starts on the first day of the year) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'WW'); --> '09'`   `IW` Week number of ISO 8601 week-numbering year (01–53) (the first Thursday of the year is in week 1) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'IW'); --> '09'`   `CC` Century (2 digits) (the twenty-first century starts on 2001-01-01) `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'CC'); --> '21'`   `Q` Single digit quarter `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'Q'); --> '1'`   `AM` or `PM` Meridiem indicator upper case without periods `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58.085109', 'hhAM'); --> '6PM'`   `am` or `pm` Meridiem indicator lower case without periods `TO_CHAR(TIMESTAMPTZ '2023-03-03 09:24:58', 'hhpm'); --> '9am'`   `A.M.` or `P.M.` Meridiem indicator upper case with periods `TO_CHAR(TIMESTAMPTZ '2023-03-03 18:24:58', 'hhP.M.'); --> '6P.M.'`   `a.m.` or `p.m.` Meridiem indicator lower case with periods `TO_CHAR(TIMESTAMPTZ '2023-03-03 09:24:58', 'hha.m.'); --> '9a.m.'`   `MONTH` Full upper case month name (blank-padded to 9 chars) `TO_CHAR(DATE '2023-03-03', 'MONTH'); --> 'MARCH    '` `Month` Full capitalized month name (blank-padded to 9 chars) `TO_CHAR(DATE '2023-08-07', 'Month'); --> 'August   '`   `month` Full lower case month name (blank-padded to 9 chars) `TO_CHAR(DATE '2023-09-10', 'month'); --> 'September'`   `MON` Abbreviated upper case month name (3 chars) `TO_CHAR(DATE '2023-07-03', 'MON'); --> 'JUL'`   `Mon` Abbreviated capitalized month name (3 chars) `TO_CHAR(DATE '2023-01-03', 'Mon'); --> 'Jan'`   `mon` Abbreviated lower case month name (3 chars) `TO_CHAR(DATE '2023-12-03', 'mon'); --> 'dec'`   `DAY` Full upper case day name (blank-padded to 9 chars) `TO_CHAR(DATE '2023-03-07', 'DAY'); --> 'TUESDAY  '`   `Day` Full capitalized day name (blank-padded to 9 chars) `TO_CHAR(DATE '2023-03-08', 'Day'); --> 'Wednesday'`   `day` Full lower case day name (blank-padded to 9 chars) `TO_CHAR(DATE '2023-03-09', 'day'); --> 'thursday '`   `DY` Abbreviated upper case day name (3 chars in English) `TO_CHAR(DATE '2023-03-09', 'DY'); --> 'THU'`   `Dy` Abbreviated capitalized day name (3 chars in English) `TO_CHAR(DATE '2023-03-10', 'Dy'); --> 'Fri'`   `dy` Abbreviated lower case day name (3 chars in English) `TO_CHAR(DATE '2023-03-11', 'dy'); --> 'sat'`   `RM` Month in upper case Roman numerals (I–XII; I=January) `TO_CHAR(DATE '2023-03-03', 'RM'); --> 'III'`   `rm` Month in lower case Roman numerals (i–xii; i=January) `TO_CHAR(DATE '2023-06-03', 'rm'); --> 'vi'`   `AD` or `BC` Upper case era indicator without periods `TO_CHAR(DATE '2023-03-03', 'BC'); --> 'AD'`   `ad` or `bc` lower case era indicator without periods `TO_CHAR(DATE '2023-03-03', 'ad'); --> 'ad'`   `A.D.` or `B.C.` Upper case era indicator with periods `TO_CHAR(DATE '2023-03-03', 'A.D.'); --> 'A.D.'`   `a.d.` or `b.c.` Upper case era indicator with periods `TO_CHAR(DATE '2023-03-03', 'b.c.'); --> 'a.d.'`   `TZ` Upper case time-zone abbreviation `SET timezone = 'America/Vancouver';`  
+`TO_CHAR(TIMESTAMPTZ '2023-03-03', 'TZ'); --> 'PST'`   `tz` Lower case time-zone abbreviation `SET timezone = 'Europe/Berlin';`  
+`TO_CHAR(TIMESTAMPTZ '2023-03-03', 'tz'); --> 'cet'`   `TZH` Time zone hours `SET TIMEZONE = 'Israel';`  
+`TO_CHAR(TIMESTAMPTZ '2023-03-03', 'TZH'); --> '+02'`   `TZM` Time zone minutes `SET TIMEZONE = 'Israel';`  
+`TO_CHAR(TIMESTAMPTZ '2023-03-03', 'tzm'); --> '00'`   `OF` Time zone offset from UTC `SET TIMEZONE = 'America/New_York';`  
+`TO_CHAR(TIMESTAMPTZ '2023-03-03', 'OF'); --> '-08:00'`  
+
+Additionally, modifiers can be applied to the format patterns above to alter their behavior.
+
+Format option Description Example `FM` prefix Surpress leading zeroes and padding blanks `TO_CHAR(CURRENT_DATE, 'Month YYYY'); --> 'March     2023'`  
+`TO_CHAR(CURRENT_DATE, 'FMMonth YYYY'); --> 'March 2023'` `TH` suffix Upper case ordinal number suffix `TO_CHAR(CURRENT_TIMESTAMP, 'MMTH'); --> '1ST'` `th` suffix Lower case ordinal number suffix `TO_CHAR(CURRENT_TIMESTAMP, 'MMth'); --> '3rd'`
+
+Any character in the format string that is not recognized as a pattern is simply copied over without being replaced. Parts that are quoted `"` will be copied over independent of possibly valid patterns. Patterns are matched in lower and upper case if there is no other behavior described above.
+
+## [](#return-types)Return Types
+
+Formatted string based on the function’s specifications
+
+## [](#examples)Examples
+
+The example below outputs the current local time in a formatted string. Note that the `"` around the words `Date` and `Time` are required, otherwise the characters `D` and `I` would be interpreted as valid patterns which would result in the output `6ate` and `T3me`.
+
+The following example outputs the current date in a formatted string with any time field set to `0` which indicates midnight. Note the quotation marks again that are required to prevent unintended replacements:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_date.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_date.md
new file mode 100644
index 0000000..aaf7150
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_date.md
@@ -0,0 +1,39 @@
+# [](#to_date)TO\_DATE
+
+Converts a string to `DATE` type using format.
+
+## [](#syntax)Syntax
+
+```
+TO_DATE(<expression> [,'<format>'])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The text to convert to a date. If no optional `<format>` argument is given that can be used to parse the `<expression>`, the following formats are supported: `'YYYY-M[M]-D[D]'` (e.g., `2023-3-28`), `'YYYY-month-D[D]'` (e.g., `2023-FEB-12`), `'month-D[D]-YYYY'` (e.g., `Dec-01-2023`), `'D[D]-month-YYYY'` (e.g., `3-jun-2023`), and `'month D[D], YYYY'` (e.g., `august 12, 2023`) `TEXT` `<format>` Optional. A string literal that specifies the format of the `<expression>` to convert. `TEXT` (see below)
+
+Accepted `<format>` patterns include the following specifications:
+
+Format option Description Example `YYYY` Year (4 or more digits) `TO_DATE('2023', 'YYYY'); --> '2023-01-01'` `YYY` Last 3 digits of year `TO_DATE('2023', 'YYY'); --> '2023-01-01'` `YY` Last 2 digits of year `TO_DATE('2023', 'YY'); --> '2023-01-01'` `Y` Last digit of year `TO_DATE('2023', 'Y'); --> '2023-01-01'` `MONTH` Full month name (case insensitive) `TO_DATE('august', 'MONTH'); --> '0001-08-01'` `MON` abbreviated month name (3 chars, case insensitive) `TO_DATE('dec', 'MON'); --> '0001-12-01'` `MM` Month number (01–12) `TO_DATE('7', 'MM'); --> '0001-07-01'` `DD` Day of month (01–31) `TO_DATE('15', 'DD'); --> '0001-01-15'`
+
+**Usage notes for formatting**
+
+- Case letters in the input `<expression>` are ignored
+- A separator (non-digit and non-letter) in the `<format>` string will match exactly one separator or is skipped
+- Any non-separator in the `<format>` that is not part of a format option will match exactly one other character.
+- Any character in quotes `"` will match exactly one other character.
+- If the year format specification is `'YYY'`, `'YY'`, or `'Y'` and the supplied year is less than four digits, the year will be adjusted to be nearest to the year 2020, (e.g., `80` becomes `1980`).
+- More specification, such as `'HH'`, `'MI'`, or, `'TZH'`, are accepted but ignored for purposes of computing the `DATE` result.
+- Modifiers (e.g., `'FM'`) are not supported.
+
+Some additional format patterns are reserved but currently not implemented: `FF1`, `FF2`, `FF3`, `FF4`, `FF5`, `FF6`, `SSSS`, `SSSSS`, `IYYY`, `IYY`, `IY`, `I`, `BC`, `AD`, `B_DOT_C_DOT`, `A_DOT_D_DOT`, `DAY`, `DY`, `DDD`, `IDDD`, `D`, `ID`, `W`, `WW`, `IW`, `CC`, `J`, `Q`. Using them in the format string raises an error.
+
+## [](#return-type)Return Type
+
+`DATE`
+
+## [](#examples)Examples
+
+The following example shows that separators and non-separators can cause skips. The separator `' '` (space) in the `<format>` matches the other separator `'/'` in the `<expression>`. The non-separator `'x'` will match any other character, in this case the `'a'`. Lastly, the two separators `'++'` will match up to two other separators, here the first `'x'` matches `'.'` while the second `'x'` will simply be ignored as no other separators follow.
+
+The following example shows how the year is adjusted to be nearest to 2020 because `YYY` was used to match a number that contains less than four digits. To receive the exact year `'180'` use `YYYY` instead. Furthermore, as the three separators are quotes `"..."` they will match any character (separator or non-separator) which in this case is `'ar '`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_timestamp.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_timestamp.md
new file mode 100644
index 0000000..c8ed4be
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_timestamp.md
@@ -0,0 +1,70 @@
+# [](#to_timestamp)TO\_TIMESTAMP
+
+See [below](#formatting-function) for the formatting function that converts from a formatted string to `TIMESTAMPTZ`.
+
+**Alias:** `FROM_UNIXTIME` - only accepts one parameter of type `DOUBLE PRECISION`
+
+## [](#conversion-function)Conversion function
+
+Converts the number of seconds since the Unix epoch (`1970-01-01 00:00:00 UTC`) to a `TIMESTAMPTZ` value.
+
+### [](#syntax)Syntax
+
+`TO_TIMESTAMP(<seconds>)`
+
+### [](#parameters)Parameters
+
+Parameter Description `<seconds>` A value expression of type `DOUBLE PRECISION` representing the number of seconds before or after the Unix epoch. If present, the fractional part is interpreted as subseconds.
+
+### [](#return-type)Return Type
+
+`TIMESTAMPTZ`
+
+### [](#remarks)Remarks
+
+`TO_TIMESTAMP(<seconds>)` is the inverse function of `EXTRACT(EPOCH FROM TIMESTAMPTZ)`.
+
+### [](#example)Example
+
+```
+SET time_zone = 'Europe/Berlin';
+SELECT TO_TIMESTAMP(42.123456::DOUBLE PRECISION);  --> 1970-01-01 01:00:42.123456+01
+```
+
+## [](#formatting-function)Formatting function
+
+Converts a string to `TIMESTAMPTZ` type (i.e., timestamp with time zone) using format.
+
+### [](#syntax-1)Syntax
+
+```
+TO_TIMESTAMP(<expression> [,'<format>'])
+```
+
+### [](#parameters-1)Parameters
+
+Parameter Description Supported input types `<expression>` The text to convert to a timestamp with time zone. If no optional `<format>` argument is given that can be used to parse the `<expression>`, the following format is required: any supported date format directly followed by `( \|T)[H]H:[m]m:[S]S[.F]`. (For supported date formats see [TO\_DATE](/sql_reference/functions-reference/date-and-time/to-date.html) `TEXT` `<format>` Optional. A string literal that specifies the format of the `<expression>` to convert. `TEXT` (see below)
+
+Accepted `<format>` patterns include the following specifications:
+
+Format option Description Example `YYYY` Year (4 or more digits) `TO_TIMESTAMP('2023', 'YYYY'); --> '2023-01-01 00:00:00+00'` `YYY` Last 3 digits of year `TO_TIMESTAMP('2023', 'YYY'); --> '2023-01-01 00:00:00+00'` `YY` Last 2 digits of year `TO_TIMESTAMP('2023', 'YY'); --> '2023-01-01 00:00:00+00'` `Y` Last digit of year `TO_TIMESTAMP('2023', 'Y'); --> '2023-01-01 00:00:00+00'` `MONTH` Full month name (case insensitive) `TO_TIMESTAMP('august', 'MONTH'); --> '0001-08-01 00:00:00+00'` `MON` abbreviated month name (3 chars, case insensitive) `TO_TIMESTAMP('dec', 'MON'); --> '0001-12-01 00:00:00+00'` `MM` Month number (01–12) `TO_TIMESTAMP('7', 'MM'); --> '0001-07-01 00:00:00+00'` `DD` Day of month (01–31) `TO_TIMESTAMP('15', 'DD'); --> '0001-01-15 00:00:00+00'` `HH` or `HH12` Hour of day (01–12) `TO_TIMESTAMP('8', 'hh'); --> '0001-01-01 08:00:00+00'` `HH24` Hour of day (00–23) `TO_TIMESTAMP('18', 'hh24'); --> '0001-01-01 18:00:00+00'` `MI` Minute (00–59) `TO_TIMESTAMP('35', 'hh'); --> '0001-01-01 00:35:00+00'` `SS` Second (00–59) `TO_TIMESTAMP('52', 'hh'); --> '0001-01-01 00:00:52+00'` `MS` Millisecond (000–999) `TO_TIMESTAMP('89', 'ms'); --> '0001-01-01 08:00:00.89+00'` `US` Microsecond (000000–999999) `TO_TIMESTAMP('04852', 'hh'); --> '0001-01-01 08:00:00.04852+00'` `AM` or `PM` meridiem indicator (without periods) `TO_TIMESTAMP('5 am', 'hh PM'); --> '0001-01-01 05:00:00+00+00'` `A.M.` or `P.M.` meridiem indicator (with periods) `TO_TIMESTAMP('5 p.m.', 'hh A.M.'); --> '0001-01-01 17:00:00+00'` `TZH` Time zone hours `TO_TIMESTAMP('12 -2', 'hh24 TZH'); --> '0001-01-01 14:00:00+00+00'` `TZM` Time zone minutes `TO_TIMESTAMP('12 45', 'hh24 TZM'); --> '0001-01-01 11:15:00+00`
+
+**Usage notes for formatting**
+
+- Case letters in the input `<expression>` are ignored
+- A separator (non-digit and non-letter) in the `<format>` string will match exactly one separator or is skipped
+- Any non-separator in the `<format>` that is not part of a format option will match exactly one other character.
+- Any character in quotes `"` will match exactly one other character.
+- If the year format specification is `'YYY'`, `'YY'`, or `'Y'` and the supplied year is less than four digits, the year will be adjusted to be nearest to the year 2020, (e.g., `80` becomes `1980`).
+- Milliseconds and microseconds are interpreted as subseconds in the form `ss.xxx[xxx]`. This means that `TO_TIMESTAMP('30.7', 'SS.MS')` is not 7 milliseconds, but 700, because it will be treated as 30 + 0.7 seconds. To achieve 7 milliseconds, one ust write `30.007` instead.
+- Modifiers (e.g., `'FM'`) are not supported.
+
+Some additional format patterns are reserved but currently not implemented: `FF1`, `FF2`, `FF3`, `FF4`, `FF5`, `FF6`, `SSSS`, `SSSSS`, `IYYY`, `IYY`, `IY`, `I`, `BC`, `AD`, `B_DOT_C_DOT`, `A_DOT_D_DOT`, `DAY`, `DY`, `DDD`, `IDDD`, `D`, `ID`, `W`, `WW`, `IW`, `CC`, `J`, `Q`. Using them in the format string raises an error.
+
+### [](#examples)Examples
+
+The example below shows our separators and non-separators can cause skips. The separator `' '` (space) in the `<format>` matches the other separator `'/'` in the `<expression>`. The non-separator `'x'` will match any other character, in this case the `'a'`. Lastly, the two separators `'++'` will match up to two other separators, here the first `'x'` matches `'.'` while the second `'x'` will simply be ignored as no other separators follow.
+
+The example below shows how the year is adjusted to be nearest to 2020 because `YYY` was used to match a less than four digit number. To receive the exact year `'180'` use `YYYY` instead. Furthermore, as the three separators are quotes `"..."` they will match any character (separator or non-separator) which in this case is `'ar '`.
+
+Due to rounding it can happen that the conversion from an extracted epoch back to a timestamp does not generate the original timestamp.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_yyyymm.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_yyyymm.md
new file mode 100644
index 0000000..5b2e2ac
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_yyyymm.md
@@ -0,0 +1,32 @@
+# [](#to_yyyymm)TO\_YYYYMM
+
+Extracts the year and month from a `DATE`, `TIMESTAMP`, or `TIMESTAMPTZ` value and combines them into an integer beginning with the four-digit year followed by the two-digit month. `TO_YYYYMM(<expression>)` is equivalent to `EXTRACT(YEAR FROM <expression>) * 100 + EXTRACT(MONTH FROM <expression>);`
+
+## [](#syntax)Syntax
+
+```
+TO_YYYYMM(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression from which the time units are extracted. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ`
+
+`TIMESTAMPTZ` values are converted to local time according to the session’s `time_zone` setting before extracting the time units.
+
+## [](#return-types)Return Types
+
+`INT`
+
+## [](#remarks)Remarks
+
+The `TO_YYYYMM` function can be used in the `PARTITION BY` clause of `CREATE TABLE` commands.
+
+```
+CREATE TABLE test (
+  t TIMESTAMP
+)
+PARTITION BY TO_YYYYMM(t);
+```
+
+## [](#example)Example
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_yyyymmdd.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_yyyymmdd.md
new file mode 100644
index 0000000..944d604
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_date_and_time_to_yyyymmdd.md
@@ -0,0 +1,32 @@
+# [](#to_yyyymmdd)TO\_YYYYMMDD
+
+Extracts year, month and day from a `DATE`, `TIMESTAMP`, or `TIMESTAMPTZ` value and combines them into an integer beginning with the four-digit year followed by the two-digit month followed by the two-digit day. `TO_YYYYMMDD(<expression>)` is equivalent to `EXTRACT(YEAR FROM <expression>) * 10000 + EXTRACT(MONTH FROM <expression>) * 100 + EXTRACT(DAY FROM <expression>);`
+
+## [](#syntax)Syntax
+
+```
+TO_YYYYMMDD(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The expression from which the time units are extracted. `DATE`, `TIMESTAMP`, `TIMESTAMPTZ`
+
+`TIMESTAMPTZ` values are converted to local time according to the session’s `time_zone` setting before extracting the time units.
+
+## [](#return-types)Return Types
+
+`INT`
+
+## [](#remarks)Remarks
+
+The `TO_YYYYMMDD` function can be used in the `PARTITION BY` clause of `CREATE TABLE` commands.
+
+```
+CREATE TABLE test (
+  t TIMESTAMP
+)
+PARTITION BY TO_YYYYMMDD(t);
+```
+
+## [](#example)Example
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_functions_glossary.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_functions_glossary.md
new file mode 100644
index 0000000..9d7179c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_functions_glossary.md
@@ -0,0 +1,5 @@
+# [](#functions-glossary)Functions glossary
+
+The following is a complete alphabetical list of all Firebolt functions:
+
+Name Function Type [ABS](/sql_reference/functions-reference/numeric/abs.html) Calculates the absolute value of an input value. Numeric [ACOS](/sql_reference/functions-reference/numeric/acos.html) Calculates the arccosine of a value in radians. Numeric [APACHE\_DATASKETCHES\_HLL\_BUILD](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-build.html) Creates a new Apache DataSketch HyperLogLog sketch. DataSketches [APACHE\_DATASKETCHES\_HLL\_ESTIMATE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-estimate.html) Extracts a cardinality estimate of a single Apache DataSketch HyperLogLog sketch. DataSketches [APACHE\_DATASKETCHES\_HLL\_MERGE](/sql_reference/functions-reference/datasketches/apache-datasketches-hll-merge.html) Merges one or more Apache DataSketch HyperLogLog sketches. DataSketches [ARRAY\_ALL\_MATCH](/sql_reference/functions-reference/Lambda/array-all-match.html) Returns `TRUE` if the provided function evaluates to `TRUE` for all elements in an array, and `FALSE` otherwise. Lambda [ARRAY\_ANY\_MATCH](/sql_reference/functions-reference/Lambda/array-any-match.html) Returns `TRUE` if the provided function evaluates to `TRUE` for any element in an array, and `FALSE` otherwise. Lambda [ARRAY\_CONCAT](/sql_reference/functions-reference/array/array-concat.html) Combines one or more arrays provided as arguments into a single array. Array [ARRAY\_CONTAINS](/sql_reference/functions-reference/array/array-contains.html) Returns `TRUE` if a specified argument is present in the array, and `FALSE` otherwise. Array [ARRAY\_COUNT](/sql_reference/functions-reference/array/array-count.html) Counts the number of elements in a boolean array for which the function applied to `(array[i])` evaluates to `TRUE`, if a function is provided. If not provided, counts the number of elements in the array that evaluate to `TRUE`. Lambda [ARRAY\_DISTINCT](/sql_reference/functions-reference/array/array-distinct.html) Returns an array containing only the distinct elements of the given array. Array [ARRAY\_FIRST](/sql_reference/functions-reference/Lambda/array-first.html) Returns the first element in the given array for which the given function returns `TRUE`. Lambda [ARRAY\_FLATTEN](/sql_reference/functions-reference/array/flatten.html) Converts a nested array of arrays into a flat array by extracting all the elements from the inner arrays into a single, continuous array. Array [ARRAY\_TO\_STRING](/sql_reference/functions-reference/array/array-to-string.html) Concatenates the elements of a string array into a single string, using an optional specified delimiter between each element. Array [ARRAY\_LENGTH](/sql_reference/functions-reference/array/array-length.html) Returns the length, or number of elements, in the given array. Array [ARRAY\_MAX](/sql_reference/functions-reference/array/array-max.html) Returns the maximum element in an array. Array [ARRAY\_MIN](/sql_reference/functions-reference/array/array-min.html) Returns the minimum element in an array. Array [ARRAY\_REVERSE](/sql_reference/functions-reference/array/array-reverse.html) Returns an array of the same size and type as the original array, with the elements in reverse order. Array [ARRAY\_REVERSE\_SORT](/sql_reference/functions-reference/array/array-reverse-sort.html) Returns the elements of the input array in descending order. If the argument function is provided, the sorting order is determined by the result of applying the function on each element of the array. Lambda [ARRAY\_SORT](/sql_reference/functions-reference/array/array-sort.html) Returns the elements of the input array in ascending order. If the argument function is provided, the sorting order is determined by the result of applying the function on each element of the array. Lambda [ARRAY\_SUM](/sql_reference/functions-reference/Lambda/array-sum.html) Returns the sum of elements of the input array. Lambda [ARRAY\_TRANSFORM](/sql_reference/functions-reference/Lambda/transform.html) Returns an array constructed by applying a lambda function to each element of the input arrays. Lambda [ASIN](/sql_reference/functions-reference/numeric/asin.html) Calculates the arcsine of a value in radians. Numeric [ATAN](/sql_reference/functions-reference/numeric/atan.html) Calculates the arctangent of a value in radians. Numeric [AVG](/sql_reference/functions-reference/aggregation/avg.html) Calculates the average of an expression. Aggregation [AVG OVER](/sql_reference/functions-reference/window/avg-window.html) Returns the average value within the requested window. Window [BIT\_AND](/sql_reference/functions-reference/aggregation/bit_and.html) Performs a bitwise `AND` operation on an integer expression. Aggregation [BIT\_OR](/sql_reference/functions-reference/aggregation/bit_or.html) Performs a bitwise `OR` operation on an integer expression. Aggregation [BIT\_XOR](/sql_reference/functions-reference/aggregation/bit_xor.html) Performs a bitwise `XOR` operation on an integer expression. Aggregation [BOOL\_AND](/sql_reference/functions-reference/aggregation/bool_and.html) Returns `TRUE` if all `NOT NULL` values in the input are `TRUE`. Aggregation [BOOL\_OR](/sql_reference/functions-reference/aggregation/bool_or.html) Returns `TRUE` if any `NOT NULL` value in the input is `TRUE`. Aggregation [BTRIM](/sql_reference/functions-reference/string/btrim.html) Removes all occurrences of optionally specified characters from both sides of a source string. If no trim parameter is specified, all occurrences of common whitespace (ASCII Decimal 32) characters from both sides of the specified source string are removed. String [CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/cast.html) Converts data types into other data types based on the specified parameters. Conditional &amp; miscellaneous [CEIL](/sql_reference/functions-reference/numeric/ceil.html) Rounds an input `<value>` up to the nearest multiple based on the specified precision or decimal place. Numeric [COS](/sql_reference/functions-reference/numeric/cos.html) Calculates the cosine of a value in radians. Numeric [COT](/sql_reference/functions-reference/numeric/cot.html) Calculates the cotangent of a value in radians. Numeric [HASH\_AGG](/sql_reference/functions-reference/aggregation/hash-agg.html) Calculates a hash value across all rows based on a specified list of arguments. Aggregation [CITY\_HASH](/sql_reference/functions-reference/conditional-and-miscellaneous/city-hash.html) Takes one or more input parameters of any data type and returns a 64-bit non-cryptographic hash value. Returns `NULL` if any input value is `NULL`. Conditional &amp; miscellaneous [COALESCE](/sql_reference/functions-reference/conditional-and-miscellaneous/coalesce.html) Checks from left to right for the first `NOT NULL` argument found for each parameter pair. Conditional &amp; miscellaneous [CONCAT or ||](/sql_reference/functions-reference/string/concat.html) Concatenates the input strings listed in the input together without adding a separator between them. String [CONVERT\_FROM](/sql_reference/functions-reference/bytea/convert-from.html) Converts a binary string encoded in a specified format to sql `TEXT` using the database’s default encoding. Binary [COUNT](/sql_reference/functions-reference/aggregation/count.html) Counts the number of rows or the number of `NOT NULL` values. Aggregation [COUNT OVER](/sql_reference/functions-reference/window/count-window.html) Counts the number of values within a specified window. Window [CURRENT\_ACCOUNT](/sql_reference/functions-reference/session/current-account.html) Returns the current account name. Session [CURRENT\_DATABASE](/sql_reference/functions-reference/session/current-database.html) Returns the current database name. If no database is set, returns `account_db`. Session [CURRENT\_DATE](/sql_reference/functions-reference/date-and-time/current-date.html) Returns the current (local) date in the time zone specified in the session’s `time_zone` setting. Date &amp; time [CURRENT\_ENGINE](/sql_reference/functions-reference/session/current-engine.html) Returns the current engine name. Returns `system` on the system engine. Session [CURRENT\_TIMESTAMP](/sql_reference/functions-reference/date-and-time/current-timestamptz.html) Returns the current (local) timestamp in the time zone specified in the session’s `time_zone` setting. Date &amp; time [DATE](/sql_reference/functions-reference/date-and-time/date.html) Converts a `TIMESTAMP`, `TIMESTAMPTZ`, `DATE` or `TEXT` value to a `DATE` value. Date &amp; time [DATE\_ADD](/sql_reference/functions-reference/date-and-time/date-add.html) Calculates a new date or timestamp by adding or subtracting a specified number of time units from an indicated expression. Date &amp; time [DATE\_DIFF](/sql_reference/functions-reference/date-and-time/date-diff.html) Calculates the difference between the start and end date based on the specified unit. Date &amp; time [DATE\_TRUNC](/sql_reference/functions-reference/date-and-time/date-trunc.html) Truncates a date or timestamp value to the selected precision. Date &amp; time [DECODE](/sql_reference/functions-reference/bytea/decode.html) Decodes binary data from a SQL expression of type `TEXT` into its original form. Binary [DEGREES](/sql_reference/functions-reference/numeric/degrees.html) Converts a value in radians to degrees. Numeric [DENSE\_RANK](/sql_reference/functions-reference/window/dense-rank.html) Ranks the current row within the specified window, ensuring that there are no gaps in the ranking sequence. Window [ENCODE](/sql_reference/functions-reference/bytea/encode.html) Encodes binary data from its original form into a SQL expression of type `TEXT`. Binary [EXTRACT](/sql_reference/functions-reference/date-and-time/extract.html) Retrieves the time unit from a date or timestamp value. Date &amp; time [FIRST\_VALUE](/sql_reference/functions-reference/window/first-value.html) Returns the first value evaluated in the specified window frame. If there are no rows in the window frame, `FIRST_VALUE` returns `NULL`. Window [FLOOR](/sql_reference/functions-reference/numeric/floor.html) Rounds an input `<value>` down to the nearest multiple based on the specified precision or decimal place. Numeric [GENERATE\_SERIES](/sql_reference/functions-reference/table-valued/generate-series.html) A table-valued function that generates a sequence of numeric values or dates, starting from `start` to `stop`, incremented by a `step` value. Table-valued [GREATEST](/sql_reference/functions-reference/conditional-and-miscellaneous/greatest.html) Selects the largest value from a list of expressions. Conditional &amp; miscellaneous [HASH](/sql_reference/functions-reference/conditional-and-miscellaneous/hash.html) Computes a 64-bit non-cryptographic hash for one or more input values, with `NULL` values always producing the same hash. Conditional &amp; miscellaneous [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html) Counts the approximate number of unique `NOT NULL` values and aggregates them into HLL++ sketches represented as the [BYTEA data type](/sql_reference/bytea-data-type.html). Conditional &amp; miscellaneous [HLL\_COUNT\_ESTIMATE](/sql_reference/functions-reference/numeric/hll-count-estimate.html) Provides a cardinality estimate of a single HLL++ sketch that was previously built using the aggregate function [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html). Conditional &amp; miscellaneous [HLL\_COUNT\_MERGE](/sql_reference/functions-reference/aggregation/hll-count-merge.html) Merges one or more HLL++ sketches that were previously built using the aggregate function [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html) into a new sketch. Conditional &amp; miscellaneous [IF](/sql_reference/functions-reference/conditional-and-miscellaneous/if.html) Emulates IF-THEN-ELSE statement expression. Conditional &amp; miscellaneous [IFNULL](/sql_reference/functions-reference/conditional-and-miscellaneous/ifnull.html) Compares two expressions. Returns the first expression if it is non-NULL, and otherwise returns the second expression. Conditional &amp; miscellaneous [ILIKE](/sql_reference/functions-reference/string/ilike.html) Case insensitive pattern of strings. String [INDEX\_OF](/sql_reference/functions-reference/array/index-of.html) Returns the index position of the first occurrence of the element in an array, or 0 if not found. Array [IS\_FINITE](/sql_reference/functions-reference/numeric/is_finite.html) Returns `TRUE` if a value is finite, and `FALSE` otherwise. Numeric [IS\_INFINITE](/sql_reference/functions-reference/numeric/is_infinite.html) Returns `TRUE` if a value is infinite, and `FALSE` otherwise. Numeric [JSON\_EXTRACT](/sql_reference/functions-reference/JSON/json-extract.html) Takes an expression containing a JSON document, a JSON path expression, and an optional path syntax. If the key specified using the JSON path expression exists, `JSON_EXTRACT` returns the sub JSON document pointed by the given JSON path. Otherwise, returns `NULL`. Semi-structured data [JSON\_EXTRACT\_ARRAY](/sql_reference/functions-reference/JSON/json-extract-array.html) Takes an expression containing a JSON document, a JSON path expression, and an optional path syntax. If the key specified using the JSON path expression exists and its value is a JSON array, `JSON_EXTRACT_ARRAY` returns SQL `ARRAY(TEXT)` contains all JSON elements as raw text inside the JSON array pointed by the given JSON path. Otherwise, returns `NULL`. Semi-structured data [JSON\_VALUE](/sql_reference/functions-reference/JSON/json-value.html) Takes an expression containing a JSON document, removes the outermost quotes and unescapes the value, and extracts a scalar value as SQL `TEXT`, or `NULL` if a non-scalar value is selected. Semi-structured data [JSON\_VALUE\_ARRAY](/sql_reference/functions-reference/JSON/json-value-array.html) Takes an expression containing a JSON document and extracts an array of scalar values out of it to SQL `ARRAY(TEXT)`. Semi-structured data [LEAST](/sql_reference/functions-reference/conditional-and-miscellaneous/greatest.html) Selects the smallest value from a list of expressions. Conditional &amp; miscellaneous [LENGTH](/sql_reference/functions-reference/string/length.html) Returns the length of an input string. String [LIKE](/sql_reference/functions-reference/string/like.html) Performs case-sensitive pattern matching of strings. String [LIST\_OBJECTS](/sql_reference/functions-reference/table-valued/list-objects.html) Returns an Amazon S3 object metadata and prefixes from the input URL up to the next forward slash (‘/’). Table-valued [LN](/sql_reference/functions-reference/numeric/ln.html) Returns the natural logarithm (base e) of a number. Numeric [LOCALTIMESTAMP](/sql_reference/functions-reference/date-and-time/localtimestamp.html) Returns the current local timestamp in the time zone specified in the session’s `time_zone` setting. Date &amp; time [LOG](/sql_reference/functions-reference/numeric/log.html) Returns the logarithm of a number using a custom base, defaulting to base 10 if no base is provided. Numeric [LOWER](/sql_reference/functions-reference/string/lower.html) Converts the input string to lowercase characters. String [LPAD](/sql_reference/functions-reference/string/lpad.html) Pads a string from the left with a specified string until it reaches the specified length. String [LTRIM](/sql_reference/functions-reference/string/ltrim.html) Removes specified characters from the left side of a source string. If no trim parameter is specified, all occurrences of common whitespace (ASCII Decimal 32) characters from the left side of the specified source string are removed. String [MAX](/sql_reference/functions-reference/aggregation/max.html) Calculates the maximum value of an expression across all input values. Aggregation [MAX\_BY](/sql_reference/functions-reference/aggregation/max-by.html) Returns the value of its first argument for the row that contains the maximum value of the second argument. Aggregation [MAX OVER](/sql_reference/functions-reference/window/max-window.html) Returns the maximum value within the requested window. Window [MAX\_BY](/sql_reference/functions-reference/aggregation/max-by.html) Returns the value of the specified input column at the row with the maximum value in the specified value column. Aggregation [MEDIAN](/sql_reference/functions-reference/aggregation/median.html) Calculates the median for a given column. If number of values are even, it returns the average of the two middle values. Aggregation [MIN](/sql_reference/functions-reference/aggregation/min.html) Calculates the minimum value of an expression across all input values. Aggregation [MIN\_BY](/sql_reference/functions-reference/aggregation/min-by.html) Returns the value of its first argument for the row that contains the minimum value of the second argument. Aggregation [MIN OVER](/sql_reference/functions-reference/window/min-window.html) Returns the maximum value within the requested window. Window [MOD](/sql_reference/functions-reference/numeric/mod.html) Calculates the remainder after dividing two values. Numeric [NTILE](/sql_reference/functions-reference/window/ntile.html) Divides an ordered set into a number of buckets. Window [NULLIF](/sql_reference/functions-reference/conditional-and-miscellaneous/nullif.html) Compares two expressions. Returns `NULL` if the expressions are equal. Returns the result of the first if they are not equal. Conditional &amp; miscellaneous [OCTET\_LENGTH](/sql_reference/functions-reference/string/octet_length.html) Calculates the length of the input string in bytes. String [PERCENT\_RANK](/sql_reference/functions-reference/window/percent-rank.html) Calculates the relative rank of the current row within the requested window. Window [PERCENTILE\_CONT](/sql_reference/functions-reference/aggregation/percentile-cont.html) Calculates a percentile value for a given expression. Aggregation [PI](/sql_reference/functions-reference/numeric/pi.html) Returns π as a `DOUBLE PRECISION` value. Numeric [POSITION](/sql_reference/functions-reference/string/position.html) Returns the position of the substring found in the string, starting from 1. The returned value is for the first matching value, and not for any subsequent valid matches. In case the substring does not exist, position will return 0. String [RANDOM](/sql_reference/functions-reference/numeric/random.html) Returns a pseudo-random unsigned value greater than 0 and less than 1 of type `DOUBLE PRECISION`. Numeric [RANK](/sql_reference/functions-reference/window/rank.html) Rank the current row within the requested window with gaps. Window [READ\_CSV](/sql_reference/functions-reference/table-valued/read_csv.html) Returns a table with data from specified CSV file. Table-valued [READ\_PARQUET](/sql_reference/functions-reference/table-valued/read_parquet.html) Returns a table with data from specified Parquet file. Table-valued [REGEXP\_LIKE](/sql_reference/functions-reference/string/regexp-like.html) Checks whether a text pattern matches a regular expression string. Returns 0 if it doesn’t match, or 1 if it matches. String [REGEXP\_LIKE\_ANY](/sql_reference/functions-reference/string/regexp-like-any.html) Checks whether a given string matches any regular expression pattern from a specified list of patterns. Returns `FALSE` if it doesn’t match, or `TRUE` if it matches. String [REGEXP\_REPLACE](/sql_reference/functions-reference/string/regexp-replace.html) Matches a pattern in the input string and replaces the first matched portion (from the left) with the specified replacement. String [REPLACE](/sql_reference/functions-reference/string/replace.html) Replaces all occurrences of the given pattern substring within the input expression with a replacement substring. String [ROUND](/sql_reference/functions-reference/numeric/round.html) Rounds a value to a specified number of decimal places. Numeric [ROW\_NUMBER](/sql_reference/functions-reference/window/row-number.html) Calculate a unique, increasing row number for each row within the window. Window [RPAD](/sql_reference/functions-reference/string/rpad.html) Adds a specified pad string to the end of the string repetitively up until the length of the resulting string is equivalent to an indicated length. String [RTRIM](/sql_reference/functions-reference/string/rtrim.html) Removes all occurrences of optionally specified characters from the right side of a source string. If no trim parameter is specified, all occurrences of common whitespace (ASCII Decimal 32) characters from the right side of the specified source string are removed. String [SESSION\_USER](/sql_reference/functions-reference/session/session-user.html) Returns the name of the user running the current query. Session [SPLIT\_PART](/sql_reference/functions-reference/string/split-part.html) Divides a string based on a specified delimiter into an array of substrings. The string in the specified index is returned, with 1 being the first index. If the string separator is empty, the input string is returned at index 1. String [SQRT](/sql_reference/functions-reference/numeric/sqrt.html) Calculates square root of a value. Numeric [STRING\_TO\_ARRAY](/sql_reference/functions-reference/string/string-to-array.html) Splits a given string by a given separator and returns the result in an array of strings. String [STRPOS](/sql_reference/functions-reference/string/strpos.html) Returns the position of the substring found in the string, starting from 1. The returned value is for the first matching value, and not for any subsequent valid matches. In case the substring does not exist, `STRPOS` will return 0. String [ST\_ASBINARY](/sql_reference/functions-reference/geospatial/st_asbinary.html) Converts shapes of the `GEOGRAPHY` data type to the [Well-Known Binary (WKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary) format for geographic objects. Geospatial [ST\_ASEWKB](/sql_reference/functions-reference/geospatial/st_asewkb.html) Converts shapes of the `GEOGRAPHY` data type to the [extended Well-Known Binary (EWKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Format_variations) format using Spatial Reference Identifier (SRID) 4326, which corresponds to the [WGS84](https://en.wikipedia.org/wiki/World_Geodetic_System#WGS_84) coordinate system. Geospatial [ST\_ASGEOJSON](/sql_reference/functions-reference/geospatial/st_asgeojson.html) Converts shapes of the `GEOGRAPHY` data type to the [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946) format. Geospatial [ST\_ASTEXT](/sql_reference/functions-reference/geospatial/st_astext.html) Converts shapes of the `GEOGRAPHY` data type to the [Well-Known Text (WKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) format. Geospatial [ST\_CONTAINS](/sql_reference/functions-reference/geospatial/st_contains.html) The `ST_CONTAINS` function determines if one `GEOGRAPHY` object fully contains another. Geospatial [ST\_COVERS](/sql_reference/functions-reference/geospatial/st_covers.html) The `ST_COVERS` function determines if one `GEOGRAPHY` object fully encompasses another. Geospatial [ST\_DISTANCE](/sql_reference/functions-reference/geospatial/st_distance.html) The `ST_DISTANCE` function calculates the shortest distance (measured as a geodesic arc) between two `GEOGRAPHY` objects, measured in meters. Geospatial [ST\_GEOGFROMGEOJSON](/sql_reference/functions-reference/geospatial/st_geogfromgeojson.html) Constructs a `GEOGRAPHY` object from a [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946) string. Geospatial [ST\_GEOGFROMTEXT](/sql_reference/functions-reference/geospatial/st_geogfromtext.html) Constructs a `GEOGRAPHY` object from a [Well-Known Text (WKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) string. Geospatial [ST\_GEOGFROMWKB](/sql_reference/functions-reference/geospatial/st_geogfromwkb.html) Constructs a `GEOGRAPHY` object from a [Well-Known Binary](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary) (WKB) byte string. Geospatial [ST\_GEOGPOINT](/sql_reference/functions-reference/geospatial/st_geogpoint.html) Constructs a Point in the `GEOGRAPHY` data type created from specified longitude and latitude coordinates. Geospatial [ST\_INTERSECTS](/sql_reference/functions-reference/geospatial/st_intersects.html) The `ST_INTERSECTS` function determines whether two input `GEOGRAPHY` objects intersect each other. Geospatial [ST\_S2CELLIDFROMPOINT](/sql_reference/functions-reference/geospatial/st_s2cellidfrompoint.html) Returns the [S2 cell ID](http://s2geometry.io/devguide/s2cell_hierarchy), which uniquely identifies the region on Earth that fully contains, or covers, a single Point `GEOGRAPHY` object. Geospatial [ST\_X](/sql_reference/functions-reference/geospatial/st_x.html) Extracts the longitude coordinate of a `GEOGRAPHY` Point. Geospatial [ST\_Y](/sql_reference/functions-reference/geospatial/st_y.html) Extracts the latitude coordinate of a `GEOGRAPHY` Point. Geospatial [SUBSTRING, SUBSTR](/sql_reference/functions-reference/string/substring.html) Returns a substring starting at the character indicated by the start index and including the number of characters defined. Character indexing starts at 1. String [SUM](/sql_reference/functions-reference/aggregation/sum.html) Calculates the sum of an expression. Aggregation [SUM OVER](/sql_reference/functions-reference/window/sum-window.html) Calculate the sum of the values within the requested window. Window [TAN](/sql_reference/functions-reference/numeric/tan.html) Calculates the tangent of a value in radians. Numeric [TO\_TIMESTAMP](/sql_reference/functions-reference/date-and-time/to-timestamp.html) Converts a string to timestamp with time zone. Date &amp; time [TO\_YYYYMM](/sql_reference/functions-reference/date-and-time/to-yyyymm.html) Extracts year and month from a `DATE`, `TIMESTAMP`, or `TIMESTAMPTZ` value and combines them into an integer beginning with the four-digit year followed by the two-digit month. Date &amp; time [TO\_YYYYMMDD](/sql_reference/functions-reference/date-and-time/to-yyyymmdd.html) Extracts year, month and day from a `DATE`, `TIMESTAMP`, or `TIMESTAMPTZ` value and combines them into an integer beginning with the four-digit year followed by the two-digit month followed by the two-digit day. Date &amp; time [TRIM](/sql_reference/functions-reference/string/trim.html) Removes all specified characters from the start, end, or both sides of a string. By default removes all consecutive occurrences of common whitespace (ASCII character 32) from both ends of a string. String [TRY\_CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/try-cast.html) Converts data types into other data types based on the specified parameters. Returns a `NULL` if the conversion cannot be performed. Conditional &amp; miscellaneous [UPPER](/sql_reference/functions-reference/string/upper.html) Converts the input string to uppercase characters. String [URL\_DECODE](/sql_reference/functions-reference/string/url_decode.html) Decodes percent-encoded characters. String [URL\_ENCODE](/sql_reference/functions-reference/string/url_encode.html) Encodes characters that are not unreserved using percent encoding. String [VECTOR\_COSINE\_DISTANCE](./vector/vector-cosine-distance) Computes the cosine distance of two vectors. vector [VECTOR\_COSINE\_SIMILARITY](./vector/vector-cosine-similarity) Computes the cosine similarity of two vectors. vector [VECTOR\_EUCLIDEAN\_DISTANCE](./vector/vector-euclidean-distance) Computes the euclidean distance of two vectors. vector [VECTOR\_INNER\_PRODUCT](./vector/vector-inner-product) Computes the inner product of two vectors. vector [VECTOR\_MANHATTAN\_DISTANCE](./vector/vector-manhattan-distance) Computes the manhattan distance of two vectors. vector [VECTOR\_SQUARED\_EUCLIDEAN\_DISTANCE](./vector/vector-squared-euclidean-distance) Computes the squared euclidean distance of two vectors. Array [VERSION](/sql_reference/functions-reference/conditional-and-miscellaneous/version.html) Returns the version number information for the Firebolt engine. Conditional &amp; miscellaneous
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_functions_reference.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_functions_reference.md
new file mode 100644
index 0000000..aa12f04
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_functions_reference.md
@@ -0,0 +1,32 @@
+# [](#sql-functions)SQL functions
+
+See a [full function glossary](/sql_reference/functions-reference/functions-glossary.html), or find functions based on type from the list below:
+
+- [Aggregation functions](/sql_reference/functions-reference/aggregation/)  
+  Perform a calculation across a set of rows, returning a single value.
+- [Array functions](/sql_reference/functions-reference/array/)  
+  Used for the manipulation and querying of `ARRAY`-type data, such as transforming and filtering. Includes [Lambda functions](/sql_reference/functions-reference/Lambda/).
+- [Binary functions](/sql_reference/functions-reference/bytea/)  
+  Used for manipulation and querying of `BYTEA`-type data, such as encoding and decoding.
+- [Conditional and miscellaneous functions](/sql_reference/functions-reference/conditional-and-miscellaneous/)  
+  Include various methods for modifying data types and applying conditional operations.
+- [DataSketches functions](/sql_reference/functions-reference/datasketches/)  
+  Apache Datasketches is a library designed to efficiently summarize and analyze large-scale data using probabilistic data structures known as sketches. These sketches provide approximate answers to complex queries, such as distinct counting, quantile estimation, and frequency estimation, with high accuracy and significantly reduced memory usage. This makes Datasketches ideal for big data applications where traditional exact methods are impractical due to time or space constraints.
+- [Date and time functions](/sql_reference/functions-reference/date-and-time/)  
+  Manipulate date and time data types.
+- [Geospatial functions](/sql_reference/functions-reference/geospatial/)  
+  Operations involving geospatial objects
+- [JSON functions](/sql_reference/functions-reference/JSON/)  
+  Extract and transform JSON into Firebolt native types, or JSON sub-objects. Used either during the ELT process or applied to columns storing JSON objects as plain `TEXT`.
+- [Numerical functions](/sql_reference/functions-reference/numeric/)  
+  Manipulate data types including `INTEGER`, `BIGINT`, `DOUBLE PRECISION`, and other numeric types.
+- [Session functions](/sql_reference/functions-reference/session/)  
+  Obtaining information about a current session.
+- [String functions](/sql_reference/functions-reference/string/)  
+  Manipulate string data types.
+- [Table-valued functions](/sql_reference/functions-reference/table-valued/)  
+  Return a set of rows. Commonly used to read files from Amazon S3.
+- [Vector functions](/sql_reference/functions-reference/vector/)  
+  Perform vector operations on `ARRAY`-type data.
+- [Window functions](/sql_reference/functions-reference/window/)  
+  Perform a calculation across a specified set of table rows.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial.md
new file mode 100644
index 0000000..8c15224
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial.md
@@ -0,0 +1,19 @@
+## [](#geospatial-functions)Geospatial functions
+
+* * *
+
+- [ST\_ASBINARY](/sql_reference/functions-reference/geospatial/st_asbinary.html)
+- [ST\_ASEWKB](/sql_reference/functions-reference/geospatial/st_asewkb.html)
+- [ST\_ASGEOJSON](/sql_reference/functions-reference/geospatial/st_asgeojson.html)
+- [ST\_ASTEXT](/sql_reference/functions-reference/geospatial/st_astext.html)
+- [ST\_CONTAINS](/sql_reference/functions-reference/geospatial/st_contains.html)
+- [ST\_COVERS](/sql_reference/functions-reference/geospatial/st_covers.html)
+- [ST\_DISTANCE](/sql_reference/functions-reference/geospatial/st_distance.html)
+- [ST\_GEOGFROMGEOJSON](/sql_reference/functions-reference/geospatial/st_geogfromgeojson.html)
+- [ST\_GEOGFROMTEXT](/sql_reference/functions-reference/geospatial/st_geogfromtext.html)
+- [ST\_GEOGFROMWKB](/sql_reference/functions-reference/geospatial/st_geogfromwkb.html)
+- [ST\_GEOGPOINT](/sql_reference/functions-reference/geospatial/st_geogpoint.html)
+- [ST\_INTERSECTS](/sql_reference/functions-reference/geospatial/st_intersects.html)
+- [ST\_S2CELLIDFROMPOINT](/sql_reference/functions-reference/geospatial/st_s2cellidfrompoint.html)
+- [ST\_X](/sql_reference/functions-reference/geospatial/st_x.html)
+- [ST\_Y](/sql_reference/functions-reference/geospatial/st_y.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asbinary.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asbinary.md
new file mode 100644
index 0000000..39e757f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asbinary.md
@@ -0,0 +1,29 @@
+# [](#st_asbinary)ST\_ASBINARY
+
+Converts shapes of the `GEOGRAPHY` data type to the [Well-Known Binary (WKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary) format for geographic objects.
+
+## [](#syntax)Syntax
+
+```
+ST_ASBINARY(<object>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<object>` The `GEOGRAPHY` object to convert to WKB format. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_ASBINARY` returns a value of type `BYTEA`.
+
+## [](#example)Example
+
+The following query uses `ST_GEOGFROMTEXT` to create a `GEOGRAPHY` object from the WKT representation of a Point at specified longitude and latitude coordinates, and then uses `ST_ASBINARY` to convert it to WKB representation:
+
+```
+SELECT ST_ASBINARY(ST_GEOGFROMTEXT('POINT(-73.98551041593687 40.75793403395676)')) AS result
+```
+
+**Returns**
+
+result (BYTEA) ‘\\x01010000003d94479a127f52c0502f80fb03614440’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asewkb.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asewkb.md
new file mode 100644
index 0000000..75a762e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asewkb.md
@@ -0,0 +1,29 @@
+# [](#st_asewkb)ST\_ASEWKB
+
+Converts shapes of the `GEOGRAPHY` data type to the [extended Well-Known Binary (EWKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Format_variations) format using Spatial Reference Identifier (SRID) 4326, which corresponds to the [WGS84](https://en.wikipedia.org/wiki/World_Geodetic_System#WGS_84) coordinate system.
+
+## [](#syntax)Syntax
+
+```
+ST_ASEWKB(<object>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<object>` The `GEOGRAPHY` object to convert to EWKB format. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_ASEWKB` returns a value of type `BYTEA`.
+
+## [](#example)Example
+
+The following code example creates a `GEOGRAPHY` object from the WKT representation of a Point at specified longitude and latitude coordinates and converts it to EWKB format:
+
+```
+SELECT ST_ASEWKB(ST_GEOGFROMTEXT('POINT(-73.98551041593687 40.75793403395676)')) AS result
+```
+
+**Returns**
+
+result (BYTEA) ‘\\x0101000020e61000003d94479a127f52c0502f80fb03614440’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asgeojson.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asgeojson.md
new file mode 100644
index 0000000..e68c8b2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_asgeojson.md
@@ -0,0 +1,35 @@
+# [](#st_asgeojson)ST\_ASGEOJSON
+
+Converts shapes of the `GEOGRAPHY` data type to the [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946) format.
+
+The [GeoJSON standard](https://datatracker.ietf.org/doc/html/rfc7946) specifies that GeoJSON points are WGS 84 coordinates, and GeoJSON line segments are planar edges, meaning straight cartesian lines. However, contrary to that, in Firebolt, the line segments are interpreted as geodesic arcs.
+
+The following image shows an extreme case of the difference between these. Both lines show the LineString from the GeoJSON string `{"coordinates": [[-0.12457505963581639,51.5006710219584],[-74.04448100812115,40.68923977267272]],"type": "LineString"}` that connect the Statue of Liberty in New York City and Big Ben in London. The gray line represents the LineString as a straight Cartesian line, following the GeoJSON standard. In contrast, the red line interprets the LineString as a geodesic arc, consistent with Firebolt’s approach.
+
+![An example showing the interpretation of a GeoJSON string according to the GeoJSON standard and in Firebolt.](../../../assets/images/geography/geojson_difference.png)
+
+## [](#syntax)Syntax
+
+```
+ST_ASGEOJSON(<object>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<object>` The `GEOGRAPHY` object to convert to GeoJSON format. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_ASGEOJSON` returns a value of type `TEXT`.
+
+## [](#example)Example
+
+The following query creates a `GEOGRAPHY` object from the WKT representation of a Point at specified longitude and latitude coordinates and converts it to GeoJSON format:
+
+```
+SELECT ST_ASGEOJSON(ST_GEOGFROMTEXT('POINT(-73.98551041593687 40.75793403395676)')) AS result
+```
+
+**Returns**
+
+result (TEXT) ’{“type”:”Point”,”coordinates”:\[-73.98551041593687,40.75793403395676]}’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_astext.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_astext.md
new file mode 100644
index 0000000..07ccaf4
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_astext.md
@@ -0,0 +1,29 @@
+# [](#st_astext)ST\_ASTEXT
+
+Converts shapes of the `GEOGRAPHY` data type to the [Well-Known Text (WKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) format.
+
+## [](#syntax)Syntax
+
+```
+ST_ASTEXT(<object>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<object>` The `GEOGRAPHY` object to convert to WKT format. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_ASTEXT` returns a value of type `TEXT`.
+
+## [](#example)Example
+
+The following code example creates a `GEOGRAPHY` object from the WKT representation of a Point at specified longitude and latitude coordinates and converts it to WKT format:
+
+```
+SELECT ST_ASTEXT(ST_GEOGFROMTEXT('POINT(-73.98551041593687 40.75793403395676)')) AS result
+```
+
+**Returns**
+
+result (TEXT) ‘POINT(-73.98551041593687 40.75793403395676)’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_contains.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_contains.md
new file mode 100644
index 0000000..e90656a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_contains.md
@@ -0,0 +1,78 @@
+# [](#st_contains)ST\_CONTAINS
+
+The `ST_CONTAINS` function determines if one `GEOGRAPHY` object fully contains another. Specifically, it checks whether every point in the second `GEOGRAPHY` object (`geo2`) lies within or on the boundary of the first `GEOGRAPHY` object (`geo1`), and the interiors of the two input objects intersect. If `geo1` contains `geo2`, the function returns `TRUE`; otherwise, it returns `FALSE`. This function is commonly used to assess spatial relationships, such as whether a larger geographic area completely includes a smaller one.
+
+If either `geo1` or `geo2` is empty, `ST_CONTAINS` will return `FALSE`.
+
+Before performing the containment check, `geo1` and `geo2` are aligned through a snapping process, ensuring precise calculation. For more details on snapping, refer to the [snapping documentation](/sql_reference/geography-data-type.html#snapping).
+
+## [](#interior-definition)Interior definition
+
+A notable part of `ST_CONTAINS` is that the interiors of the inputs must intersect. The interior for the different `GEOGRAPHY` shape types is defined as follows:
+
+- Point: The interior of a point consists only of the point itself, and is defined by its location.
+- LineString: All vertices and line segments of a LineString are part of the interior, except for the first and the last vertex.
+  
+  - If the first and the last vertex are the same point after snapping, then this point is also part of the interior.
+  - If the interior passes through the first and last vertex, or just one of them, then it is part of the interior.
+- Polygon: Every point within the boundaries, excluding points on the boundaries themselves, is part of the interior.
+- MultiPoint, MultiLineString, MultiPolygon, GeometryCollection: Any point that lies within the interior of one of the shapes in the collection is part of the collection’s interior.
+
+## [](#comparison-with-st_covers)Comparison with [ST\_COVERS](/sql_reference/functions-reference/geospatial/st_covers.html)
+
+`ST_CONTAINS` is similar to `ST_COVERS`, but there is a key distinction: `ST_CONTAINS` returns `FALSE` if all points in `geo2` lie exactly on the boundary of `geo1`, while `ST_COVERS` will return `TRUE` in this case. This behavior arises from an additional requirement in `ST_CONTAINS` that the interiors of the geometries must intersect. If this distinction is not important, use `ST_COVERS`, which is more efficient to compute in Firebolt.
+
+## [](#syntax)Syntax
+
+```
+ST_CONTAINS(<geo1>, <geo2>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<geo1>` The object being checked to see if it fully contains the second object. `GEOGRAPHY` `<geo2>` The object being checked to see if it is fully contained by the first object. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_CONTAINS` returns a value of type `BOOLEAN`.
+
+## [](#example)Example
+
+The following codes example creates a Polygon and a Point around Times Square in New York City from their WKT representations and checks if the Polygon contains the Point:
+
+```
+SELECT ST_CONTAINS(
+ST_GEOGFROMTEXT('POLYGON((-73.98519512134791 40.75939223091697, -73.98566488210841 40.75807135585606, -73.9856079414103 40.75804080469413, -73.98470163529633 40.75918017383259, -73.98519512134791 40.75939223091697))'),
+ST_GEOGFROMTEXT('POINT(-73.98504378555772 40.75894662495352)')
+) AS result
+```
+
+**Returns**
+
+result (BOOLEAN) t
+
+## [](#example-1)Example
+
+The following example illustrates the difference between `ST_CONTAINS` and `ST_COVERS`. The Polygon `POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))` covers, but does not contain the LineString `LINESTRING(0 0, 0 0.5)` because it only lies on the Polygon’s boundary and does not intersect the interior of the Polygon. The LineString `LINESTRING(0 0, 0 0.5, 0.5 0.5)` only partially lies on the Polygon’s boundary but also intersects its interior, so it is covered and contained.
+
+```
+SELECT 
+    polygon, 
+    linestring, 
+    ST_CONTAINS(
+        ST_GEOGFROMTEXT(polygon),
+        ST_GEOGFROMTEXT(linestring)
+    ) AS contains,
+    ST_COVERS(
+        ST_GEOGFROMTEXT(polygon),
+        ST_GEOGFROMTEXT(linestring)
+    ) AS covers
+    FROM UNNEST (
+        ['POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))','POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))'], 
+        ['LINESTRING(0 0, 0 0.5)','LINESTRING(0 0, 0 0.5, 0.5 0.5)']
+    ) AS shapes(polygon, linestring)
+```
+
+**Returns**
+
+polygon (TEXT) linestring (TEXT) contains (BOOLEAN) covers (BOOLEAN) ‘POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))’ ‘LINESTRING(0 0, 0 0.5)’ f t ‘POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))’ ‘LINESTRING(0 0, 0 0.5, 0.5 0.5)’ t t
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_covers.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_covers.md
new file mode 100644
index 0000000..7991ae2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_covers.md
@@ -0,0 +1,66 @@
+# [](#st_covers)ST\_COVERS
+
+The `ST_COVERS` function determines if one `GEOGRAPHY` object fully encompasses another. Specifically, it checks whether every point in the second `GEOGRAPHY` object (`geo2`) lies within or on the boundary of the first `GEOGRAPHY` object (`geo1`). If `geo1` covers `geo2`, the function returns `TRUE`; otherwise, it returns `FALSE`. This function is commonly used to assess spatial relationships, such as whether a larger geographic area completely includes a smaller one.
+
+If either `geo1` or `geo2` is empty, `ST_COVERS` will return `FALSE`.
+
+Before performing the coverage check, `geo1` and `geo2` are aligned through a snapping process, ensuring precise calculation. For more details on snapping, refer to the [snapping documentation](/sql_reference/geography-data-type.html#snapping).
+
+## [](#comparison-with-st_contains)Comparison with [ST\_CONTAINS](/sql_reference/functions-reference/geospatial/st_contains.html)
+
+`ST_COVERS` is similar to `ST_CONTAINS`, but there is a key distinction: `ST_CONTAINS` returns `FALSE` if all points in `geo2` lie exactly on the boundary of `geo1`, while `ST_COVERS` will return `TRUE` in this case. If this distinction is not important, use `ST_COVERS`, which is more efficient to compute in Firebolt.
+
+## [](#syntax)Syntax
+
+```
+ST_COVERS(<geo1>, <geo2>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<geo1>` The object being checked to see if it fully covers the second object. `GEOGRAPHY` `<geo2>` The object being checked to see if it fully covers the first object. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_COVERS` returns a value of type `BOOLEAN`.
+
+## [](#example)Example
+
+The following codes example creates a Polygon and a Point around Times Square in New York City from their WKT representations and checks if the Polygon covers the Point:
+
+```
+SELECT ST_COVERS(
+ST_GEOGFROMTEXT('POLYGON((-73.98519512134791 40.75939223091697, -73.98566488210841 40.75807135585606, -73.9856079414103 40.75804080469413, -73.98470163529633 40.75918017383259, -73.98519512134791 40.75939223091697))'),
+ST_GEOGFROMTEXT('POINT(-73.98504378555772 40.75894662495352)')
+) AS result
+```
+
+**Returns**
+
+result (BOOLEAN) t
+
+## [](#example-1)Example
+
+The following example illustrates the difference between `ST_CONTAINS` and `ST_COVERS`. The Polygon `POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))` covers, but does not contain the LineString `LINESTRING(0 0, 0 0.5)` because it only lies on the Polygon’s boundary and does not intersect the interior of the Polygon. The LineString `LINESTRING(0 0, 0 0.5, 0.5 0.5)` only partially lies on the Polygon’s boundary but also intersects its interior, so it is covered and contained.
+
+```
+SELECT 
+    polygon, 
+    linestring, 
+    ST_CONTAINS(
+        ST_GEOGFROMTEXT(polygon),
+        ST_GEOGFROMTEXT(linestring)
+    ) AS contains,
+    ST_COVERS(
+        ST_GEOGFROMTEXT(polygon),
+        ST_GEOGFROMTEXT(linestring)
+    ) AS covers
+    FROM UNNEST (
+        ['POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))','POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))'], 
+        ['LINESTRING(0 0, 0 0.5)','LINESTRING(0 0, 0 0.5, 0.5 0.5)']
+    ) AS shapes(polygon, linestring)
+```
+
+**Returns**
+
+polygon (TEXT) linestring (TEXT) contains (BOOLEAN) covers (BOOLEAN) ‘POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))’ ‘LINESTRING(0 0, 0 0.5)’ f t ‘POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))’ ‘LINESTRING(0 0, 0 0.5, 0.5 0.5)’ t t
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_distance.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_distance.md
new file mode 100644
index 0000000..8f89f7e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_distance.md
@@ -0,0 +1,34 @@
+# [](#st_distance)ST\_DISTANCE
+
+The `ST_DISTANCE` function calculates the shortest distance, measured as a geodesic arc between two `GEOGRAPHY` objects, measured in meters. It models the earth as a perfect sphere with a fixed radius of 6,371,008 meters.
+
+If either input is empty, `ST_DISTANCE` will return `NULL`.
+
+## [](#syntax)Syntax
+
+```
+ST_DISTANCE(<geo1>, <geo2>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<geo1>` The first `GEOGRAPHY` object to calculate the distance between. `GEOGRAPHY` `<geo2>` The second `GEOGRAPHY` object to calculate the distance between. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_DISTANCE` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following code example constructs two Points from their WKT representations: One at the Statue of Liberty in New York City, and one at the Big Ben in London. It then returns the shortest distance between them, as measured as a geodesic arc, in meters:
+
+```
+SELECT ST_DISTANCE(
+ST_GEOGFROMTEXT('POINT(-74.04447010745835 40.68924450077543)'),
+ST_GEOGFROMTEXT('POINT(-0.12418551935155021 51.50086274661804)')
+) AS result
+```
+
+**Returns**
+
+result (DOUBLE PRECISION) 5574863.932096738
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromgeojson.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromgeojson.md
new file mode 100644
index 0000000..dae6769
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromgeojson.md
@@ -0,0 +1,35 @@
+# [](#st_geogfromgeojson)ST\_GEOGFROMGEOJSON
+
+Constructs a `GEOGRAPHY` object from a [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946) string.
+
+The [GeoJSON standard](https://datatracker.ietf.org/doc/html/rfc7946) specifies that GeoJSON points are WGS 84 coordinates, and GeoJSON line segments are planar edges, meaning straight cartesian lines. However, contrary to that, in Firebolt, the line segments are interpreted as geodesic arcs.
+
+The following image shows an extreme case of the difference between these. Both lines show the LineString from the GeoJSON string `{"coordinates": [[-0.12457505963581639,51.5006710219584],[-74.04448100812115,40.68923977267272]],"type": "LineString"}` that connect the Statue of Liberty in New York City and Big Ben in London. The gray line represents the LineString as a straight Cartesian line, following the GeoJSON standard. In contrast, the red line interprets the LineString as a geodesic arc, consistent with Firebolt’s approach.
+
+![An example showing the interpretation of a GeoJSON string according to the GeoJSON standard and in Firebolt.](../../../assets/images/geography/geojson_difference.png)
+
+## [](#syntax)Syntax
+
+```
+ST_GEOGFROMGEOJSON(<GeoJSON>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<GeoJSON>` GeoJSON text representing the `GEOGRAPHY` object. `TEXT`
+
+## [](#return-type)Return Type
+
+`ST_GEOGFROMGEOJSON` returns a value of type `GEOGRAPHY`.
+
+## [](#example)Example
+
+The following code example constructs a Point from a GeoJSON string describing a Point at specified longitude and latitude coordinates and converts it to WKT format:
+
+```
+SELECT ST_ASTEXT(ST_GEOGFROMGEOJSON('{"type":"Point","coordinates":[-73.98551041593687,40.75793403395676]}')) AS result
+```
+
+**Returns**
+
+result (TEXT) ‘POINT(-73.98551041593687 40.75793403395676)’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromtext.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromtext.md
new file mode 100644
index 0000000..9492172
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromtext.md
@@ -0,0 +1,29 @@
+# [](#st_geogfromtext)ST\_GEOGFROMTEXT
+
+Constructs a `GEOGRAPHY` object from a [Well-Known Text (WKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) string. The [extended WKT format](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Format_variations) is supported only for Spatial Reference Identifier (SRID) 4326, which corresponds to the [WGS84](https://en.wikipedia.org/wiki/World_Geodetic_System#WGS_84) coordinate system.
+
+## [](#syntax)Syntax
+
+```
+ST_GEOGFROMTEXT(<WKT>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<WKT>` A WKT string to convert to a `GEOGRAPHY` object. `TEXT`
+
+## [](#return-type)Return Type
+
+`ST_GEOGFROMTEXT` returns a value of type `GEOGRAPHY`.
+
+## [](#example)Example
+
+The following code example constructs a Point from a WKT string describing a Point at specified longitude and latitude coordinates and converts it to WKT format:
+
+```
+SELECT ST_ASTEXT(ST_GEOGFROMTEXT('POINT(-73.98551041593687 40.75793403395676)')) AS result
+```
+
+**Returns**
+
+result (TEXT) ‘POINT(-73.98551041593687 40.75793403395676)’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromwkb.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromwkb.md
new file mode 100644
index 0000000..f3afdab
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogfromwkb.md
@@ -0,0 +1,29 @@
+# [](#st_geogfromwkb)ST\_GEOGFROMWKB
+
+Constructs a `GEOGRAPHY` object from a [Well-Known Binary](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary) (WKB) byte string. The [extended WKB](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Format_variations) format is supported only for Spatial Reference Identifier (SRID) 4326, which corresponds to the [WGS84](https://en.wikipedia.org/wiki/World_Geodetic_System#WGS_84) coordinate system.
+
+## [](#syntax)Syntax
+
+```
+ST_GEOGFROMWKB(<WKB>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<WKB>` WKB representation of the `GEOGRAPHY` object. `BYTEA`
+
+## [](#return-type)Return Type
+
+`ST_GEOGFROMWKB` returns a value of type `GEOGRAPHY`.
+
+## [](#example)Example
+
+The following code example constructs a Point in the `GEOGRAPHY` data type from a WKB byte string and converts it to WKT format:
+
+```
+SELECT ST_ASTEXT(ST_GEOGFROMWKB('\x01010000003d94479a127f52c0502f80fb03614440'::BYTEA)) AS result
+```
+
+**Returns**
+
+result (TEXT) ‘POINT(-73.98551041593687 40.75793403395676)’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogpoint.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogpoint.md
new file mode 100644
index 0000000..63ee3ad
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_geogpoint.md
@@ -0,0 +1,29 @@
+# [](#st_geogpoint)ST\_GEOGPOINT
+
+Constructs a Point in the `GEOGRAPHY` data type created from specified longitude and latitude coordinates.
+
+## [](#syntax)Syntax
+
+```
+ST_GEOGPOINT(<longitude>, <latitude>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<langitude>` The longitude coordinate of the `GEOGRAPHY` Point to construct. `DOUBLE PRECISION` `<latitude>` The latitude of the `GEOGRAPHY` Point to construct. `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`ST_GEOGPOINT` returns a value of type `GEOGRAPHY`.
+
+## [](#example)Example
+
+The following code example constructs a Point in the `GEOGRAPHY` data type from longitude and latitude coordinates and converts it to WKT format:
+
+```
+SELECT ST_ASTEXT(ST_GEOGPOINT(-73.98551041593687, 40.75793403395676)) AS result
+```
+
+**Returns**
+
+result (TEXT) ‘POINT(-73.98551041593687 40.75793403395676)’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_intersects.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_intersects.md
new file mode 100644
index 0000000..73c0e1b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_intersects.md
@@ -0,0 +1,36 @@
+# [](#st_intersects)ST\_INTERSECTS
+
+The `ST_INTERSECTS` function determines whether two input `GEOGRAPHY` objects intersect each other.
+
+If either input is empty, `ST_INTERSECTS` will return `FALSE`.
+
+Before performing the intersection check, the two inputs are aligned through a snapping process, ensuring precise calculation. For more details on snapping, refer to the [snapping documentation](/sql_reference/geography-data-type.html#snapping).
+
+## [](#syntax)Syntax
+
+```
+ST_INTERSECTS(<geo1>, <geo2>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<geo1>` The first `GEOGRAPHY` object to check for intersection with the second object. `GEOGRAPHY` `<geo2>` The second `GEOGRAPHY` object to check for intersection with the first object. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_INTERSECTS` returns a value of type `BOOLEAN`.
+
+## [](#example)Example
+
+The following code example constructs two LineStrings near Times Square in New York City from their WKT representations as `GEOGRAPHY` objects and determines if the LineStrings intersect:
+
+```
+SELECT ST_INTERSECTS(
+    ST_GEOGFROMTEXT('LINESTRING(-73.98507474330196 40.75858394491826, -73.98601039902333 40.7573327842733)'),
+    ST_GEOGFROMTEXT('LINESTRING(-73.98625022413634 40.758256445020976, -73.98473358363454 40.757637261118134)')
+    ) AS result
+```
+
+**Returns**
+
+result (BOOLEAN) t
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_s2cellidfrompoint.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_s2cellidfrompoint.md
new file mode 100644
index 0000000..1c22042
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_s2cellidfrompoint.md
@@ -0,0 +1,43 @@
+# [](#st_s2cellidfrompoint)ST\_S2CELLIDFROMPOINT
+
+Returns the [S2 cell ID](http://s2geometry.io/devguide/s2cell_hierarchy), which uniquely identifies the region on Earth that fully contains, or covers, a single Point `GEOGRAPHY` object.
+
+`ST_S2CELLIDFROMPOINT` exclusively supports single Point `GEOGRAPHY` objects, and returns `NULL` for all other values including MultiPoint, LineString, Polygon, and an empty `GEOGRAPHY` object.
+
+## [](#syntax)Syntax
+
+```
+ST_S2CELLIDFROMPOINT(<geo> [, <cell_level> ])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<geo>` A single valid `GEOGRAPHY` Point for which `ST_S2CELLIDFROMPOINT` calculates and returns the S2 cell that covers it. `GEOGRAPHY` `<cell_level>` The resolution of the S2 cell to return. Valid levels range from 0, the coarsest level, to 30, the finest level. The default level is 30 if unspecified. `BIGINT`
+
+## [](#return-type)Return Type
+
+`ST_S2CELLIDFROMPOINT` returns a value of type `BIGINT`, which may include negative values.
+
+## [](#example)Example
+
+The following code example constructs a dataset containing three `GEOGRAPHY` objects: a valid Point, an empty Point, and a LineString. The code example computes their S2 cell IDs at cell levels 30 and 10, returning results only for the valid Point:
+
+```
+WITH data AS (
+  SELECT 1 AS id, ST_GEOGFROMTEXT('POINT(-122 47)') AS geo
+  UNION ALL
+  SELECT 2 AS id, ST_GEOGFROMTEXT('POINT EMPTY') AS geo
+  UNION ALL
+  SELECT 3 AS id, ST_GEOGFROMTEXT('LINESTRING(1 2, 3 4)') AS geo
+)
+SELECT id,
+       ST_S2CELLIDFROMPOINT(geo) cell30,
+       ST_S2CELLIDFROMPOINT(geo, 10) cell10
+FROM data;
+```
+
+**Returns**
+
+id (INTEGER) cell30 (BIGINT) cell10 (BIGINT) 1 6093613931972369317 6093613287902019584 2 NULL NULL 3 NULL NULL
+
+The previous code example returns the S2 cell ID for the first input at the default, finest resolution of 30. The function returns `NULL` for the second input because it is empty and contains no geographic data, and for the third input because LineString is not a supported `GEOGRAPHY` type.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_x.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_x.md
new file mode 100644
index 0000000..299aa36
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_x.md
@@ -0,0 +1,29 @@
+# [](#st_x)ST\_X
+
+Extracts the longitude coordinate of a `GEOGRAPHY` Point. Returns `NULL` for empty geography objects. Returns an error if the input is not a single Point (and not an empty `GEOGRAPHY` object).
+
+## [](#syntax)Syntax
+
+```
+ST_X(<object>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<object>` The `GEOGRAPHY` Point to extract the longitude of. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_X` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following code example constructs a Point in the `GEOGRAPHY` data type from longitude and latitude coordinates and extracts its longitude coordinate:
+
+```
+SELECT ST_X(ST_GEOGPOINT(-73.98551041593687, 40.75793403395676)) AS result
+```
+
+**Returns**
+
+result (DOUBLE PRECISION) -73.98551041593687
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_y.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_y.md
new file mode 100644
index 0000000..2a22655
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_geospatial_st_y.md
@@ -0,0 +1,29 @@
+# [](#st_y)ST\_Y
+
+Extracts the latitude coordinate of a `GEOGRAPHY` Point. Returns `NULL` for empty geography objects. Returns an error if the input is not a single Point (and not an empty `GEOGRAPHY` object).
+
+## [](#syntax)Syntax
+
+```
+ST_Y(<object>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<object>` The `GEOGRAPHY` Point to extract the latitude of. `GEOGRAPHY`
+
+## [](#return-type)Return Type
+
+`ST_Y` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following code example constructs a Point in the `GEOGRAPHY` data type from longitude and latitude coordinates and extracts its latitude coordinate:
+
+```
+SELECT ST_Y(ST_GEOGPOINT(-73.98551041593687, 40.75793403395676)) AS result
+```
+
+**Returns**
+
+result (DOUBLE PRECISION) 40.75793403395676
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json.md
new file mode 100644
index 0000000..32ba032
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json.md
@@ -0,0 +1,117 @@
+## [](#json-functions-overview)JSON Functions Overview
+
+The JSON functions provide a way to extract specific values from JSON documents, particularly from those stored in a column.
+
+There are three types of JSON functions:
+
+1. These functions extract part of the document, but preserve the original data in the result:
+   
+   - [JSON\_EXTRACT](/sql_reference/functions-reference/JSON/json-extract.html)
+   - [JSON\_EXTRACT\_ARRAY](/sql_reference/functions-reference/JSON/json-extract-array.html)
+   - [JSON\_POINTER\_EXTRACT\_VALUES](/sql_reference/functions-reference/JSON/json-pointer-extract-values.html)
+2. These functions convert a JSON value to a SQL value:
+   
+   - [JSON\_VALUE](/sql_reference/functions-reference/JSON/json-value.html)
+   - [JSON\_VALUE\_ARRAY](/sql_reference/functions-reference/JSON/json-value-array.html)
+   - [JSON\_POINTER\_EXTRACT\_KEYS](/sql_reference/functions-reference/JSON/json-pointer-extract-keys.html)
+3. This function extracts a JSON value and converts it to a SQL value, combining the functionalities of the previous two types of functions:
+   
+   - [JSON\_POINTER\_EXTRACT\_TEXT](/sql_reference/functions-reference/JSON/json-pointer-extract-text.html)
+
+The first two types of functions can be used in conjunction with each other to extract and convert JSON values to SQL values. The following code uses `JSON_POINTER_EXTRACT` to extract a value from a JSON document and `JSON_VALUE` to convert it into a SQL value:
+
+```
+SELECT JSON_VALUE(JSON_POINTER_EXTRACT('{"key1":{"key3":"val1" }, "key2":"val2", "key3":5}', '/key1/key3'));
+```
+
+**Returns** Returns `val1` as a SQL `TEXT` value, rather than the original JSON value `"val1"` with the double quotes.
+
+Currently, JSON functions support only JSON pointer expressions, which provide a method for accessing specific elements within a JSON document. For convenience, the following aliases are available for JSON functions that use JSON pointer expressions:
+
+- `JSON_POINTER_EXTRACT` is an alias for `JSON_EXTRACT` with the `path_syntax` parameter set to `'JSONPointer'`.
+- `JSON_POINTER_EXTRACT_ARRAY` is an alias for `JSON_EXTRACT_ARRAY` with the `path_syntax` parameter set to `'JSONPointer'`.
+
+### [](#json-pointer-expression-syntax)JSON pointer expression syntax
+
+The placeholder `<json_pointer_expression>` indicates where you should use a JSON pointer, which allows access to specific elements in a JSON document. For a formal specification, see [RFC6901](https://tools.ietf.org/html/rfc6901).
+
+A JSON pointer begins with a forward slash (`/`), indicating the root of the JSON document, followed by a sequence of property (key) names or zero-based ordinal numbers separated by slashes. Property names identify specific keys, while index numbers specify the Nth element in an array or object.
+
+The tilde (`~`) and forward slash (`/`) characters have special meanings and need to be escaped as follows:
+
+- To specify a literal tilde (`~`), use `~0`.
+- To specify a literal forward slash (`/`), use `~1`.
+
+For example, consider the following JSON document:
+
+```
+{
+    "key": 123,
+    "key~with~tilde": 2,
+    "key/with/slash": 3,
+    "value": {
+      "dyid": 987,
+      "keywords" : ["insanely","fast","analytics"]
+    }
+}
+```
+
+In the previous JSON document, the JSON pointer expressions evaluate to the following:
+
+Pointer Result Notes `/` `{`  
+`"key": 123,`  
+`"key~with~tilde": 2,`  
+`"key/with/slash": 3,`  
+`"value": {`  
+`"dyid": 987,`  
+`"keywords" : ["insanely","fast","analytics"]`  
+`}` Returns the whole document. `/key` 123   `/key~0with~0tilde` 2 Indicates the value associated with the `key~with~tilde` property name. `/key~1with~1slash` 3 Indicates the value associated with the `key/with/slash` property name. `/0` 123 Uses an ordinal to indicate the value associated with the `key` property name. The `key` property is in the first 0-based position. `/value/keywords/2` analytics Indicates the element “analytics”, which is in the third 0-based position of the array value associated with the keywords property.
+
+### [](#json-common-example)JSON common example
+
+The following JSON document, represented by the `<json_common_example>` placeholder, is used as a basis for all JSON function examples in this reference.
+
+```
+{
+    "key": 123,
+    "value": {
+      "dyid": 987,
+      "uid": "987654",
+      "keywords" : ["insanely","fast","analytics"],
+      "tagIdToHits": {
+        "map": {
+          "1737729": 32,
+          "1775582": 35
+        }
+      },
+      "events":[
+        {
+            "EventId": 547,
+            "EventProperties" :
+            {
+                "UserName":"John Doe",
+                "Successful": true
+            }
+        },
+        {
+            "EventId": 548,
+            "EventProperties" :
+            {
+                "ProductID":"xy123",
+                "items": 2
+            }
+        }
+    ]
+    }
+}
+```
+
+* * *
+
+- [JSON\_EXTRACT](/sql_reference/functions-reference/JSON/json-extract.html)
+- [JSON\_EXTRACT\_ARRAY](/sql_reference/functions-reference/JSON/json-extract-array.html)
+- [JSON\_POINTER\_EXTRACT\_KEYS](/sql_reference/functions-reference/JSON/json-pointer-extract-keys.html)
+- [JSON\_POINTER\_EXTRACT\_TEXT](/sql_reference/functions-reference/JSON/json-pointer-extract-text.html)
+- [JSON\_POINTER\_EXTRACT\_VALUES](/sql_reference/functions-reference/JSON/json-pointer-extract-values.html)
+- [JSON\_VALUE](/sql_reference/functions-reference/JSON/json-value.html)
+- [JSON\_VALUE\_ARRAY](/sql_reference/functions-reference/JSON/json-value-array.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_extract.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_extract.md
new file mode 100644
index 0000000..677fb45
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_extract.md
@@ -0,0 +1,92 @@
+# [](#json_extract)JSON\_EXTRACT
+
+Accepts an expression containing a JSON document, a JSON path expression, and an optional path syntax. If the key specified in the JSON path exists, `JSON_EXTRACT` returns the sub-JSON document at the specified path, and otherwise, returns `NULL`.
+
+## [](#syntax)Syntax
+
+```
+JSON_EXTRACT
+(<json>, <json_path_expression>, path_syntax => <path_syntax>)
+```
+
+### [](#aliases)Aliases
+
+```
+JSON_POINTER_EXTRACT
+(<json>, <json_path_expression>) ->
+JSON_EXTRACT(<json>, <json_path_expression>, path_syntax => 'JSONPointer')
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<json>` The JSON document. `TEXT` `<json_path_expression>` A JSON path that specifies the location of the desired sub-document within the JSON document. `TEXT` `<path_syntax>` The expected syntax of the `<json_path_expression>`, currently supports only the ‘JSONPointer’ syntax. For more information, see [JSON pointer expression syntax](/sql_reference/functions-reference/JSON/#json-pointer-expression-syntax). `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+- If any input values are `NULL`, the function will return `NULL`.
+
+## [](#examples)Examples
+
+For the JSON document indicated by `<json_common_example>` below, see [JSON common example](/sql_reference/functions-reference/JSON/#json-common-example). The **returned result** is based on the following example.
+
+**Example**
+
+The following code example extracts the value at the path `/value/dyid` from the JSON document represented by `<json_common_example>` using the `JSONPointer` syntax:
+
+```
+SELECT JSON_EXTRACT(<json_common_example>, '/value/dyid', 'JSONPointer')
+```
+
+**Returns**
+
+The previous example returns “987” because the key `dyid` is associated with the value `987` within the `value` object, and the function retrieves and returns this value as a string.
+
+**Example**
+
+The following code example attempts to extract a value from the path `/value/no_such_key` in the JSON document represented by `<json_common_example>`:
+
+```
+SELECT JSON_EXTRACT(<json_common_example>, '/value/no_such_key', 'JSONPointer')
+```
+
+**Returns**
+
+The previous code example returns `NULL` because the key `no_such_key` does not exist.
+
+**Example**
+
+The following code example extracts the value at the path `/value/uid` from the JSON document represented by `<json_common_example>`:
+
+```
+SELECT JSON_POINTER_EXTRACT(<json_common_example>, '/value/uid')
+```
+
+**Returns**
+
+The previous code example returns `'"987654"'` because the value associated with the `uid` key in the JSON document is the string `987654`. The function retrieves this value with double quotes, indicating it’s a JSON string.
+
+**Example**
+
+The following code example extracts the value at the path `/value/keywords` from the JSON document represented by `<json_common_example>`:
+
+```
+SELECT JSON_POINTER_EXTRACT(<json_common_example>,'/value/keywords')
+```
+
+**Returns**
+
+The previous code example returns the array `["insanely","fast","analytics"]` that is associated with the `keywords` key.
+
+**Example**
+
+The following code example extracts the third element at index `2` from the array located at the path `/value/keywords` in the JSON document represented by `<json_common_example>`:
+
+```
+SELECT JSON_POINTER_EXTRACT(<json_common_example>,'/value/keywords/2')
+```
+
+**Returns**
+
+The previous code example returns `'"analytics"'` because it accesses the third element in the JSON array, which uses zero-based indexing.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_extract_array.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_extract_array.md
new file mode 100644
index 0000000..adff755
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_extract_array.md
@@ -0,0 +1,101 @@
+# [](#json_extract_array)JSON\_EXTRACT\_ARRAY
+
+Accepts a JSON document, path expression, and optional path syntax. If the key exists and holds a JSON array, `JSON_EXTRACT_ARRAY` returns an SQL ARRAY(TEXT) with the array’s elements as raw text, and otherwise returns `NULL`.
+
+## [](#syntax)Syntax
+
+```
+JSON_EXTRACT_ARRAY
+(<json>, <json_path_expression>, path_syntax => <path_syntax>)
+```
+
+### [](#aliases)Aliases
+
+```
+JSON_POINTER_EXTRACT_ARRAY
+(<json>, <json_path_expression>) ->
+JSON_EXTRACT_ARRAY(<json>, <json_path_expression>, path_syntax => 'JSONPointer')
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<json>` The JSON document. `TEXT` `<json_path_expression>` A JSON path to the location of the desired element within the JSON document. `TEXT` `<path_syntax>` The expected syntax of the `<json_path_expression>` currently only supports ‘JSONPointer’. For more information, see [JSON pointer expression syntax](/sql_reference/functions-reference/JSON/#json-pointer-expression-syntax). `TEXT`
+
+## [](#return-type)Return Type
+
+`ARRAY(TEXT)`
+
+- If any input values are `NULL`, the function will return `NULL`.
+
+## [](#examples)Examples
+
+For the JSON document indicated by `<json_common_example>` below, see [JSON common example](/sql_reference/functions-reference/JSON/#json-common-example). The **returned result** is based on the following example.
+
+**Example**
+
+The following code extracts the value at the path `value/dyid` from the JSON document represented by `<json_common_example>`, and returns it as an SQL array using the `JSONPointer` syntax:
+
+```
+SELECT JSON_EXTRACT_ARRAY(<json_common_example>, '/value/dyid', 'JSONPointer')
+```
+
+**Returns**
+
+The previous example returns `NULL` because the specified path does not reference an array.
+
+**Example**
+
+The following code example attempts to extract an array from a path `/value/no_such_key` in the JSON document represented by `<json_common_example>`:
+
+```
+SELECT JSON_EXTRACT_ARRAY(<json_common_example>, '/value/no_such_key', 'JSONPointer')
+```
+
+**Returns**
+
+The previous code example returns `NULL` because the key does not exist.
+
+**Example**
+
+The following code example extracts the array at the path `/value/keywords` from the JSON document represented by `<json_common_example>` using the JSON pointer syntax:
+
+```
+SELECT JSON_POINTER_EXTRACT_ARRAY(<json_common_example>,'/value/keywords')
+```
+
+**Returns**
+
+The previous code example returns the following: `{"insanely", "fast", "analytics"}`.
+
+**Example**
+
+The following code example extracts the array located at the path `/value/events` from the JSON document represented by `<json_common_example>` using the JSON pointer syntax:
+
+```
+SELECT JSON_POINTER_EXTRACT_ARRAY(<json_common_example>,'/value/events')
+```
+
+**Returns**
+
+The previous code example returns the following SQL array, containing two text elements:
+
+```
+{
+        '{
+            "EventId": 547,
+            "EventProperties" :
+            {
+                "UserName":"John Doe",
+                "Successful": true
+            }
+        }',
+        '{
+            "EventId": 548,
+            "EventProperties" :
+            {
+                "ProductID":"xy123",
+                "items": 2
+            }
+        }'
+}
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_keys.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_keys.md
new file mode 100644
index 0000000..1ede976
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_keys.md
@@ -0,0 +1,66 @@
+# [](#json_pointer_extract_keys)JSON\_POINTER\_EXTRACT\_KEYS
+
+Accepts a JSON document and pointer expression. If the key exists and holds a JSON object (map), `JSON_POINTER_EXTRACT_KEYS` returns all the keys in that object as SQL `ARRAY(TEXT)`, removing outer quotes and decoding characters. Otherwise, it returns `NULL`.
+
+## [](#syntax)Syntax
+
+```
+JSON_POINTER_EXTRACT_KEYS
+(<json>, <json_pointer_expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<json>` The JSON document. `TEXT` `<json_pointer_expression>` A JSON pointer expression to the location of the desired sub-document in the JSON. For more information, see [JSON pointer expression syntax](/sql_reference/functions-reference/JSON/#json-pointer-expression-syntax). `TEXT`
+
+## [](#return-type)Return Type
+
+`ARRAY(TEXT)`
+
+- If any input values are `NULL`, the function will return `NULL`.
+
+## [](#examples)Examples
+
+For the JSON document indicated by `<json_common_example>` below, see [JSON common example](/sql_reference/functions-reference/JSON/#json-common-example).
+
+**Example**
+
+The following code example extracts all the keys at path `/value` from the JSON document, removes the outermost quotes, and returns the result as SQL `ARRAY(TEXT)`, labeled as `res`:
+
+```
+SELECT JSON_POINTER_EXTRACT_KEYS(<json_common_example>, '/value') AS res
+```
+
+**Returns**
+
+The previous code example returns the following:
+
+res (ARRAY(TEXT)) {‘dyid’, ‘uid’, ‘keywords’, ‘tagIdToHits’, ‘events’}
+
+**Example**
+
+The following code example attempts to extract the keys at the path `/value/no_such_key` from the JSON document:
+
+```
+SELECT JSON_POINTER_EXTRACT_KEYS(<json_common_example>, '/value/no_such_key') AS res
+```
+
+**Returns**
+
+The previous code example returns the `NULL` with the result labeled as `res`, because the key does not exist:
+
+res (ARRAY(TEXT)) NULL
+
+**Example**
+
+The following code example attempts to extract the value at the path `/value/keywords` from the JSON document:
+
+```
+SELECT JSON_POINTER_EXTRACT_KEYS(<json_common_example>,'/value/keywords') AS res
+```
+
+**Returns**
+
+The previous code example returns `NULL`, labeled as `res` because the value at the specified path is an array, not an object:
+
+res (ARRAY(TEXT)) NULL
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_text.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_text.md
new file mode 100644
index 0000000..85e05d5
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_text.md
@@ -0,0 +1,80 @@
+# [](#json_pointer_extract_text)JSON\_POINTER\_EXTRACT\_TEXT
+
+Accepts a JSON document and pointer expression. If the key exists and the value is a JSON string, `JSON_POINTER_EXTRACT_TEXT` returns it as SQL `TEXT`, removing outer quotes and decoding characters. Otherwise, it returns `NULL`.
+
+## [](#syntax)Syntax
+
+```
+JSON_POINTER_EXTRACT_TEXT
+(<json>, <json_pointer_expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<json>` The JSON document. `TEXT` `<json_pointer_expression>` A JSON pointer expression to the location of the desired sub-document in the JSON. For more information, see [JSON pointer expression syntax](/sql_reference/functions-reference/JSON/#json-pointer-expression-syntax). `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+- If any input values are `NULL`, the function will return `NULL`.
+
+## [](#examples)Examples
+
+For the JSON document indicated by `<json_common_example>` below, see [JSON common example](/sql_reference/functions-reference/JSON/#json-common-example). The **returned result** is based on the following example.
+
+**Example**
+
+The following code example extracts the value at path `/value/uid` from the JSON document, removes the outermost quotes, and returns the result as SQL `TEXT`, labeled as `res`:
+
+```
+SELECT JSON_POINTER_EXTRACT_TEXT('{"value": {"uid": "987654"} }', '/value/uid') AS res
+```
+
+**Returns**
+
+The previous code example returns the following:
+
+res (TEXT) 987654
+
+**Example**
+
+The following code example attempts to extract the value at the path `/value/no_such_key` from the JSON document:
+
+```
+SELECT JSON_POINTER_EXTRACT_TEXT('{"value": {"uid": "987654"} }', '/value/no_such_key') AS res
+```
+
+**Returns**
+
+The previous code example returns the `NULL` with the result labeled as `res`, because the key does not exist:
+
+res (TEXT) NULL
+
+**Example**
+
+The following code example attempts to extract the value at the path `/value/code` from the JSON document:
+
+```
+SELECT JSON_POINTER_EXTRACT_TEXT('{"value": {"code": 12} }', '/value/code') AS res
+```
+
+**Returns**
+
+The previous code example returns `NULL`, labeled as `res` because the value at the specified path is an integer, not a string:
+
+res (TEXT) NULL
+
+**Example**
+
+The following code example navigates to the third element at index `2` of the array at `/value/keywords` in the JSON document, removes the outermost quotes, and returns it as SQL `TEXT`, labeled as `res`:
+
+```
+SELECT JSON_POINTER_EXTRACT_TEXT(<json_common_example>,'/value/keywords/2') AS res
+```
+
+**Returns**
+
+The previous code example returns `"analytics"`, which is the third element in the JSON array, which uses zero-based indexing:
+
+res (TEXT) analytics
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_values.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_values.md
new file mode 100644
index 0000000..e8f06dd
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_pointer_extract_values.md
@@ -0,0 +1,66 @@
+# [](#json_pointer_extract_values)JSON\_POINTER\_EXTRACT\_VALUES
+
+Accepts a JSON document and pointer expression. If the key exists and holds a JSON object (map), `JSON_POINTER_EXTRACT_VALUES` returns all the values in that object as SQL `ARRAY(TEXT)`, while the values remain raw as they appeared in the original JSON document. Otherwise, it returns `NULL`.
+
+## [](#syntax)Syntax
+
+```
+JSON_POINTER_EXTRACT_VALUES
+(<json>, <json_pointer_expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<json>` The JSON document. `TEXT` `<json_pointer_expression>` A JSON pointer expression to the location of the desired sub-document in the JSON. For more information, see [JSON pointer expression syntax](/sql_reference/functions-reference/JSON/#json-pointer-expression-syntax). `TEXT`
+
+## [](#return-type)Return Type
+
+`ARRAY(TEXT)`
+
+- If any input values are `NULL`, the function will return `NULL`.
+
+## [](#examples)Examples
+
+For the JSON document indicated by `<json_common_example>` below, see [JSON common example](/sql_reference/functions-reference/JSON/#json-common-example). The **returned result** is based on the following example.
+
+**Example**
+
+The following code example extracts all the values at path `/value/events/0/EventProperties` from the JSON document, and returns the raw values as SQL `ARRAY(TEXT)`, labeled as `res`:
+
+```
+SELECT JSON_POINTER_EXTRACT_VALUES(<json_common_example>, '/value/events/0/EventProperties') AS res
+```
+
+**Returns**
+
+The previous code example returns the following:
+
+res (ARRAY(TEXT)) {‘“John Doe”’, ‘true’}
+
+**Example**
+
+The following code example attempts to extract the keys at the path `/value/no_such_key` from the JSON document:
+
+```
+SELECT JSON_POINTER_EXTRACT_VALUES(<json_common_example>, '/value/no_such_key') AS res
+```
+
+**Returns**
+
+The previous code example returns the `NULL` with the result labeled as `res`, because the key does not exist:
+
+res (ARRAY(TEXT)) NULL
+
+**Example**
+
+The following code example attempts to extract the value at the path `/value/keywords` from the JSON document:
+
+```
+SELECT JSON_POINTER_EXTRACT_VALUES(<json_common_example>,'/value/keywords') AS res
+```
+
+**Returns**
+
+The previous code example returns `NULL`, labeled as `res` because the value at the specified path is an array, not an object:
+
+res (ARRAY(TEXT)) NULL
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_value.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_value.md
new file mode 100644
index 0000000..7a3f6d8
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_value.md
@@ -0,0 +1,63 @@
+# [](#json_value)JSON\_VALUE
+
+Takes a JSON document and extracts a JSON scalar value to SQL `TEXT` value. For JSON strings, removes the outermost quotes and unescapes the values. Other JSON scalars are not changed. Returns a SQL `NULL` if a non-scalar value is given.
+
+This function pairs with the [JSON\_EXTRACT](/sql_reference/functions-reference/JSON/json-extract.html) function, which doesn’t convert the JSON values to SQL values.
+
+## [](#syntax)Syntax
+
+```
+JSON_VALUE(<json>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<json>` The JSON document. `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+- If any of the input is `NULL` the output is `NULL` (propagates nulls).
+
+## [](#example)Example
+
+For the JSON document indicated by `<json_common_example>` below, see [JSON common example](/sql_reference/functions-reference/JSON/#json-common-example). The **returned result** is based on this example.
+
+```
+SELECT JSON_VALUE(JSON_POINTER_EXTRACT(<json_common_example>, '/value/uid')), JSON_POINTER_EXTRACT(<json_common_example>, '/value/uid')
+```
+
+**Returns**
+
+`'987654', '"987654"'`
+
+**Example**
+
+```
+SELECT JSON_VALUE(JSON_POINTER_EXTRACT(<json_common_example>, '/key'))::INT
+```
+
+**Returns**
+
+`123`
+
+**Example**
+
+```
+SELECT JSON_VALUE(JSON_POINTER_EXTRACT(<json_common_example>,'/value/keywords'))
+```
+
+**Returns**
+
+`NULL`
+
+**Example**
+
+```
+SELECT JSON_VALUE(NULL)
+```
+
+**Returns**
+
+`NULL`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_value_array.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_value_array.md
new file mode 100644
index 0000000..1e94692
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_json_json_value_array.md
@@ -0,0 +1,43 @@
+# [](#json_value_array)JSON\_VALUE\_ARRAY
+
+Takes a JSON document and extracts a JSON array of scalar values to SQL `ARRAY(TEXT)` value. For JSON strings, removes the outermost quotes and unescapes the values. Other JSON scalars are not changed. Returns a SQL `NULL` if a non-array is given, or non-scalar value is given (inside the array).
+
+This function pairs with the [JSON\_EXTRACT](/sql_reference/functions-reference/JSON/json-extract.html) function, which doesn’t convert the JSON values to SQL values.
+
+## [](#syntax)Syntax
+
+```
+JSON_VALUE_ARRAY(<json>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<json>` The JSON document. `TEXT`
+
+## [](#return-type)Return Type
+
+`ARRAY(TEXT)`
+
+- If any of the input is `NULL` the output is `NULL` (propagates nulls).
+
+## [](#example)Example
+
+For the JSON document indicated by `<json_common_example>` below, see [JSON common example](/sql_reference/functions-reference/JSON/#json-common-example). The **returned result** is based on this example.
+
+```
+SELECT JSON_VALUE_ARRAY(JSON_POINTER_EXTRACT(<json_common_example>, '/value/uid')), JSON_POINTER_EXTRACT(<json_common_example>, '/value/uid')
+```
+
+**Returns**: `NULL, '"987654"'`
+
+```
+SELECT JSON_VALUE_ARRAY(JSON_POINTER_EXTRACT(<json_common_example>,'/value/keywords'))
+```
+
+**Returns**: `{'insanely','fast','analytics'}`
+
+```
+SELECT JSON_VALUE_ARRAY(NULL)
+```
+
+**Returns**: `NULL`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda.md
new file mode 100644
index 0000000..7aeb4f3
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda.md
@@ -0,0 +1,12 @@
+### [](#lambda-functions)Lambda functions
+
+For more information about using Lambda functions, see [Manipulating arrays with Lambda functions](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html#manipulating-arrays-with-lambda-functions).
+
+* * *
+
+- [ARRAY\_ALL\_MATCH](/sql_reference/functions-reference/Lambda/array-all-match.html)
+- [ARRAY\_ANY\_MATCH](/sql_reference/functions-reference/Lambda/array-any-match.html)
+- [ARRAY\_FILTER](/sql_reference/functions-reference/Lambda/filter.html)
+- [ARRAY\_FIRST](/sql_reference/functions-reference/Lambda/array-first.html)
+- [ARRAY\_SUM](/sql_reference/functions-reference/Lambda/array-sum.html)
+- [ARRAY\_TRANSFORM](/sql_reference/functions-reference/Lambda/transform.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_all_match.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_all_match.md
new file mode 100644
index 0000000..0deb37b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_all_match.md
@@ -0,0 +1,53 @@
+# [](#array_all_match)ARRAY\_ALL\_MATCH
+
+- Returns `TRUE` if all elements in the array are `TRUE` or if the array is empty.
+- Returns `FALSE` if any element in the array is `FALSE`.
+- Returns `NULL` if any element is `NULL` and no element is `FALSE`.
+
+When an optional lambda function is provided, `ARRAY_ALL_MATCH` applies the function to each element and then evaluates the resulting array.
+
+**Alias:** `ALL_MATCH`
+
+## [](#syntax)Syntax
+
+```
+{ ALL_MATCH | ARRAY_ALL_MATCH }([<expression> -> <condition>], <array> [, <array2>, ...])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` A lambda function applied to each element of the input arrays, returning a `BOOLEAN`. If no lambda function is provided, the function can only evaluate a single `BOOLEAN` array. For more information, see [Manipulating arrays with Lambda functions](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html#manipulating-arrays-with-lambda-functions). Same as the element data types of the input arrays. `<condition>` A `BOOLEAN` expression that evaluates each array value using a comparison operator. See [Comparison operators](/sql_reference/operators.html#comparison). `<array>` The array to evaluate. `ARRAY`
+
+## [](#return-type)Return Type
+
+The `ARRAY_ALL_MATCH` function returns a result of type `BOOLEAN`.
+
+## [](#examples)Examples
+
+Check if all player nicknames end with `'2024'`:
+
+```
+SELECT ARRAY_ALL_MATCH(name -> name like '%2024', [ 'kennethpark2024', 'sabrina2024', 'steven2024']) AS result;
+```
+
+result (BOOLEAN) t
+
+Check if all elements in the first array can be divided by the elements in the second array:
+
+```
+SELECT ARRAY_ALL_MATCH(x, y -> (x % y) = 0, [ 10, 20, 30, 45 ], [ 5, 10, 2, 15]) AS divisable;
+```
+
+divisable (BOOLEAN) t
+
+Check if all elements in an input array are `true`:
+
+```
+SELECT ARRAY_ALL_MATCH([])          as empty,
+    ARRAY_ALL_MATCH([true])         as single_true,
+    ARRAY_ALL_MATCH([false])        as single_false,
+    ARRAY_ALL_MATCH([NULL])         as single_null ,
+    ARRAY_ALL_MATCH([false, NULL])  as false_and_null;
+```
+
+empty (BOOLEAN) single\_true (BOOLEAN) single\_false (BOOLEAN) single\_null (BOOLEAN) false\_and\_null (BOOLEAN) t t f NULL f
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_any_match.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_any_match.md
new file mode 100644
index 0000000..dec4b41
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_any_match.md
@@ -0,0 +1,59 @@
+# [](#array_any_match)ARRAY\_ANY\_MATCH
+
+- Returns `TRUE` if any element in the array is `TRUE`.
+- Returns `FALSE` if all elements in the array are `FALSE` or if the array is empty.
+- Returns `NULL` if any element is `NULL` and no element is `TRUE`.
+
+When an optional lambda function is provided, `ARRAY_ANY_MATCH` applies the function to each element and then evaluates the resulting arrayt.
+
+**Alias:** `ANY_MATCH`
+
+## [](#syntax)Syntax
+
+```
+{ ANY_MATCH | ARRAY_ANY_MATCH }([<expression> -> <condition>], <array> [, <array2>, ...])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types     `<expression>` A lambda function applied to each element of the input arrays, returning a `BOOLEAN`. If no lambda function is provided, the function can only evaluate a single `BOOLEAN` array. For more information, see [Manipulating arrays with Lambda functions](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html#manipulating-arrays-with-lambda-functions). Same as the element data types of the input arrays.   `<condition>` A `BOOLEAN` expression that evaluates each array value using a comparison operator. See [Comparison operators](/sql_reference/operators.html#comparison).   `<array>` The array to evaluate. `ARRAY`
+
+## [](#return-types)Return Types
+
+The `ARRAY_ANY_MATCH` function returns a result of type `BOOLEAN`.
+
+## [](#examples)Examples
+
+**Example** The following code example checks if an array contains the value `esimpson` as the result `is_he_playing`:
+
+```
+SELECT ARRAY_ANY_MATCH(x -> x = 'esimpson', [ 'kennethpark', 'sabrina21', 'steven70']) AS is_he_playing;
+```
+
+**Returns** The previous code returns `FALSE` because the array does not contain the specified value:
+
+is\_he\_playing (BOOLEAN) f
+
+**Example** The following code example checks if each element in the first array is divisible by the corresponding element in the second array in a result labeled `divisible`:
+
+```
+SELECT ARRAY_ANY_MATCH(x, y -> (x % y) = 0, [ 10, 20, 30, 45 ], [ 12, 3, 42, 15]) AS divisible;
+```
+
+**Returns** The previous code returns `TRUE` because each element in the first array is divisible by its corresponding element in the second array:
+
+divisible (BOOLEAN) t
+
+**Example** The following code example evaluates multiple arrays using `ARRAY_ANY_MATCH`:
+
+```
+SELECT ARRAY_ANY_MATCH([])          as empty,
+    ARRAY_ANY_MATCH([true])         as single_true,
+    ARRAY_ANY_MATCH([false])        as single_false,
+    ARRAY_ANY_MATCH([NULL])         as single_null ,
+    ARRAY_ANY_MATCH([false, NULL])  as false_and_null;
+```
+
+**Returns** The previous code returns `FALSE` for the empty array, `TRUE` for the `[TRUE]` array, `FALSE` for the `[FALSE]` array, `NULL` for the `[NULL]` array, and `FALSE` for the `[FALSE, NULL]` array:
+
+empty (BOOLEAN) single\_true (BOOLEAN) single\_false (BOOLEAN) single\_null (BOOLEAN) false\_and\_null (BOOLEAN) f t f NULL NULL
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_first.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_first.md
new file mode 100644
index 0000000..8bdb386
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_first.md
@@ -0,0 +1,28 @@
+# [](#array_first)ARRAY\_FIRST
+
+Returns the first element in the given array for which the given function returns `true`. The `<function>` parameter must be included.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_FIRST(<function>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<function>` A [Lambda function](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html#manipulating-arrays-with-lambda-functions) used to check elements in the array A Lambda function returning `BOOLEAN` `<array>` The array evaluated by the function Any array
+
+## [](#return-type)Return Type
+
+The element type of `<array>`
+
+## [](#examples)Examples
+
+The following example returns the first value in the `levels` array greater than 2:
+
+```
+SELECT
+	ARRAY_FIRST(x -> x > 2, [ 1, 2, 4, 9 ]) AS levels;
+```
+
+**Returns**: `4`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_sum.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_sum.md
new file mode 100644
index 0000000..245799f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_array_sum.md
@@ -0,0 +1,28 @@
+# [](#array_sum)ARRAY\_SUM
+
+Returns the sum of elements of `<array>`.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_SUM(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array to be used to calculate the function. Any array of numeric types
+
+## [](#return-type)Return Type
+
+The return type depends on the input type:
+
+Array element type Return type `INTEGER` `BIGINT` `BIGINT` `NUMERIC(38, 0)` `NUMERIC(precision, scale)` `NUMERIC(precision, scale)` `REAL` `REAL` `DOUBLE` `DOUBLE`
+
+## [](#example)Example
+
+```
+SELECT
+	ARRAY_SUM([ 4, 1, 3, 2 ]) AS levels;
+```
+
+**Returns**: `10`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_filter.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_filter.md
new file mode 100644
index 0000000..30e24ba
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_filter.md
@@ -0,0 +1,57 @@
+# [](#array_filter)ARRAY\_FILTER
+
+Returns an array containing the elements from `<array>` for which the given Lambda function `<function>` returns something other than `0`.
+
+The function can receive one or more arrays as its arguments. If more than one array is provided the following conditions should be met:
+
+- The number of arguments of the Lambda function must be equal to the number of arrays provided. If the condition isn’t met, the query will not run and an error will be returned.
+- All the provided arrays should be of the same length. If the condition isn’t met a runtime error will occur.
+
+When multiple arrays are provided to the function, the function will evaluate the current elements from each array as its parameter. All of the elements at that index position must evaluate to true (or `1`) for this index to be included in the results. The elements that are returned are taken only from the first array provided.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_FILTER(<function>, <array> [, ...] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<function>` A [Lambda function](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html#manipulating-arrays-with-lambda-functions) used to check elements in the array. Any Lambda function `<array> [, ...]` One or more arrays that will be evaluated by the Lambda function. Only the first array that is included will be filtered in the results. All the arrays must have exactly same number of elements. Arrays that each contain the same amount of elements
+
+## [](#return-type)Return Type
+
+`ARRAY` of the same type as the first input array
+
+## [](#examples)Examples
+
+In the example below, there is only one array.
+
+```
+SELECT
+	ARRAY_FILTER(x -> x = 'a', [ 'a', 'b', 'c', 'd' ]);
+```
+
+**Returns**: `['a']`
+
+In this example below, there are two arrays and two separate arguments for evaluation. The Lambda function searches the second array for all elements that are greater than 2. The elements in these positions are returned from the first array. The returned elements highlight the players who have completed above level 2.
+
+```
+SELECT
+	ARRAY_FILTER(x, y -> y > 2, [ 'esimpson', 'sabrina21', 'kennethpark', 'rileyjon' ], [ 1, 2, 3, 9 ]) AS levels;
+```
+
+**Returns**: `['kennethpark', 'rileyjon']`
+
+In this example below, there are three arrays, and Lambda function which meet the condition on two of them.
+
+```
+SELECT
+	ARRAY_FILTER(x, y, z -> (y > 2 AND z = 'kennethpark'),
+		[ 'Player A', 'Player B', 'Player C', 'Player D' ],
+		[ 1, 2, 3, 9 ],
+		[ 'kennethpark', 'rileyjon', 'kennethpark', 'rileyjon' ] )
+	AS levels;
+```
+
+**Returns**: `['Player C']`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_transform.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_transform.md
new file mode 100644
index 0000000..216a010
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_lambda_transform.md
@@ -0,0 +1,85 @@
+# [](#array_transform)ARRAY\_TRANSFORM
+
+Returns an array by applying `<function>` on each element of `<array>`.
+
+The Lambda function `<function>` is a mandatory parameter.
+
+**Alias:** `TRANSFORM`
+
+## [](#syntax)Syntax
+
+```
+ARRAY_TRANSFORM(<function>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input type `<function>` A [Lambda function](/Guides/loading-data/working-with-semi-structured-data/working-with-arrays.html#manipulating-arrays-with-lambda-functions) used to check elements in the array. Any Lambda function `<array>` The array to be transformed by the function. Any array
+
+## [](#return-type)Return Type
+
+`ARRAY` having the return type of `<function>` as its element type
+
+## [](#examples)Examples
+
+```
+SELECT
+	ARRAY_TRANSFORM(x -> x * 2, [ 1, 2, 3, 9 ] ) AS levels;
+```
+
+**Returns**: `[2, 4, 6, 18]`
+
+In the example below, the `TRANSFORM` function is used to [CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/cast.html) each element from a string to a date type. With each element now as a date type, the [INTERVAL](/Reference/interval-arithmetic.html) function is then used to add 5 years to each.
+
+```
+SELECT
+    ARRAY_TRANSFORM(x -> CAST(x as DATE) + INTERVAL '5 year',
+        [ '1979-01-01', '1986-02-26', '1975-04-04' ] )
+    AS registeredon;
+```
+
+**Returns**: `['1984-01-01 00:00:00'::TIMESTAMP, '1991-02-26 00:00:00'::TIMESTAMP, '1980-04-04 00:00:00'::TIMESTAMP]`
+
+In the example below, `ARRAY_TRANSFORM` is used with `CASE` to modify specific elements based on a condition.
+
+```
+SELECT
+    ARRAY_TRANSFORM(x, y -> CASE
+        WHEN y = 'esimpson' THEN x
+        ELSE 0
+        END,
+        [ 1, 2, 3 ],
+        [ 'kennethpark', 'esimpson', 'sabrina21' ] )
+    AS levels;
+```
+
+**Returns**: `[0, 2, 0]`
+
+This example again uses `ARRAY_TRANSFORM` with `CASE`. Elements that don’t meet the condition are left unchanged.
+
+```
+SELECT
+    ARRAY_TRANSFORM(x, y -> CASE
+        WHEN y % 2 == 0
+        THEN UPPER(x)
+        ELSE x END,
+        [ 'esimpson', 'sabrina21', 'kennethpark' ],
+        [ 1, 2, 3 ] )
+    AS players;
+```
+
+**Returns**: `['esimpson', 'SABRINA21', 'kennethpark']`
+
+This is another example using `CASE` that changes elements only if they meet the condition.
+
+```
+SELECT
+    ARRAY_TRANSFORM(x, y -> CASE
+        WHEN x < y THEN y
+        ELSE x END,
+        [ 100, 700, 800 ],
+        [ 300, 500, 200 ] )
+    AS res;
+```
+
+**Returns**: `[300, 700, 800]`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric.md
new file mode 100644
index 0000000..b95d274
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric.md
@@ -0,0 +1,32 @@
+## [](#numeric-functions)Numeric functions
+
+* * *
+
+- [ABS](/sql_reference/functions-reference/numeric/abs.html)
+- [ACOS](/sql_reference/functions-reference/numeric/acos.html)
+- [ARRAY\_ENUMERATE](/sql_reference/functions-reference/numeric/array-enumerate.html)
+- [ASIN](/sql_reference/functions-reference/numeric/asin.html)
+- [ATAN](/sql_reference/functions-reference/numeric/atan.html)
+- [ATAN2](/sql_reference/functions-reference/numeric/atan2.html)
+- [BIT\_SHIFT\_LEFT](/sql_reference/functions-reference/numeric/bit_shift_left.html)
+- [BIT\_SHIFT\_RIGHT](/sql_reference/functions-reference/numeric/bit_shift_right.html)
+- [CEIL](/sql_reference/functions-reference/numeric/ceil.html)
+- [COS](/sql_reference/functions-reference/numeric/cos.html)
+- [COT](/sql_reference/functions-reference/numeric/cot.html)
+- [DEGREES](/sql_reference/functions-reference/numeric/degrees.html)
+- [FLOOR](/sql_reference/functions-reference/numeric/floor.html)
+- [HLL\_COUNT\_ESTIMATE](/sql_reference/functions-reference/numeric/hll-count-estimate.html)
+- [IS\_FINITE](/sql_reference/functions-reference/numeric/is_finite.html)
+- [IS\_INFINITE](/sql_reference/functions-reference/numeric/is_infinite.html)
+- [LN](/sql_reference/functions-reference/numeric/ln.html)
+- [LOG](/sql_reference/functions-reference/numeric/log.html)
+- [MOD](/sql_reference/functions-reference/numeric/mod.html)
+- [PARAM](/sql_reference/functions-reference/numeric/param.html)
+- [PI](/sql_reference/functions-reference/numeric/pi.html)
+- [POW](/sql_reference/functions-reference/numeric/pow.html)
+- [RADIANS](/sql_reference/functions-reference/numeric/radians.html)
+- [RANDOM](/sql_reference/functions-reference/numeric/random.html)
+- [ROUND](/sql_reference/functions-reference/numeric/round.html)
+- [SIN](/sql_reference/functions-reference/numeric/sin.html)
+- [SQRT](/sql_reference/functions-reference/numeric/sqrt.html)
+- [TAN](/sql_reference/functions-reference/numeric/tan.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_abs.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_abs.md
new file mode 100644
index 0000000..5b24411
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_abs.md
@@ -0,0 +1,21 @@
+# [](#abs)ABS
+
+Calculates the absolute value of a number `<value>`, displaying the number’s distance from `0`.
+
+## [](#syntax)Syntax
+
+```
+ABS(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<numeric_type>` The number that the absolute value function is applied to. Any `NUMERIC` type
+
+## [](#return-type)Return Type
+
+`NUMERIC`
+
+## [](#example)Example
+
+The following example returns the absolute value of `-200.5`:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_acos.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_acos.md
new file mode 100644
index 0000000..0a3d8d7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_acos.md
@@ -0,0 +1,21 @@
+# [](#acos)ACOS
+
+Calculates the arccosine of a value in radians.
+
+## [](#syntax)Syntax
+
+```
+ACOS(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The number that the arccosine function is applied to. `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`ACOS` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following query calculates the arccosine of 1:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_array_enumerate.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_array_enumerate.md
new file mode 100644
index 0000000..a1f0e08
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_array_enumerate.md
@@ -0,0 +1,31 @@
+# [](#array_enumerate)ARRAY\_ENUMERATE
+
+This function takes an array of arbitrary type as input, and produces an integer array of the same length containing increasing numbers. The returned array starts with value one. Every successive element is incremented by one, it holds that `array[i] = array[i - 1] + 1`.
+
+`NULLs` contained in the parameter array are treated like any other value, and result in a non-null element in the returned array.
+
+If the parameter array is `NULL`, then the function also returns `NULL`.
+
+## [](#syntax)Syntax
+
+```
+ARRAY_ENUMERATE(<array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The array to be enumerated. The length of the returned array is the same as the length of the parameter array. Any array type.
+
+## [](#return-type)Return Type
+
+`ARRAY(INT)`
+
+## [](#example)Example
+
+The following example returns an array with values one to four:
+
+The array passed to the function can contain arbitrary types:
+
+NULL values are still reflected in the returned result:
+
+If the array passed to the function is NULL, so is the result:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_asin.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_asin.md
new file mode 100644
index 0000000..17d8b89
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_asin.md
@@ -0,0 +1,21 @@
+# [](#asin)ASIN
+
+Calculates the arcsine of a value in radians.
+
+## [](#syntax)Syntax
+
+```
+ASIN(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input type `<value>` The number that the arcsine function is applied to. `DOUBLE_PRECISION`
+
+## [](#return-type)Return Type
+
+`ASIN` returns a value of type `DOUBLE_PRECISION`.
+
+## [](#example)Example
+
+The following query calculates the arcsine of 1:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_atan.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_atan.md
new file mode 100644
index 0000000..b836a42
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_atan.md
@@ -0,0 +1,21 @@
+# [](#atan)ATAN
+
+Calculates the arctangent of a value in radians.
+
+## [](#syntax)Syntax
+
+```
+ATAN(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The number that the arctangent function is applied to. `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`ATAN` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following query calculates the arctangent of 1:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_atan2.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_atan2.md
new file mode 100644
index 0000000..6982ca1
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_atan2.md
@@ -0,0 +1,21 @@
+# [](#atan2)ATAN2
+
+Two-argument arc tangent function. Calculates the angle, in radians, between the specified positive x-axis value and the ray from the origin to the point `(y,x)`.
+
+## [](#syntax)Syntax
+
+```
+ATAN2(<value_y>,<value_x>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value_y>` The `y value` in the arc tangent calculation `DOUBLE PRECISION` `<value_x>` The `x value` in the arc tangent calculation `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`DOUBLE PRECISION`
+
+## [](#example)Example
+
+The following example calculates the arc tangent of the values `11` and `3`:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_bit_shift_left.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_bit_shift_left.md
new file mode 100644
index 0000000..62e5aa5
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_bit_shift_left.md
@@ -0,0 +1,31 @@
+# [](#bit_shift_left)BIT\_SHIFT\_LEFT
+
+Shifts the bits in the first argument to the left by `n` bits, where `n` is the second argument. Shifting left by `n` positions is equivalent to multiplying the number by `2^n`.
+
+## [](#syntax)Syntax
+
+```
+BIT_SHIFT_LEFT(<value>, <bits>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` Specifies the value to shift. `INT`, `BIGINT` `<bits>` The number of bits to shift. `INT`
+
+## [](#return-types)Return Types
+
+The `BIT_SHIFT_LEFT` function returns a result of either type `INT` or `BIGINT`, depending on the type of the input `<expression>`.
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example shifts `0001`, the binary representation of `1`, to the left by two bits, which yields `0100`, the binary representation for `4`:
+
+**Example**
+
+The following code example shifts `00101`, the binary representation of `5`, to the left by two bits, which yields `10100`, the binary representation of `20`:
+
+**Example**
+
+The following code example shifts the binary representation of `-3`, which is `1111111111111101` in signed two’s complement, one bit to the left, resulting in `1111111111111010`, the binary signed two’s complement of `-6`:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_bit_shift_right.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_bit_shift_right.md
new file mode 100644
index 0000000..5192646
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_bit_shift_right.md
@@ -0,0 +1,31 @@
+# [](#bit_shift_right)BIT\_SHIFT\_RIGHT
+
+Shifts the bits in the first argument to the right by `n` bits, where `n` is the second argument. Shifting right by `n` positions is equivalent to dividing the number by `2^n`.
+
+## [](#syntax)Syntax
+
+```
+BIT_SHIFT_RIGHT(<value>, <bits>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` Specifies the value to shift. `INT`, `BIGINT` `<bits>` The number of bits to shift. `INT`
+
+## [](#return-types)Return Types
+
+The `BIT_SHIFT_RIGHT` function returns a result of either type `INT` or `BIGINT`, depending on the type of the input `<expression>`.
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example shifts `0001`, the binary representation of `1`, to the right by two bits, which yields `0000`, the binary representation for `0`:
+
+**Example**
+
+The following code example shifts `00101`, the binary representation of `5`, to the right by two bits, which yields `00001`, the binary representation for `1`:
+
+**Example**
+
+The following code example shifts the binary representation of `-3`, which is `1111111111111101` in signed two’s complement, one bit to the right, resulting in `1111111111111110`, the signed two’s complement of `-2`:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_ceil.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_ceil.md
new file mode 100644
index 0000000..cd76a05
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_ceil.md
@@ -0,0 +1,51 @@
+# [](#ceil)CEIL
+
+Rounds an input `<value>` up to the nearest multiple based on the specified precision or decimal place. Optionally, you can specify a second parameter to determine which decimal place the value should be rounded up to.
+
+**Alias:** `CEILING`
+
+## [](#syntax)Syntax
+
+```
+CEIL(<value>);
+CEIL(<value>, <digit>);
+```
+
+OR
+
+```
+CEILING(<value>);
+CEILING(<value>, <digit>);
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The number to be rounded up to the nearest specified place. `NUMERIC`, `DOUBLE PRECISION` `<digit>` (Optional) You can specify a second parameter to define the position of the digit to round up to, based on its distance from the decimal point. Positive numbers indicate digits after the decimal, while negative numbers refer to digits before. For example, `1` rounds up to the first digit after the decimal, and `-1` rounds up to the nearest ten. A value of `0` rounds up to the nearest whole number. The default is `0`, which means that rounding up happens at the whole number. `INTEGER`
+
+## [](#return-type)Return Type
+
+Input Type Output Type `NUMERIC` `NUMERIC` with same `precision` and `scale`. `DOUBLE PRECISION` `DOUBLE PRECISION`
+
+## [](#remarks)Remarks
+
+When the input is of type `NUMERIC`, `CEIL` throws an overflow error if the result of `CEIL` exceeds the defined precision and scale limits of the return data type.
+
+The following code example calculates the nearest whole number larger than `99.99` and specifies that the output should contain a total of `4` digits, with only `2` digits reserved for the decimal part:
+
+```
+SELECT CEIL('99.99'::NUMERIC(4,2));
+```
+
+**Returns**
+
+The previous code returns an `OVERFLOW ERROR` because `CEIL` returns `100.00`, which exceeds the `NUMERIC(4,2)` data type’s limit of `2` digits before the decimal point, and `100` requires `3` digits.
+
+## [](#examples)Examples
+
+The following example returns the nearest whole number larger than `2.5549900`:
+
+The following example calculates the nearest whole number larger than `213.1549`, and returns a result of type `NUMERIC(20,4)`, which allows for a total of 20 digits, with 4 values allowed after the decimal point:
+
+The following example rounds the number `2.5549900` up to the second decimal place. It returns `2.56` because the second parameter 2 specifies rounding to the second digit after the decimal, which corresponds to the hundredths place.
+
+The following example calculates the nearest whole number greater than `1998` that is a multiple of `1000`. It returns `2000` because the second parameter -3 specifies rounding to the third digit before the decimal point, which corresponds to the thousands place.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_cos.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_cos.md
new file mode 100644
index 0000000..f9c2ce6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_cos.md
@@ -0,0 +1,23 @@
+# [](#cos)COS
+
+Trigonometric function that calculates the cosine of a specific value in radians.
+
+## [](#syntax)Syntax
+
+```
+COS(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value that determines the returned cosine in radians. `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`COS` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following query calculates the cosine of 0:
+
+The following query calculates the cosine of pi:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_cot.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_cot.md
new file mode 100644
index 0000000..82c38e3
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_cot.md
@@ -0,0 +1,21 @@
+# [](#cot)COT
+
+Trigonometric function that calculates the cotangent of a specific value in radians.
+
+## [](#syntax)Syntax
+
+```
+COT(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value which the `COT` function will be applied to in radians. `DOUBLE PRECISION`
+
+## [](#return-types)Return Types
+
+`COT` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following query calculates the cotangent of 1.57 radians. 1.57 is approximately pi/2:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_degrees.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_degrees.md
new file mode 100644
index 0000000..93287de
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_degrees.md
@@ -0,0 +1,21 @@
+# [](#degrees)DEGREES
+
+Converts a value in radians to degrees.
+
+## [](#syntax)Syntax
+
+```
+DEGREES(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value to be converted to degrees from radians. `DOUBLE PRECISION`
+
+## [](#return-types)Return Types
+
+`DEGREES` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following example converts the value `3.14` in radians to degrees:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_floor.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_floor.md
new file mode 100644
index 0000000..9e404eb
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_floor.md
@@ -0,0 +1,42 @@
+# [](#floor)FLOOR
+
+Rounds an input `<value>` down to the nearest multiple based on the specified precision or decimal place. Optionally, you can specify a second parameter to determine which decimal place the value should be rounded down to.
+
+## [](#syntax)Syntax
+
+```
+FLOOR(<value>);
+FLOOR(<value>, <digit>);
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The number to be rounded down to the nearest specified place. `NUMERIC`, `DOUBLE PRECISION` `<digit>` (Optional) You can specify a second parameter to define the position of the digit to round down to, based on its distance from the decimal point. Positive numbers indicate digits after the decimal, while negative numbers refer to digits before the decimal. For example, `1` rounds down to the first digit after the decimal, and `-1` rounds down to the nearest ten. A value of `0` rounds down to the nearest whole number. The default is `0`, which means that rounding down happens at the whole number. `INTEGER`
+
+## [](#return-type)Return Type
+
+Input Type Output Type `NUMERIC` `NUMERIC` with same `precision` and `scale`. `DOUBLE PRECISION` `DOUBLE PRECISION`
+
+## [](#remarks)Remarks
+
+When the input is of type `NUMERIC`, `FLOOR` throws an overflow error if the result of `FLOOR` exceeds the defined precision and scale limits of the return data type.
+
+The following code example calculates the nearest whole number smaller than `-99.99` and specifies that the output should contain a total of `4` digits, with only `2` digits reserved for the decimal part:
+
+```
+SELECT FLOOR(-'99.99'::NUMERIC(4,2));
+```
+
+**Returns**
+
+The previous code returns an `OVERFLOW ERROR` because `FLOOR` returns `-100.00`, which exceeds the `NUMERIC(4,2)` data type’s limit of `2` digits before the decimal point, and `-100` requires `3` digits.
+
+## [](#examples)Examples
+
+The following example returns the nearest whole number smaller than `2.5549900`:
+
+The following example calculates the nearest whole number smaller than `213.1549`, and returns a result of type `NUMERIC(20,4)`, which allows for a total of 20 digits, with 4 values allowed after the decimal point:
+
+The following code example rounds the number `2.5549900` down to the second decimal place. It returns `2.55` because the second parameter 2 specifies rounding to the second digit after the decimal, which corresponds to the hundredths place.
+
+The following example calculates the nearest whole number smaller than `1998` that is a multiple of `1000`. It returns `1000` because the second parameter -3 specifies rounding to the third digit before the decimal point, which corresponds to the thousands place.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_hll_count_estimate.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_hll_count_estimate.md
new file mode 100644
index 0000000..b9459ae
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_hll_count_estimate.md
@@ -0,0 +1,36 @@
+# [](#hll_count_estimate)HLL\_COUNT\_ESTIMATE
+
+Extracts a cardinality estimate of a single HLL++ sketch that was previously built using the aggregate function [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html).
+
+## [](#syntax)Syntax
+
+```
+HLL_COUNT_ESTIMATE(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An HLL++ sketch produced by the [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html) function. `BYTEA`
+
+## [](#return-type)Return Type
+
+`BIGINT`
+
+## [](#example)Example
+
+Following the [example](/sql_reference/functions-reference/aggregation/hll-count-build.html#example) in [HLL\_COUNT\_BUILD](/sql_reference/functions-reference/aggregation/hll-count-build.html):
+
+```
+SELECT hll_count_estimate(a) AS hll_estimate
+FROM sketch_of_data_to_count
+ORDER BY 1;
+```
+
+hll\_estimate (BIGINT) 3291008 4948957
+
+```
+SELECT hll_count_estimate(hll_count_merge(a)) AS hll_estimate
+FROM sketch_of_data_to_count;
+```
+
+hll\_estimate (BIGINT) 6606880
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_is_finite.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_is_finite.md
new file mode 100644
index 0000000..312a88c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_is_finite.md
@@ -0,0 +1,23 @@
+# [](#is_finite)IS\_FINITE
+
+Returns `TRUE` if the argument is finite, and `FALSE` otherwise. Only `REAL` and `DOUBLE PRECISION` types can represent infinity in Firebolt, meaning that `IS_FINITE` will always return `TRUE` for `NUMERIC` inputs.
+
+## [](#syntax)Syntax
+
+```
+IS_FINITE(<value>);
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The input that will be checked to determine if it is a finite number. `NUMERIC`, `DOUBLE PRECISION`, `REAL`
+
+## [](#return-type)Return Type
+
+`IS_FINITE` returns a value of type `BOOLEAN`.
+
+## [](#examples)Examples
+
+The following example checks whether the value inf, after being cast to a `DOUBLE PRECISION` data type, is a finite number:
+
+The following code example checks whether the value 10, after being cast to a `REAL` data type, is an infinite number:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_is_infinite.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_is_infinite.md
new file mode 100644
index 0000000..cbe80ef
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_is_infinite.md
@@ -0,0 +1,23 @@
+# [](#is_infinite)IS\_INFINITE
+
+Returns `TRUE` if the argument is infinite, and `FALSE` otherwise. Only `REAL` and `DOUBLE PRECISION` types can represent infinity in Firebolt, meaning that `IS_INFINITE` will always return `FALSE` for `NUMERIC` inputs.
+
+## [](#syntax)Syntax
+
+```
+IS_FINITE(<value>);
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The input that will be checked to determine if it is an infinite number. `NUMERIC`, `DOUBLE PRECISION`, `REAL`
+
+## [](#return-type)Return Type
+
+`IS_INFINITE` returns a value of type `BOOLEAN`.
+
+## [](#examples)Examples
+
+The following code example checks whether the value inf, after being cast to a `DOUBLE PRECISION` data type, is an infinite number:
+
+The following code example checks whether the value 10, after being cast to a `REAL` data type, is an infinite number:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_ln.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_ln.md
new file mode 100644
index 0000000..576c3b8
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_ln.md
@@ -0,0 +1,25 @@
+# [](#ln)LN
+
+Returns natural (base e) logarithm of a numerical expression. The value for which `ln` is computed needs to be larger than 0, otherwise an error is returned. You can use the function [LOG](/sql_reference/functions-reference/numeric/log.html) if you want to provide a different base.
+
+## [](#syntax)Syntax
+
+```
+LN(<value>);
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value for which to compute the natural logarithm. `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`DOUBLE PRECISION`
+
+## [](#examples)Examples
+
+The following example computes the natural logarithm of 1.0:
+
+The following example returns the natural logarithm close to e:
+
+The natural logarithm can only be computed for values that are larger than 0. All the following functions return an error:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_log.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_log.md
new file mode 100644
index 0000000..32d20e6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_log.md
@@ -0,0 +1,29 @@
+# [](#log)LOG
+
+Returns the common (base 10) logarithm of a numerical expression, or the logarithm to an arbitrary base if specified as the first argument. The value for which `log` is computed needs to be larger than 0, otherwise an error is returned. If a base is provided, it also needs to be larger than 0 and not equal to 1. You can use the function [LN](/sql_reference/functions-reference/numeric/ln.html) to compute the natural logarithm (base e).
+
+**Alias:** `LOG10` (does not support a custom `base` argument)
+
+## [](#syntax)Syntax
+
+```
+LOG([<base>,] <value>);
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<base>` Optional. The base for the logarithm. The default base is 10. `DOUBLE PRECISION` `<value>` The value for which to compute the logarithm. `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`DOUBLE PRECISION`
+
+## [](#example)Example
+
+The following example returns the logarithm of 64.0 to base 2:
+
+The following example returns the logarithm of 100.0 to the default base 10:
+
+The logarithm can only be computed for values that are larger than 0. All the following functions return an error:
+
+When a base is provided, it needs to be positive and not equal to zero. All the following functions return an error:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_mod.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_mod.md
new file mode 100644
index 0000000..7b6da6b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_mod.md
@@ -0,0 +1,21 @@
+# [](#mod)MOD
+
+Calculates the remainder after dividing two values, `<value_n>` / `<value_d>.`
+
+## [](#syntax)Syntax
+
+```
+MOD(<value_n>,<value_d>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value_n>` The numerator of the division equation `INT`, `BIGINT` `<value_d>` The denominator of the division equation `INT`, `BIGINT`
+
+## [](#return-type)Return Type
+
+`BIGINT` if one of the inputs is `BIGINT`. `INT`, otherwise.
+
+## [](#example)Example
+
+The following example returns the remainder of 45 divided by 7:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_param.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_param.md
new file mode 100644
index 0000000..270f15c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_param.md
@@ -0,0 +1,54 @@
+# [](#param)PARAM
+
+Evaluates a provided query parameter and returns its value as `TEXT`.
+
+## [](#syntax)Syntax
+
+```
+PARAM(<parameter>)
+```
+
+Parameter Description Supported input types `<parameter>` Constant string containing the name of the query parameter to evaluate. `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#specifying-query-parameters)Specifying query parameters
+
+To use the `PARAM` function, you need to define query parameters using the `SET PARAM` command. The function relies on a request property named `query_parameters` in JSON format. Use the following schema:
+
+```
+query_parameters: json_array | json_object
+json_array: [ json_object, … ]
+json_object: { "name" : parameter_name, "value" : parameter_value }
+```
+
+You can include a single query parameter in the request properties, for example:
+
+`{ "name": "country", "value": "USA" }`
+
+or multiple query parameters:
+
+`[ { "name": "country", "value": "USA" }, { "name": "states", "value": "WA, OR, CA" }, { "name": "max_sales", "value": 10000 } ]`
+
+## [](#example)Example
+
+The following example shows how to use a Common Table Expression (CTE), through a `WITH` clause, to generate input data and apply a query parameter in a computation. The `WITH` clause defines a temporary dataset, and the query evaluates whether each row matches the parameter value using `PARAM`.
+
+```
+SET query_parameters = [{ "name": "level_type_value", "value": "Drift" }];
+
+WITH Table AS (
+  SELECT 'Drift' AS col1
+  UNION ALL
+  SELECT 'FastestLap'
+)
+SELECT col1,
+       (col1 = PARAM('level_type_value')) AS match_status
+FROM Table;
+```
+
+**Returns**
+
+col1 match\_status Drift 1 FastestLap 0
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_pi.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_pi.md
new file mode 100644
index 0000000..a29bfd2
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_pi.md
@@ -0,0 +1,17 @@
+# [](#pi)PI
+
+Returns π as a `DOUBLE PRECISION` value.
+
+## [](#syntax)Syntax
+
+```
+PI() 
+```
+
+## [](#return-type)Return Type
+
+`PI` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following example gets the value of pi:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_pow.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_pow.md
new file mode 100644
index 0000000..bcebd45
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_pow.md
@@ -0,0 +1,23 @@
+# [](#pow)POW
+
+Returns a number `<value>` raised to the specified power `<value>`.
+
+**Alias:** `POWER`
+
+## [](#syntax)Syntax
+
+```
+POW(<value>, <exponent>);
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The base value of the exponent `DOUBLE PRECISION` `<exponent>` The power value of the exponent `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`DOUBLE PRECISION`
+
+## [](#example)Example
+
+The following example calculates 2 to the power of 5:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_radians.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_radians.md
new file mode 100644
index 0000000..9a08e5d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_radians.md
@@ -0,0 +1,21 @@
+# [](#radians)RADIANS
+
+Converts degrees to radians.
+
+## [](#syntax)Syntax
+
+```
+RADIANS(<value>) 
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value to be converted to radians `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`DOUBLE PRECISION`
+
+## [](#example)Example
+
+The following example converts the value `180` in degrees to radians:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_random.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_random.md
new file mode 100644
index 0000000..88459a3
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_random.md
@@ -0,0 +1,19 @@
+# [](#random)RANDOM
+
+Returns a pseudo-random unsigned value greater than 0 and less than 1 of type `DOUBLE PRECISION`.
+
+## [](#syntax)Syntax
+
+```
+RANDOM()
+```
+
+## [](#return-types)Return Types
+
+`DOUBLE PRECISION`
+
+## [](#examples)Examples
+
+The following code example demonstrates using `RANDOM` without any other numeric functions. This generates a `DOUBLE PRECISION` value less than 1:
+
+To create a random integer number between two values, you can use `RANDOM` with the `FLOOR` function. If `a` is the lesser value and `b` is the greater value, compute `FLOOR(RANDOM() * (b - a + 1)) + a`. The following code example generates a random integer between 50 and 100:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_round.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_round.md
new file mode 100644
index 0000000..cbd55c3
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_round.md
@@ -0,0 +1,23 @@
+# [](#round)ROUND
+
+Rounds a value to a specified number of decimal places.
+
+## [](#syntax)Syntax
+
+```
+ROUND(<value> [, <decimal>])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value to be rounded   `<decimal>` Optional. An `INTEGER` constant that defines the decimal range of the returned value. By default, `ROUND` returns whole numbers. `INTEGER`
+
+## [](#return-types)Return Types
+
+`DOUBLE PRECISION`
+
+## [](#example)Example
+
+The following example returns the rounded value of 5.4. Since there is no specification of the decimal range, the functions returns a whole number:
+
+The following example rounds the value 5.6930 to 1 decimal place:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_sin.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_sin.md
new file mode 100644
index 0000000..b7be647
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_sin.md
@@ -0,0 +1,23 @@
+# [](#sin)SIN
+
+Trigonometric function that calculates the sine of a provided value.
+
+## [](#syntax)Syntax
+
+```
+SIN(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value that determines the returned sine in radians. `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`DOUBLE PRECISION`
+
+## [](#example)Example
+
+The following query calculates the sine of 0:
+
+The following query calculates the sine of pi:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_sqrt.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_sqrt.md
new file mode 100644
index 0000000..504599b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_sqrt.md
@@ -0,0 +1,27 @@
+# [](#sqrt)SQRT
+
+Returns the square root of a numeric expression.
+
+## [](#syntax)Syntax
+
+```
+SQRT(<value>);
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` Value that the `SQRT` function is applied to `DOUBLE PRECISION`
+
+## [](#notes)Notes
+
+- When input value is integer data type, it is implicitly converted to `DOUBLE PRECISION`.
+- When input value is `NUMERIC`, the `SQRT` function returns an error.
+- When input value is negative, the `SQRT` function returns an error.
+
+## [](#return-types)Return Types
+
+`DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following example returns the square root of 64:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_tan.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_tan.md
new file mode 100644
index 0000000..4aefd9c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_numeric_tan.md
@@ -0,0 +1,23 @@
+# [](#tan)TAN
+
+Trigonometric function that calculates the tangent of a specific value in radians.
+
+## [](#syntax)Syntax
+
+```
+TAN(<value>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The value that determines the returned tangent in radians. `DOUBLE PRECISION`
+
+## [](#return-type)Return Type
+
+`TAN` returns a value of type `DOUBLE PRECISION`.
+
+## [](#example)Example
+
+The following query calculates the tangent of 1.57 radians. 1.57 is approximately pi/2:
+
+The following query calculates the tangent of pi:
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session.md
new file mode 100644
index 0000000..cb979b8
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session.md
@@ -0,0 +1,8 @@
+## [](#session-functions)Session functions
+
+* * *
+
+- [CURRENT\_ACCOUNT](/sql_reference/functions-reference/session/current-account.html)
+- [CURRENT\_DATABASE](/sql_reference/functions-reference/session/current-database.html)
+- [CURRENT\_ENGINE](/sql_reference/functions-reference/session/current-engine.html)
+- [SESSION\_USER](/sql_reference/functions-reference/session/session-user.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_account.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_account.md
new file mode 100644
index 0000000..b7a18ea
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_account.md
@@ -0,0 +1,15 @@
+# [](#current_account)CURRENT\_ACCOUNT
+
+Returns the current account name
+
+## [](#syntax)Syntax
+
+```
+CURRENT_ACCOUNT()
+```
+
+## [](#return-types)Return Types
+
+`TEXT`
+
+## [](#example)Example
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_database.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_database.md
new file mode 100644
index 0000000..52eb8b0
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_database.md
@@ -0,0 +1,15 @@
+# [](#current_database)CURRENT\_DATABASE
+
+Returns the current database name
+
+## [](#syntax)Syntax
+
+```
+CURRENT_DATABASE()
+```
+
+## [](#return-types)Return Types
+
+`TEXT`
+
+## [](#example)Example
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_engine.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_engine.md
new file mode 100644
index 0000000..0662ff4
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_current_engine.md
@@ -0,0 +1,15 @@
+# [](#current_engine)CURRENT\_ENGINE
+
+Returns the current engine name. Returns `system` on the [system engine](/Guides/operate-engines/system-engine.html).
+
+## [](#syntax)Syntax
+
+```
+CURRENT_ENGINE()
+```
+
+## [](#return-types)Return Types
+
+`TEXT`
+
+## [](#example)Example
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_session_user.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_session_user.md
new file mode 100644
index 0000000..eb41f7d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_session_session_user.md
@@ -0,0 +1,33 @@
+# [](#session_user)SESSION\_USER
+
+Returns the name of the user running the current query.
+
+## [](#syntax)Syntax
+
+```
+SESSION_USER()
+```
+
+## [](#return-types)Return Types
+
+`TEXT`
+
+## [](#examples)Examples
+
+The following code example shows the effective privileges of the roles directly assigned to the user running the query:
+
+**Example**
+
+Dynamic security through a view which uses `session_user()`.
+
+```
+-- user bob created view:
+create view my_employee_data as select * from employees where user_name = session_user();
+
+-- user alice queries it:
+select * from my_employee_data; -- session_user() will be evaluated to 'alice' for this query
+```
+
+**Returns**
+
+user\_name … alice …
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string.md
new file mode 100644
index 0000000..8fa636e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string.md
@@ -0,0 +1,31 @@
+## [](#string-functions)String functions
+
+* * *
+
+- [BTRIM](/sql_reference/functions-reference/string/btrim.html)
+- [CONCAT](/sql_reference/functions-reference/string/concat.html)
+- [GEN\_RANDOM\_UUID\_TEXT](/sql_reference/functions-reference/string/gen-random-uuid-text.html)
+- [ILIKE](/sql_reference/functions-reference/string/ilike.html)
+- [LENGTH](/sql_reference/functions-reference/string/length.html)
+- [LIKE](/sql_reference/functions-reference/string/like.html)
+- [LOWER](/sql_reference/functions-reference/string/lower.html)
+- [LPAD](/sql_reference/functions-reference/string/lpad.html)
+- [LTRIM](/sql_reference/functions-reference/string/ltrim.html)
+- [OCTET\_LENGTH](/sql_reference/functions-reference/string/octet_length.html)
+- [POSITION](/sql_reference/functions-reference/string/position.html)
+- [REGEXP\_EXTRACT](/sql_reference/functions-reference/string/regexp-extract.html)
+- [REGEXP\_EXTRACT\_ALL](/sql_reference/functions-reference/string/regexp-extract-all.html)
+- [REGEXP\_LIKE](/sql_reference/functions-reference/string/regexp-like.html)
+- [REGEXP\_LIKE\_ANY](/sql_reference/functions-reference/string/regexp-like-any.html)
+- [REGEXP\_REPLACE](/sql_reference/functions-reference/string/regexp-replace.html)
+- [REPLACE](/sql_reference/functions-reference/string/replace.html)
+- [RPAD](/sql_reference/functions-reference/string/rpad.html)
+- [RTRIM](/sql_reference/functions-reference/string/rtrim.html)
+- [SPLIT\_PART](/sql_reference/functions-reference/string/split-part.html)
+- [STRING\_TO\_ARRAY](/sql_reference/functions-reference/string/string-to-array.html)
+- [STRPOS](/sql_reference/functions-reference/string/strpos.html)
+- [SUBSTRING, SUBSTR](/sql_reference/functions-reference/string/substring.html)
+- [TRIM](/sql_reference/functions-reference/string/trim.html)
+- [UPPER](/sql_reference/functions-reference/string/upper.html)
+- [URL\_DECODE](/sql_reference/functions-reference/string/url_decode.html)
+- [URL\_ENCODE](/sql_reference/functions-reference/string/url_encode.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_btrim.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_btrim.md
new file mode 100644
index 0000000..fa28a36
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_btrim.md
@@ -0,0 +1,43 @@
+# [](#btrim)BTRIM
+
+Removes the longest string containing only characters in `<trim_characters>` from both sides of the source string `<expression>`. If no `<trim_characters>` parameter is specified, the longest string containing only whitespace characters (ASCII Decimal 32) is removed from both sides of the specified source string `<expression>`.
+
+## [](#syntax)Syntax
+
+```
+BTRIM(<expression>[, <trim_characters>])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An expression that returns the string to be trimmed. `TEXT` `<trim_characters>` Optional. An expression that returns characters to trim from both sides of the `<expression>` string. If omitted, whitespace (ASCII Decimal 32) is trimmed. `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#examples)Examples
+
+The following example trims the character `x` from both sides of a string:
+
+```
+SELECT BTRIM('xxThe Acceleration Cupxxx', 'x') as result
+```
+
+result (TEXT) ‘The Acceleration Cup’
+
+The following example trims the characters `x` and `y` from both sides of a string. Note that the ordering of characters in `<trim_characters>` is irrelevant:
+
+```
+SELECT BTRIM('xyxyThe Acceleration Cupyyxx', 'xy') as result;
+```
+
+result (TEXT) ‘The Acceleration Cup’
+
+The following example omits the parameter, and thus trims whitespace from both sides of a string:
+
+```
+SELECT BTRIM('   The Acceleration Cup     ') as result;
+```
+
+result (TEXT) ‘The Acceleration Cup’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_concat.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_concat.md
new file mode 100644
index 0000000..72f7629
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_concat.md
@@ -0,0 +1,50 @@
+# [](#concat)CONCAT
+
+Concatenates, i.e. combines, the text representations of all the input parameters without a separator, in the order they are provided.
+
+## [](#syntax)Syntax
+
+```
+CONCAT( <expression>[, <expression>[, ...n]] );
+```
+
+**—OR—**
+
+```
+<expression> || <expression>
+```
+
+## [](#parameters)Parameters
+
+### [](#concat-function)`CONCAT` function
+
+Parameter Description Supported input types `<expression>[, ...n]` The expressions to be concatenated. Any type
+
+The parameters to the `CONCAT` function can be of any data type, and will be converted to their text representation before concatenation. `NULL` parameters to the `CONCAT` function are treated as empty strings and ignored. If all parameters are `NULL`, the result will be an empty string.
+
+### [](#-operator)`||` operator
+
+Parameter Description Supported input types `<expression>` The expressions to be concatenated. Any non-array type, but at least one `TEXT`
+
+To enable string concatenation, one parameter to the `||` operator must be of type `TEXT`, while the other parameter may be of any non-array data type. If one parameter to the `||` operator is `NULL`, the result will also be the non-null parameter; if both parameters are `NULL`, the result will be `NULL`.
+
+The concatenation operator `||` can also be used for [array concatenation](/sql_reference/functions-reference/array/array-concat.html).
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#example)Example
+
+The following example concatenates users’ `nicknames` and `emails` from the players table:
+
+```
+SELECT
+	CONCAT(nickname, ': ', email) as user_info
+FROM players
+LIMIT 5;
+```
+
+**Returns**:
+
+user\_info steven70: daniellegraham@example.net burchdenise: keith84@example.org stephanie86: zjenkins@example.org sabrina21: brianna65@example.org kennethpark: williamsdonna@example.com
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_gen_random_uuid_text.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_gen_random_uuid_text.md
new file mode 100644
index 0000000..2c3efaf
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_gen_random_uuid_text.md
@@ -0,0 +1,23 @@
+# [](#gen_random_uuid_text)GEN\_RANDOM\_UUID\_TEXT
+
+Returns a version 4 universally unique identifier (UUID) as defined by [RFC-4122](https://tools.ietf.org/html/rfc4122#section-4.4) as a `TEXT` value. This function accepts no arguments.
+
+## [](#syntax)Syntax
+
+```
+GEN_RANDOM_UUID_TEXT()
+```
+
+## [](#return-type)Return Type
+
+`GEN_RANDOM_UUID_TEXT` returns a result of type `TEXT`.
+
+## [](#example)Example
+
+The following code example generates a random UUID as a `TEXT` value:
+
+```
+SELECT gen_random_uuid_text() as id_col
+```
+
+id\_col (TEXT) ‘acc612ea-1a7d-4a49-b977-2486c7963d84’
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_ilike.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_ilike.md
new file mode 100644
index 0000000..2614d0e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_ilike.md
@@ -0,0 +1,49 @@
+# [](#ilike)ILIKE
+
+Allows matching of strings based on comparison to a pattern. `ILIKE` is normally used as part of a `WHERE` clause. `ILIKE` is case-insensitive; use [LIKE](/sql_reference/functions-reference/string/like.html) for case-sensitive pattern matching. Note that Firebolt uses the `POSIX` locale, which means that it only classifies the ASCII letters “A” through “Z” and “a” through “z” as letters.
+
+## [](#syntax)Syntax
+
+```
+<expression> ILIKE '<pattern>'
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` Any expression that evaluates to `TEXT` `TEXT` `<pattern>` Specifies the pattern to match (case-insensitive). `TEXT` constant. SQL wildcards are supported:
+
+\* Use an underscore (`_`) to match any single character  
+\* Use a percent sign (`%`) to match any number of any characters, including no characters.
+
+## [](#return-type)Return Type
+
+`BOOLEAN`
+
+## [](#example)Example
+
+Find nicknames from the `players` table that partially match the string “Joe” and any following characters as follows:
+
+```
+SELECT
+	playerid, nickname, email
+FROM
+	players
+WHERE
+	nickname ILIKE 'Joe%';
+```
+
+**Returns**:
+
+playerid nickname email 160 joedavis cgarcia@example.org 519 joe79 jennifer10@example.net 3692 joeli cperez@example.net 3891 joel11 joanncain@example.net 4233 joellong millerholly@example.net 4627 joebowen amandalewis@example.net
+
+## [](#unicode-behavior)Unicode Behavior
+
+Firebolt uses the `POSIX` locale, therefore `ILIKE` case insensitivity is limited to ASCII characters. The uppercase and lowercase versions of non-ASCII characters are not matched:
+
+```
+SELECT 'ENCYCLOPÆDIA' ILIKE 'encyclopædia'; -- returns false
+SELECT 'ENCYCLOPÆDIA' ILIKE 'encyclopÆdia'; -- returns true
+SELECT 'MÜNCHEN' ILIKE 'München'; -- returns false
+SELECT 'MÜNCHEN' ILIKE 'mÜnchen'; -- returns true
+SELECT 'Πσρ⋈' ILIKE 'πΣΡ%'; -- returns false
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_length.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_length.md
new file mode 100644
index 0000000..e914582
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_length.md
@@ -0,0 +1,31 @@
+# [](#length)LENGTH
+
+Calculates the length of the input string.
+
+When used with an array argument, `LENGTH` is a synonym for [ARRAY\_LENGTH](/sql_reference/functions-reference/array/array-length.html)
+
+## [](#syntax)Syntax
+
+```
+LENGTH(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The string or binary data for which to return the length. `TEXT`, `BYTEA`. For `ARRAY`, see [ARRAY\_LENGTH](/sql_reference/functions-reference/array/array-length.html)
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#example)Example
+
+Use the `LENGTH` to find the length of any string, such as:
+
+```
+SELECT LENGTH('The Accelerator Cup')
+```
+
+Spaces are included in the calculation of the total length of the string.
+
+**Returns**: `19`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_like.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_like.md
new file mode 100644
index 0000000..d400fac
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_like.md
@@ -0,0 +1,83 @@
+# [](#like)LIKE
+
+The LIKE is used for pattern matching to find similar strings in data. It’s often employed in the WHERE clause to filter results based on specific patterns. `LIKE` is case-sensitive; use [ILIKE](/sql_reference/functions-reference/string/ilike.html) for case-insensitive pattern matching.
+
+## [](#syntax)Syntax
+
+```
+<expression> LIKE '<pattern>'
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` Any expression that evaluates to `TEXT`. `TEXT` `<pattern>` Specifies the pattern to match (case-sensitive). `TEXT` constant. SQL wildcards are supported:
+
+\* Use an underscore (`_`) to match any single character  
+\* Use a percent sign (`%`) to match any number of any characters, including no characters.
+
+## [](#return-type)Return Type
+
+`BOOLEAN`
+
+## [](#example)Example
+
+Find nicknames from the `players` table that partially match the string “joe” and any following characters as follows:
+
+```
+SELECT
+	playerid, nickname, email
+FROM
+	players
+WHERE
+	nickname LIKE 'joe%';
+```
+
+**Returns**:
+
+```
++----------+----------+-------------------------+
+| playerid | nickname | email                   |
++----------+----------+-------------------------+
+| 160      | joedavis | cgarcia@example.org     |
+| 519 	   | joe79    | jennifer10@example.net  |
+| 3692 	   | joeli    | cperez@example.net      |
+| 3891	   | joel11   | joanncain@example.net   |
+| 4233 	   | joellong | millerholly@example.net |
+| 4627 	   | joebowen | amandalewis@example.net |
++----------+----------+-------------------------+
+```
+
+Note that the following would return no results, as `LIKE` matches case-sensitively, unlike `ILIKE`:
+
+```
+SELECT
+	playerid, nickname, email
+FROM
+	players
+WHERE
+	nickname LIKE 'Joe%';
+```
+
+Find nicknames from the `players` table that have a specific pattern:
+
+```
+SELECT
+	playerid, nickname, email
+FROM
+	players
+WHERE
+	nickname LIKE '%oe_e%';
+```
+
+The pattern %oe\_e% signifies any string that contains “oe” followed by any character (_ acts as a wildcard for a single character) and then “e”.
+
+**Returns**
+
+```
++----------+----------+-------------------------+
+| playerid | nickname | email                   |
++----------+----------+-------------------------+
+| 3891     | joel11    | joanncain@example.net  |
+| 4233     | joellong  | millerholly@example.net|
++----------+----------+-------------------------+
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_lower.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_lower.md
new file mode 100644
index 0000000..f94fba6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_lower.md
@@ -0,0 +1,36 @@
+# [](#lower)LOWER
+
+Converts the input string to lowercase characters. Note that Firebolt uses the `POSIX` locale, therefore `lower` only converts the ASCII characters “A” through “Z” to lowercase. Non-ASCII characters remain unchanged.
+
+## [](#syntax)Syntax
+
+```
+LOWER(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The string to be converted to lowercase characters. `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#example)Example
+
+The following example converts a game player’s username from uppercase to lowercase characters:
+
+```
+SELECT
+	LOWER('ESIMPSON') as username
+```
+
+**Returns**: `esimpson`
+
+Because Firebolt uses the `POSIX` locale, non-ASCII characters are not lowercased:
+
+```
+SELECT LOWER('MÜNCHEN')
+```
+
+**Returns**: `mÜnchen`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_lpad.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_lpad.md
new file mode 100644
index 0000000..94f78dc
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_lpad.md
@@ -0,0 +1,34 @@
+# [](#lpad)LPAD
+
+Adds a specified pad string to the start of the string repetitively up until the length of the resulting string is equivalent to an indicated length.
+
+The similar function to pad the end of a string is [RPAD](/sql_reference/functions-reference/string/rpad.html).
+
+## [](#syntax)Syntax
+
+```
+LPAD(<expression>, <value>[, <pad>])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types   `<expression>` The original string. If the length of the original string is larger than the length parameter, this function removes the overflowing characters from the string. `TEXT`   `<value>` The length of the string as an integer after it has been left-padded. `INTEGER`   `<pad>` The string to add to the start of the primary string `<expression>`. If left blank, `<pad>` defaults to whitespace characters. `TEXT`  
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#example)Example
+
+The following statement adds the string “UserName:” in front of the username string “esimpson” repetitively until the resulting string is equivalent to 17 characters in length.
+
+```
+SELECT
+	LPAD('esimpson', 17, 'UserName:');
+```
+
+**Returns**:
+
+```
+UserName:esimpson
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_ltrim.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_ltrim.md
new file mode 100644
index 0000000..fb48cdb
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_ltrim.md
@@ -0,0 +1,58 @@
+# [](#ltrim)LTRIM
+
+Removes the longest string containing only characters in `<trim_characters>` from the left side of the source string `<expression>`. If no `<trim_characters>` parameter is specified, the longest string containing only whitespace characters (ASCII Decimal 32) is removed from the left side of the specified source string `<expression>`.
+
+## [](#syntax)Syntax
+
+```
+LTRIM(<expression>[, <trim_characters>])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An expression that returns the string to be trimmed. `TEXT` `<trim_characters>` Optional. An expression that returns characters to trim from the left side of the `<expression>` string. If omitted, whitespace (ASCII Decimal 32) is trimmed. `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#examples)Examples
+
+The following example trims the character `x` from the left side of a string:
+
+```
+SELECT
+  LTRIM('xxThe Acceleration Cupxxx', 'x') 
+```
+
+**Returns**:
+
+```
+'The Acceleration Cupxxx'
+```
+
+The following example trims the characters `x` and `y` from the left side of a string. Note that the ordering of characters in `<trim_characters>` is irrelevant:
+
+```
+SELECT
+  LTRIM('xyxyThe Acceleration Cupyyxx', 'xy');
+```
+
+**Returns**:
+
+```
+'The Acceleration Cupyyxx'
+```
+
+The following example omits the `<trim_characters>` parameter, and thus trims whitespace from the left side of a string:
+
+```
+SELECT
+  LTRIM('   The Acceleration Cup     ');
+```
+
+**Returns**:
+
+```
+'The Acceleration Cup     '
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_octet_length.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_octet_length.md
new file mode 100644
index 0000000..e9c60ae
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_octet_length.md
@@ -0,0 +1,29 @@
+# [](#octet_length)OCTET\_LENGTH
+
+Calculates the length of the input string in bytes.
+
+## [](#syntax)Syntax
+
+```
+OCTET_LENGTH(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The string or binary data for which to return the length. `TEXT`, `BYTEA`
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#example)Example
+
+Use the `OCTET_LENGTH` to find the length of any string in bytes, such as:
+
+```
+SELECT LENGTH('🔥')
+```
+
+**Returns**: `4`
+
+Because the UTF8 encoding of ‘🔥’ has the byte sequence `0xF0 0x9F 0x94 0xA5`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_position.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_position.md
new file mode 100644
index 0000000..deb2504
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_position.md
@@ -0,0 +1,40 @@
+# [](#position)POSITION
+
+Returns the position of the substring found in the string, starting from 1. The returned value is for the first matching value, and not for any subsequent valid matches. In case the substring does not exist, functions will return 0.
+
+## [](#syntax)Syntax
+
+```
+POSITION(<substring> IN <string>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<substring>` The substring to search for. `TEXT` `<string>` The string that will be searched. `TEXT`
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#example)Example
+
+```
+SELECT
+	POSITION('hello' IN 'hello world') AS res;
+```
+
+**Returns**: `1`
+
+```
+SELECT
+	POSITION('world' IN 'hello world') AS res;
+```
+
+**Returns**: `7`
+
+```
+SELECT
+	POSITION('work' IN 'hello world') AS res;
+```
+
+**Returns**: `0`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_extract.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_extract.md
new file mode 100644
index 0000000..6edbe89
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_extract.md
@@ -0,0 +1,48 @@
+# [](#regexp_extract)REGEXP\_EXTRACT
+
+Returns the first match of `<pattern>` within the `<expression>`. If the pattern does not match, returns `NULL`. If you want to extract all matches, use [REGEXP\_EXTRACT\_ALL](/sql_reference/functions-reference/string/regexp-extract-all.html).
+
+## [](#syntax)Syntax
+
+```
+REGEXP_EXTRACT(<expression>, <pattern>[,'<flag>[...]',[<index>]])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The string from which to extract a substring, based on a regular expression. `TEXT` `<pattern` A [re2 regular expression](https://github.com/google/re2/wiki/Syntax) for matching with the string. `TEXT` `<flag>` Optional. Flag that allows additional controls over the regular’s expression matching behavior. If using multiple flags, you can include them in the same single-quote block without any separator character. Firebolt supports the following RE2 flags to override default matching behavior. With `-` in front, you can disable the flag.  
+\* `i` - Specifies case-insensitive matching.  
+\* `m` - Specifies multi-line mode. In this mode, `^` and `$` characters in the regex match the beginning and end of the line.  
+\* `s` - (Enabled per default) Specifies that the `.` metacharacter in regex matches the newline character in addition to any character in `.`  
+\* `U` - Specifies non-greedy mode. In this mode, the meaning of the metacharacters `*` and `+` in regex `<pattern>` are swapped with `*?` and `+?`, respectively. See the examples using flags below for the difference in how results are returned. `<index>` Optional. Indicates which subgroup of the expression match should be returned. The default value is `0` which means the whole match is returned, independent of any number of given subgroups. An `INTEGER` between `0` and `N` where `N` is the number subgroups in the `<pattern>`.
+
+## [](#return-types)Return Types
+
+`TEXT`
+
+## [](#example)Example
+
+```
+SELECT
+	REGEXP_EXTRACT('ABC 2024', '^[A-Z]+');
+```
+
+**Returns**: `"ABC"`
+
+Despite using subgroups in the regular expression, the full match will be returned as the optional `<index>` argument is not set (the default value `0` is used instead).
+
+```
+SELECT
+	REGEXP_EXTRACT('Learning about #REGEX in #Firebolt 2024', '#([A-Za-z]+) (\d+)');
+```
+
+**Returns**: `"#Firebolt 2024"`
+
+The regular expression contains two subgroups which allows us to set the `<index>` argument to something between `0` and `2`. Every other value will cause an exception to be thrown. Setting `<index>` to `0` would cause the full match `"#Firebolt 2024"` to be returned (same behavior as not setting this value, see the example above), while a `2` would return the second subgroup `"2024"`.
+
+```
+SELECT
+	REGEXP_EXTRACT('Learning about #REGEX in #Firebolt 2024', '#([a-z]+) (\d+)', 'i', 1);
+```
+
+**Returns**: `"Firebolt"`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_extract_all.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_extract_all.md
new file mode 100644
index 0000000..238aa3b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_extract_all.md
@@ -0,0 +1,44 @@
+# [](#regexp_extract_all)REGEXP\_EXTRACT\_ALL
+
+Returns an array that contains all matches of a `<pattern>` within the given `<expression>`. If the pattern does not match, returns an empty array. If you want return the first match of `<pattern>` within the `<expression>`, use [REGEXP\_EXTRACT](/sql_reference/functions-reference/string/regexp-extract.html).
+
+```
+REGEXP_EXTRACT_ALL(<expression>, <pattern>[,'<flag>[...]',[<index>]])
+```
+
+Parameter Description Supported input types `<expression>` The string from which to extract a substring, based on a regular expression. `TEXT` `<pattern>` A [re2 regular expression](https://github.com/google/re2/wiki/Syntax) for matching with the string. `TEXT` `<flag>` Optional. Flag that allows additional controls over the regular’s expression matching behavior. If using multiple flags, you can include them in the same single-quote block without any separator character. Firebolt supports the following RE2 flags to override default matching behavior. With `-` in front, you can disable the flag.  
+\* `i` - Specifies case-insensitive matching.  
+\* `m` - Specifies multi-line mode. In this mode, `^` and `$` characters in the regex match the beginning and end of the line.  
+\* `s` - (Enabled per default) Specifies that the `.` metacharacter in regex matches the newline character in addition to any character in `.`  
+\* `U` - Specifies non-greedy mode. In this mode, the meaning of the metacharacters `*` and `+` in regex `<pattern>` are swapped with `*?` and `+?`, respectively. See the examples using flags below for the difference in how results are returned. `<index>` Optional. Indicates which subgroup of each expression match should be returned. The default value is `0` which means the whole match is returned, independent of any number of given subgroups. An `INTEGER` between `0` and `N` where `N` is the number subgroups in the `<pattern>`.
+
+## [](#return-types)Return Types
+
+`ARRAY<TEXT>`
+
+## [](#example)Example
+
+```
+SELECT
+	REGEXP_EXTRACT_ALL('Hello Year 2023, yeah!', '[A-Za-z]+');
+```
+
+**Returns**: `["Hello", "Year", "yeah"]`
+
+Despite using subgroups in the regular expression, each full match will be returned as the optional `<index>` argument is not set (the default value `0` is used instead).
+
+```
+SELECT
+	REGEXP_EXTRACT_ALL('Learning about #REGEX in #Firebolt 2023', '#([A-Z])[a-z]+', 'i');
+```
+
+**Returns**: `["#REGEX", "#Firebolt"]`
+
+The regular expression contains two subgroups which allows us to set the `<index>` argument to something between `0` and `2`. Every other value will cause an exception to be thrown. Setting `<index>` to `0` would cause that all full matches `["#REGEX", "#Firebolt"]` are returned (same behavior as not setting this value, see the example above), while a `2` would return the second subgroup of each match `["EGEX", "irebolt"]`.
+
+```
+SELECT
+	REGEXP_EXTRACT_ALL('Learning about #REGEX in #Firebolt 2023', '#([A-Z])([a-z]+)', 'i', 1);
+```
+
+**Returns**: `["R", "F"]`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_like.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_like.md
new file mode 100644
index 0000000..4b5e821
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_like.md
@@ -0,0 +1,48 @@
+# [](#regexp_like)REGEXP\_LIKE
+
+Checks whether a text pattern matches a regular expression string. Returns a `BOOLEAN` value, specifically `false` if the text doesn’t match and `true` if it does match. This is a RE2 regular expression.
+
+## [](#syntax)Syntax
+
+```
+REGEXP_LIKE(<expression>, '<pattern>'[,'<flag>[...]'])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The text searched for a match using the RE2 pattern. `TEXT` `<pattern>` An RE2 regular expression pattern used to search for a match in the `<expression>`. [RE2 regular expression](https://github.com/google/re2/wiki/Syntax) `<flag>` Optional. Flags allow additional controls over the regular’s expression matching behavior. If using multiple flags, you can include them in the same single-quote block without any separator character. Firebolt supports the following RE2 flags to override default matching behavior. With `-` in front you can disable the flag.  
+\* `i` - Specifies case-insensitive matching.  
+\* `m` - Specifies multi-line mode. In this mode, `^` and `$` characters in the regex match the beginning and end of line.  
+\* `s` - (Enabled per default) Specifies that the `.` metacharacter in regex matches the newline character in addition to any character in `.`  
+\* `U` - Specifies non-greedy mode. In this mode, the meaning of the metacharacters `*` and `+` in regex `<pattern>` are swapped with `*?` and `+?`, respectively. See the examples using flags below for the difference in how results are returned.
+
+## [](#return-type)Return Type
+
+`BOOLEAN`
+
+## [](#example)Example
+
+```
+SELECT
+    REGEXP_LIKE('123','[a-z]');
+```
+
+**Returns**: `false`
+
+```
+SELECT
+    REGEXP_LIKE('123','\\\\d+');
+```
+
+**Returns**: `true`
+
+## [](#example-using-flags)Example using flags
+
+The `i` flag causes the regular expression to be case-insensitive. Without this flag, this query would return `false` as no match is found.
+
+```
+SELECT
+	REGEXP_LIKE('ABC', '[a-z]', 'i');
+```
+
+**Returns**: `true`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_like_any.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_like_any.md
new file mode 100644
index 0000000..ea13fdd
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_like_any.md
@@ -0,0 +1,53 @@
+# [](#regexp_like_any)REGEXP\_LIKE\_ANY
+
+Checks whether a given string matches any regular expression pattern from a specified list of patterns. Returns `FALSE` if it doesn’t match, or `TRUE` if it matches.
+
+## [](#syntax)Syntax
+
+```
+REGEXP_LIKE_ANY(<expression>, ['<pattern1>', '<pattern2>', ...])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The input string or column to be evaluated against the regular expression patterns. `TEXT` `<pattern>` A list of regular expression patterns to match against the expression. ARRAY\[`TEXT`] where each element complies to the [RE2 regular expression](https://github.com/google/re2/wiki/Syntax) syntax
+
+## [](#return-type)Return Type
+
+`BOOLEAN`
+
+## [](#examples)Examples
+
+The following code example checks whether the string `123` matches either the `[a-z]` expression, which specifies any lowercase letter, or the `[1-9]+` expression, which specifies one or more digits:
+
+```
+SELECT
+    REGEXP_LIKE_ANY('123',['[a-z]','[1-9]+']);
+```
+
+**Returns**: The function returns `TRUE` because the string `'123'` matches the second pattern.
+
+The following code example checks whether the string `!@#$%^&*()` matches either the `\d+` expression, which specifies one or more digits, or the `[a-z|A-Z]+` expression, which specifies one or more lowercase or uppercase characters:
+
+```
+SELECT 
+    REGEXP_LIKE_ANY('!@#$%^&*()', [ '\d+', '[a-z|A-Z]+' ]);
+```
+
+**Returns**: The function returns `FALSE` because the string does not match any of the regular expressions in the array.
+
+The following code example checks if the string `a` matches either the `[1-9]+` expression, which specifies one or more digits, or a `NULL` value:
+
+```
+SELECT 
+    REGEXP_LIKE_ANY('a', ['[1-9]+', NULL]);
+```
+
+The following code example checks whether the string `123` matches either the `[1-9]+` expression, which specifies one or more digits, or the `NULL` value, in the array.
+
+```
+SELECT 
+    REGEXP_LIKE_ANY('123', ['[1-9]+', NULL]);
+```
+
+**Returns**: The function returns `TRUE` because the string matches the first regular expression. The `NULL` element does not affect the result as long as a match is found. If a match is not found, the function returns `FALSE`, even if there is a `NULL` element in the array.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_replace.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_replace.md
new file mode 100644
index 0000000..27a8674
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_regexp_replace.md
@@ -0,0 +1,99 @@
+# [](#regexp_replace)REGEXP\_REPLACE
+
+Matches a pattern in the input string and replaces the first matched portion (from the left) with the specified replacement.
+
+## [](#syntax)Syntax
+
+```
+REGEXP_REPLACE(<input>, <pattern>, <replacement>)
+```
+
+# [](#regexp_replace_all)REGEXP\_REPLACE\_ALL
+
+Matches a pattern in the input string and replaces all matched portions with the specified replacement.
+
+## [](#syntax-1)Syntax
+
+```
+REGEXP_REPLACE_ALL(<input>, <pattern>, <replacement>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<input>` The string to search for a matching pattern `TEXT` `<pattern>` An [RE2 regular expression](https://github.com/google/re2/wiki/Syntax) for matching with the string input. `TEXT` `<replacement>` The string to replace the matching pattern found in the input. This argument can include the following special sequences:  
+\* `\&` - To indicate that the substring matching the entire pattern should be inserted.  
+\* `\n` - Where *n* is a digit from 1 to 9, to indicate that the substring matching the n’th capturing group (parenthesized subexpression) of the pattern should be inserted. If pattern doesn’t have *n* capturing groups, the `\n` is ignored.  
+\* `\\` - results in a single &lt;br&gt;* `\c` - Specifies for any other character, c results in the same sequence \\c  
+Note, that for string literals the above escaping rules apply *after* string literals escaping rules for `\`. See examples below. `TEXT`
+
+If any of the arguments to these functions is `NULL`, the return value is `NULL`.
+
+### [](#return-type)Return Type
+
+`TEXT`
+
+## [](#examples)Examples
+
+Replace first occurence of `!` with `!!!`
+
+```
+SELECT REGEXP_REPLACE('Hello, world!', '!', '!!!');
+```
+
+**Returns**: `'Hello, world!!!'`
+
+Remove leading and trailing spaces
+
+```
+SELECT REGEXP_REPLACE_ALL('     Hello world ! ', '^[ ]+|[ ]+$', '');
+```
+
+**Returns**: `'Hello world !'`
+
+Duplicate every character
+
+```
+SELECT REGEXP_REPLACE_ALL('Hello, World!', '.', '\&\&')
+```
+
+**Returns**: `'HHeelllloo,, WWoorrlldd!!'`
+
+Mask email address by leaving first character only (Note: this is for illustrative purposes only, the email matching pattern is too simplistic)
+
+```
+SELECT REGEXP_REPLACE(email, '(\w)[\w\.]+@([\w]+\.)+([\w]+)', '\1***@\2\3')
+FROM UNNEST([
+  'matt123@hotmail.com',
+  'joe.doe@gmail.com',
+  '12345@www.atg.wa.gov'
+]) email
+```
+
+**Returns**:
+
+```
+'m***@hotmail.com'
+'j***@gmail.com'
+'1***@www.atg.wa.gov'
+```
+
+Convert dates into US format
+
+```
+SELECT REGEXP_REPLACE(event_date::TEXT, '(\d{4})-(\d{2})-(\d{2})', '\2/\3/\1')
+FROM UNNEST([
+  DATE '1970-08-07',
+  DATE '2000-04-22',
+  DATE '2002-07-25',
+  DATE '2010-11-11'
+]) event_date
+```
+
+**Returns**
+
+```
+08/07/1970
+04/22/2000
+07/25/2002
+11/11/2010
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_replace.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_replace.md
new file mode 100644
index 0000000..ef732fb
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_replace.md
@@ -0,0 +1,42 @@
+# [](#replace)REPLACE
+
+Replaces all occurrences of the `<pattern>` substring within the `<expression>` with the `<replacement>` substring.
+
+## [](#syntax)Syntax
+
+```
+REPLACE (<expression>, <pattern, <replacement>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The original string that will be searched for instances of the `<pattern>`. `TEXT` `<pattern>` The substring to be searched and replaced in the string. `TEXT` `<replacement>` The substring to replace the original substring defined by `<pattern>`. To remove the `<pattern>` substring with no replacement, you can use a empty string `''` as the replacement value. `TEXT`
+
+## [](#example)Example
+
+In the example below, “two” in “Level two” is replaced with “three”.
+
+```
+SELECT
+	REPLACE('Level two','two','three') AS level; 
+```
+
+**Returns**: `Level three`
+
+In this example below, “eight” is replaced by an empty string.
+
+```
+SELECT
+	REPLACE('Level eight',' eight','') AS level;
+```
+
+**Returns**: `Level`
+
+In this following example, the substring “five” is not found in the original string, so the string is returned unchanged.
+
+```
+SELECT
+	REPLACE('Level four','five','six') AS level;
+```
+
+**Returns**: `Level four`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_rpad.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_rpad.md
new file mode 100644
index 0000000..0d6206d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_rpad.md
@@ -0,0 +1,26 @@
+# [](#rpad)RPAD
+
+Adds a specified pad string to the end of the string repetitively up until the length of the resulting string is equivalent to an indicated length.
+
+The similar function to pad the start of a string is [LPAD](/sql_reference/functions-reference/string/lpad.html).
+
+## [](#syntax)Syntax
+
+```
+RPAD(<expression>, <value>[, <pad>])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The original string. If the length of the original string is larger than the length parameter, this function removes the overflowing characters from the string. `TEXT` `<value>` The integer length that the string will be after it has been left-padded. A negative number returns an empty string. `INTEGER` `<pad>` The string to add to the end of the primary string `<expression`. If left blank, `<pad>` defaults to whitespace characters.  
+
+## [](#example)Example
+
+The following statement adds the string “ABC” to the end of the string “Firebolt” repetitively until the resulting string is equivalent to 20 characters in length.
+
+```
+SELECT
+	RPAD('Firebolt', 20, 'ABC');
+```
+
+**Returns**: `FireboltABCABCABCABC`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_rtrim.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_rtrim.md
new file mode 100644
index 0000000..0b00faf
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_rtrim.md
@@ -0,0 +1,58 @@
+# [](#rtrim)RTRIM
+
+Removes the longest string containing only characters in `<trim_characters>` from the right side of the source string `<expression>`. If no `<trim_characters>` parameter is specified, the longest string containing only whitespace characters (ASCII Decimal 32) is removed from the right side of the specified source string `<expression>`.
+
+## [](#syntax)Syntax
+
+```
+RTRIM(<expression>[, <trim_characters>])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` An expression that returns the string to be trimmed. `TEXT` `<trim_characters>` Optional. An expression that returns characters to trim from the right side of the `<expression>` string. If omitted, whitespace (ASCII Decimal 32) is trimmed. `TEXT`
+
+## [](#return-types)Return Types
+
+`TEXT`
+
+## [](#examples)Examples
+
+The following example trims the character `x` from the right side of a string:
+
+```
+SELECT
+  RTRIM('xxThe Acceleration Cupxxx', 'x') 
+```
+
+**Returns**:
+
+```
+'xxThe Acceleration Cup'
+```
+
+The following example trims the characters `x` and `y` from the right side of a string. Note that the ordering of characters in `<trim_characters>` is irrelevant:
+
+```
+SELECT
+  RTRIM('xyxyThe Acceleration Cupyyxx', 'xy');
+```
+
+**Returns**:
+
+```
+'xyxyThe Acceleration Cup'
+```
+
+The following example omits the `<trim_characters>` parameter, and thus trims whitespace from the right side of a string:
+
+```
+SELECT
+  RTRIM('   The Acceleration Cup     ');
+```
+
+**Returns**:
+
+```
+'   The Acceleration Cup'
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_split_part.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_split_part.md
new file mode 100644
index 0000000..10af77d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_split_part.md
@@ -0,0 +1,75 @@
+# [](#split_part)SPLIT\_PART
+
+Splits `<string>` at occurrences of `<delimiter>` and returns the `<index>`‘th field, with 1 being the first index. If `<index>` is negative, returns the `abs(<index>)`‘th-from-last field. If `<delimiter>` is empty, `<string>` is returned at `<index>` 1. If `abs(<index>)` is larger than the number of fields, returns an empty string. The function raises an error for `<index>` 0.
+
+## [](#syntax)Syntax
+
+```
+SPLIT_PART(<string>, <delimiter>, <index>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<string>` The string to be split. `TEXT` `<delimiter>` The character used to split the string. `TEXT` `<index>` The index position of the substring to return within the split parts. `INTEGER`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example uses the delimiter `#` to split the string `'hello#world'`, and returns the first segment:
+
+```
+SELECT
+	SPLIT_PART('hello#world','#',1) AS res;
+```
+
+**Returns**
+
+`'hello'`
+
+**Example**
+
+The following code example uses the delimiter `|` to split the string `'this|is|my|test'`, and returns the second to last segment:
+
+```
+SELECT
+	SPLIT_PART('this|is|my|test', '|', -2) AS res;
+```
+
+**Returns**
+
+`'my'`
+
+**Example**
+
+The following code example uses an empty delimiter `''` to split the string `'hello world'`, and returns the first segment:
+
+```
+SELECT
+	SPLIT_PART('hello world', '', 1) AS res;
+```
+
+**Returns**
+
+`hello world`
+
+In the previous code example, `SPLIT_PART` sees the empty delimiter and interprets the entire string as the first and only part of the string and returns ‘hello world’.
+
+**Example**
+
+The following code example uses an empty delimiter `''` to split the string `'hello world'`, and returns the first segment:
+
+```
+SELECT
+	SPLIT_PART('hello world', '', 7) AS res;
+```
+
+**Returns**
+
+`''`
+
+In the previous code example, `SPLIT_PART` sees the empty delimiter and interprets the entire string as the first and only part of the string. Because there is no seventh part to return, `SPLIT_PART` returns an empty string.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_string_to_array.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_string_to_array.md
new file mode 100644
index 0000000..3c22a9c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_string_to_array.md
@@ -0,0 +1,58 @@
+# [](#string_to_array)STRING\_TO\_ARRAY
+
+Splits a string into an array of strings based on a specified delimiter, with the following behaviors:
+
+- If the delimiter is an empty string `''`, the result is an array containing the entire original input string as a single element.
+- If the delimiter is `NULL`, the string is split into individual characters, with one character per array element.
+
+## [](#syntax)Syntax
+
+```
+STRING_TO_ARRAY(<string>, <delimiter>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description `<string>` The string to split. `<delimiter>` The separator to split the string by.
+
+## [](#return-types)Return Types
+
+`ARRAY(TEXT)`
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example splits the string `stephen70|esimpson|ruthgill|` at each `|` character and returns the resulting array as `nicknames`:
+
+```
+SELECT STRING_TO_ARRAY('stephen70|esimpson|ruthgill|', '|') AS nicknames;
+```
+
+**Returns**
+
+nicknames (ARRAY(TEXT)) {stephen70,esimpson,ruthgill,””}
+
+**Example**
+
+The following code example calls `STRING_TO_ARRAY` with an empty delimiter, producing an array containing a single element which contains the input text:
+
+```
+SELECT STRING_TO_ARRAY('firebolt', '') as size_one_array;
+```
+
+**Returns**
+
+size\_one\_array (ARRAY(TEXT)) {firebolt}
+
+**Example**
+
+The following example calls `STRING_TO_ARRAY` with `NULL` as the delimiter, splitting the text into individual characters:
+
+```
+SELECT STRING_TO_ARRAY('firebolt', NULL) AS single_characters;
+```
+
+**Returns**
+
+single\_characters (ARRAY(TEXT)) {f,i,r,e,b,o,l,t}
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_strpos.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_strpos.md
new file mode 100644
index 0000000..70d6439
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_strpos.md
@@ -0,0 +1,40 @@
+# [](#strpos)STRPOS
+
+Returns the position of the substring found in the string, starting from 1. The returned value is for the first matching value, and not for any subsequent valid matches. In case the substring does not exist, functions will return 0.
+
+## [](#syntax)Syntax
+
+```
+STRPOS(<string>, <substring>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<string>` The string that will be searched. `TEXT` `<substring>` The substring to search for. `TEXT`
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#example)Example
+
+```
+SELECT
+	STRPOS('hello world','hello') AS res;
+```
+
+**Returns**: `1`
+
+```
+SELECT
+	STRPOS('hello world','world') AS res;
+```
+
+**Returns**: `7`
+
+```
+SELECT
+	STRPOS('hello world','work') AS res;
+```
+
+**Returns**: `0`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_substring.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_substring.md
new file mode 100644
index 0000000..f8df81c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_substring.md
@@ -0,0 +1,61 @@
+## [](#substring-substr)SUBSTRING, SUBSTR
+
+Returns a substring starting at the character indicated by the `<start>` index and including the number of characters defined by `<length>`. Character indexing starts at index 1.
+
+## [](#syntax)Syntax
+
+```
+SUBSTRING(<expression> [FROM <start>] [FOR <length>])
+SUBSTRING(<expression>, <start> [, <length>])
+SUBSTR(<expression>, <start> [, <length>])
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The input string. `TEXT`,`BYTEA` `<start>` Optional. The starting position for the substring. 1 is the first character. If value &lt; 1 then it start from negative position (all negative positions treated as empty). `BIGINT` `<length>` Optional. The number of characters to be returned by the `SUBSTRING` function. Must be positive or 0. If not specified, `count` by default returns all of the string not specified by the `start` parameter. `BIGINT`
+
+At least one of the optional arguments `<start>` and `<length>` must be given.
+
+Negative `<start>` values begin the substring before the input `<expression>`. Positions before the input `<expression>` are considered empty.
+
+## [](#return-type)Return Type
+
+`TEXT` or `BYTEA`. The type of `<expression>`
+
+##### [](#example)Example
+
+In the example below, the string is offset by 1 and so the `SUBSTRING` command begins at the first letter, “h”. The `<length>` of 5 indicates the resulting string should be only five characters long.
+
+```
+SELECT
+	SUBSTRING('hello world' FROM 1 FOR 5);
+```
+
+**Returns**: `hello`
+
+In this next example `<length>` is not provided. This means all characters are included after the `<start>` index, which is 7.
+
+```
+SELECT
+	SUBSTRING('hello world' FROM 7);
+```
+
+**Returns**: `world`
+
+For negative `<start>` values, empty positions before the input string are selected. Thus, without `<length>` negative values will select the entire input `<string>`.
+
+```
+SELECT
+	SUBSTRING('hello world' FROM -2);
+```
+
+**Returns**: `hello world`
+
+With a negative `<start>` value and `<length>`, the empty positions before the string are counted towards the substring length. In this example, beginning the substring at `-2` for `8` characters includes 3 empty positions and 5 positions with characters from the input `<expression>`.
+
+```
+SELECT
+	SUBSTRING('hello world' FROM -2 FOR 8);
+```
+
+**Returns**: `hello`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_trim.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_trim.md
new file mode 100644
index 0000000..93f9907
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_trim.md
@@ -0,0 +1,77 @@
+# [](#trim)TRIM
+
+Removes the longest string containing only characters in `<trim_characters>` from the left, right, or both sides of the source string `<expression>`. If no `<trim_characters>` parameter is specified, the longest string containing only whitespace characters (ASCII Decimal 32) is removed. If neither `LEADING`, `TRAILING`, nor `BOTH` are specified, characters are removed from both sides of the specified source string `<expression>`.
+
+## [](#syntax)Syntax
+
+```
+TRIM([LEADING | TRAILING | BOTH] [<trim_characters>] FROM <expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `LEADING | TRAILING | BOTH` Optional. Specifies from which part or parts of the `<expression>` to remove the specified `<trim_characters>`. If omitted, this defaults to `BOTH`.
+
+`LEADING` - trims from the beginning of the specified string
+
+`TRAILING` - trims from the end of the specified string.
+
+`BOTH` - trims from the beginning and the end of the specified string. `<trim_characters>` Optional. An expression that returns characters to trim from the right side of the `<expression>` string. If omitted, whitespace (ASCII Decimal 32) is trimmed. `TEXT` `<expression>` An expression that returns the string to be trimmed. `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#example)Example
+
+The following example trims the characters `x` and `y` from the right side of a string, since the `TRAILING` parameter is specified. Note that the ordering of characters in `<trim_characters>` is irrelevant:
+
+```
+SELECT
+  TRIM(TRAILING 'xy' FROM 'xyxyThe Acceleration Cupyyxx');
+```
+
+**Returns**:
+
+```
+'xyxyThe Acceleration Cup'
+```
+
+In the following example, no part of the string is specified for `TRIM`, so it defaults to `BOTH`.
+
+```
+SELECT
+  TRIM('xy' FROM 'xyxyThe Acceleration Cupyyxx');
+```
+
+**Returns**:
+
+```
+'The Acceleration Cup'
+```
+
+The following example omits the `<trim_characters>` parameter but specifies the `TRAILING` parameter, and thus trims whitespace from the right side of a string:
+
+```
+SELECT
+  TRIM(TRAILING FROM '   The Acceleration Cup     ');
+```
+
+**Returns**:
+
+```
+'   The Acceleration Cup'
+```
+
+The following example omits the `<trim_characters>` parameter and specifies no part of the string, and thus trims whitespace from both sides of a string:
+
+```
+SELECT
+  TRIM(FROM '   The Acceleration Cup     ');
+```
+
+**Returns**:
+
+```
+'The Acceleration Cup'
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_upper.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_upper.md
new file mode 100644
index 0000000..aab3df5
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_upper.md
@@ -0,0 +1,36 @@
+# [](#upper)UPPER
+
+Converts the input string to uppercase characters. Note that Firebolt uses the `POSIX` locale, therefore `upper` only converts the ASCII characters “a” through “z” to uppercase. Non-ASCII characters remain unchanged.
+
+## [](#syntax)Syntax
+
+```
+UPPER(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The string to be converted to uppercase characters. `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#example)Example
+
+The following example converts a game player’s username from lowercase to uppercase characters:
+
+```
+SELECT
+	UPPER('esimpson') as username
+```
+
+**Returns**: `ESIMPSON`
+
+Because Firebolt uses the `POSIX` locale, non-ASCII characters are not uppercased:
+
+```
+SELECT UPPER('München')
+```
+
+**Returns**: `MüNCHEN`
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_url_decode.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_url_decode.md
new file mode 100644
index 0000000..44a0938
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_url_decode.md
@@ -0,0 +1,31 @@
+# [](#url_decode)URL\_DECODE
+
+Decodes [percent-encoded](https://en.wikipedia.org/wiki/Percent-encoding) characters and replaces them with their binary value.
+
+## [](#syntax)Syntax
+
+```
+URL_DECODE(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The string to be decoded. `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#example)Example
+
+The example below decodes the percent-encoded parameters of an URL:
+
+```
+SELECT URL_DECODE('https://www.firebolt.io/?example_id%3D1%26hl%3Den');
+```
+
+**Returns**: https://www.firebolt.io/?example\_id=1&amp;hl=en
+
+## [](#related)Related
+
+- [URL\_ENCODE](/sql_reference/functions-reference/string/url_encode.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_url_encode.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_url_encode.md
new file mode 100644
index 0000000..cb2584f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_string_url_encode.md
@@ -0,0 +1,37 @@
+# [](#url_encode)URL\_ENCODE
+
+Encodes all characters that are not unreserved using [percent-encoding](https://en.wikipedia.org/wiki/Percent-encoding).
+
+Unreserved characters are defined according to [W3C RFC 3986](https://www.rfc-editor.org/rfc/rfc3986.html).
+
+```
+unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"
+```
+
+## [](#syntax)Syntax
+
+```
+URL_ENCODE(<expression>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` The string to be encoded. `TEXT`
+
+## [](#return-type)Return Type
+
+`TEXT`
+
+## [](#example)Example
+
+The example below converts characters that are not unreserved that appear in the parameter section of the URL:
+
+```
+SELECT CONCAT('https://www.firebolt.io/?', URL_ENCODE('example_id=1&hl=en'));
+```
+
+**Returns**: https://www.firebolt.io/?example\_id%3D1%26hl%3Den
+
+## [](#related)Related
+
+- [URL\_DECODE](/sql_reference/functions-reference/string/url_decode.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued.md
new file mode 100644
index 0000000..2e66060
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued.md
@@ -0,0 +1,18 @@
+## [](#table-valued-functions)Table-valued functions
+
+A table-valued function (TVF) returns a set of rows. You can use a table-valued function anywhere you can use a table. For example, the `generate_series` TVF generates a range of numbers as rows.
+
+The following code example generates a series of numbers from 1 to 100 and selects each number as x from the resulting series:
+
+```
+SELECT x FROM generate_series(1, 100) r(x);
+```
+
+You can use the `list_objects` TVF to explore files on Amazon S3. Use functions such as `read_parquet` to read data from Amazon S3.
+
+* * *
+
+- [GENERATE\_SERIES](/sql_reference/functions-reference/table-valued/generate-series.html)
+- [LIST\_OBJECTS](/sql_reference/functions-reference/table-valued/list-objects.html)
+- [READ\_CSV](/sql_reference/functions-reference/table-valued/read_csv.html)
+- [READ\_PARQUET](/sql_reference/functions-reference/table-valued/read_parquet.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_generate_series.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_generate_series.md
new file mode 100644
index 0000000..941a245
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_generate_series.md
@@ -0,0 +1,29 @@
+# [](#generate_series)GENERATE\_SERIES
+
+Generates a single rowset of values from `start` to `stop`, with a step size of `step`. `GENERATE_SERIES` is a table-valued function.
+
+## [](#syntax)Syntax
+
+```
+GENERATE_SERIES ( <start>, <stop> [, <step> ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<start>` The first value in the interval. `BIGINT`, `INTEGER` `<stop>` The last value in the interval.  
+The series stops once the last generated step value exceeds the stop value. `BIGINT`, `INTEGER` `<step>` Optional literal integer value to set step. If not included, the default step is 1. `BIGINT`, `INTEGER`
+
+## [](#return-type)Return Type
+
+Setof `INTEGER` if all operands are of type `INTEGER`, otherwise setof `BIGINT`.
+
+## [](#example)Example
+
+```
+SELECT n, DATE_ADD('DAY', n, '2023-02-02') result 
+FROM GENERATE_SERIES(1, 10, 2) s(n)
+```
+
+**Returns**:
+
+n result 1 2023-02-03 00:00:00 3 2023-02-05 00:00:00 5 2023-02-07 00:00:00 7 2023-02-09 00:00:00 9 2023-02-11 00:00:00
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_list_objects.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_list_objects.md
new file mode 100644
index 0000000..94fb6fb
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_list_objects.md
@@ -0,0 +1,122 @@
+# [](#list_objects)LIST\_OBJECTS
+
+A table-valued function (TVF) that lists objects and their metadata from Amazon S3. The function can use either a location object (recommended) or direct credentials to access the data. Each row in the output contains four columns: `object_name` (`TEXT`), `object_type` (`TEXT`), `object_bytes` (`BIGINT`), and `file_timestamp` (`TIMESTAMPTZ`).
+
+## [](#syntax)Syntax
+
+```
+-- Using location object (recommended)
+LIST_OBJECTS (
+  LOCATION => location_name
+)
+|
+-- Using static credentials
+LIST_OBJECTS (
+  URL => <url>
+  [, AWS_ACCESS_KEY_ID => <aws_access_key_id>]
+  [, AWS_SECRET_ACCESS_KEY => <aws_secret_access_key>]
+  [, AWS_SESSION_TOKEN => <aws_session_token>]
+  [, AWS_ROLE_ARN => <aws_role_arn>]
+  [, AWS_ROLE_EXTERNAL_ID => <aws_role_externakl_id>]
+)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `LOCATION` The name of a location object that contains the S3 URL and credentials. This is the recommended approach. See [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html) for details. `IDENTIFIER` `URL` The location of the Amazon S3 bucket containing your files. The expected format is `s3://{bucket_name}/{full_file_path}`. `TEXT` `AWS_ACCESS_KEY_ID` The AWS access key ID. `TEXT` `AWS_SECRET_ACCESS_KEY` The AWS secret access key. `TEXT` `AWS_SESSION_TOKEN` The AWS session token. `TEXT` `AWS_ROLE_ARN` The AWS role ARN. `TEXT` `AWS_ROLE_EXTERNAL_ID` The AWS role external ID. `TEXT`
+
+## [](#return-type)Return Type
+
+The output is a table with four columns:
+
+- `object_name` (`TEXT`)
+- `object_type` (`TEXT`)
+- `object_bytes` (`BIGINT`)
+- `last_modified` (`TIMESTAMPTZ`)
+
+**Column Descriptions**
+
+- **`object_name`** : Contains both the full path and the file extension.
+- **`object_type`** : Can be either “file” or “folder”.
+  
+  - If `object_type` = “folder”, the `object_bytes` and `last_modified` columns will contain `NULL` values, as folders do not have associated sizes or timestamps.
+  - If `object_type` = “file”, the following apply:
+    
+    1. The `last_modified` column is populated from the `LastModified` attribute in Amazon S3. Note that AWS does not expose the creation timestamp, so the values in this column only differ from the creation time if an immutable object has been overwritten.
+    2. The `object_bytes` column contains the size of the file in bytes.
+
+Amazon S3 is not a traditional filesystem. In AWS, what is commonly referred to as “folders” is called “common\_prefixes,” and what are typically considered “files” are referred to as “objects.”
+
+## [](#examples)Examples
+
+### [](#using-location-object-to-store-credentials)Using LOCATION object to store credentials
+
+**Best practice**
+
+Firebolt recommends using a `LOCATION` object to store credentials for authentication.
+
+The following code example retrieves all objects from the specified `LOCATION` using the `LIST_OBJECTS` function:
+
+```
+SELECT * FROM LIST_OBJECTS(
+    LOCATION => my_location
+);
+```
+
+**Returns**:
+
+object\_name object\_type object\_bytes last\_modified data/file1.csv file 1421277 2023-02-27 10:49:13+01 data/folder1/ folder NULL NULL
+
+### [](#using-static-credentials)Using static credentials
+
+The following code examples show how to list all objects (folders) that start with a specified prefix within an Amazon S3 bucket. You can specify either a part of the prefix or the full prefix. For example, the URLs ending with the prefixes `fire` or `firebolt_sample_dataset` both return identical results because both are valid matches for the `firebolt_sample_dataset` folder as follows:
+
+```
+SELECT * FROM LIST_OBJECTS(url => 's3://firebolt-publishing-public/help_center_assets/fire')
+```
+
+and
+
+```
+SELECT * FROM LIST_OBJECTS(url => 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset')
+```
+
+**Both return**:
+
+object\_name (TEXT) object\_type (TEXT) object\_bytes (BIGINT) last\_modified (TIMESTAMPTZ) help\_center\_assets/firebolt\_sample\_dataset/ folder NULL NULL
+
+The following code example shows how to list all objects such as files, folders, and associated metadata, that start with a specified prefix in an Amazon S3 bucket:
+
+```
+SELECT * FROM LIST_OBJECTS(url => 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/')
+```
+
+**Returns**:
+
+object\_name (TEXT) object\_type (TEXT) object\_bytes (BIGINT) last\_modified (TIMESTAMPTZ) help\_center\_assets/firebolt\_sample\_dataset/players.json file 1,421,277 2023-02-27 10:49:13+01 help\_center\_assets/firebolt\_sample\_dataset/levels.csv file 83,596 2023-02-27 11:06:52+01 help\_center\_assets/firebolt\_sample\_dataset/tournaments.csv file 83,351 2022-12-15 15:34:14+01 help\_center\_assets/firebolt\_sample\_dataset/games.json file 872 2023-02-27 13:18:54+01 help\_center\_assets/firebolt\_sample\_dataset/rankings/ folder NULL NULL help\_center\_assets/firebolt\_sample\_dataset/playstats/ folder NULL NULL
+
+The following code examples show how to list all objects such as files and associated metadata, that start with a specified prefix in an Amazon S3 bucket. The URLs ending with the prefixes `lev` or `levels.csv` return identical results because both are valid matches for the `levels.csv` file as follows:
+
+```
+SELECT * FROM LIST_OBJECTS(url => 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/lev')
+```
+
+and
+
+```
+SELECT * FROM LIST_OBJECTS(url => 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv')
+```
+
+**Both Return**:
+
+object\_name (TEXT) object\_type (TEXT) object\_bytes (BIGINT) last\_modified (TIMESTAMPTZ) help\_center\_assets/firebolt\_sample\_dataset/levels.csv file 83,596 2023-02-27 11:06:52+01
+
+The following code example shows how to use your Amazon credentials to list objects in an Amazon S3 bucket that is not publicly accessible:
+
+```
+SELECT * FROM LIST_OBJECTS(url => 's3://example_bucket/foo.csv', AWS_ACCESS_KEY_ID => 'my_key_id', AWS_SECRET_ACCESS_KEY => 'my_secret_key')
+```
+
+**Returns**:
+
+object\_name (TEXT) object\_type (TEXT) object\_bytes (BIGINT) last\_modified (TIMESTAMPTZ) foo.csv file 10 2024-06-12 9:30:00 UTC
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_read_csv.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_read_csv.md
new file mode 100644
index 0000000..a5f8bba
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_read_csv.md
@@ -0,0 +1,110 @@
+# [](#read_csv)READ\_CSV
+
+A table-valued function (TVF) that reads CSV files from Amazon S3. The function can use either a location object (recommended) or direct credentials to access the data. `READ_CSV` returns a table with data from the specified CSV file, where each cell is read as `TEXT`.
+
+## [](#syntax)Syntax
+
+```
+-- Using LOCATION object (recommended)
+READ_CSV ( 
+  LOCATION => location_name
+  [, COMPRESSION => <file_compression>]
+  [, HEADER => { TRUE | FALSE }]
+  [, DELIMITER => <field_delimiter>]
+  [, QUOTE => { "'" | '"' | SINGLE_QUOTE | DOUBLE_QUOTE}]
+  [, NULL_STRING => <null_string>]
+  [, ESCAPE => <escape_character>]
+  [, SKIP_BLANK_LINES => { TRUE | FALSE }]
+  [, EMPTY_FIELD_AS_NULL => { TRUE | FALSE }]
+)
+|
+-- Using static credentials
+READ_CSV ( 
+  URL => <url>
+  [, COMPRESSION => <file_compression>]
+  [, AWS_ACCESS_KEY_ID => <aws_access_key_id>]
+  [, AWS_SECRET_ACCESS_KEY => <aws_secret_access_key>]
+  [, AWS_SESSION_TOKEN => <aws_session_token>]
+  [, AWS_ROLE_ARN => <aws_role_arn>]
+  [, AWS_ROLE_EXTERNAL_ID => <aws_role_external_id>]
+  [, HEADER => { TRUE | FALSE }]
+  [, DELIMITER => <field_delimiter>]
+  [, QUOTE => { "'" | '"' | SINGLE_QUOTE | DOUBLE_QUOTE}]
+  [, NULL_STRING => <null_string>]
+  [, ESCAPE => <escape_character>]
+  [, SKIP_BLANK_LINES => { TRUE | FALSE }]
+  [, EMPTY_FIELD_AS_NULL => { TRUE | FALSE }]
+)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types LOCATION The name of a location object that contains the Amazon S3 URL and credentials. Firebolt recommends using `LOCATION` to store credentials for authentication. See [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html) for details. `IDENTIFIER` `URL` The location containing your files in an Amazon S3 bucket. The expected format is `s3://{bucket_name}/{full_file_path_glob_pattern}`. `TEXT` `COMPRESSION` The [compression type](/sql_reference/commands/data-definition/create-external-table.html#compression) of the input file. If `compression` is not set, `compression` is inferred from the file extension. `TEXT` `AWS_ACCESS_KEY_ID` The AWS access key ID. `TEXT` `AWS_SECRET_ACCESS_KEY` The AWS secret access key. `TEXT` `AWS_SESSION_TOKEN` The AWS session token. `TEXT` `AWS_ROLE_ARN` The AWS role arn. `TEXT` `AWS_ROLE_EXTERNAL_ID` The AWS role external ID. `TEXT` `HEADER` Set to `TRUE` if the first row of the CSV file contains a header row containing the column names. `BOOL` `DELIMITER` Specify the character used to separate fields. The default delimiter is a comma (`,`). `TEXT` `QUOTE` Specify the character used for quoting fields. The default is double quote (`"`). If a single quote is specified, the quote character will be set to (`'`). Accepts only `DOUBLE_QUOTE`, `SINGLE_QUOTE`, `'`, or `"`. `TEXT` `NULL_STRING` Specify the string used to represent `NULL` values. The default is an empty string, which means that empty strings are interpreted as `NULL` values. `TEXT` `ESCAPE` Specify the character used to escape special characters. The default character is the quote (`'`) character. `TEXT` `SKIP_BLANK_LINES` Set to `TRUE` to ignore blank lines in the file. `BOOL` `EMPTY_FIELD_AS_NULL` Specify whether empty fields should be interpreted as `NULL` values. The default is `TRUE`. If set to `FALSE`, empty fields are interpreted as empty strings. `BOOL`
+
+## [](#return-type)Return Type
+
+The result is a table with the data from the CSV file. Each cell is read as a `TEXT`.
+
+## [](#examples)Examples
+
+### [](#using-location-object)Using LOCATION object
+
+**Best practice**
+
+Firebolt recommends using a `LOCATION` object to store credentials for authentication.
+
+The following code example reads a CSV file from the location specified by `my_location`, treating the first row as a header containing column names:
+
+```
+SELECT * FROM READ_CSV(
+    LOCATION => my_location,
+    HEADER => true
+);
+```
+
+### [](#using-static-credentials)Using static credentials
+
+```
+SELECT * FROM READ_CSV(
+    URL => 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv',
+    HEADER => true
+);
+```
+
+**Example**
+
+In the following example, the `URL` is set as the first positional parameter and reads a CSV file:
+
+```
+SELECT * FROM READ_CSV('s3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv');
+```
+
+**Returns**:
+
+f0 f1 f2 f3 f4 f5 f6 f7 f8 … LevelID GameID Level Name LevelType NextLevel MinPointsToPass MaxPoints NumberOfLaps … 1 1 1 Thunderbolt Circuit FastestLap 2 5 20 5 … 2 1 2 Velocity Vale FirstToComplete 3 15 30 10 … 3 1 3 Raceway Ridge FastestLap 4 25 40 20 … 4 1 4 Nitro Narrows FirstToComplete 5 60 100 10 … 5 1 5 Thunder Road FirstToComplete 6 80 150 15 … 6 1 6 Burnout Boulevard Drift 7 50 80 8 … 7 1 7 Speed Street FastestLap 8 40 70 7 … 8 1 8 Racing Ravine FastestLap 9 60 100 20 … 9 1 9 Drift District Drift 10 100 250 25 … 10 1 10 Acceleration Alley FirstToComplete null 200 500 50 …
+
+**Example**
+
+The following example accepts `URL` as a named parameter and reads a CSV file with column names in the first row:
+
+```
+SELECT * FROM READ_CSV(URL => 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv', 
+        HEADER => true);
+```
+
+**Returns**
+
+LevelID GameID Level Name LevelType NextLevel MinPointsToPass MaxPoints NumberOfLaps … 1 1 Thunderbolt Circuit FastestLap 2 5 20 5 20 … 2 1 Velocity Vale FirstToComplete 3 15 30 10 10 … 3 1 Raceway Ridge FastestLap 4 25 40 20 20 … 4 1 Nitro Narrows FirstToComplete 5 60 100 10 10 … 5 1 Thunder Road FirstToComplete 6 80 150 15 15 … 6 1 Burnout Boulevard Drift 7 50 80 8 8 … 7 1 Speed Street FastestLap 8 40 70 7 7 … 8 1 Racing Ravine FastestLap 9 60 100 20 20 … 9 1 Drift District Drift 10 100 250 25 25 … 10 1 Acceleration Alley FirstToComplete null 200 500 50 50 …
+
+**Example**
+
+The following example reads a CSV with headers and reads empty values as empty strings, rather than `NULL` values:
+
+```
+SELECT * FROM READ_CSV(URL => 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/levels.csv',
+        HEADER => true, EMPTY_FIELD_AS_NULL => false);
+```
+
+**Returns**:
+
+LevelID GameID Level Name LevelType … 1 1 Thunderbolt Circuit FastestLap 2 … 2 1 Velocity Vale FirstToComplete 3 … 3 1 Raceway Ridge FastestLap 4 … 4 1 Nitro Narrows FirstToComplete 5 … 5 1 Thunder Road FirstToComplete 6 … 6 1 Burnout Boulevard Drift 7 … 7 1 Speed Street FastestLap 8 … 8 1 Racing Ravine FastestLap 9 … 9 1 Drift District Drift 10 … 10 1 Acceleration Alley FirstToComplete   …
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_read_parquet.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_read_parquet.md
new file mode 100644
index 0000000..19d7285
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_table_valued_read_parquet.md
@@ -0,0 +1,87 @@
+# [](#read_parquet)READ\_PARQUET
+
+A table-valued function (TVF) that reads data from Parquet files stored in Amazon S3. The function can use either a location object (recommended) or direct credentials to access the data. `READ_PARQUET` returns a table with data from the specified Parquet file.
+
+## [](#syntax)Syntax
+
+```
+-- Using location object (recommended)
+READ_PARQUET (
+  LOCATION => location_name
+)
+|
+-- Using static credentials
+READ_PARQUET (
+  URL => <file_url>
+  [, AWS_ACCESS_KEY_ID => <aws_access_key_id>]
+  [, AWS_SECRET_ACCESS_KEY => <aws_secret_access_key>]
+  [, AWS_SESSION_TOKEN => <aws_session_token>]
+  [, AWS_ROLE_ARN => <aws_role_arn>]
+  [, AWS_ROLE_EXTERNAL_ID => <aws_role_external_id>]
+)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `LOCATION` The name of a location object that contains the Amazon S3 URL and credentials. Firebolt recommends using `LOCATION` to store credentials for authentication. See [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html) for details. `IDENTIFIER` `URL` The location of the Amazon S3 bucket containing your files. The expected format is `s3://{bucket_name}/{full_file_path_glob_pattern}`. `TEXT` `AWS_ACCESS_KEY_ID` The AWS access key ID. `TEXT` `AWS_SECRET_ACCESS_KEY` The AWS secret access key. `TEXT` `AWS_SESSION_TOKEN` The AWS session token. `TEXT` `AWS_ROLE_ARN` The AWS role ARN. `TEXT` `AWS_ROLE_EXTERNAL_ID` The AWS role external ID. `TEXT`
+
+- When using static credentials:
+  
+  - The `URL` can be passed as either the first positional parameter or a named parameter
+  - If you provide either `AWS_ACCESS_KEY_ID` or `AWS_SECRET_ACCESS_KEY`, you must provide both
+  - Providing an AWS session token is optional
+  - Credentials are not required for accessing public buckets
+
+## [](#return-type)Return Type
+
+The result is a table with data from the Parquet files. Columns are read and parsed using their inferred data types.
+
+## [](#best-practice)Best practice
+
+Firebolt recommends using a `LOCATION` object to store credentials for authentication.
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example reads the first 5 rows from a Parquet file using a `LOCATION` object to store credentials for authentication:
+
+```
+SELECT * 
+FROM READ_PARQUET(
+    LOCATION => my_location
+) 
+LIMIT 5;
+```
+
+**Example**
+
+The following code example reads the first 5 rows from a Parquet file using static credentials for authentication:
+
+```
+SELECT * 
+FROM READ_PARQUET(
+    URL => 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/playstats/TournamentID=92/cc2a2a0b4e8b4fb39abf20a956e7cc3e-0.parquet'
+) 
+LIMIT 5;
+```
+
+**Returns**
+
+GameID PlayerID Timestamp SelectedCar CurrentLevel CurrentSpeed CurrentPlayTime CurrentScore Event ErrorCode 1 845 2022-10-27 13:36:33 Solara 1 0 0 0 Brake NoError 1 845 2022-10-27 13:36:33 Solara 1 339 0.9872 2 RightTurn GraphicsFreeze 1 845 2022-10-27 13:36:34 Solara 1 288 1.9744 20 Tilt NoError 1 845 2022-10-27 13:36:35 Solara 1 260 2.9616 53 Block TextNotFound 1 845 2022-10-27 13:36:36 Solara 1 196 3.9488 81 FullSpeed NoError
+
+### [](#using-url)Using URL
+
+- The `URL` can be passed as either the first positional parameter or a named parameter. For example, the following two queries will both read the same file:
+- Credentials are optional.
+
+```
+SELECT * FROM READ_PARQUET('s3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/playstats/TournamentID=92/cc2a2a0b4e8b4fb39abf20a956e7cc3e-0.parquet');
+SELECT * FROM READ_PARQUET(URL => 's3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/playstats/TournamentID=92/cc2a2a0b4e8b4fb39abf20a956e7cc3e-0.parquet');
+```
+
+- The `url` can represent a single file or a [glob](https://en.wikipedia.org/wiki/Glob_%28programming%29) pattern. If a glob pattern is used, all files matching the pattern will be read:
+
+```
+SELECT * FROM READ_PARQUET('s3://firebolt-publishing-public/help_center_assets/firebolt_sample_dataset/playstats/*.parquet')
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector.md
new file mode 100644
index 0000000..d811ed7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector.md
@@ -0,0 +1,12 @@
+## [](#vector-functions)Vector functions
+
+* * *
+
+- [VECTOR\_ADD](/sql_reference/functions-reference/vector/vector-add.html)
+- [VECTOR\_COSINE\_DISTANCE](/sql_reference/functions-reference/vector/vector-cosine-distance.html)
+- [VECTOR\_COSINE\_SIMILARITY](/sql_reference/functions-reference/vector/vector-cosine-similarity.html)
+- [VECTOR\_EUCLIDEAN\_DISTANCE](/sql_reference/functions-reference/vector/vector-euclidean-distance.html)
+- [VECTOR\_INNER\_PRODUCT](/sql_reference/functions-reference/vector/vector-inner-product.html)
+- [VECTOR\_MANHATTAN\_DISTANCE](/sql_reference/functions-reference/vector/vector-manhattan-distance.html)
+- [VECTOR\_SQUARED\_EUCLIDEAN\_DISTANCE](/sql_reference/functions-reference/vector/vector-squared-euclidean-distance.html)
+- [VECTOR\_SUBTRACT](/sql_reference/functions-reference/vector/vector-subtract.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_add.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_add.md
new file mode 100644
index 0000000..0bc7903
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_add.md
@@ -0,0 +1,35 @@
+## [](#vector_add)VECTOR\_ADD
+
+Returns an array that is the sum of two input arrays.
+
+## [](#syntax)Syntax
+
+```
+VECTOR_ADD(<array>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The first array in the addition calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric). `<array>` The second array in the addition calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric).
+
+## [](#notes)Notes
+
+Both input `ARRAY` arguments must have the same number of elements.
+
+## [](#return-type)Return Type
+
+`VECTOR_ADD` returns a result of type `ARRAY(BIGINT)` if the elements of `<array>` are of type `INT`, and returns a result of type `ARRAY(DOUBLE PRECISION)` if the elements are of type `REAL`. For other element types, `VECTOR_ADD` returns a result that matches the original element type, or follows Firebolt’s [type conversion](../../data-types.html#type-conversion) rules to convert them to compatible data types.
+
+## [](#examples)Examples
+
+**Example**
+
+The following code example adds the two vectors, `[1, 2, 5]` and `[3, 4, -1]`, by computing `1+3`, `2+4`, and `5+(-1)`, which yields `[4, 6, 3]`:
+
+```
+select vector_add([1, 2, 5], [3, 4, -2]) as res
+```
+
+**Returns**
+
+res (ARRAY(BIGINT)) {4,6,3}
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_cosine_distance.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_cosine_distance.md
new file mode 100644
index 0000000..34ebc47
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_cosine_distance.md
@@ -0,0 +1,35 @@
+## [](#vector_cosine_distance)VECTOR\_COSINE\_DISTANCE
+
+Returns the cosine distance between two vectors, calculated based on the angle (θ) between them. Vector cosine distance emphasizes the directional difference between the vectors, rather than magnitude. It is calculated as `1 - cos(θ)`, where `cos(θ)` is the [cosine similarity](./vector-cosine-similarity) between the vectors. `VECTOR_COSINE_DISTANCE` returns a value in the range `[0, 2]`. A vector cosine distance of `0` means that the vectors are identical in direction. A distance of `1` means that they are orthogonal and have no correlation. A distance of `2` means that they point in opposite directions.
+
+## [](#syntax)Syntax
+
+```
+VECTOR_COSINE_DISTANCE(<array>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The first array used in the distance calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric). `<array>` The second array used in the distance calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric).
+
+## [](#notes)Notes
+
+Both input `array` arguments must have the same number of elements.
+
+## [](#return-type)Return Type
+
+`DOUBLE`
+
+## [](#examples)Examples
+
+**Example**
+
+The following code returns the cosine distance between two vectors:
+
+```
+SELECT VECTOR_COSINE_DISTANCE([1, 2], [3, 4]) AS distance;
+```
+
+**Returns**
+
+distance (DOUBLE PRECISION) 0.01613008990009257
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_cosine_similarity.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_cosine_similarity.md
new file mode 100644
index 0000000..55f1b7b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_cosine_similarity.md
@@ -0,0 +1,59 @@
+## [](#vector_cosine_similarity)VECTOR\_COSINE\_SIMILARITY
+
+Returns the cosine similarity between two vectors, calculated based on the angle (θ) between them. Vector cosine similarity measures how closely two vectors point in the same direction, and is calculated as `cos(θ)`. `VECTOR_COSINE_SIMILARITY` returns a value in the range `[-1, 1]`. A vector cosine similarity of `1` means that the vectors are identical in direction. A similarity of `0` means that they are orthogonal and have no correlation. A similarity of `-1` means that they point in opposite directions.
+
+## [](#syntax)Syntax
+
+```
+VECTOR_COSINE_SIMILARITY(<array>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The first array used in the similarity calculation Any array of [numeric data types](/sql_reference/data-types.html#numeric). `<array>` The second array used in the similarity calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric).
+
+## [](#notes)Notes
+
+Both input `array` arguments must have the same number of elements.
+
+## [](#return-type)Return Type
+
+`DOUBLE`
+
+## [](#examples)Examples
+
+**Example**
+
+The following code returns the cosine similarity between two vectors that point in very similar directions:
+
+```
+SELECT VECTOR_COSINE_SIMILARITY([1, 2], [3, 4]) AS similarity;
+```
+
+**Returns**
+
+similarity (DOUBLE PRECISION) 0.9838699100999074
+
+**Example**
+
+The following code returns the cosine similarity between two vectors that point in very different directions:
+
+```
+SELECT VECTOR_COSINE_SIMILARITY([1, 2], [-3, -4]) AS similarity;
+```
+
+**Returns**
+
+similarity (DOUBLE PRECISION) -0.9838699100999074
+
+**Example**
+
+The following code returns the cosine similarity between two vectors that are orthogonal to each other:
+
+```
+SELECT VECTOR_COSINE_SIMILARITY([2, 0], [0, 2]) AS similarity;
+```
+
+**Returns**
+
+similarity (DOUBLE PRECISION) 0
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_euclidean_distance.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_euclidean_distance.md
new file mode 100644
index 0000000..2414aea
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_euclidean_distance.md
@@ -0,0 +1,35 @@
+## [](#vector_euclidean_distance)VECTOR\_EUCLIDEAN\_DISTANCE
+
+Returns the Euclidean distance, or L2 distance, between two vectors. The Euclidean distance measures the shortest distance between two points in space along a straight line. It is calculated by summing the squared distances of a pair of vector elements, and then taking the square root.
+
+## [](#syntax)Syntax
+
+```
+VECTOR_EUCLIDEAN_DISTANCE(<array>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The first array used in the distance calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric). `<array>` The second array used in the distance calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric).
+
+## [](#notes)Notes
+
+Both input `array` arguments must have the same number of elements.
+
+## [](#return-type)Return Type
+
+`DOUBLE`
+
+## [](#examples)Examples
+
+**Example**
+
+The following code returns the Euclidean distance between two vectors:
+
+```
+SELECT VECTOR_EUCLIDEAN_DISTANCE([1, 2], [3, 4]) AS distance;
+```
+
+**Returns**
+
+distance (DOUBLE PRECISION) 2.8284271247461903
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_inner_product.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_inner_product.md
new file mode 100644
index 0000000..b292979
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_inner_product.md
@@ -0,0 +1,61 @@
+## [](#vector_inner_product)VECTOR\_INNER\_PRODUCT
+
+Returns the inner product, also known as the dot or scalar product, between two vectors. The inner product measures how closely two vectors align with each other, both in magnitude and the cosine of the angle between them. It is calculated by multiplying the corresponding elements of the vectors and then summing the results.
+
+If the vectors have similar directions and large magnitudes, the inner product has a large positive value. If they are orthogonal, the inner product is zero, regardless of magnitude. If they point in roughly opposite directions, and at least one has a small magnitude, the inner product is small and negative.
+
+## [](#syntax)Syntax
+
+```
+VECTOR_INNER_PRODUCT(<array>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The first array used in the inner product calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric). `<array>` The second array used in the inner product calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric).
+
+## [](#notes)Notes
+
+Both input `array` arguments must have the same number of elements.
+
+## [](#return-type)Return Type
+
+`DOUBLE`
+
+## [](#examples)Examples
+
+**Example**
+
+The following code returns the inner product of two vectors that have similar directions and magnitudes:
+
+```
+SELECT VECTOR_INNER_PRODUCT([1, 2], [3, 4]) AS product;
+```
+
+**Returns**
+
+product (DOUBLE PRECISION) 11
+
+**Example**
+
+The following code returns the inner product of two vectors that are orthogonal to each other:
+
+```
+SELECT VECTOR_INNER_PRODUCT([3, 4], [-4, 3]) AS product;
+```
+
+**Returns**
+
+product (DOUBLE PRECISION) 0
+
+**Example**
+
+The following code returns the inner product of two vectors that are pointing in very different directions that are not orthogonal:
+
+```
+SELECT VECTOR_INNER_PRODUCT([3, 4], [4, -2]) AS product;
+```
+
+**Returns**
+
+product (DOUBLE PRECISION) 4
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_manhattan_distance.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_manhattan_distance.md
new file mode 100644
index 0000000..a0712e4
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_manhattan_distance.md
@@ -0,0 +1,35 @@
+## [](#vector_manhattan_distance)VECTOR\_MANHATTAN\_DISTANCE
+
+Returns the Manhattan, or L1 distance, between two vectors. The Manhattan distance measures the total distance by moving strictly along orthogonal axes, similar to navigating streets in a city grid. It is calculated as the sum of absolute differences between corresponding elements of two vectors.
+
+## [](#syntax)Syntax
+
+```
+VECTOR_MANHATTAN_DISTANCE(<array>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The first array used in the distance calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric). `<array>` The second array used in the distance calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric).
+
+## [](#notes)Notes
+
+Both input `array` arguments must have the same number of elements.
+
+## [](#return-type)Return Type
+
+`DOUBLE`
+
+## [](#examples)Examples
+
+**Example**
+
+The following code returns the Manhattan distance between two vectors: The Manhattan distance is calculated as the sum of absolute differences: |3 - 1| + |2 - 4| = 4.
+
+```
+SELECT VECTOR_MANHATTAN_DISTANCE([1, 4], [3, 2]) AS distance;
+```
+
+**Returns**
+
+distance (DOUBLE PRECISION) 4
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_squared_euclidean_distance.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_squared_euclidean_distance.md
new file mode 100644
index 0000000..e1f0226
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_squared_euclidean_distance.md
@@ -0,0 +1,59 @@
+## [](#vector_squared_euclidean_distance)VECTOR\_SQUARED\_EUCLIDEAN\_DISTANCE
+
+Returns the squared [Euclidean distance](/sql_reference/functions-reference/vector/vector-euclidean-distance.html), or squared [L2 distance](/sql_reference/functions-reference/vector/vector-euclidean-distance.html) between two vectors. The squared Euclidean distance measures how far apart two vectors based on the size of their differences, without considering direction. By squaring the difference, it emphasizes larger differences, which can help in finding outliers or large deviations.
+
+## [](#syntax)Syntax
+
+```
+VECTOR_SQUARED_EUCLIDEAN_DISTANCE(<array>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The first array used in the distance calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric). `<array>` The second array used in the distance calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric).
+
+## [](#notes)Notes
+
+Both input `array` arguments must have the same number of elements.
+
+## [](#return-type)Return Type
+
+`DOUBLE`
+
+## [](#examples)Examples
+
+**Example**
+
+The following code returns the squared Euclidean distance between two vectors:
+
+```
+SELECT VECTOR_SQUARED_EUCLIDEAN_DISTANCE([1, 2], [3, 4]) AS distance;
+```
+
+**Returns**
+
+distance (DOUBLE PRECISION) 8
+
+**Example**
+
+The following code returns the squared Euclidean distance between two identical vectors:
+
+```
+SELECT VECTOR_SQUARED_EUCLIDEAN_DISTANCE([1, 1], [1, 1]) AS distance;
+```
+
+**Returns**
+
+distance (DOUBLE PRECISION) 0
+
+**Example**
+
+The following code returns the squared Euclidean distance between two vectors that are very far apart:
+
+```
+SELECT VECTOR_SQUARED_EUCLIDEAN_DISTANCE([1, 1], [10, 10]) AS distance;
+```
+
+**Returns**
+
+distance (DOUBLE PRECISION) 162
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_subtract.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_subtract.md
new file mode 100644
index 0000000..9fa03e7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_vector_vector_subtract.md
@@ -0,0 +1,35 @@
+## [](#vector_subtract)VECTOR\_SUBTRACT
+
+Returns an array that is the difference of two input arrays.
+
+## [](#syntax)Syntax
+
+```
+VECTOR_SUBTRACT(<array>, <array>)
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<array>` The first array in the difference calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric). `<array>` The second array in the difference calculation. Any array of [numeric data types](/sql_reference/data-types.html#numeric).
+
+## [](#notes)Notes
+
+Both input `array` arguments must have the same number of elements.
+
+## [](#return-type)Return Type
+
+`VECTOR_SUBTRACT` returns a result of type `ARRAY(BIGINT)` if the elements of `<array>` are of type `INT`, and returns a result of type `ARRAY(DOUBLE PRECISION)` if the elements are of type `REAL`. For other element types, `VECTOR_ADD` returns a result that matches the original element type, or follows Firebolt’s [type conversion](../../data-types.html#type-conversion) rules to convert them to compatible data types.
+
+## [](#examples)Examples
+
+**Example**
+
+The following example subtracts the vector `[3, 4, -4]` from `[1, 5, 6]` by computing `1-3`, `5-4`, and `6-(-2)`, which yields `[-2, 1, 8]`:
+
+```
+select vector_subtract([1, 5, 6], [3, 4, -2]) as res
+```
+
+**Returns**
+
+res (ARRAY(BIGINT)) {-2,1,8}
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window.md
new file mode 100644
index 0000000..d19a884
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window.md
@@ -0,0 +1,117 @@
+## [](#window-functions)Window functions
+
+Some functions support an optional `frame_clause`.
+
+The `frame_clause` can be one of the following:
+
+```
+    { RANGE | ROWS } <frame_start>
+    { RANGE | ROWS } BETWEEN <frame_start> AND <frame_end>
+```
+
+where `<frame_start>` and `<frame_end>` is one of the following:
+
+```
+  UNBOUNDED PRECEDING
+  offset PRECEDING
+  CURRENT ROW
+  offset FOLLOWING
+  UNBOUNDED FOLLOWING
+```
+
+The `frame_clause` specifies the set of rows constituting the window frame within the current partition. The frame can be specified in `RANGE` or `ROWS` mode; in each case, the frame runs from the `<frame_start>` to the `<frame_end>`. If `<frame_end>` is omitted, the end defaults to `CURRENT ROW`.
+
+**Usage**
+
+- The default framing option is `RANGE UNBOUNDED PRECEDING`, which is the same as `RANGE BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW`. With an `ORDER BY` clause, this sets the frame to be all rows from the partition start through the current row’s last `ORDER BY` peer. Without an `ORDER BY` clause, all rows of the partition are included in the window frame, since all rows become peers of the current row.
+- The number of rows to the end of the frame is limited by the number of rows to the end of the partition; for rows near the partition ends, the frame might contain fewer rows than elsewhere.
+
+**UNBOUNDED PRECEDING, UNBOUNDED FOLLOWING**
+
+- A `<frame_start>` of `UNBOUNDED PRECEDING` means that the frame starts with the first row of the partition. Similarly a `<frame_end>` of `UNBOUNDED FOLLOWING` means that the frame ends with the last row of the partition.
+
+**CURRENT ROW**
+
+- In `RANGE` mode, a `<frame_start>` of `CURRENT ROW` means the frame starts with the current row’s first peer row (a row that the window’s `ORDER BY` clause sorts as equivalent to the current row), while a `<frame_end>` of `CURRENT ROW` means the frame ends with the current row’s last peer row.
+- In `ROWS` mode, `CURRENT ROW` simply means the current row.
+
+**offset PRECEDING, offset FOLLOWING**
+
+- For the `offset PRECEDING` and `offset FOLLOWING` frame options, the offset must be an expression not containing any variables, aggregate functions, or window functions. The meaning of the offset depends on the frame mode:
+  
+  - In `ROWS` mode, the offset must yield a non-null, non-negative integer, and the option means that the frame starts or ends the specified number of rows before or after the current row.
+  - In `RANGE` mode, these options require that the `ORDER BY` clause specify exactly one column. The offset specifies the maximum difference between the value of that column in the current row and its value in preceding or following rows of the frame. The data type of the offset expression varies depending on the data type of the ordering column. For numeric ordering columns it is typically of the same type as the ordering column. The offset is still required to be non-null and non-negative, though the meaning of “non-negative” depends on the data type.
+  - In `ROWS` mode, `0 PRECEDING` and `0 FOLLOWING` are equivalent to `CURRENT ROW`. This normally holds in `RANGE` mode as well, for an appropriate data-type-specific meaning of “zero”.
+
+**Restrictions**
+
+- `frame_start` cannot be `UNBOUNDED FOLLOWING`
+- `frame_end` cannot be `UNBOUNDED PRECEDING`
+- `frame_end` cannot appear earlier in the above list of `frame_start` and `frame_end` options than the `frame_start` choice does. For example `RANGE BETWEEN CURRENT ROW AND offset PRECEDING` is not allowed, but `ROWS BETWEEN 7 PRECEDING AND 8 PRECEDING` is allowed, even though it would never select any rows.
+
+**Example**
+
+The example below is querying test scores for students in various grade levels. Unlike a regular `AVG()` aggregation, the window function allows us to see how each student individually compares to the average test score for their grade level, as well as compute the average test score while looking at different slices of the data for different grade levels – narrowing down the set of rows that constitutes the window using framing options such as PRECEDING or FOLLOWING.
+
+```
+SELECT
+  first_name,
+  grade_level,
+  test_score,
+  ROUND(AVG(test_score) OVER (PARTITION BY grade_level), 2) AS test_score_avg,
+  ROUND(AVG(test_score) OVER (PARTITION BY grade_level ORDER BY test_score ASC ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING), 2) AS avg_1p_1f,
+  ROUND(AVG(test_score) OVER (PARTITION BY grade_level ORDER BY test_score ASC ROWS BETWEEN 2 PRECEDING AND 2 FOLLOWING), 2) AS avg_2p_2f,
+  ROUND(AVG(test_score) OVER (PARTITION BY grade_level ORDER BY test_score ASC ROWS BETWEEN UNBOUNDED PRECEDING AND 1 FOLLOWING), 2) AS avg_up_2f
+FROM
+  class_test
+ORDER BY 
+  grade_level, 
+  test_score;
+```
+
+**Returns**:
+
+```
+' | first_name | grade_level | test_score | test_score_avg | avg_1p_1f | avg_2p_2f | avg_up_2f |
+  +------------+-------------+------------+----------------+-----------+-----------+-----------+
+' | Frank      | 9           | 76         | 81.33          | 77        | 77.67     | 77        |
+' | Jojo       | 9           | 78         | 81.33          | 77.67     | 78.25     | 77.67     |
+' | Iris       | 9           | 79         | 81.33          | 79        | 79.6      | 78.25     |
+' | Peter      | 9           | 80         | 81.33          | 81.33     | 82.4      | 79.6      |
+' | Sammy      | 9           | 85         | 81.33          | 85        | 83.5      | 81.33     |
+' | Humphrey   | 9           | 90         | 81.33          | 87.5      | 85        | 81.33     |
+' | Yolinda    | 10          | 30         | 68.2           | 44.5      | 55.67     | 44.5      |
+' | Albert     | 10          | 59         | 68.2           | 55.67     | 63        | 55.67     |
+' | Deborah    | 10          | 78         | 68.2           | 74        | 68.2      | 63        |
+' | Mary       | 10          | 85         | 68.2           | 84        | 77.75     | 68.2      |
+' | Shawn      | 10          | 89         | 68.2           | 87        | 84        | 68.2      |
+' | Carol      | 11          | 52         | 73             | 60        | 64.33     | 60        |
+' | Larry      | 11          | 68         | 73             | 64.33     | 67        | 64.33     |
+' | Wanda      | 11          | 73         | 73             | 72        | 68.8      | 67        |
+' | Otis       | 11          | 75         | 73             | 74.67     | 77.2      | 68.8      |
+' | Shangxiu   | 11          | 76         | 73             | 81.67     | 79.5      | 73        |
+' | Roseanna   | 11          | 94         | 73             | 85        | 81.67     | 73        |
+' | Thomas     | 12          | 66         | 89             | 77.5      | 82.33     | 77.5      |
+' | Jesse      | 12          | 89         | 89             | 82.33     | 85        | 82.33     |
+' | Brunhilda  | 12          | 92         | 89             | 91.33     | 86.8      | 85        |
+' | Charles    | 12          | 93         | 89             | 93        | 93.6      | 86.8      |
+' | Franco     | 12          | 94         | 89             | 95.67     | 94.75     | 89        |
+' | Gary       | 12          | 100        | 89             | 97        | 95.67     | 89        |
+  +------------+-------------+------------+----------------+-----------+-----------+-----------+
+```
+
+* * *
+
+- [AVG OVER](/sql_reference/functions-reference/window/avg-window.html)
+- [COUNT OVER](/sql_reference/functions-reference/window/count-window.html)
+- [DENSE\_RANK OVER](/sql_reference/functions-reference/window/dense-rank.html)
+- [FIRST\_VALUE](/sql_reference/functions-reference/window/first-value.html)
+- [LAG OVER](/sql_reference/functions-reference/window/lag.html)
+- [LEAD OVER](/sql_reference/functions-reference/window/lead.html)
+- [MAX OVER](/sql_reference/functions-reference/window/max-window.html)
+- [MIN OVER](/sql_reference/functions-reference/window/min-window.html)
+- [NTILE OVER](/sql_reference/functions-reference/window/ntile.html)
+- [PERCENT\_RANK OVER](/sql_reference/functions-reference/window/percent-rank.html)
+- [RANK OVER](/sql_reference/functions-reference/window/rank.html)
+- [ROW\_NUMBER OVER](/sql_reference/functions-reference/window/row-number.html)
+- [SUM OVER](/sql_reference/functions-reference/window/sum-window.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_avg_window.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_avg_window.md
new file mode 100644
index 0000000..45a9681
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_avg_window.md
@@ -0,0 +1,38 @@
+# [](#avg)AVG
+
+Returns the average value within the requested window.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+AVG( <value> ) OVER ( [ PARTITION BY <partition_by> ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` A value used for the `AVG()` function Any numeric type `<partition_by` An expression used for the `PARTITION BY` clause Any
+
+## [](#return-types)Return Types
+
+- `NUMERIC` if the input is type `INTEGER`, `BIGINT` or `NUMERIC`
+- `DOUBLE PRECISION` if the input is type `REAL` or `DOUBLE PRECISION`
+
+## [](#example)Example
+
+The example below is querying test scores for players in various game levels. Unlike a regular `AVG()` aggregation, the window function allows us to see how each student individually compares to the average test score for their game level.
+
+```
+SELECT
+	nickname,
+	level,
+	currentscore,
+	AVG(game_score) OVER (PARTITION BY level) AS score_average
+FROM
+	class_test;
+```
+
+**Returns**:
+
+nickname level currentscore score\_average kennethpark 9 76 75.77777 sabrina21 7 90 81.33333 burchdenise 8 79 79.55555 ymatthews 6 85 93.88888 rileyjon 8 80 84.99999
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_count_window.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_count_window.md
new file mode 100644
index 0000000..5e863fd
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_count_window.md
@@ -0,0 +1,35 @@
+# [](#count)COUNT
+
+Count the number of values within the requested window.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/)
+
+## [](#syntax)Syntax
+
+```
+COUNT( <value> ) OVER ( [ PARTITION BY <partition_by> ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` A value used for the `COUNT()` function. Any numeric type `<partition_by>` An expression used for the `PARTITION BY` clause. Any
+
+## [](#return-type)Return Type
+
+`NUMERIC`
+
+## [](#example)Example
+
+The following example generates a count of how many video game players have registered on a specific day:
+
+```
+SELECT
+	registeredon,
+	COUNT(agecategory) OVER (PARTITION BY registeredon) AS count_of_players
+FROM
+	players;
+```
+
+**Returns**:
+
+registeredon count\_of\_players 2020-11-15 12 2020-11-16 8 2020-11-17 4 2020-11-18 9
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_dense_rank.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_dense_rank.md
new file mode 100644
index 0000000..0db6a87
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_dense_rank.md
@@ -0,0 +1,37 @@
+# [](#dense_rank)DENSE\_RANK
+
+Rank the current row within the requested window.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+DENSE_RANK() OVER ([PARTITION BY <partition_by>] ORDER BY <order_by> [ASC|DESC] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<partition_by>` The expression used for the `PARTITION BY` clause. Any `<order_by>` The expression used in the `ORDER BY` clause. This parameter determines what value will be ranked. Any
+
+## [](#return-types)Return Types
+
+Same as input type
+
+## [](#example)Example
+
+In this example below, players are ranked based on their high scores for their game level.
+
+```
+SELECT
+	nickname,
+	level,
+	highscore,
+	DENSE_RANK() OVER (PARTITION BY level ORDER BY highscore DESC ) AS game_rank
+FROM
+	players;
+```
+
+**Returns**:
+
+nickname level highscore game\_rank kennethpark 9 76 6 sabrina21 10 78 3 rileyjon 11 94 1 ymatthews 12 92 4
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_first_value.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_first_value.md
new file mode 100644
index 0000000..89407aa
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_first_value.md
@@ -0,0 +1,53 @@
+# [](#first_value)FIRST\_VALUE
+
+Returns the first value evaluated in the specified window frame. If there are no rows in the window frame, returns NULL.
+
+## [](#syntax)Syntax
+
+```
+FIRST_VALUE( <expression> ) OVER ( [ PARTITION BY <partition_by> ] ORDER BY <order_by> [ASC|DESC] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` A SQL expression of any type to evaluate. Any `<partition_by>` An expression used for the `PARTITION BY` clause. Any `<order_by>` An expression used for the order by clause. Any
+
+## [](#return-types)Return Types
+
+Same as the input type of `<expression>`.
+
+This function respects `NULL` values, and the results will be ordered with the default `NULL` ordering `NULLS LAST` unless
+
+otherwise specified in the `ORDER BY` clause. If no `ORDER BY` clause is applied, the order will be undefined.
+
+## [](#examples)Examples
+
+The following code example selects the `nickname`, `level`, `current_score`, and `highest_score` for each level, using the `NTH_VALUE` function to retrieve the top score within each level, ordered by `current_score` in descending order.
+
+**Example**
+
+The following query uses `UNNEST` to convert an array `[1,2,5]` into a column, order the values, and returns the first value as `result`:
+
+```
+SELECT FIRST_VALUE(a) OVER (ORDER BY a) as result FROM UNNEST(array[1,2,5]) as a;
+```
+
+**Returns**
+
+result (INTEGER) 1 1 1
+
+The previous code example returns the first element after ordering.
+
+**Example**
+
+The following query uses `UNNEST` to convert an array `[100, NULL, 1]` into a column, order the values, and returns the first value as `result`:
+
+```
+SELECT FIRST_VALUE(a) OVER (ORDER BY a desc nulls first) as result FROM UNNEST(array[100,NULL,1]) as a;
+```
+
+**Returns**
+
+result (INTEGER) NULL NULL NULL
+
+The previous code example returns `NULL` values because `ORDER BY` specifies ‘nulls first’.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_lag.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_lag.md
new file mode 100644
index 0000000..ef647c6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_lag.md
@@ -0,0 +1,34 @@
+# [](#lag)LAG
+
+Returns the value of the input expression at the given offset before the current row within the requested window.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+LAG ( <expression> [, <offset> [, <default> ]] )
+    OVER ( [ PARTITION BY <partition_by> ] ORDER BY <order_by> [ { ASC | DESC } ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` Any valid expression that will be returned based on the `<offset>.` Any `<offset>` The number of rows backward from the current row from which to obtain a value. A negative number will act as [LEAD()](/sql_reference/functions-reference/window/lead.html). The offset must be a literal `INTEGER`. `INTEGER` `<default>` The expression to return when the offset goes out of the bounds of the window. Must be a literal of the same type as `<expression>`. The default is `NULL`. Any `<partition_by>` The expression used for the `PARTITION BY` clause. Any `<order_by>` An expression used for the `ORDER BY` clause. Any
+
+## [](#example)Example
+
+In the example below, the `LAG` function is being used to find the players in each level who ranked before and after a certain player. In some cases, if the player has no one ranked before or after them, the `LAG` function returns `NULL`.
+
+```
+SELECT
+	nickname,
+	level,
+	LAG(nickname, 1) OVER (PARTITION BY level ORDER BY nickname) AS player_before,
+	LAG(first_name, -1) OVER (PARTITION BY level ORDER BY nickname) AS player_after
+FROM
+	players;
+```
+
+**Returns**:
+
+nickname level player\_before player\_after kennethpark 9 NULL rileyjon rileyjon 9 kennethpark sabrina21 sabrina21 9 rileyjon ymatthews ymatthews 9 sabrina21 NULL
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_lead.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_lead.md
new file mode 100644
index 0000000..e4b53d7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_lead.md
@@ -0,0 +1,34 @@
+# [](#lead)LEAD
+
+Returns values from the row after the current row within the requested window.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+LEAD ( <expression> [, <offset> [, <default> ]] )
+    OVER ( [ PARTITION BY <partition_by> ] ORDER BY <order_by> [ { ASC | DESC } ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` Any valid expression that will be returned based on the `<offset>.` Any `<offset>` The number of rows forward from the current row from which to obtain a value. A negative number will act as [LAG()](/sql_reference/functions-reference/window/lag.html). The offset must be a literal `INTEGER`. `INTEGER` `<default>` The expression to return when the offset goes out of the bounds of the window. Must be a literal of the same type as `<expression>`. The default is `NULL`. Any `<partition_by>` The expression used for the `PARTITION BY` clause. Any `<order_by>` An expression used for the `ORDER BY` clause. Any
+
+## [](#example)Example
+
+In the example below, the `LEAD` function is being used to find the players in each level who ranked before and after a certain player. In some cases, if the player has no one ranked before or after them, the `LEAD` function returns `NULL`.
+
+```
+SELECT
+	nickname,
+	level,
+	LEAD(nickname, -1) OVER (PARTITION BY level ORDER BY nickname) AS player_before,
+	LEAD(nickname, 1) OVER (PARTITION BY level ORDER BY nickname) AS player_after
+FROM
+	players;
+```
+
+**Returns**:
+
+nickname level player\_before player\_after kennethpark 9 NULL rileyjon rileyjon 9 kennethpark sabrina21 sabrina21 9 rileyjon ymatthews ymatthews 9 sabrina21 NULL
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_max_window.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_max_window.md
new file mode 100644
index 0000000..5db262a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_max_window.md
@@ -0,0 +1,37 @@
+# [](#max-over)MAX OVER
+
+Returns the maximum value within the requested window.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+MAX( <expression> ) OVER ( [ PARTITION BY <partition_by> ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` A value used for the `MAX` function Any `<partition_by>` An expression used for the `PARTITION BY` clause. Any
+
+## [](#return-types)Return Types
+
+Same as input type
+
+## [](#example)Example
+
+The example below queries test scores for players in various grade levels. Unlike a regular `MAX()` aggregation, the window function highlights how each player individually compares to the highest game score for their level.
+
+```
+SELECT
+	nickname,
+	level,
+	current_score,
+	MAX(current_score) OVER (PARTITION BY level) AS highest_score
+FROM
+	players;
+```
+
+**Returns**:
+
+nickname level current\_score highest\_score kennethpark 9 76 95 sabrina21 7 90 98 burchdenise 5 79 99 ymatthews 6 85 93 rileyjon 8 80 84
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_min_window.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_min_window.md
new file mode 100644
index 0000000..28941b5
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_min_window.md
@@ -0,0 +1,33 @@
+# [](#min)MIN
+
+Returns the minimum value within the requested window.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+MIN( <expression> ) OVER ( [ PARTITION BY <partition_by> ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<expression>` A value used for the `MIN` function Any `<partition_by>` An expression used for the `PARTITION BY` clause. Any
+
+## [](#example)Example
+
+The example below queries test scores for players in various grade levels. Unlike a regular `MIN()` aggregation, the window function highlights how each player individually compares to the lowest game score for their level.
+
+```
+SELECT
+	nickname,
+	level,
+	current_score,
+	MIN(current_score) OVER (PARTITION BY level) AS lowest_score
+FROM
+	players;
+```
+
+**Returns**:
+
+nickname level current\_score lowest\_score kennethpark 9 76 2 sabrina21 7 90 15 burchdenise 5 79 4 ymatthews 6 85 9 rileyjon 8 80 20
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_ntile.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_ntile.md
new file mode 100644
index 0000000..2e8fdca
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_ntile.md
@@ -0,0 +1,42 @@
+# [](#ntile)NTILE
+
+Divides an ordered data set equally into the number of buckets specified by the argument value. Buckets are sequentially numbered 1 through the argument value.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+NTILE( <value> ) OVER ( [ PARTITION BY <partition_by> ] ORDER BY <order_by> [ { ASC | DESC } ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` An integer expression used for the `NTILE()` function to specify the number of buckets for division. `INTEGER`/`BIGINT` `<partition_by>` An expression used for the partition by clause. Any `<order_by>` An expression used for the order by clause. Any
+
+## [](#return-type)Return Type
+
+`INTEGER`/`BIGINT`
+
+If there is a remainder after dividing the rows in a partition by the argument value, it will result in buckets of different sizes. For example,
+
+- `NTILE(2)` over 5 rows will result in 2 buckets, the first with 3 rows, the second with 2
+- `NTILE(3)` over 5 rows results in 3 buckets, the first 2 with 2 rows each and the last with one.
+
+## [](#example)Example
+
+The example below divides students test results into three buckets depending on their score.
+
+```
+SELECT
+	student_name,
+	score,
+	NTILE(3) OVER (ORDER BY score) AS bucket
+FROM
+	student_test_results
+ORDER BY score;
+```
+
+**Returns**:
+
+student\_name score bucket James 9 1 Emma 10 1 Harry 11 1 Liam 11 2 Ava 12 2 Charly 12 2 Noah 13 3 Olivia 13 3
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_percent_rank.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_percent_rank.md
new file mode 100644
index 0000000..8d15cb7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_percent_rank.md
@@ -0,0 +1,36 @@
+# [](#percent_rank)PERCENT\_RANK
+
+Calculates the relative rank of the current row within an ordered data set, as `( rank - 1 ) / ( rows - 1 )` where rank is the current row’s rank within the partition, and rows is the number of rows in the partition. PERCENT\_RANK always returns values from 0 to 1 inclusive. The first row in any set has a `PERCENT_RANK` of 0.
+
+## [](#syntax)Syntax
+
+```
+PERCENT_RANK() OVER ( [ PARTITION BY <partition_by> ] ORDER BY <order_by> [ASC|DESC] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types Parameter Description   `<partition_by>` An expression used for the partition by clause. Any `<order_by>` An expression used for the order by clause. Any
+
+## [](#return-type)Return Type
+
+`DOUBLE PRECISION`
+
+This function respects `NULL` values, and results will be ordered with default null ordering `NULLS LAST` unless otherwise specified in the `ORDER BY` clause.
+
+## [](#example)Example
+
+The example below calculates, for each student in grade nine, the percent rank of the student’s test score by their grade level.
+
+```
+SELECT
+	nickname, current_score,
+	PERCENT_RANK() OVER (PARTITION BY level ORDER BY current_score DESC) as percent_rank
+FROM
+	class_test
+WHERE grade_level=9;
+```
+
+**Returns**:
+
+nickname current\_score percent\_rank kennethpark 90 0 sabrina21 85 0.2 rileyjon 80 0.4 ymatthews 79 0.6
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_rank.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_rank.md
new file mode 100644
index 0000000..86d7820
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_rank.md
@@ -0,0 +1,37 @@
+# [](#rank)RANK
+
+Rank the current row within the requested window with gaps.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+RANK() OVER ([PARTITION BY <partition_by>] ORDER BY <order_by> [ASC|DESC] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<partition_by>` The expression used for the `PARTITION BY` clause. Any `<order_by>` The expression used in the `ORDER BY` clause. This parameter determines what value will be ranked. Any
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#example)Example
+
+In this example below, players are ranked based on their test scores for their game level.
+
+```
+SELECT
+	nickname,
+	level,
+	current_score,
+	RANK() OVER (PARTITION BY level ORDER BY current_score DESC ) AS rank_in_game
+FROM
+	players;
+```
+
+**Returns**:
+
+first\_name grade\_level test\_score rank\_in\_class kennethpark 9 76 6 burchdenise 12 89 5 ymatthews 11 75 3 sabrina21 10 78 3
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_row_number.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_row_number.md
new file mode 100644
index 0000000..cb789ad
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_row_number.md
@@ -0,0 +1,36 @@
+# [](#row_number)ROW\_NUMBER
+
+Returns a unique row number for each row within the requested window.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+ROW_NUMBER() OVER ([PARTITION BY <partition_by>] ORDER BY <order_by> [ASC|DESC] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<partition_by>` The expression used for the `PARTITION BY` clause. Any `<order_by>` The expression used in the `ORDER BY` clause. This parameter determines what value will be used for `ROW_NUMBER`. Any
+
+## [](#return-type)Return Type
+
+`INTEGER`
+
+## [](#example)Example
+
+In this example below, players in each game level are assigned a player ID.
+
+```
+SELECT
+	nickname,
+	level,
+	ROW_NUMBER() OVER (PARTITION BY level ORDER BY level ASC ) AS player_id
+FROM
+	players;
+```
+
+**Returns**:
+
+nickname level player\_id ymatthews 9 1 rileyjon 12 2 sabrina21 11 3 burchdenise 10 4
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_sum_window.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_sum_window.md
new file mode 100644
index 0000000..d2a137a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_functions_reference_window_sum_window.md
@@ -0,0 +1,39 @@
+# [](#sum-over)SUM OVER
+
+Calculate the sum of the values within the requested window.
+
+The SUM function works with numeric values and ignores `NULL` values.
+
+For more information on usage, please refer to [Window Functions](/sql_reference/functions-reference/window/).
+
+## [](#syntax)Syntax
+
+```
+SUM([ DISTINCT ] <value> ) OVER ( [ PARTITION BY <partition_by> ] )
+```
+
+## [](#parameters)Parameters
+
+Parameter Description Supported input types `<value>` The expression used for the `SUM` function Any numeric type `<partition_by>` An expression used for the `PARTITION BY` clause Any
+
+## [](#return-types)Return Types
+
+`NUMERIC`
+
+When `DISTINCT` is specified, duplicate values from `<expression>` are removed before calculating the sum.
+
+## [](#example)Example
+
+The example below shows how many players are on a specific level.
+
+```
+SELECT
+	level,
+	SUM(players) OVER (PARTITION BY level ) AS current_players
+FROM
+	players;
+```
+
+**Returns**:
+
+level current\_players 1 156 2 108 3 127 4 198 5 207
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_geography_data_type.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_geography_data_type.md
new file mode 100644
index 0000000..098056b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_geography_data_type.md
@@ -0,0 +1,173 @@
+Firebolt’s geospatial capabilities are currently in public preview. We are gathering feedback and further refining this feature.
+
+# [](#geography-data-type)GEOGRAPHY data type
+
+This topic describes the Firebolt implementation of the `GEOGRAPHY` data type.
+
+- [Overview](#overview)
+  
+  - [GEOGRAPHY types in Firebolt](#geography-types-in-firebolt)
+- [Input and output](#input-and-output)
+  
+  - [Literal string interpretation](#literal-string-interpretation)
+  - [Cast from BYTEA](#cast-from-bytea)
+  - [Cast to BYTEA](#cast-to-bytea)
+  - [Cast from TEXT](#cast-from-text)
+  - [Cast to TEXT](#cast-to-text)
+  - [Normalization](#normalization)
+  - [Invalid inputs](#invalid-inputs)
+- [Snapping](#snapping)
+- [Comparison, sorting, and grouping](#comparison-sorting-and-grouping)
+- [Driver version requirements](#driver-version-requirements)
+
+## [](#overview)Overview
+
+The `GEOGRAPHY` data type represents geospatial data on the earth’s surface. It represents Points, LineStrings, Polygons, or combinations of these. Points in Firebolt’s `GEOGRAPHY` data type represent points on the [WGS84 reference spheroid](https://en.wikipedia.org/wiki/World_Geodetic_System) (SRID 4326). All edges between points in LineStrings and Polygons are geodesics, meaning they represent the shortest path between points along the Earth’s curvature. Functions that use the `GEOGRAPHY` data type model the Earth as a sphere with a radius of 6,371,008 meters.
+
+### [](#geography-types-in-firebolt)GEOGRAPHY types in Firebolt
+
+Firebolt supports the following `GEOGRAPHY` types, with examples provided in the [Well-Known Text](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) (WKT) format for spatial data representation:
+
+- Point: A 0-dimensional object representing a single location in coordinate space.
+  
+  - Example: `POINT (1 2)`
+- LineString: A 1-dimensional line made up of a contiguous sequence of line segments, where each segment connects two points. The end of one segment forms the start of the next.
+  
+  - Example: `LINESTRING (1 2, 3 4, 5 6)`
+- Polygon: A 2-dimensional area, defined by an outer boundary (shell) and optionally one or more inner boundaries (holes).
+  
+  - Example: `POLYGON ((0 0 ,4 0 ,4 4 ,0 4 ,0 0 ), (1 1 ,2 1 ,2 2 ,1 2 ,1 1 )`
+- MultiPoint: A collection of multiple Points.
+  
+  - Example: `MULTIPOINT ((0 0), (1 2))`
+- MultiLineString: A collection of multiple LineStrings.
+  
+  - Example: `MULTILINESTRING ((0 0,1 1,1 2), (2 3,3 2,5 4))`
+- MultiPolygon: A collection of Polygons that do not overlap or share adjacent boundaries, although they may touch at finite Points.
+  
+  - Example: `MULTIPOLYGON (((1 5, 5 5, 5 1, 1 1, 1 5)), ((6 5, 9 1, 6 1, 6 5)))`
+- GeometryCollection: A mixed collection of Geographies.
+  
+  - Example: `GEOMETRYCOLLECTION (POINT(2 3), LINESTRING(2 3, 3 4))`
+
+## [](#input-and-output)Input and output
+
+Firebolt supports creating `GEOGRAPHY` from the industry standard GeoJSON, Well-Known Text (WKT), and Well-Known Binary (WKB) representations, as well as the extended formats EWKT and EWKB introduced by the PostGIS extension. See the corresponding [function documentations](/sql_reference/functions-reference/geospatial/) for further detail.
+
+### [](#literal-string-interpretation)Literal string interpretation
+
+You can create a `GEOGRAPHY` object from a string by using the `GEOGRAPHY` prefix in a query, as shown in the following code example:
+
+```
+SELECT GEOGRAPHY '<string in supported format>';
+```
+
+`GEOGRAPHY` literals are automatically decoded based on the encoding format used. Supported formats include:
+
+- [(Extended) Well-Known Text (EWKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry).
+- [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946).
+- Hex-encoded [(Extended) Well-Known Binary (EWKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary).
+
+For more information, refer to [Cast from TEXT](#cast-from-text).
+
+**Examples**
+
+You can use any supported format to create a `GEOGRAPHY` object. The following examples demonstrate how to create the same `GEOGRAPHY` object representing a Point at longitude -73.98551041593687 and latitude 40.75793403395676 using WKT, GeoJSON, and EWKB formats:
+
+```
+-- Example: WKT format
+SELECT GEOGRAPHY 'POINT(-73.98551041593687 40.75793403395676)';
+-- Example: GeoJSON format
+SELECT GEOGRAPHY '{"type":"Point","coordinates":[-73.98551041593687,40.75793403395676]}';
+-- Example: Hex-encoded EWKB format
+SELECT GEOGRAPHY '0101000020E61000003D94479A127F52C0502F80FB03614440';
+```
+
+### [](#cast-from-bytea)Cast from BYTEA
+
+The cast from `BYTEA` to `GEOGRAPHY` behaves exactly like the [ST\_GEOGFROMWKB](/sql_reference/functions-reference/geospatial/st_geogfromwkb.html) function.
+
+### [](#cast-to-bytea)Cast to BYTEA
+
+The cast from `GEOGRAPHY` to `BYTEA` behaves exactly like the [ST\_ASEWKB](/sql_reference/functions-reference/geospatial/st_asewkb.html) function.
+
+### [](#cast-from-text)Cast from TEXT
+
+The cast from `TEXT` to `GEOGRAPHY` automatically detects the decoding used and supports the [Extended Well-Known Text (EWKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry), [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946), and hex-encoded [Extended Well-Known Binary (EWKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary) formats. It behaves exactly like [ST\_GEOGFROMTEXT](/sql_reference/functions-reference/geospatial/st_geogfromtext.html) for [Well-Known Text (WKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) inputs, like [ST\_GEOGFROMGEOJSON](/sql_reference/functions-reference/geospatial/st_geogfromgeojson.html) for [GeoJSON](https://datatracker.ietf.org/doc/html/rfc7946) inputs, and like [ST\_GEOGFROMWKB](/sql_reference/functions-reference/geospatial/st_geogfromwkb.html)[(DECODE(input, ‘HEX’))](/sql_reference/functions-reference/bytea/decode.html) for hex-encoded [Well-Known Binary (WKB)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary) inputs.
+
+### [](#cast-to-text)Cast to TEXT
+
+The cast from `GEOGRAPHY` to `TEXT` returns the hexadecimal representation of the output of the [ST\_ASEWKB](/sql_reference/functions-reference/geospatial/st_asewkb.html) function in upper case letters.
+
+### [](#normalization)Normalization
+
+For all input formats, Firebolt applies normalization steps to the input. These steps ensure that Firebolt can perform operations efficiently and correctly.
+
+- All shapes that overlap a Polygon will be removed. This means that Polygons may be merged if they overlap and LineStrings may be cut to only include the parts outside of any Polygons.
+
+![Overlapping Polygons with holes and a LineString crossing through them.](../assets/images/geography/normalization_before.png)
+
+Input with overlapping Polygons and a LineString.
+
+![A single Polygon that combines the two input Polygons and three LineStrings covering the parts of the input LineString not covered by Polygons.](../assets/images/geography/normalization_after.png)
+
+In the output, the Polygons have been merged and the LineString was cut at the Polygon boundaries.
+
+- Duplicate Points in MultiPoints and GeometryCollections are removed.
+- Duplicate vertices in LineStrings are removed.
+- Any empty shapes will be removed.
+- Polygon orientations are adjusted such that the interior of the Polygon is the smaller possible option. This means that any Polygon can cover at most half of the earth.
+
+### [](#invalid-inputs)Invalid inputs
+
+Additionally, Firebolt fixes some otherwise invalid inputs when reading:
+
+- Polygons are split at self-intersections.
+
+![A Polygon with a hole that intersects itself.](../assets/images/geography/intersection_in_hole_before.png)
+
+Input with a self-intersecting hole. The purple vertices are the input vertices of the hole.
+
+![The same Polygon but the hole has been split into two holes with no intersections.](../assets/images/geography/intersection_in_hole_after.png)
+
+In the output, the hole has been split at the intersection. The resulting Polygon has two holes. One consisting of the purple vertices and one consisting of the yellow vertices.
+
+- Degenerate parts of Polygons are removed, potentially splitting the Polygon. Parts of Polygons are considered degenerate if they collapse to a single line or point.
+
+![A Polygon with a part that has no area.](../assets/images/geography/degenerate_part_removal_before.png)
+
+Input Polygon with a degenerate part.
+
+![The same Polygon split into two with the degenerate part removed.](../assets/images/geography/degenerate_part_removal_after.png)
+
+In the output, the degenerate part has been removed, turning the Polygon into a MultiPolygon.
+
+- A special case of removing these degeneracies occurs when Polygon holes share a boundary edge with the Polygon. In this case, the hole is removed from the Polygon and the outer boundary is reshaped accordingly, but only if the edge vertices of the hole are also vertices of the Polygon.
+
+![A Polygon with a hole that shares two edges with the outer shell of the Polygon.](../assets/images/geography/outer_and_inner_ring_share_edge_before.png)
+
+Input Polygon with a hole that shares two edges with the outer shell, making these edges degenerate.
+
+![The same Polygon but with the degenerate parts removed.](../assets/images/geography/outer_and_inner_ring_share_edge_after.png)
+
+In the output, the degenerate part has been removed.
+
+## [](#snapping)Snapping
+
+Functions that determine relations between `GEOGRAPHY` objects perform a process called snapping on their inputs. During snapping, any points of the inputs objects that are less than 1 micrometer apart from each other are moved to be exactly the same. For example, this means that a Point that is less than 1 micrometer away from a Polygon is treated as being on the Polygon’s boundary and two Polygons that are separated by less than 1 micrometer are treated as intersecting.
+
+## [](#comparison-sorting-and-grouping)Comparison, sorting, and grouping
+
+Objects with a `GEOGRAPHY` data type cannot be compared. This means that `ORDER BY` or comparison operators are not supported on `GEOGRAPHY` columns.
+
+This also means that `GEOGRAPHY` columns cannot be used in `GROUP BY` clauses because they cannot be compared for equality.
+
+## [](#driver-version-requirements)Driver version requirements
+
+The following minimum driver versions are required to use the `GEOGRAPHY` data type:
+
+- [Python](/Guides/developing-with-firebolt/connecting-with-Python.html) - version 1.6.0.
+- [JDBC](/Guides/developing-with-firebolt/connecting-with-jdbc.html) - version 3.4.0.
+- [Node.js](/Guides/developing-with-firebolt/connecting-with-nodejs.html) - any version.
+- [Go](/Guides/developing-with-firebolt/connecting-with-go.html) - version 1.3.1.
+- [.NET](/Guides/developing-with-firebolt/connecting-with-net-sdk.html) - version 1.4.0.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema.md
new file mode 100644
index 0000000..e74e5e1
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema.md
@@ -0,0 +1,41 @@
+## [](#information-schema-views)Information Schema Views
+
+The Firebolt information schema consists of a set of system views that contain metadata information on the objects defined in the current account, as well as database usage views. Firebolt supports `information_schema` schema based on ANSI SQL standard, but extended with Firebolt specific information, both as additional columns in standard views, and as additional views. For better compatibility with applications that rely on Postgres specific system views, Firebolt also supports `pg_catalog` schema and subset of Postgres compatible views in it.
+
+Not all information schema views are available on Firebolt’s system engine or within the **Firebolt Workspace**. The following views are unavailable:
+
+- `engine_metrics_history`
+- `engine_running_queries`
+- `engine_query_history`
+- `engine_user_query_history`
+
+* * *
+
+- [Accounts](/sql_reference/information-schema/accounts.html)
+- [Applicable roles](/sql_reference/information-schema/applicable-roles.html)
+- [Catalogs](/sql_reference/information-schema/catalogs.html)
+- [Columns](/sql_reference/information-schema/columns.html)
+- [Enabled roles](/sql_reference/information-schema/enabled-roles.html)
+- [Engine history](/sql_reference/information-schema/engine-history.html)
+- [Engine metering history](/sql_reference/information-schema/engine-metering-history.html)
+- [Engine metrics history](/sql_reference/information-schema/engine-metrics-history.html)
+- [Engine query history](/sql_reference/information-schema/engine-query-history.html)
+- [Engine running queries](/sql_reference/information-schema/engine-running-queries.html)
+- [Engine user query history](/sql_reference/information-schema/engine-user-query-history.html)
+- [Engines](/sql_reference/information-schema/engines.html)
+- [Engines Billing](/sql_reference/information-schema/engines-billing.html)
+- [Indexes](/sql_reference/information-schema/indexes.html)
+- [Locations](/sql_reference/information-schema/locations.html)
+- [Logins](/sql_reference/information-schema/logins.html)
+- [Network policies](/sql_reference/information-schema/network_policies.html)
+- [Object privileges](/sql_reference/information-schema/object-privileges.html)
+- [Routines](/sql_reference/information-schema/routines.html)
+- [Schemata](/sql_reference/information-schema/schemata.html)
+- [Service accounts](/sql_reference/information-schema/service-accounts.html)
+- [Storage Billing](/sql_reference/information-schema/storage-billing.html)
+- [Storage Metering History](/sql_reference/information-schema/storage-metering-history.html)
+- [Storage history](/sql_reference/information-schema/storage-history.html)
+- [Tables](/sql_reference/information-schema/tables.html)
+- [Transitive applicable roles](/sql_reference/information-schema/transitive-applicable-roles.html)
+- [Users](/sql_reference/information-schema/users.html)
+- [Views](/sql_reference/information-schema/views.html)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_accounts.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_accounts.md
new file mode 100644
index 0000000..8329794
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_accounts.md
@@ -0,0 +1,20 @@
+# [](#information-schema-for-accounts)Information schema for accounts
+
+You can use the `information_schema.accounts` view to return information about accounts.
+
+You can use a `SELECT` query to return information about each account, as shown in the example below.
+
+```
+SELECT
+  *
+FROM
+  information_schema.accounts;
+```
+
+Read more about managing accounts [here](/Guides/managing-your-organization/managing-accounts.html).
+
+## [](#columns-in-information_schemaaccounts)Columns in information\_schema.accounts
+
+Each row has the following columns with information about the account.
+
+Column Name Data Type Description account\_name TEXT The name of the account. organization\_name TEXT The name of the organization to which the account belongs. region TEXT The region in which the account can be used. url TEXT The account login page URL. account\_id TEXT The unique account ID. trust\_policy\_role TEXT Role provided by Firebolt to enable access to customer S3 buckets created TIMESTAMP Time (UTC) that the account was created. account\_owner TEXT The name of the login that created the account. last\_altered TIMESTAMP Time (UTC) that the user was last edited. last\_altered\_by TEXT Name of the last user to edit the role.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_applicable_roles.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_applicable_roles.md
new file mode 100644
index 0000000..fde185d
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_applicable_roles.md
@@ -0,0 +1,22 @@
+# [](#information-schema-for-applicable_roles)Information schema for applicable\_roles
+
+The `information_schema.applicable_roles` view shows every role in the account and its grantees, who include other users or roles to whom the role is granted.
+
+You can use a `SELECT` query to return information about each role as shown in the example below.
+
+```
+SELECT
+  *
+FROM
+  information_schema.applicable_roles;
+```
+
+See also `information_schema.transitive_applicable_roles` [here](/sql_reference/information-schema/transitive-applicable-roles.html).
+
+Read more about RBAC roles [here](/Guides/security/rbac.html).
+
+## [](#columns-in-information_schemaapplicable_roles)Columns in information\_schema.applicable\_roles
+
+Each row has the following columns with information about the role.
+
+Column Name Data Type Description grantee TEXT User or role to whom the role is granted. role\_name TEXT Name of the role. is\_grantable TEXT `YES` if the grantee has the admin option on the role, `NO` if not. created TIMESTAMPTZ Creation time of the role.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_catalogs.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_catalogs.md
new file mode 100644
index 0000000..69f2f43
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_catalogs.md
@@ -0,0 +1,18 @@
+# [](#information-schema-for-catalogs)Information schema for catalogs
+
+You can use the `information_schema.catalogs` view to get information about catalogs (databases in SQL terminology). You can use a `SELECT` query to return information about each database as shown in the example below.
+
+In order to view catalog information, you must have [catalog](/Overview/Security/Role-Based%20Access%20Control/database-permissions/#database-level-privileges) privileges or have ownership of the catalog object.
+
+```
+SELECT
+  *
+FROM
+  information_schema.catalogs;
+```
+
+## [](#columns-in-information_schemacatalogs)Columns in information\_schema.catalogs
+
+Each row has the following columns with information about the database.
+
+Column Name Data Type Description catalog\_name TEXT Name of the database. default\_collation TEXT Always ‘POSIX’. default\_character\_set TEXT Always ‘UTF-8’. description TEXT The description of the database. created TIMESTAMPTZ The time the database was created. ddl TEXT The text of the SQL statement that created the database. catalog\_owner TEXT The owner of the database, `NULL` if there is none. last\_altered TIMESTAMPTZ Time the database was last altered. last\_altered\_by TEXT Name of the last user to alter the database.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_columns.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_columns.md
new file mode 100644
index 0000000..046fef6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_columns.md
@@ -0,0 +1,18 @@
+# [](#information-schema-for-columns)Information schema for columns
+
+You can use the `information_schema.columns` view to return information about all columns in a table in a database. The view is available in each database and contains one row for each column. You can use a `SELECT` query to return information about each column as shown in the example below.
+
+To view column information, the user must have `USAGE` privileges on both the [schema](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html#schema-level-privileges) and the [database](/Overview/Security/Role-Based%20Access%20Control/database-permissions/#database-level-privileges), as well as any necessary [table-level privileges](/Overview/Security/Role-Based%20Access%20Control/database-permissions/table-permissions.html#table-level-privileges) or ownership of the table.
+
+```
+SELECT
+  *
+FROM
+  information_schema.columns;
+```
+
+## [](#columns-in-information_schemacolumns)Columns in information\_schema.columns
+
+Each row has the following columns with information about each column.
+
+Column Name Data Type Description table\_catalog TEXT Name of the catalog. Firebolt provides a single `default` catalog. table\_schema TEXT Name of the database containing the table. table\_name TEXT Name of the table containing the column. column\_name TEXT Name of the column. is\_nullable TEXT `YES` if the column may contain NULL, `NO` otherwise. data\_type TEXT The data type of the column. is\_in\_partition\_expr TEXT `YES` if the column is included in the table’s `PARTITION BY` clause, `NO` otherwise. is\_in\_primary\_index TEXT `YES` if the column is included in the tables’s `PRIMARY INDEX` clause, `NO` otherwise. character\_maximum\_length NULL Not applicable for Firebolt. character\_octet\_length NULL Not applicable for Firebolt. numeric\_precision\_radix NULL Not applicable for Firebolt. interval\_type NULL Not applicable for Firebolt. interval\_precision NULL Not applicable for Firebolt. character\_set\_catalog NULL Not applicable for Firebolt. character\_set\_schema NULL Not applicable for Firebolt. character\_set\_name NULL Not applicable for Firebolt. collation\_catalog NULL Not applicable for Firebolt. collation\_schema NULL Not applicable for Firebolt. collation\_name NULL Not applicable for Firebolt. domain\_catalog NULL Not applicable for Firebolt. domain\_schema NULL Not applicable for Firebolt. domain\_name NULL Not applicable for Firebolt. udt\_catalog NULL Not applicable for Firebolt. udt\_schema NULL Not applicable for Firebolt. udt\_name NULL Not applicable for Firebolt. scope\_catalog NULL Not applicable for Firebolt. scope\_schema NULL Not applicable for Firebolt. scope\_name NULL Not applicable for Firebolt. maximum\_cardinality NULL Not applicable for Firebolt. dtd\_identifier NULL Not applicable for Firebolt. is\_self\_referencing NULL Not applicable for Firebolt. is\_identity NULL Not applicable for Firebolt. identity\_generation NULL Not applicable for Firebolt. identity\_start NULL Not applicable for Firebolt. identity\_increment NULL Not applicable for Firebolt. identity\_maximum NULL Not applicable for Firebolt. identity\_minimum NULL Not applicable for Firebolt. identity\_cycle NULL Not applicable for Firebolt. is\_generated NULL Not applicable for Firebolt. generation\_expression NULL Not applicable for Firebolt. is\_updatable NULL Not applicable for Firebolt.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_enabled_roles.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_enabled_roles.md
new file mode 100644
index 0000000..90e214b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_enabled_roles.md
@@ -0,0 +1,20 @@
+# [](#information-schema-for-enabled_roles)Information schema for enabled\_roles
+
+The `information_schema.enabled_roles` view lists roles in a Firebolt account that is either owned by a user or comes with [role privileges](/Overview/Security/Role-Based%20Access%20Control/role-permissions.html#role-permissions) to access.
+
+The following code example uses a `SELECT` query to return information about each role:
+
+```
+SELECT
+  *
+FROM
+  information_schema.enabled_roles;
+```
+
+For more information about permissions to access and perform operations on specific objects by role, see [Manage role-based access control](/Guides/security/rbac.html).
+
+## [](#columns-in-information_schemaenabled_roles)Columns in information\_schema.enabled\_roles
+
+Each row contains the following columns with information about the role:
+
+Column Name Data Type Description role\_name TEXT The name of the role. created TIMESTAMPTZ The time that the role was created. role\_owner TEXT The name of the user who created the role.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_history.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_history.md
new file mode 100644
index 0000000..5248ee6
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_history.md
@@ -0,0 +1,18 @@
+# [](#information-schema-for-engine-history)Information schema for engine history
+
+You can use the `information_schema.engine_history` view to return information about each engine’s history in an account. The view shows operations performed on each engine, including creation, deletion, starts, stops, resizing, and logical operations like renames. It is often useful to filter this view to a particular engine. In the example below, a filter is applied to look at the history of engines starting with `capacity_test_`. By default, shows the events from the last 30 days.
+
+```
+SELECT
+  *
+FROM
+  information_schema.engine_history
+WHERE
+  engine_name LIKE 'capacity_test_%'
+```
+
+## [](#columns-in-information_schemaengines_history)Columns in information\_schema.engines\_history
+
+Each row has the following columns with information about each engine.
+
+Column Name Data Type Description engine\_name TEXT The last known name of the engine. Either reflects the current name or the name at time of deletion. engine\_owner TEXT The name of the user who owns the engine. cluster\_id INT Ordinal numbers to identify engine clusters. type TEXT(5) Node type used in a given engine (S, M, L or XL). family TEXT The family of a given engine. Choose from `STORAGE_OPTIMIZED` or `COMPUTE_OPTIMIZED`. nodes INT Number of nodes in each of the cluster of the engine. clusters INT The number of clusters used in the engine. auto\_start BOOLEAN If True, automatically start the engine if in stopped state when a query comes in. auto\_stop INT Automatically stop the engine after specified number of minutes. initially\_stopped BOOLEAN If True, the engine will not be automatically started after creation. url TEXT Engine URL used by the users to issue queries to the engine. default\_database TEXT Default database for the engine as specified by the user. version TEXT Engine version. event\_type TEXT Name of the event. event\_reason TEXT Reason why the engine event was triggered. event\_status TEXT Status of the event, indicating whether the action corresponding to the event has succeeded, failed or is in process. Can have one of the following values: SUCCEEDED, FAILED or IN\_PROGRESS. event\_start\_time TIMESTAMPTZ Time when the event was initiated. event\_finish\_time TIMESTAMPTZ Time when the event was completed. user\_name TEXT User who triggered the event. description TEXT Description of the engine as specified by the user. query\_id TEXT Unique identifier for the SQL query used for engine operations.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_metering_history.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_metering_history.md
new file mode 100644
index 0000000..151f099
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_metering_history.md
@@ -0,0 +1,18 @@
+# [](#information-schema-for-engine-metering-history)Information schema for engine metering history
+
+You can use the `information_schema.engine_metering_history` view to return information about each engine’s FBU consumed over time in an account. See [Engine Consumption](/Overview/engine-consumption.html) for more details on consumption, nodes, and FBU. It is often useful to filter this view to a particular engine. In the example below, a filter is applied to look at the history of engines starting with `capacity_test_`. By default, shows hourly data from the last 30 days.
+
+```
+SELECT
+  *
+FROM
+  information_schema.engine_metering_history
+WHERE
+  engine_name LIKE 'capacity_test_%'
+```
+
+## [](#columns-in-information_schemaengine_metering_history)Columns in information\_schema.engine\_metering\_history
+
+Each row has the following columns with information about each engine.
+
+Column Name Data Type Description engine\_name TEXT The last known name of the engine. Either reflects the current name or the name at time of deletion. start\_hour TIMESTAMPTZ Start time for the hour. end\_hour TIMESTAMPTZ End time for the hour. consumed\_FBU TEXT Firebolt units consumed within the hour based on the the duration the engine has been running.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_metrics_history.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_metrics_history.md
new file mode 100644
index 0000000..875a80a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_metrics_history.md
@@ -0,0 +1,19 @@
+# [](#information-schema-for-engine-metrics-history)Information schema for engine metrics history
+
+You can use the `information_schema.engine_metrics_history` view to return information about the resource consumption of your engine. As engines can have 1 or more engine clusters that are transient, this provides visibilty into the utilization of each engine cluster. Each row represents the aggregate resource metrics for a single engine cluster at the given event time. Per default, we collect 2 metric snapshots per minute for the last 30 days. You can use a `SELECT` query to return the metrics for each engine cluster at a given point in time as shown in the example below.
+
+```
+SELECT
+  *
+FROM
+  information_schema.engine_metrics_history
+WHERE
+  event_time > now() - INTERVAL '2 hours'
+LIMIT 100;
+```
+
+## [](#columns-in-information_schemaengine_metrics_history)Columns in information\_schema.engine\_metrics\_history
+
+Each row has the following columns with information about each engine cluster.
+
+Column Name Data Type Description engine\_ordinal BIGINT the cluster number event\_time TIMESTAMPTZ timestamp at which the metrics where collected cpu\_used DECIMAL current CPU utilization (percentage) memory\_used DECIMAL current memory used (percentage) disk\_used DECIMAL currently used disk space which encompasses space used for cache and spilling (percentage) cache\_hit\_ratio DECIMAL current SSD cache hit ratio spilled\_bytes BIGINT amount of spilled data to disk in bytes running\_queries BIGINT number of currently running queries in the system suspended\_queries BIGINT number of queries that have been suspended (not-running and awaiting to be executed)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_query_history.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_query_history.md
new file mode 100644
index 0000000..545ee35
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_query_history.md
@@ -0,0 +1,25 @@
+# [](#information-schema-for-engine-query-history)Information schema for engine query history
+
+You can use the `information_schema.engine_query_history` view to return information about queries saved to query history. The view is available in each database and contains two rows, the starting and ending row for each historical query in the database. The table includes the last ten thousand queries per engine cluster. You can run a `SELECT` query to retrieve details about recent queries, as shown in the following example:
+
+```
+SELECT
+  *
+FROM
+  information_schema.engine_query_history
+LIMIT
+  100;
+```
+
+The `information_schema.engine_query_history` view retains only the most recent 10,000 queries. Queries exceeding this limit are excluded and will not appear in the query history. This limitation is important for high-volume workloads and tools like the [OTEL exporter](/Guides/integrations/otel-exporter.html), which can rapidly fill the query history. To retain critical query data, regularly export or archive query history.
+
+## [](#columns-in-information_schemaengine_query_history)Columns in information\_schema.engine\_query\_history
+
+Each row has the following columns with information about each query in query history.
+
+Column Name Data Type Description   account\_name TEXT The name of the account that ran the query.   user\_name TEXT The user name that was used to run the query. The `user_name` is present for account-level operations, and `NULL` for organization-level operations.   login\_name TEXT The login name that was used to run the query. The `login_name` is present for organization-level statements, and otherwise `NULL`.   service\_account\_name TEXT The service account name that was used to run the query. The `service_account_name` is present for organization-level statements, and otherwise `NULL`.   submitted\_time TIMESTAMPTZ The time that the user submitted the query.   start\_time TIMESTAMPTZ The time that the query started running in Coordinated Universal Time (UTC).   end\_time TIMESTAMPTZ The time that the query stopped running in UTC.   duration\_us BIGINT The duration of query run time in microseconds.   e2e\_duration\_us BIGINT The end-to-end duration of query run time. Starting from the time the query was submitted and ending when the result was fully returned in microseconds.   status TEXT Can be one of the following values:  
+`STARTED_EXECUTION`–Successful start of query execution.  
+`ENDED_SUCCESSFULLY`–Successful end of query execution.  
+`CANCELED_EXECUTION`–Query was canceled.  
+`PARSE_ERROR`–Query could not be parsed.  
+`EXECUTION_ERROR`–Query could not be executed successfully.   request\_id TEXT The ID of the request from which the query originates.   query\_id TEXT The unique identifier of the SQL query.   query\_label TEXT A user-provided query label.   query\_text TEXT The text of the SQL statement.   query\_text\_normalized TEXT The normalized text of the SQL statement.   query\_text\_normalized\_hash TEXT The hash of the normalized text of the SQL statement.   error\_message TEXT The returned error message.   scanned\_rows BIGINT The total number of rows scanned.   scanned\_bytes BIGINT The total number of uncompressed bytes scanned.   scanned\_cache\_bytes BIGINT The total number of compressed bytes scanned from disk-based cache.   scanned\_storage\_bytes BIGINT The total number of compressed bytes scanned from Firebolt-managed storage. Does not apply to [EXTERNAL tables](/Overview/indexes/using-indexes.html#external-tables).   inserted\_rows BIGINT The total number of rows written.   inserted\_bytes BIGINT The total number of bytes written to both cache and storage.   spilled\_bytes BIGINT The total number of uncompressed bytes spilled.   returned\_rows BIGINT The total number of rows returned from the query.   returned\_bytes BIGINT The total number of bytes returned from the query.   time\_in\_queue\_us BIGINT The number of microseconds the query spent in queue.   retries BIGINT The number of retried attempts in case of query failure. Defaults to 0.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_running_queries.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_running_queries.md
new file mode 100644
index 0000000..fbbac77
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_running_queries.md
@@ -0,0 +1,18 @@
+# [](#information-schema-for-engine-running-queries)Information schema for engine running queries
+
+You can use the `information_schema.engine_running_queries` view to return information about queries currently running in a database. This view is available in each database and includes one row for each running query. The table contains a maximum of ten thousand queries per engine cluster. You can use a `SELECT` query to return information about each running query as shown in the example below.
+
+```
+SELECT
+  *
+FROM
+   information_schema.engine_running_queries
+LIMIT
+  100;
+```
+
+## [](#columns-in-information_schemaengine_running_queries)Columns in information\_schema.engine\_running\_queries
+
+Each row has the following columns with information about each running query.
+
+Column Name Data Type Description account\_name TEXT The name of the account in which the query was executed. user\_name TEXT The user that executed the query submitted\_time TIMESTAMPTZ The time when the query was submitted by a user (UTC) start\_time TIMESTAMPTZ The query execution start time (UTC). duration\_us BIGINT The time elapsed in microseconds from `<START_TIME>` to when the query on `information_schema.engine_running_queries` returns results. e2e\_duration\_us BIGINT The time elapsed in microseconds from the time of query submission to when the query on `information_schema.engine_running_queries` returns results. status TEXT The status of the query, eiteher `RUNNING`, `SUSPENDED`, or `CANCELING`. request\_id TEXT The ID of the request from which the query originates. query\_id TEXT The query id of this query. query\_label TEXT User provided query label (query\_label parameter) query\_text TEXT Text of the SQL statement. scanned\_rows BIGINT The number of rows scanned to return query results. scanned\_bytes BIGINT The number of bytes scanned from cache and storage. inserted\_rows BIGINT The number of rows written inserted\_bytes BIGINT The number of bytes written. async\_token TEXT If the query is an async query, this handle can be used to check the status via the built in stored procedure fb\_GetAsyncStatus(). retries BIGINT The total number of retries to execute a given query after a failure (by default, the number of retries is 0 and the number increases with each retry)
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_user_query_history.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_user_query_history.md
new file mode 100644
index 0000000..39b2b7e
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engine_user_query_history.md
@@ -0,0 +1,25 @@
+# [](#information-schema-for-engine-user-query-history)Information schema for engine user query history
+
+The system table `information_schema.engine_user_query_history` is a view, which is a virtual table based on [ENGINE\_QUERY\_HISTORY](/sql_reference/information-schema/engine-query-history.html). It applies filters to only show queries that were made by actual users.
+
+Queries generated by the system, such as those from connectors, drivers, or SDKs, are marked with the boolean HTTP header `Firebolt-Machine-Query`. These system queries can include actions such UI page loads or query progress updates. These queries do not appear in `information_schema.engine_user_query_history`, but are available in [ENGINE\_QUERY\_HISTORY](/sql_reference/information-schema/engine-query-history.html), which acts as a complete audit log.
+
+```
+SELECT
+  *
+FROM
+  information_schema.engine_user_query_history
+LIMIT
+  100;
+```
+
+## [](#columns-in-information_schemaengine_user_query_history)Columns in information\_schema.engine\_user\_query\_history
+
+Each row contains columns with detailed information about each query in the history. This schema has the same structure and information as [ENGINE\_QUERY\_HISTORY](/sql_reference/information-schema/engine-query-history.html).
+
+Column Name Data Type Description account\_name TEXT The name of the account that ran the query. user\_name TEXT The user name used to run the query. The `user name` is provided for account-level operations but is `NULL` for organization-level operations. login\_name TEXT The login name that was used to run the query. The `login_name` is provided for organization-level statements, and is otherwise `NULL`. service\_account\_name TEXT The service account name that was used to run the query. The `service_account_name` is provided for organization-level statements, and otherwise `NULL`. submitted\_time TIMESTAMPTZ The time that the user submitted the query. start\_time TIMESTAMPTZ The time that the query started running in Coordinated Universal Time (UTC). end\_time TIMESTAMPTZ The time that the query stopped running in UTC. duration\_us BIGINT The duration of query run time in microseconds. e2e\_duration\_us BIGINT The end-to-end duration of query run time. Starting from the time the query was submitted and ending when the result was fully returned in microseconds. status TEXT Can be one of the following values:  
+`STARTED_EXECUTION`–Successful start of query execution.  
+`ENDED_SUCCESSFULLY`–Successful end of query execution.  
+`CANCELED_EXECUTION`–Query was canceled.  
+`PARSE_ERROR`–Query could not be parsed.  
+`EXECUTION_ERROR`–Query could not be executed successfully. request\_id TEXT The ID of the request from which the query originates. query\_id TEXT The unique identifier of the SQL query. query\_label TEXT A user-provided query label. query\_text TEXT The text of the SQL statement. query\_text\_normalized TEXT The normalized text of the SQL statement. query\_text\_normalized\_hash TEXT The hash of the normalized text of the SQL statement. error\_message TEXT The returned error message. scanned\_rows BIGINT The total number of rows scanned. scanned\_bytes BIGINT The total number of bytes scanned from both cache and storage. scanned\_cache\_bytes BIGINT The total number of compressed bytes scanned from disk-based cache. scanned\_storage\_bytes BIGINT The total number of compressed bytes scanned from Firebolt-managed storage. Does not apply to [EXTERNAL tables](/Overview/indexes/using-indexes.html#external-tables). inserted\_rows BIGINT The total number of rows written. inserted\_bytes BIGINT The total number of bytes written to both cache and storage. spilled\_bytes BIGINT The total number of uncompressed bytes spilled. total\_ram\_consumed BIGINT The total number of bytes in RAM consumed by the engine during the query process. returned\_rows BIGINT The total number of rows returned from the query. returned\_bytes BIGINT The total number of bytes returned from the query. time\_in\_queue\_us BIGINT The number of microseconds the query spent in queue. retries BIGINT The number of retried attempts in case of query failure. Defaults to 0.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engines.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engines.md
new file mode 100644
index 0000000..2c0b868
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engines.md
@@ -0,0 +1,20 @@
+# [](#information-schema-for-engines)Information schema for engines
+
+You can use the `information_schema.engines` view to return information about each engine in an account. The view is available for each database and contains one row for each engine in the account. You can use a `SELECT` query to return information about each engine as shown in the example below, which uses a `WHERE` clause to return all engines attached to databases that begin with `deng`.
+
+To view engine information, the user must have ownership of the engine or access to the necessary [engine](/Overview/Security/Role-Based%20Access%20Control/engine-permissions.html#engine-permissions) privileges.
+
+```
+SELECT
+  *
+FROM
+  information_schema.engines
+WHERE
+  attached_to ILIKE 'deng%'
+```
+
+## [](#columns-in-information_schemaengines)Columns in information\_schema.engines
+
+Each row has the following columns with information about each engine.
+
+Column Name Data Type Description engine\_name TEXT The name of the engine. region TEXT \[DEPRECATED] The region in which the engine was created. spec TEXT \[DEPRECATED] The specification of nodes comprising the engine. scale INTEGER \[DEPRECATED] The number of nodes in the engine. type TEXT Determines the capability of the nodes in the engine. family TEXT The family of a given engine. Choose from `STORAGE_OPTIMIZED` or `COMPUTE_OPTIMIZED`. nodes INTEGER The number of nodes in a cluster. clusters INTEGER The number of node groupings in an engine. status TEXT The engine status. For more information, see [Viewing and understanding engine status](/Overview/engine-fundamentals.html#viewing-and-understanding-engine-status). attached\_to TEXT \[DEPRECATED] The name of the database to which the engine is attached. auto\_start BOOLEAN When true, queries issued to a stopped engine will attempt to start the engine first. auto\_stop INTEGER Indicates the amount of time (in minutes) after which the engine automatically stops. engine\_type TEXT \[DEPRECATED] The type of the engine. initially\_stopped BOOLEAN When true, the engine will have attempted to start after creation. url TEXT A url which can be used to issue queries to this engine. warmup TEXT \[DEPRECATED] The warmup method of the engine. default\_database TEXT The database an engine will attempt to use by default when dealing with queries that require a database. version TEXT The engine version. last\_started TIMESTAMPTZ The last time this engine was started (UTC). last\_stopped TIMESTAMPTZ The last time this engine was stopped (UTC). description TEXT A user defined description for the engine. created TIMESTAMPTZ The time when this engine was created (UTC). engine\_owner TEXT The name of the user who created the engine. last\_altered\_by TEXT The user who last altered this engine. last\_altered TIMESTAMPTZ The time when this engine was last altered (UTC). fbu\_rate NUMERIC Hourly FBU consumption rate of engines based on engine topology at the time the view is invoked by the user.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engines_billing.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engines_billing.md
new file mode 100644
index 0000000..ecdc5d4
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_engines_billing.md
@@ -0,0 +1,16 @@
+# [](#information-schema-for-engines-billing)Information schema for engines billing
+
+You can use the `information_schema.engines_billing` view to see daily billing information for all the engines in all the accounts across all the regions in organization.
+
+```
+SELECT
+  *
+FROM
+  information_schema.engines_billing;
+```
+
+## [](#columns-in-information_schemaengines_billing)Columns in information\_schema.engines\_billing
+
+Each row has the following columns.
+
+Column Name Data Type Description engine\_name TEXT Name of the engine account\_name TEXT Account to which the engine belongs engine\_description TEXT Description of engine as entered by user when the engine is created region TEXT Region where the engine was created usage\_date DATE Date for which the usage is reported consumed\_fbu NUMERIC Number of FBUs consumed by the engine for the given date billed\_cost NUMERIC The cost for the FBUs consumed for the given date is\_credit BOOLEAN Indicates whether costs were used as credit
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_indexes.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_indexes.md
new file mode 100644
index 0000000..2b68f50
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_indexes.md
@@ -0,0 +1,22 @@
+# [](#information-schema-for-indexes)Information schema for indexes
+
+You can use the `information_schema.indexes` view to return information about each index in a database. The view is available for each database and contains one row for each index in the database. You can use a `SELECT` query to return information about each index.
+
+In order to view index information, you need the USAGE privilege on both the [schema](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html#schema-level-privileges) and the [database](/Overview/Security/Role-Based%20Access%20Control/database-permissions/#database-level-privileges). You also need ownership of the table or the necessary [table-level privileges](/Overview/Security/Role-Based%20Access%20Control/database-permissions/table-permissions.html#table-level-privileges) required for the intended action.
+
+The following query returns all aggregating indexes defined within the current database.
+
+```
+SELECT
+  *
+FROM
+  information_schema.indexes
+WHERE
+  index_type='aggregating`;
+```
+
+## [](#columns-in-information_schemaindexes)Columns in information\_schema.indexes
+
+Each row has the following columns with information about the database.
+
+Column Name Data Type Description table\_catalog TEXT Name of the catalog. Firebolt provides a single ‘default’ catalog. table\_schema TEXT Name of the database. table\_name TEXT The name of the table for which the index is defined. index\_name TEXT The name defined for the index. index\_type TEXT One of either `primary` or `aggregating`. index\_owner TEXT The owner of the table, which is the owner of the index. index\_definition TEXT The part of the index statement that specifies the columns and any aggregations included in the index. compressed\_bytes BIGINT The compressed size of the index, in bytes. uncompressed\_bytes BIGINT The uncompressed size of the index, in bytes. number\_of\_tablets BIGINT The number of tablets in the index. created TIMESTAMPTZ Time that the index was created.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_locations.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_locations.md
new file mode 100644
index 0000000..8fa6510
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_locations.md
@@ -0,0 +1,39 @@
+# [](#information-schema-for-locations)Information schema for locations
+
+You can use the `information_schema.locations` view to return information about each location in your Firebolt [account](/Overview/organizations-accounts.html#accounts). The view contains one row for each location. Use a `SELECT` query to return information about each location as shown in the example below.
+
+To view location information, you must have `LIST LOCATION` or `LIST ANY LOCATION` privileges. For more information about location permissions, see [CREATE LOCATION](/sql_reference/commands/data-definition/create-location.html).
+
+```
+SELECT
+  *
+FROM
+  information_schema.locations;
+```
+
+## [](#columns-in-information_schemalocations)Columns in information\_schema.locations
+
+Each row has the following columns with information about each location:
+
+Column Name Data Type Description location\_name TEXT The name of the location. source TEXT The type of the external data source. Firebolt currently supports only `AMAZON_S3`. url TEXT The data source URL. For Amazon S3, the format is `s3://{bucket_name}/{path}`. description TEXT Optional metadata describing the location’s purpose. location\_owner TEXT The owner of the location. created TIMESTAMPTZ The timestamp when the location was created.
+
+## [](#example)Example
+
+The following query returns information about all locations in your account:
+
+```
+SELECT 
+  location_name,
+  source,
+  url,
+  description,
+  location_owner,
+  created
+FROM 
+  information_schema.locations;
+```
+
+## [](#notes)Notes
+
+- All identifiers are case-insensitive unless enclosed in double-quotes.
+- For more information about object identifiers, see [Object identifiers](/Reference/object-identifiers.html).
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_logins.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_logins.md
new file mode 100644
index 0000000..d50329b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_logins.md
@@ -0,0 +1,20 @@
+# [](#information-schema-for-logins)Information schema for logins
+
+You can use the `information_schema.logins` view to return information about logins.
+
+You can use a `SELECT` query to return information about each login, as shown in the example below.
+
+```
+SELECT
+  *
+FROM
+  information_schema.logins;
+```
+
+For more information, see [Managing logins](/Guides/managing-your-organization/managing-logins.html).
+
+## [](#columns-in-information_schemalogins)Columns in information\_schema.logins
+
+Each row has the following columns with information about each login.
+
+Column Name Data Type Description login\_name TEXT Name of the login (email address). first\_name TEXT First name of the user linked to the login. last\_name TEXT Last name of the user linked to the login. organization\_name TEXT Name of the organization. network\_policy\_name TEXT Name of the network policy associated with the login. is\_mfa\_enabled BOOLEAN Specifies if the login has multi-factor authentication enabled. is\_sso\_provisioned BOOLEAN Specifies if the login was provisioned with an identity provider defined in the organization’s SSO configuration. is\_password\_enabled BOOLEAN Specifies if log in with password is enabled. is\_organization\_admin BOOLEAN Specifies if the login is an organization admin. is\_enabled BOOLEAN Specifies if the login is allowed to authenticate. created TIMESTAMPTZ Time the login was created. login\_owner TEXT Name of the login who created the login. If the login was created by a service account, the service account name appears instead. last\_altered TIMESTAMPTZ Time the login was last altered. last\_altered\_by TEXT Name of the login who edited the login. If the login was edited by a service account, the service account name appears instead.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_network_policies.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_network_policies.md
new file mode 100644
index 0000000..8619f83
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_network_policies.md
@@ -0,0 +1,18 @@
+# [](#information-schema-for-network_policies)Information schema for network\_policies
+
+You can use the `information_schema.network_policies` view to return information about network policies. You can use a `SELECT` query to return information about each network policy as shown in the example below.
+
+```
+SELECT
+  *
+FROM
+  information_schema.network_policies;
+```
+
+Read more about network policies [here](/Guides/security/network-policies.html).
+
+## [](#columns-in-information_schemanetwork_policies)Columns in information\_schema.network\_policies
+
+Each row has the following columns with information about a network policy.
+
+Column Name Data Type Description network\_policy\_name TEXT The name of the network policy. allowed\_ips ARRAY(TEXT) List of allowed ips blocked\_ips ARRAY(TEXT) List of blocked ips is\_organizational BOOLEAN Specifies if the network policy is active at the organization level . network\_policy\_description TEXT The description of the network policy. created TIMESTAMPTZ Time the service account was created. network\_policy\_owner TEXT The name of the login that created the network policy. If the network policy was created by a service account, the service account name appears instead. last\_altered TIMESTAMPTZ Time the service account was last altered. last\_altered\_by TEXT The name of the login that edited the network policy. If the network policy was edited by a service account, the service account name appears instead.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_object_privileges.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_object_privileges.md
new file mode 100644
index 0000000..6cc9187
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_object_privileges.md
@@ -0,0 +1,56 @@
+# [](#information-schema-for-object_privileges)Information schema for object\_privileges
+
+The `information_schema.object_privileges` view provides information about permissions granted to each role.
+
+To be able to access this information, you must have [role privileges](/Overview/Security/Role-Based%20Access%20Control/role-permissions.html#role-permissions), ownership of the role, or ownership of the object to which the role is granted.
+
+### [](#view-account-role-user-engine-and-database-permissions)View account, role, user, engine, and database permissions
+
+To view account, role, user, engine and database permissions, make sure that current database is **not** selected. Then, query the `information_schema.object_privileges` view as shown in the following examples:
+
+**View privileges directly under an account**
+
+To view all privileges directly under an account, ensure that no database is selected, and query the `information_schema` as follows:
+
+```
+SELECT
+  *
+FROM
+  information_schema.object_privileges;
+```
+
+You can also deselect the current database in the **Firebolt Develop Space** user interface (UI), by choosing `None` in [the current database selector](/assets/images/current_database_dropdown_none_option.png).
+
+**View privileges in a specific database**
+
+To view all privileges under a user defined database `db`, specify the database in the query as follows:
+
+```
+SELECT
+  *
+FROM
+  db.information_schema.object_privileges;
+```
+
+### [](#view-object-permissions-in-the-current-database)View object permissions in the current database
+
+When the current database is selected,`information_schema.object_privileges` only shows permissions for objects within that database. It does not show permissions for accounts, roles, users, engines, databases, and objects in other databases.
+
+To view permissions for schemas, tables and views in the current database, set the current database with [USE DATABASE](/sql_reference/commands/data-definition/use-database.html), then select and view privileges in a query as follows:
+
+```
+USE DATABASE db;
+
+SELECT
+  *
+FROM
+  information_schema.object_privileges;
+```
+
+You can also use the [database selector](/assets/images/current_database_dropdown.png) in the UI.
+
+## [](#columns-in-information_schemaobject_privileges)Columns in `information_schema.object_privileges`
+
+Each row in `information_schema.object_privileges` contains the following columns:
+
+Column Name Data Type Description grantor TEXT The name of the user that granted the privilege. grantee TEXT The name of the role that the privilege was granted to. object\_catalog TEXT The database containing the object on which the privilege is granted. object\_schema TEXT The schema containing the object on which the privilege is granted. object\_name TEXT The name of the object on which the privilege is granted. object\_type TEXT The type of the object on which the privilege is granted. privilege\_type TEXT The type of the privilege granted on the object. is\_grantable TEXT Specify `YES` if the privilege is grantable, and `NO` otherwise. created TIMESTAMPTZ The creation time of the privilege.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_routines.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_routines.md
new file mode 100644
index 0000000..fb20ee1
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_routines.md
@@ -0,0 +1,36 @@
+# [](#information-schema-routines)Information schema routines
+
+You can use the `information_schema.routines` view to return information about SQL functions including their database, schema, name, type, return data type, parameter data types, and whether they are deterministic.
+
+**Example**
+
+The following code example lists all aggregate functions in the database and displays their name, parameters, and return data type, sorted by function name:
+
+```
+SELECT
+  routine_name || '(' || array_to_string(routine_parameters) || ') => ' || data_type
+FROM
+  information_schema.routines
+WHERE
+  routine_type = 'AGGREGATE FUNCTION'
+ORDER BY routine_name
+```
+
+**Example**
+
+The following code example retrieves the names of all routines from the database that return a data type of `GEOGRAPHY`:
+
+```
+SELECT
+  routine_name
+FROM
+  information_schema.routines
+WHERE
+  data_type = 'geography'
+```
+
+## [](#columns-in-information_schemaroutines)Columns in `information_schema.routines`
+
+Each row in `information_schema.routines` contains the following information about the SQL function:
+
+Column Name Data Type Description routine\_catalog TEXT The database containing the function. routine\_schema TEXT The schema containing the function. routine\_name TEXT The name of the function. routine\_type TEXT The type of the function, which can be either `FUNCTION`, `AGGREGATE FUNCTION`, `WINDOW FUNCTION` or `TABLE FUNCTION`. data\_type TEXT The return type name of the function. These type names are simplified, for example, returning `ARRAY` instead of `ARRAY(INT)`. If the function accepts and returns data any type, its `data_type` is `ANY`. is\_deterministic TEXT A flag that indicates if the function is deterministic or not. A deterministic function returns the same output when called with the same inputs *within the same query*, even if it can produce a different output when called in a different query. An example of a deterministic function is `CURRENT_TIMESTAMP`. An example of a non-deterministic function is `RANDOM`. routine\_parameters ARRAY(TEXT) An array of data types representing the function’s parameters.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_schemata.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_schemata.md
new file mode 100644
index 0000000..4bcb6f7
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_schemata.md
@@ -0,0 +1,18 @@
+# [](#information-schema-for-schemata)Information schema for schemata
+
+You can use the `information_schema.schemata` view to return information about schemas available in the database. Run a `SELECT` query to return information about each schema as shown in the example below.
+
+To view schema information, you must have [schema privilege](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html#schema-level-privileges) or ownership of the schema object.
+
+```
+SELECT
+  *
+FROM
+  information_schema.schemata;
+```
+
+## [](#columns-in-information_schemaschemata)Columns in information\_schema.schemata
+
+Each row has the following columns with information about the schema.
+
+Column Name Data Type Description   catalog\_name TEXT Name of the catalog.   schema\_name TEXT Name of the schema.   schema\_owner TEXT Owner of the schema.   default\_character\_set\_catalog TEXT The catalog that contains the character set. Defaults to NULL.   default\_character\_set\_schema TEXT The schema that contains the character set. Defaults to NULL.   default\_character\_set\_name TEXT Default character set of the schema. Defaults to `UTF-8`.   sql\_path TEXT SQL path of the schema.   description TEXT Description of the schema.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_service_accounts.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_service_accounts.md
new file mode 100644
index 0000000..745a72f
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_service_accounts.md
@@ -0,0 +1,22 @@
+# [](#information-schema-for-service_accounts)Information schema for service\_accounts
+
+Use the `information_schema.service_accounts` view to return information about service accounts. The following code example uses a `SELECT` query to return information about each service account:
+
+```
+SELECT
+  *
+FROM
+  information_schema.service_accounts;
+```
+
+For more information about service accounts, see [Manage programmatic access to Firebolt](/Guides/managing-your-organization/service-accounts.html).
+
+## [](#columns-in-information_schemaservice_accounts)Columns in information\_schema.service\_accounts
+
+Each row has the following columns with information about a service account:
+
+Column Name Data Type Description service\_account\_id TEXT The ID of the service account. service\_account\_name TEXT The name of the service account. network\_policy\_name TEXT The name of the network policy used by this service account. service\_account\_description TEXT The description of the service account. is\_organization\_admin BOOLEAN Specifies if the user associated with the service account has an [organizational administrative role](/Overview/organizations-accounts.html#organizational-administrative-role). connection\_preference TEXT Defines the connectivity preference for a service account. The default value is `PREFER_PUBLIC` if not specified. A user with an [organizational administrator role](/Overview/organizations-accounts.html#organizational-administrative-role) can configure this setting, and it can be modified after creation. Available options include the following:  
+\- **`PUBLIC_ONLY`** : Allows access only through public APIs.  
+\- **`PRIVATE_ONLY`** : Allows access only using AWS PrivateLink.  
+\- **`PREFER_PUBLIC`** (Default): Prefers public APIs but can use AWS PrivateLink if needed.  
+\- **`PREFER_PRIVATE`** : Prefers AWS PrivateLink but can use public APIs if needed. is\_enabled BOOLEAN Specifies if the service account is allowed to authenticate. created TIMESTAMPTZ Time of the service account creation. service\_account\_owner TEXT The name of the login that created the service account. If the service account was created by a service account, the service account name appears instead. last\_altered TIMESTAMPTZ Time the service account was last altered. last\_altered\_by TEXT The name of the login that edited the service account. If the service account was edited by a service account, the service account name appears instead.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_billing.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_billing.md
new file mode 100644
index 0000000..4126228
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_billing.md
@@ -0,0 +1,16 @@
+# [](#information-schema-for-storage-billing)Information schema for storage billing
+
+You can use the `information_schema.storage_billing` view to see daily billing information for storage in all the accounts across all the regions in organization.
+
+```
+SELECT
+  *
+FROM
+  information_schema.storage_billing;
+```
+
+## [](#columns-in-information_schemastorage_billing)Columns in information\_schema.storage\_billing
+
+Each row has the following columns.
+
+Column Name Data Type Description account\_name TEXT Account for which the storage is billed region TEXT Region where the data is stored usage\_date DATE Date for which the usage is reported consumed\_gib\_per\_month NUMERIC Amount of data billed for the given date in GiB billed\_cost NUMERIC The cost for the storage consumed for the given date is\_credit BOOLEAN Indicates whether costs were used as credit
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_history.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_history.md
new file mode 100644
index 0000000..07a791a
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_history.md
@@ -0,0 +1,38 @@
+# [](#information-schema-for-storage-history)Information schema for storage history
+
+You can use the `information_schema.storage_history` view to return information about the storage consumption of your catalogs (databases). Due to the nature of this view’s computation, it is eventually consistent. DROP / INSERT / UPDATE / VACUUM operations may take up to 2 days to be fully reflected.
+
+In the example below, a filter is applied to look at the metrics of all catalogs over the last week. By default, the view shows data as far back as each catalog has existed.
+
+```
+SELECT
+  *
+FROM
+  information_schema.storage_history
+WHERE
+  usage_date > now() - INTERVAL '7 days'
+  and catalog_id is not null
+LIMIT 100;
+```
+
+Dropped catalogs display NULL `catalog_name`, but are trackable by `catalog_id`.
+
+Rows not attributed to any one catalog (NULL `catalog_id`) carry special meaning. This storage consumption is account-wide. It covers inactive data (garbage files that are preserved for the duration of a 1 week fail-safe period), as well as active in-flight data (any new files that were not yet transactionally attributed to a catalog during consumption computation).
+
+This example shows how to look up storage consumption not associated with any particular catalog.
+
+```
+SELECT
+  *
+FROM
+  information_schema.storage_history
+WHERE
+  catalog_id is null
+LIMIT 100;
+```
+
+## [](#columns-in-information_schemastorage_history)Columns in information\_schema.storage\_history
+
+Each row has the following columns with information about storage consumption.
+
+Column Name Data Type Description catalog\_name TEXT Catalog (database) for which storage is reported catalog\_id TEXT Catalog (database) id for which storage is reported usage\_date DATE Date for which the usage is reported active\_data\_size\_bytes BIGINT Number of bytes consumed by active data inactive\_data\_size\_bytes BIGINT Number of bytes consumed by inactive data
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_metering_history.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_metering_history.md
new file mode 100644
index 0000000..2b2bf48
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_storage_metering_history.md
@@ -0,0 +1,16 @@
+# [](#information-schema-for-storage-metering-history)Information schema for storage metering history
+
+You can use the `information_schema.storage_metering_history` view to see daily information about aggregated storage consumption within an account.
+
+```
+SELECT
+  *
+FROM
+  information_schema.storage_metering_history;
+```
+
+## [](#columns-in-information_schemastorage_metering_history)Columns in information\_schema.storage\_metering\_history
+
+Each row has the following columns.
+
+Column Name Data Type Description usage\_date DATE Date for which the usage is reported consumed\_gib\_per\_month NUMERIC Number of bytes consumed by the account for the given date
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_tables.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_tables.md
new file mode 100644
index 0000000..65eeb59
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_tables.md
@@ -0,0 +1,18 @@
+# [](#information-schema-for-tables)Information schema for tables
+
+You can use the `information_schema.tables` view to return information about each table in a database. The view is available for each database and contains one row for each table in the database. You can use a `SELECT` query to return information about each table as shown in the example below.
+
+To view table information, you must have `USAGE` privileges on both the [schema](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html#schema-level-privileges) and the [database](/Overview/Security/Role-Based%20Access%20Control/database-permissions/#database-level-privileges). You also need ownership of the table or the necessary [table-level privileges](/Overview/Security/Role-Based%20Access%20Control/database-permissions/table-permissions.html#table-level-privileges) required for the intended action.
+
+```
+SELECT
+  *
+FROM
+  information_schema.tables;
+```
+
+## [](#columns-in-information_schematables)Columns in information\_schema.tables
+
+Each row has the following columns with information about each table.
+
+Column Name Data Type Description table\_catalog TEXT The name of the database. table\_schema TEXT The name of the schema. table\_name TEXT The name of the table. table\_type TEXT The table’s type, such as `BASE TABLE`, `EXTERNAL` `VIEW`. table\_owner TEXT The owner of the table, or `NULL` if there is no owner. created TIMESTAMPTZ The time that the table or view was created. last\_altered TIMESTAMPTZ Not applicable for Firebolt. last\_altered\_by TEXT Not applicable for Firebolt. primary\_index TEXT An ordered array of the column names that comprise the primary index definition, if applicable. number\_of\_rows BIGINT The number of rows in the table. compressed\_bytes BIGINT The compressed size of the table in bytes. uncompressed\_bytes BIGINT The uncompressed size of the table in bytes. compression\_ratio NUMERIC The compression ratio (`<uncompressed_bytes>`/`<compressed_bytes>`). number\_of\_tablets INTEGER The number of tablets that comprise the table. fragmentation DECIMAL The table fragmentation percentage (between 0-100). type TEXT The table’s type. location\_name TEXT Not applicable for Firebolt. ddl TEXT The text of the SQL statement that created the table. self\_referencing\_column\_name NULL Not applicable for Firebolt. reference\_generation NULL Not applicable for Firebolt. user\_defined\_type\_catalog NULL Not applicable for Firebolt. user\_defined\_type\_schema NULL Not applicable for Firebolt. user\_defined\_type\_name NULL Not applicable for Firebolt. is\_insertable\_into TEXT `YES` if the table is insertable, `NO` otherwise. is\_typed TEXT Always `NO`. commit\_action NULL Not applicable for Firebolt.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_transitive_applicable_roles.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_transitive_applicable_roles.md
new file mode 100644
index 0000000..5b6267b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_transitive_applicable_roles.md
@@ -0,0 +1,24 @@
+# [](#information-schema-for-transitive_applicable_roles)Information schema for transitive\_applicable\_roles
+
+The `information_schema.applicable_roles` view shows every role in the account and its grantees, who include other users or roles to whom the role is granted.
+
+Unlike, `information_schema.applicable_roles` that shows only direct grantees, `information_schema.transitive_applicable_roles` also shows indirect grantees. For example, if role `engineer` is granted to role `manager` and role `manager` is granted to user `alice` then user `alice` is a direct grantee of `manager` and an indirect grantee of `engineer`.
+
+You can use a `SELECT` query to return information about each role as shown in the example below.
+
+```
+SELECT
+  *
+FROM
+  information_schema.transitive_applicable_roles;
+```
+
+See also `information_schema.applicable_roles` [here](/sql_reference/information-schema/applicable-roles.html).
+
+Read more about RBAC roles [here](/Guides/security/rbac.html#check-assigned-privileges-using-sql).
+
+## [](#columns-in-information_schematransitive_applicable_roles)Columns in information\_schema.transitive\_applicable\_roles
+
+Each row has the following columns with information about the role.
+
+Column Name Data Type Description grantee TEXT User or role to whom the role is granted (directly or indirectly). role\_name TEXT Name of the role. is\_grantable TEXT `YES` if the grantee has the admin option on the role, `NO` if not. created TIMESTAMPTZ Creation time of the role.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_users.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_users.md
new file mode 100644
index 0000000..abdc2af
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_users.md
@@ -0,0 +1,20 @@
+# [](#information-schema-for-users)Information schema for users
+
+You can use the `information_schema.users` view to return information about users. You can use a `SELECT` query to return information about each user, as shown in the example below.
+
+To view information about users, you must have [user privilege](/Overview/Security/Role-Based%20Access%20Control/user-permissions.html#user-permissions) or ownership of the user object.
+
+```
+SELECT
+  *
+FROM
+  information_schema.users;
+```
+
+For more information, see [Managing users](/Guides/managing-your-organization/managing-users.html).
+
+## [](#columns-in-information_schemausers)Columns in information\_schema.users
+
+Each row has the following columns with information about each user.
+
+Column Name Data Type Description user\_name TEXT The name of the user. login\_name TEXT The name of the login linked to the user. Empty if the login is linked to a service account. service\_account\_name TEXT The name of the service account linked to the user. Empty if the login is linked to a service account. account\_name TEXT The name of the account. organization\_name TEXT The name of the organization. default\_database TEXT The default database set for the user. default\_engine TEXT The default engine set for the user. created TIMESTAMPTZ Time the user was created. user\_owner TEXT The name of the user who created the user. last\_altered TIMESTAMPTZ Time the user was last altered. last\_altered\_by TEXT The name of the last user to edit the user.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_views.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_views.md
new file mode 100644
index 0000000..8a12158
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_information_schema_views.md
@@ -0,0 +1,18 @@
+# [](#information-schema-for-views)Information schema for views
+
+You can use the `information_schema.views` view to return information about each view in a database. The view is available for each database and contains one row for each view in the database. You can use a `SELECT` query to return information about each view as shown in the example below.
+
+To access information about views, you must have `USAGE` privileges on both the [schema](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html#schema-level-privileges) and the [database](/Overview/Security/Role-Based%20Access%20Control/database-permissions/schema-permissions.html#schema-level-privileges). You also need ownership of the view or [view-level privileges](/Overview/Security/Role-Based%20Access%20Control/database-permissions/view-permissions.html#view-permissions).
+
+```
+SELECT
+  *
+FROM
+  information_schema.views;
+```
+
+## [](#columns-in-information_schemaviews)Columns in information\_schema.views
+
+Each row has the following columns with information about each view.
+
+Column Name Data Type Description table\_catalog TEXT The name of the catalog. Firebolt offers a single ‘default’ catalog. table\_schema TEXT The name of the database. table\_name TEXT The name of the view. view\_definition TEXT The query statement that defines the view. check\_option NULL Not applicable for Firebolt. is\_updatable TEXT Always `NO`. insertable\_into TEXT Always `NO`. is\_trigger\_updatable TEXT Always `NO`. is\_trigger\_deletable TEXT Always `NO`. is\_trigger\_insertable\_into TEXT Always `NO`. created TIMESTAMPTZ Time that the view was created. view\_owner TEXT The owner of the view. last\_altered TIMESTAMPTZ Time that the view was last changed. last\_altered\_by TEXT The user who last altered this view.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_numeric_data_type.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_numeric_data_type.md
new file mode 100644
index 0000000..23fefc9
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_numeric_data_type.md
@@ -0,0 +1,77 @@
+# [](#numeric-data-type)NUMERIC data type
+
+This topic describes the Firebolt implementation of the `NUMERIC` data type.
+
+- [Overview](#overview)
+  
+  - [Storage size for precision](#storage-size-for-precision)
+  - [Default values for precision and scale](#default-values-for-precision-and-scale)
+  - [Precision vs. scale](#precision-vs-scale)
+  - [Type conversion (type promotion)](#type-conversion-type-promotion)
+  - [Supported operators](#supported-operators)
+
+## [](#overview)Overview
+
+The `NUMERIC` data type is an exact numeric data type defined by its precision (total number of digits) and scale (number of digits to the right of the decimal point).
+
+`NUMERIC` has two optional input parameters: `NUMERIC(precision, scale)`
+
+The maximum precision is 38. The scale value is bounded by the precision value `(scale<=precision)`.
+
+The precision must be positive, while the scale can be zero or positive.
+
+The `DECIMAL` data type is a synonym to the `NUMERIC` data type.
+
+### [](#storage-size-for-precision)Storage size for precision
+
+The storage size of the data type depends on the precision, as described in the following table:
+
+precision bytes 1-9 4 10-18 8 18-38 16
+
+For example, if the precision is between 1 and 9 digits, the data type will use 4 bytes of storage.
+
+### [](#default-values-for-precision-and-scale)Default values for precision and scale
+
+If the scale is not specified when declaring a column of `NUMERIC` data type, then it defaults to `NUMERIC(precision, min(9, precision))`
+
+If both the precision and scale are not specified, then it defaults to `NUMERIC(38, 9)`
+
+### [](#precision-vs-scale)Precision vs. scale
+
+If the scale of a value to be stored is greater than the declared scale of the column, the system will round the value to the specified number of fractional digits. If the number of digits to the left of the decimal point exceeds the declared precision, minus the declared scale, an error results.
+
+```
+  SELECT CAST(100.76 AS NUMERIC(5,2)); -- 100.76
+  SELECT CAST(100.76 AS NUMERIC(5,1)); -- 100.8
+  SELECT(100.76 AS NUMERIC(3,1)); -- error
+```
+
+### [](#type-conversion-type-promotion)Type conversion (type promotion)
+
+Note: `NUMERIC` precision and scale does not change with any operation, i.e., there is no automatic widening of the result type to prevent overflows. If a wider type is desired, cast the inputs to perform the operations on wider types.
+
+1. **P1≠P2 or S1≠S2** (casting required)
+   
+   Any operation between two `NUMERIC`s with different precision and/or scale requires explicit casting of the input to the desired precision and scale.
+   
+   ```
+    NUMERIC(P1, S1) <OP> NUMERIC(P2, S2) -> ERROR (P1≠P2 or S1≠S2) 
+   ```
+   
+   where P1≠P2 or S1≠S2
+2. **P1=P2 and S1=S2** (casting optional)
+   
+   If the two `NUMERIC`s have the same precision and scale, the result will implicitly cast to the same precision and scale. You can still explicitly cast to any other precision and scale.
+   
+   ```
+    NUMERIC(P1, S1) <OP> NUMERIC(P2, S2) -> NUMERIC(P1, S1)
+   ```
+
+### [](#supported-operators)Supported operators
+
+**Operators:**
+
+\+  
+\-  
+\*  
+/
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_operators.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_operators.md
new file mode 100644
index 0000000..5562d6c
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_operators.md
@@ -0,0 +1,242 @@
+# [](#operators)Operators
+
+Operators are represented by special characters or keywords, they do not use function call syntax.
+
+## [](#operator-precedence)Operator Precedence
+
+The following table lists all SQL operators from highest to lowest precedence, alongside with their associativity. The precedence and associativity of the operators is hard-coded into the parser. Add parentheses if you want an expression with multiple operators to be interpreted in some other way than what the precedence rules imply.
+
+Operator Description Associativity `.` Table/column name separator left `::` Type cast left `[]` Array element left `+` `-` Unary plus and minus right `AT` `AT TIME ZONE` left `^` exponentiation left `*` `/` `%` multiplication, division, modulo left `+` `/` addition, subtraction left `\|\|` concatenation left `BETWEEN` range containment   `LIKE` `ILIKE` string matching   `<` `>` `=` `<=` `>=` `<>` comparison   `IS` `IS NULL`, `IS DISTINCT FROM`, `IS TRUE`   `NOT` logical negation right `AND` logical conjunction left `OR` logical disjunction left
+
+- [Operator Precedence](#operator-precedence)
+- [:: Type cast](#-type-cast)
+- [Arithmetic (numbers)](#arithmetic-numbers)
+- [Logical](#logical)
+- [Comparison](#comparison)
+- [CASE](#case)
+  
+  - [Return type](#return-type)
+- [Date and time arithmetic](#date-and-time-arithmetic)
+- [String](#string)
+- [Subquery operators](#subquery-operators)
+
+## [](#-type-cast):: Type cast
+
+Use can use the `::` operator instead of the [CAST](/sql_reference/functions-reference/conditional-and-miscellaneous/cast.html) function to convert one [data type](/sql_reference/data-types.html) to another.
+
+### [](#syntax)Syntax
+
+```
+ -- CAST function
+ CAST(<value> AS <type>)
+ -- :: operator
+ <value>::<type>
+```
+
+Component Description `<value>` The value to convert or an expression that results in a value to convert. Can be a column name, a function applied to a column or another function, or a literal value. `<type>` The target [data type](/sql_reference/data-types.html) (case-insensitive).
+
+### [](#example)Example
+
+```
+SELECT '2021-12-31'::DATE;
+SELECT 8.5::REAL;
+SELECT col_a::BIGINT;
+```
+
+## [](#arithmetic-numbers)Arithmetic (numbers)
+
+Operator Operator description Input Data Types Output Data Types Example Result + addition INTEGER, BIGINT, NUMERIC, REAL, DOUBLE PRECISION Corresponding type `SELECT 2 + 3;` 5 - subtraction INTEGER, BIGINT, NUMERIC, REAL, DOUBLE PRECISION Corresponding type `SELECT 2 - 3;` -1 * multiplication INTEGER, BIGINT, NUMERIC, REAL, DOUBLE PRECISION Corresponding type `SELECT 2 * 3;` 6 / division (integer division truncates the result) INTEGER, BIGINT, NUMERIC, REAL, DOUBLE PRECISION Corresponding type `SELECT 4 / 2;` 2 % modulo (remainder) INTEGER, BIGINT Corresponding type `SELECT 5 % 4;` 1 ^ exponentiation INTEGER, BIGINT, NUMERIC, REAL, DOUBLE PRECISION DOUBLE PRECISION `SELECT 2 ^ 3.0;` 8
+
+In arithmetic operations like +, -, \*, and / , the result’s data type aligns with the most encompassing type of the operands indicated as “ Corresponding type” in the table above. For clarity:
+
+- When both operands are of the same data type (e.g., two INTEGERs or two NUMERICs), the result will also be of that same data type.
+  
+  - `INTEGER <op> INTEGER = INTEGER`
+  - `INTEGER <op> BIGINT = BIGINT`
+- For operations involving two different numeric data types, the result will typically be of the more precise or larger data type.
+  
+  - `INTEGER <op> REAL = DOUBLE PRECISION`
+- Overflow checks and floating point errors are applied according to the result data type only.
+
+> Floating point note:
+> 
+> Precision means that the representation of a number is accurate up to a certain number of digits. In Firebolt, `REAL` data types have 6-digit precision and `DOUBLE PRECISION` have 16-digit precision. This means that calculations have a precision of 6 or 16 respectively, and numbers are truncated to that precision. For example, if a number is stored as 1.234567, it is automatically truncated to 1.23456 for `REAL`.
+> 
+> When performing arithmetic, the number of leading digits in the output is the product of the leading digits in both inputs. This means that if either or both of the input numbers are larger than 6, those numbers are the first truncated, and then the arithmetic is performed.
+
+## [](#logical)Logical
+
+Logical operators return the result of a boolean operation using [three valued logic](https://en.wikipedia.org/wiki/Three-valued_logic)
+
+Operator Example Explanation `AND` `x AND y` True if both x and y are true `NOT` `NOT x` True if x is false `OR` `x OR y` True if either x or y is true
+
+## [](#comparison)Comparison
+
+Operator Syntax Explanation = `a=b` a is equal to b. != `a!=b` a is not equal to b. &lt;&gt; `a<>b` a is not equal to b. &lt;= `a<=b` a is less than or equal to b. &gt; `a>b` a is greater than b. &gt;= `a>=b` a is greater than or equal to b. &lt; `a<b` a is less than b. BETWEEN `a BETWEEN b AND c` equivalent to b &lt;= a &lt;= c IS NULL `a IS NULL` a contains a NULL value IS NOT NULL `a IS NOT NULL` a doesn’t contain a NULL value IS NOT DISTINCT FROM `a IS NOT DISTINCT FROM b` equivalent to a=b where NULL is considered equal to NULL. IS DISTINCT FROM `a IS DISTINCT FROM b` equivalent to a!=b where NULL is considered equal to NULL.
+
+Example of using comparison operator in `WHERE` clause
+
+```
+SELECT
+  *
+FROM
+  Table
+WHERE
+  Price >= 100;
+```
+
+## [](#case)CASE
+
+Conditional expression similar to if-then-else statements. If the result of the condition is true, then the value of the CASE expression is the result that follows the condition. If the result is false, any subsequent WHEN clauses (conditions) are searched in the same manner. If no WHEN condition is true, then the value of the case expression is the result specified in the ELSE clause. If the ELSE clause is omitted and no condition matches, the result is NULL.
+
+### [](#syntax-1)Syntax
+
+```
+CASE
+    WHEN <condition> THEN <result>
+    [ WHEN ...n ]
+    [ ELSE <result> ]
+END;
+```
+
+### [](#parameters)Parameters
+
+Parameter Description Supported input types `<condition>` A condition can be defined for each `WHEN`, and `ELSE` clause. `BOOLEAN` `<result>` The result of any condition. Every `THEN` clause receives a single result. All results in a single `CASE` function must share the same data type. Any
+
+### [](#return-type)Return type
+
+Same data type as `<result>`
+
+### [](#example-1)Example
+
+This example references a table `player_level` with the following columns and values:
+
+player currentlevel kennethpark 3 esimpson 8 sabrina21 11 rileyjon 15 burchdenise 4
+
+The following example categorizes each entry by length. If the movie is longer than zero minutes and less than 50 minutes it is categorized as SHORT. When the length is 50-120 minutes, it’s categorized as Medium, and when even longer, it’s categorized as Long.
+
+```
+SELECT
+	player,
+	currentlevel,
+	CASE
+		WHEN length > 0
+		AND length <= 5 THEN 'Beginner'
+		WHEN length > 5
+		AND length <= 12 THEN 'Intermediate'
+		WHEN length > 12 THEN 'Expert'
+	END ranking
+FROM
+	player_level
+ORDER BY
+	player;
+```
+
+**Returns**:
+
+player currentlevel ranking kennethpark 3 Beginner esimpson 8 Intermediate sabrina21 11 Intermediate rileyjon 15 Expert burchdenise 4 Beginner
+
+## [](#date-and-time-arithmetic)Date and time arithmetic
+
+Use the `INTERVAL` operator to add to or subtract from a period of time in `DATE`, `TIME`, or `TIMESTAMP` data types.
+
+### [](#syntax-2)Syntax
+
+```
+{ +|- } INTERVAL '<quantity> [ <date_unit> ] [ ...]'
+```
+
+Component Description `<quantity>` An integer. Multiple `<quantities>` and `<date_units>` can be used in the same `INTERVAL` command if they are separated by spaces. `<date_unit>` A date measurement including any of the following: `millennium`, `century`, `decade`, `year`, `month`, `week`, `day`, `hour`, `minute`, `second`, `millisecond`, `microsecond`or their plural forms. If unspecified, `<date_unit>` defaults to `second`.
+
+### [](#example-2)Example
+
+```
+<date_column> + INTERVAL '1 year 2 months 3 days'
+<date_column> - INTERVAL '2 weeks'
+<date_column> - INTERVAL '1 year 3 hours 20 minutes'
+```
+
+## [](#string)String
+
+To concatenate strings, you can use the `CONCAT` function.
+
+```
+SELECT concat('This', ' is', ' a', ' parenthetical', 'concantenation.') AS concatenated_String
+```
+
+Alternatively, you can use the double pipe `||` operator.
+
+```
+SELECT 'This' || ' is' || ' a' || ' double pipe' || ' concantenation.' AS concatenated_String
+```
+
+## [](#subquery-operators)Subquery operators
+
+Subqueries are queries nested within another query. They allow complex data retrieval by enabling a query to filter results based on the outcome of another query. Subquery operators are crucial in constructing these nested queries, especially within the WHERE clause, to filter data based on specific conditions.
+
+Operator Explanation `EXISTS` The `EXISTS` operator is used to check for the existence of any record in a subquery. It returns TRUE if the subquery returns one or more records. The subquery within EXISTS is executed repeatedly, once for each row that might be selected by the outer query. If the subquery returns any row, the EXISTS condition is met, and the outer query processing continues for that row. `NOT EXISTS` It is opposite of EXISTS and is used to find records in one table that have no related records in another table. If the subquery returns no rows, NOT EXISTS returns TRUE. `IN` The `IN` operator checks if a specific value is present in a list of values or the results of a subquery. Commonly utilized in a `WHERE` clause, it compares a column’s value against a predefined set. When the column’s value matches any value in this set, `IN` yields `TRUE`. `NOT IN` Retrieve all entries from the value list that don’t match the required value.
+
+### [](#exampleusing-exists-to-find-all-suppliers-with-products-equal-to-the-price-of-22)Example–using EXISTS to find all suppliers with products equal to the price of 22
+
+```
+SELECT supplier_name
+FROM suppliers
+WHERE EXISTS (
+  SELECT
+    product_name
+  FROM
+    products
+  WHERE
+    products.supplier_id = suppliers.supplier_id
+  AND
+    price = 22);
+```
+
+### [](#exampleusing-the-in-operator-to-return-all-customers-from-mannheim-or-london)Example–using the IN operator to return all customers from Mannheim or London
+
+```
+SELECT
+  customer_name
+FROM
+  customers
+WHERE
+  customer_address IN ('Mannheim','London');
+```
+
+### [](#exampleusing-a-correlated-subquery-to-retrieve-all-the-products-that-cost-more-than-the-avgerage-price)Example–using a correlated subquery to retrieve all the products that cost more than the avgerage price
+
+```
+SELECT
+  product_id,
+  product_name,
+  list_price
+FROM
+  products p
+WHERE
+  list_price > (
+    SELECT
+      AVG( list_price )
+    FROM
+      products
+    WHERE
+      category_id = p.category_id);
+```
+
+### [](#exampleusing-a-scalar-boolean-subquery-to-retrieve-rows-based-on-truefalse-condition)Example–using a scalar boolean subquery to retrieve rows based on true/false condition
+
+```
+SELECT
+  *
+FROM
+  products
+WHERE (
+  SELECT CASE WHEN
+    MIN(list_price) > 100
+  THEN
+    true
+  ELSE
+    false
+  END
+  FROM
+    products);
+```
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_timestampntz_data_type.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_timestampntz_data_type.md
new file mode 100644
index 0000000..3246d8b
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_timestampntz_data_type.md
@@ -0,0 +1,93 @@
+# [](#timestamp-data-type)TIMESTAMP data type
+
+This topic describes the Firebolt implementation of the `TIMESTAMP` data type.
+
+- [Overview](#overview)
+- [Literal string interpretation](#literal-string-interpretation)
+- [Functions and operators](#functions-and-operators)
+  
+  - [Type conversions](#type-conversions)
+  - [Comparison operators](#comparison-operators)
+  - [Arithmetic operators](#arithmetic-operators)
+- [Serialization and deserialization](#serialization-and-deserialization)
+
+## [](#overview)Overview
+
+Name Size Min Max Resolution `TIMESTAMP` 8 bytes `0001-01-01 00:00:00.000000` `9999-12-31 23:59:59.999999` 1 microsecond
+
+The `TIMESTAMP` data type represents a date and time with microsecond resolution independent of a time zone. To represent an absolute point in time, use [TIMESTAMPTZ](/sql_reference/timestamptz-data-type.html).
+
+## [](#literal-string-interpretation)Literal string interpretation
+
+`TIMESTAMP` literals follow the ISO 8601 and RFC 3339 format: `YYYY-[M]M-[D]D[( |T)[h]h:[m]m:[s]s[.f]]`.
+
+- `YYYY`: Four-digit year (`0001` - `9999`)
+- `[M]M`: One or two digit month (`01` - `12`)
+- `[D]D`: One or two digit day (`01` - `31`)
+- `( |T)`: A space or `T` separator
+- `[h]h`: One or two digit hour (`00` - `23`)
+- `[m]m`: One or two digit minute (`00` - `59`)
+- `[s]s`: One or two digit second (`00` - `59`)
+- `[.f]`: Up to six digits after the decimal separator (`000000` - `999999`)
+
+If only the date is specified, the time is assumed to be `00:00:00.000000`.
+
+**Examples**
+
+```
+SELECT TIMESTAMP '1996-09-03 11:19:33.123456';
+SELECT '2023-02-13'::TIMESTAMP;  --> 2023-02-13 00:00:00
+SELECT CAST('2019-7-23T16:9:3.1' as TIMESTAMP);  --> 2019-07-23 16:09:03.1
+```
+
+## [](#functions-and-operators)Functions and operators
+
+### [](#type-conversions)Type conversions
+
+The `TIMESTAMP` data type can be cast to and from types as follows:
+
+#### [](#to-timestamp)To TIMESTAMP
+
+From type Example Note `TEXT` `SELECT CAST(TEXT '2023-02-13 11:19:42' as TIMESTAMP); --> 2023-02-13 11:19:42` Interprets the text according to the literal string format. `DATE` `SELECT CAST(DATE '2023-02-13' as TIMESTAMP); --> 2023-02-13 00:00:00` Extends the date with `00:00:00`. `TIMESTAMPTZ` `SELECT CAST(TIMESTAMPTZ '2023-02-13 Europe/Berlin' as TIMESTAMP); --> 2023-02-13 22:00:00` Converts the timestamptz value to local time in the time zone specified by the [session’s `time_zone` setting](/Reference/system-settings.html#setting-the-time-zone). This example assumes `SET time_zone = 'UTC';`.
+
+#### [](#from-timestamp)From TIMESTAMP
+
+To type Example Note `TEXT` `SELECT CAST(TIMESTAMP '2023-02-13 11:19:42' as TEXT); --> 2023-02-13 11:19:42` Converts the timestamp to text in the format `YYYY-MM-DD hh:mm:ss[.f]`. `DATE` `SELECT CAST(TIMESTAMP '2023-02-13 11:19:42' as DATE); --> 2023-02-13` Truncates the timestamp to date. `TIMESTAMPTZ` `SELECT CAST(TIMESTAMP '2023-02-13 11:19:42' as TIMESTAMPTZ); --> 2023-02-13 11:19:42+00` Interprets the timestamp to be local time in the time zone specified by the [session’s `time_zone` setting](/Reference/system-settings.html#setting-the-time-zone). This example assumes `SET time_zone = 'UTC';`.
+
+### [](#comparison-operators)Comparison operators
+
+Operator Description `TIMESTAMP < TIMESTAMP` Less than `TIMESTAMP > TIMESTAMP` Greater than `TIMESTAMP <= TIMESTAMP` Less than or equal to `TIMESTAMP >= TIMESTAMP` Greater than or equal to `TIMESTAMP = TIMESTAMP` Equal to `TIMESTAMP <> TIMESTAMP` Not equal to
+
+A `TIMESTAMP` value is also comparable with a `DATE` or `TIMESTAMPTZ` value:
+
+- The `DATE` value is cast to the `TIMESTAMP` type for comparison with a `TIMESTAMP` value.
+- The `TIMESTAMP` value is cast to the `TIMESTAMPTZ` type for comparison with a `TIMESTAMPTZ` value.
+
+### [](#arithmetic-operators)Arithmetic operators
+
+Arithmetic with intervals can be used to add or subtract a duration to or from a timestamp. The result is of type `TIMESTAMP`.
+
+```
+SELECT TIMESTAMP '1996-09-03' + INTERVAL '42' YEAR;  --> 2038-09-03 00:00:00
+SELECT TIMESTAMP '2023-03-18' - INTERVAL '26 years 5 months 44 days 12 hours 41 minutes';  --> 1996-09-03 11:19:00
+```
+
+For more information, see [Arithmetic with intervals](/Reference/interval-arithmetic.html).
+
+## [](#serialization-and-deserialization)Serialization and deserialization
+
+### [](#text-csv-json)Text, CSV, JSON
+
+In the text, CSV, and JSON format, a `TIMESTAMP` value is output as a `YYYY-MM-DD hh:mm:ss[.f]` string. Firebolt outputs as few digits after the decimal separator as possible (at most six). Input is accepted in the literal format described above: `YYYY-[M]M-[D]D[( |T)[h]h:[m]m:[s]s[.f]]`.
+
+### [](#parquet)Parquet
+
+`TIMESTAMP` maps to Parquet’s 64-bit signed integer `TIMESTAMP` type with the parameter `isAdjustedToUTC` set to `false` and `unit` set to `MICROS`, also representing the number of microseconds before or after `1970-01-01 00:00:00.000000`.
+
+### [](#avro)Avro
+
+It’s not possible to import directly from Avro into a `TIMESTAMP` column. Instead, first import using a `TIMESTAMPTZ` column and then use the `AT TIME ZONE` expression to convert to `TIMESTAMP`.
+
+### [](#orc)ORC
+
+`TIMESTAMP` maps to ORC’s “timezone-unaware” logical type “timestamp”.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/fireboltdocs/sql_reference_timestamptz_data_type.md b/cmd/docs-scrapper/fireboltdocs/sql_reference_timestamptz_data_type.md
new file mode 100644
index 0000000..0fda6ad
--- /dev/null
+++ b/cmd/docs-scrapper/fireboltdocs/sql_reference_timestamptz_data_type.md
@@ -0,0 +1,160 @@
+# [](#timestamptz-data-type)TIMESTAMPTZ data type
+
+This topic describes the Firebolt implementation of the `TIMESTAMPTZ` data type.
+
+- [Overview](#overview)
+- [Literal string interpretation](#literal-string-interpretation)
+- [Daylight savings time transitions](#daylight-savings-time-transitions)
+- [Functions and operators](#functions-and-operators)
+  
+  - [Type conversions](#type-conversions)
+    
+    - [AT TIME ZONE](#at-time-zone)
+  - [Comparison operators](#comparison-operators)
+  - [Arithmetic operators](#arithmetic-operators)
+- [Serialization and deserialization](#serialization-and-deserialization)
+
+## [](#overview)Overview
+
+Name Size Min Max Resolution `TIMESTAMPTZ` 8 bytes `0001-01-01 00:00:00.000000 UTC` `9999-12-31 23:59:59.999999 UTC` 1 microsecond
+
+The `TIMESTAMPTZ` data type represents an absolute point in time as a date and time with microsecond resolution. Firebolt stores `TIMESTAMPTZ` values as [Unix time](https://en.wikipedia.org/wiki/Unix_time), which is UTC without leap seconds.
+
+### [](#difference-between-timestamptz-and-timestamp)Difference between TIMESTAMPTZ and TIMESTAMP
+
+With `TIMESTAMP`, the time zone is deliberately unspecified. For example, the start of the third millennium was celebrated on New Year’s Day at `TIMESTAMP '2001-01-01 00:00:00'`, independent of the geographical location. However, that doesn’t mean that everybody in the world celebrated at the same absolute point in time. In Munich, Germany, the new year was celebrated at `TIMESTAMPTZ '2001-01-01 00:00:00 Europe/Berlin'`, which was `TIMESTAMPTZ '2000-12-31 23:00:00 UTC'`. Seattle in the United States celebrated nine hours later at `TIMESTAMPTZ '2001-01-01 00:00:00 US/Pacific'`, which was `TIMESTAMPTZ '2001-01-01 08:00:00 UTC'`.
+
+## [](#literal-string-interpretation)Literal string interpretation
+
+`TIMESTAMPTZ` literals can be specified in one of three formats:
+
+1. `local_timestamp [time_zone]`
+2. `local_timestamp[time_zone_offset]`
+3. `local_timestamp[utc_time_zone]`
+
+<!--THE END-->
+
+- `local_timestamp` follows the ISO 8601 and RFC 3339 format: `YYYY-[M]M-[D]D[( |T)[h]h:[m]m:[s]s[.f]]`.
+  
+  - `YYYY`: Four-digit year (`0001` - `9999`)
+  - `[M]M`: One or two digit month (`01` - `12`)
+  - `[D]D`: One or two digit day (`01` - `31`)
+  - `( |T)`: A space or `T` separator
+  - `[h]h`: One or two digit hour (`00` - `23`)
+  - `[m]m`: One or two digit minutes (`00` - `59`)
+  - `[s]s`: One or two digit seconds (`00` - `59`)
+  - `[.f]`: Up to six digits after the decimal separator (`000000` - `999999`)
+- `time_zone` is a string containing the name of the time zone.
+- `time_zone_offset` is a string representing the offset from the UTC time zone.
+  
+  - Format: `(+|-)H[H][:m[m]]`.
+- `utc_time_zone`: The letter `Z` representing the UTC time zone.
+
+Time zone names are from the [tz database](http://www.iana.org/time-zones) (see the [list of tz database time zones](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones)). For times in the future, the latest known rule for the given time zone is applied. Firebolt does not support time zone abbreviations, as they cannot account for daylight savings time transitions, and some time zone abbreviations implied different UTC offsets at different times.
+
+If a `TIMESTAMPTZ` literal has an explicit time zone specified, it is converted to Unix time using the appropriate offset. If not, Firebolt uses the session’s `timezone` setting and assumes the `TIMESTAMPTZ` literal is in that time zone. The default value of the `timezone` setting is UTC. To set it to, e.g., `Europe/Berlin`, you can issue: `SET timezone = 'Europe/Berlin';`. For more information, see [system settings](/Reference/system-settings.html#setting-the-time-zone).
+
+If only the date is specified, the time is assumed to be `00:00:00.000000`.
+
+**Example**
+
+```
+SET timezone = 'UTC';
+SELECT TIMESTAMPTZ '1996-09-03 11:19:33.123456 Europe/Berlin';  --> 1996-09-03 09:19:33.123456+00
+SELECT TIMESTAMPTZ '2023-1-29 6:3:42.7-3:30';  --> 2023-01-29 09:33:42.7+00
+```
+
+## [](#daylight-savings-time-transitions)Daylight savings time transitions
+
+During a daylight savings time transition, a seemingly valid timestamp can represent a nonexistent or ambiguous timestamp. Firebolt resolves the problem by returning the later time point.
+
+### [](#spring-forward-transitions)“Spring forward” transitions
+
+```
+SET timezone = 'UTC';
+SELECT TIMESTAMPTZ '2022-03-27 01:59:59 Europe/Berlin';  --> 2022-03-27 00:59:59+00
+SELECT TIMESTAMPTZ '2022-03-27 02:00:00 Europe/Berlin';  --> 2022-03-27 01:00:00+00
+SELECT TIMESTAMPTZ '2022-03-27 03:00:00 Europe/Berlin';  --> 2022-03-27 01:00:00+00
+```
+
+### [](#fall-back-transitions)“Fall back” transitions
+
+```
+SET timezone = 'UTC';
+SELECT TIMESTAMPTZ '2022-10-30 01:59:59 Europe/Berlin';  --> 2022-10-29 23:59:59+00
+SELECT TIMESTAMPTZ '2022-10-30 02:00:00 Europe/Berlin';  --> 2022-10-30 01:00:00+00
+SELECT TIMESTAMPTZ '2022-10-30 03:00:00 Europe/Berlin';  --> 2022-10-30 02:00:00+00
+```
+
+## [](#functions-and-operators)Functions and operators
+
+### [](#type-conversions)Type conversions
+
+The `TIMESTAMPTZ` data type can be cast to and from types as follows:
+
+#### [](#to-timestamptz)To TIMESTAMPTZ
+
+From type Example Note `TEXT` `SELECT CAST(TEXT '2023-02-13 11:19:42 Europe/Berlin' as TIMESTAMPTZ); --> 2023-02-13 00:00:00+00` Interprets the text according to the literal string format. `DATE` `SELECT CAST(DATE '2023-02-13' as TIMESTAMPTZ); --> 2023-02-13 00:00:00+00` Interprets the timestamp to be midnight in the time zone specified by the session’s `timezone` setting. `TIMESTAMP` `SELECT CAST(TIMESTAMP '2023-02-13 11:19:42' as TIMESTAMPTZ); --> 2023-02-13 11:19:42+00` Interprets the timestamp to be local time in the time zone specified by the session’s `timezone` setting.
+
+#### [](#from-timestamptz)FROM TIMESTAMPTZ
+
+To type Example Note `TEXT` `SELECT CAST(TIMESTAMPTZ '2023-02-13 11:19:42 Europe/Berlin' as TEXT); --> 2023-02-13 10:19:42+00` Converts from Unix time to local time in the time zone specified by the session’s `timezone` setting and appends the UTC offset. `DATE` `SELECT CAST(TIMESTAMPTZ '2023-02-13 11:19:42 Europe/Berlin' as DATE); --> 2023-02-13` Converts from Unix time to local time in the time zone specified by the session’s `timezone` setting and then truncates the timestamp to the date. `TIMESTAMP` `SELECT CAST(TIMESTAMPTZ '2023-02-13 11:19:42 Europe/Berlin' as TIMESTAMP); --> 2023-02-13 10:19:42` Convert from Unix time to local time in the time zone specified by the session’s `timezone` setting.
+
+#### [](#at-time-zone)AT TIME ZONE
+
+The dependence on the session’s `timezone` setting for type conversions can be problematic for implicit conversions. Therefore, we recommend using the `AT TIME ZONE` construct to be explicit about which time zone to use.
+
+- `TIMESTAMP AT TIME ZONE time_zone_str -> TIMESTAMPTZ`  
+  Converts the given `TIMESTAMP` to `TIMESTAMPTZ` by interpreting it as local time in the time zone `time_zone_str`.
+
+**Example:** `SELECT TIMESTAMP '1996-09-03' at time zone 'Europe/Berlin' = TIMESTAMPTZ '1996-09-03 Europe/Berlin'; --> 1`
+
+- `TIMESTAMPTZ AT TIME ZONE time_zone_str -> TIMESTAMP`:  
+  Converts the given `TIMESTAMPTZ` to `TIMESTAMP` by transforming it from Unix time to local time in the time zone `time_zone_str`.
+
+**Example:** `SELECT TIMESTAMPTZ '1996-09-03 Europe/Berlin' AT TIME ZONE 'US/Pacific'; --> 1996-09-02 15:00:00`
+
+The `AT TIME ZONE` construct cannot be used with values of type `DATE`. However, you can explicitly cast a `DATE` value to `TIMESTAMP` and use the converted value instead.
+
+### [](#comparison-operators)Comparison operators
+
+Operator Description `TIMESTAMPTZ < TIMESTAMPTZ` Less than `TIMESTAMPTZ > TIMESTAMPTZ` Greater than `TIMESTAMPTZ <= TIMESTAMPTZ` Less than or equal to `TIMESTAMPTZ >= TIMESTAMPTZ` Greater than or equal to `TIMESTAMPTZ = TIMESTAMPTZ` Equal to `TIMESTAMPTZ <> TIMESTAMPTZ` Not equal to
+
+A `TIMESTAMPTZ` value is also comparable with a `DATE` or `TIMESTAMP` value:
+
+- The `DATE` value is converted to the `TIMESTAMPTZ` type for comparison with a `TIMESTAMPTZ` value.
+- The `TIMESTAMP` value is converted to the `TIMESTAMPTZ` type for comparison with a `TIMESTAMPTZ` value.
+
+### [](#arithmetic-operators)Arithmetic operators
+
+`TIMESTAMPTZ` values can be used for arithmetic with intervals:
+
+```
+SET timezone = 'Europe/Berlin';
+SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '1 day';  --> 2022-10-31 00:00:00+01
+SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '24' hour;  --> 2022-10-30 23:00:00+01
+
+SET timezone = 'US/Pacific';
+SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '1 day';  --> 2022-10-30 15:00:00-07
+SELECT TIMESTAMPTZ '2022-10-30 Europe/Berlin' + interval '24' hour;  --> 2022-10-30 15:00:00-07
+```
+
+For more information, see [Arithmetic with intervals](/Reference/interval-arithmetic.html).
+
+## [](#serialization-and-deserialization)Serialization and deserialization
+
+### [](#text-csv-json)Text, CSV, JSON
+
+In the text, CSV, and JSON format, a `TIMESTAMPTZ` value is shown as local time after conversion from Unix time using the time zone specified in the session’s `timezone` setting. Time zone information using the session’s `timezone` setting is shown as a signed numeric offset from UTC (`hh` if it is an integral number of hours, `hh:mm` if it is an integral number of minutes, else `hh:mm:ss`), with a positive sign for zones east of Greenwich. The date and time components are output as a `YYYY-MM-DD hh:mm:ss[.f]` string. Firebolt outputs as few digits after the decimal separator as possible (at most six). Input is accepted in one of the literal formats described above.
+
+### [](#parquet)Parquet
+
+`TIMESTAMPTZ` maps to Parquet’s 64-bit signed integer `TIMESTAMP` type with the parameter `isAdjustedToUTC` set to `true` and `unit` set to `MICROS`, representing the number of microseconds before or after `1970-01-01 00:00:00.000000 UTC`. It’s also possible to import into a `TIMESTAMPTZ` column from Parquet’s 64-bit signed integer `TIMESTAMP` type with the parameter `isAdjustedToUTC` set to `true` and the `unit` set to `MILLIS` or `NANOS`. In this case, Firebolt implicitly extends or truncates to resolve in microseconds.
+
+### [](#avro)Avro
+
+`TIMESTAMPTZ` maps to Avro’s 64-bit signed integer `timestamp-micros` type, representing the number of microseconds before or after `1970-01-01 00:00:00.000000 UTC`. It’s also possible to import into a `TIMESTAMPTZ` column from Avro’s `timestamp-millis` type.
+
+### [](#orc)ORC
+
+It’s not possible to import directly from ORC into a `TIMESTAMPTZ` column. ORC’s logical `TIMESTAMP` type is independent of a time zone and this would require a possibly unintended time zone conversion on import. Instead, first import using a `TIMESTAMP` column and then use the `AT TIME ZONE` expression to convert to `TIMESTAMPTZ`.
\ No newline at end of file
diff --git a/cmd/docs-scrapper/main.go b/cmd/docs-scrapper/main.go
new file mode 100644
index 0000000..5a2c096
--- /dev/null
+++ b/cmd/docs-scrapper/main.go
@@ -0,0 +1,39 @@
+package main
+
+import (
+	"context"
+	"fmt"
+	"log/slog"
+	"os"
+	"os/signal"
+	"syscall"
+)
+
+func main() {
+
+	ctx, cancel := signal.NotifyContext(context.Background(), syscall.SIGTERM, syscall.SIGINT)
+	defer cancel()
+
+	if err := run(ctx); err != nil {
+		println(err.Error())
+		os.Exit(1)
+	}
+}
+
+func run(ctx context.Context) error {
+
+	logger := slog.New(slog.NewTextHandler(os.Stderr, nil))
+	articles := Scrape(ctx, logger)
+
+	for article := range articles {
+		err := os.WriteFile(
+			fmt.Sprintf("./fireboltdocs/%s.md", article.ID),
+			[]byte(article.Content),
+			0644,
+		)
+		if err != nil {
+			logger.Error("Failed to write article", "id", article.ID, "error", err)
+		}
+	}
+	return nil
+}
diff --git a/cmd/docs-scrapper/scrapper.go b/cmd/docs-scrapper/scrapper.go
new file mode 100644
index 0000000..24b585b
--- /dev/null
+++ b/cmd/docs-scrapper/scrapper.go
@@ -0,0 +1,97 @@
+package main
+
+import (
+	"context"
+	"log/slog"
+	"strings"
+
+	htmltomarkdown "github.com/JohannesKaufmann/html-to-markdown/v2"
+	"github.com/gocolly/colly/v2"
+)
+
+type DocumentationArticle struct {
+	ID      string `json:"id"`
+	Content string `json:"content"`
+}
+
+func Scrape(ctx context.Context, logger *slog.Logger) <-chan DocumentationArticle {
+
+	const maxWorkers = 5
+
+	c := colly.NewCollector(
+		colly.Async(true),
+		colly.MaxDepth(2),
+	)
+	c.Context = ctx
+
+	err := c.Limit(&colly.LimitRule{
+		DomainGlob:  "*",
+		Parallelism: maxWorkers,
+	})
+	if err != nil {
+		logger.Error("Failed to set limit", "error", err)
+		return nil
+	}
+
+	results := make(chan DocumentationArticle, maxWorkers)
+
+	c.OnXML("//url/loc/text()", func(e *colly.XMLElement) {
+		if err := e.Request.Visit(e.Text); err != nil {
+			logger.Warn("Failed to visit URL", "url", e.Text, "error", err)
+		}
+	})
+
+	c.OnHTML("div#main-content main", func(e *colly.HTMLElement) {
+
+		clone := e.DOM.Clone()
+		clone.Find("div.query-window").Remove()
+		content, err := clone.Html()
+		if err != nil {
+			logger.Warn("Failed to find content", "error", err)
+			return
+		}
+		content, err = htmltomarkdown.ConvertString(
+			strings.TrimSpace(content),
+		)
+		if err != nil {
+			logger.Warn("Failed to convert content to markdown", "error", err)
+			return
+		}
+
+		results <- DocumentationArticle{
+			ID:      generateID(e.Request.URL.String()),
+			Content: content,
+		}
+	})
+
+	if err := c.Visit("https://docs.firebolt.io/sitemap.xml"); err != nil {
+		logger.Error("Failed to visit sitemap", "error", err)
+	}
+
+	go func() {
+		c.Wait()
+		close(results)
+	}()
+
+	c.OnError(func(response *colly.Response, err error) {
+		logger.Warn("Request failed", "url", response.Request.URL.String(), "error", err)
+	})
+
+	return results
+}
+
+func generateID(url string) string {
+
+	id := strings.TrimPrefix(url, "https://docs.firebolt.io/")
+	id = strings.TrimSuffix(id, ".html")
+	id = strings.TrimSuffix(id, "/")
+	id = strings.ReplaceAll(id, "/", "_")
+	id = strings.ReplaceAll(id, "-", "_")
+	id = strings.ToLower(id)
+
+	if id == "" {
+		return "index"
+	}
+
+	return id
+}
diff --git a/cmd/firebolt-mcp-server/main.go b/cmd/firebolt-mcp-server/main.go
new file mode 100644
index 0000000..9c19223
--- /dev/null
+++ b/cmd/firebolt-mcp-server/main.go
@@ -0,0 +1,159 @@
+package main
+
+import (
+	"context"
+	"fmt"
+	"log/slog"
+	"math/rand"
+	"os"
+	"os/signal"
+	"syscall"
+
+	"github.com/urfave/cli/v3"
+
+	"github.com/firebolt-db/mcp-server/cmd/docs-scrapper/fireboltdocs"
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+	"github.com/firebolt-db/mcp-server/pkg/clients/discovery"
+	"github.com/firebolt-db/mcp-server/pkg/prompts"
+	"github.com/firebolt-db/mcp-server/pkg/resources"
+	"github.com/firebolt-db/mcp-server/pkg/server"
+	"github.com/firebolt-db/mcp-server/pkg/tools"
+	"github.com/firebolt-db/mcp-server/pkg/version"
+)
+
+func main() {
+
+	ctx, cancel := signal.NotifyContext(context.Background(), syscall.SIGTERM, syscall.SIGINT)
+	defer cancel()
+
+	cmd := &cli.Command{
+		Name:    "firebolt-mcp-server",
+		Usage:   "Model Context Protocol implementation that connects your LLM to Firebolt",
+		Version: version.GetFullVersion(),
+		Authors: []any{"Firebolt Team"},
+		Description: "" +
+			"This MCP makes your LLM an expert in Firebolt cloud data warehouse with access to specialized tools and resources.\n" +
+			"It can assist with SQL queries, data modeling, performance optimization, and analytics for Firebolt.",
+		Flags: []cli.Flag{
+			&cli.StringFlag{
+				Name:     "transport",
+				Category: "MCP Transport",
+				Value:    "stdio",
+				Usage:    "Transport type (stdio or sse)",
+				Sources:  cli.EnvVars("FIREBOLT_MCP_TRANSPORT"),
+				Validator: func(s string) error {
+					if s != "stdio" && s != "sse" {
+						return fmt.Errorf("invalid transport type: %s, valid options: stdio, sse", s)
+					}
+					return nil
+				},
+			},
+			&cli.StringFlag{
+				Name:     "transport-sse-listen-address",
+				Category: "MCP Transport",
+				Value:    ":8080",
+				Usage:    "SSE transport listen address (used only if transport is set to sse)",
+				Sources:  cli.EnvVars("FIREBOLT_MCP_TRANSPORT_SSE_LISTEN_ADDRESS"),
+			},
+			&cli.StringFlag{
+				Name:     "client-id",
+				Category: "Firebolt Authentication",
+				Required: true,
+				Value:    "",
+				Usage:    "Service account client ID for authentication",
+				Sources:  cli.EnvVars("FIREBOLT_MCP_CLIENT_ID"),
+			},
+			&cli.StringFlag{
+				Name:     "client-secret",
+				Category: "Firebolt Authentication",
+				Required: true,
+				Value:    "",
+				Usage:    "Service account client secret for authentication",
+				Sources:  cli.EnvVars("FIREBOLT_MCP_CLIENT_SECRET"),
+			},
+			&cli.StringFlag{
+				Name:     "environment",
+				Category: "Firebolt Environment",
+				Hidden:   true,
+				Value:    "app.firebolt.io",
+				Usage:    "Firebolt environment to connect to",
+				Sources:  cli.EnvVars("FIREBOLT_MCP_ENVIRONMENT"),
+			},
+		},
+		Action: run,
+	}
+
+	if err := cmd.Run(ctx, os.Args); err != nil {
+		println(err.Error())
+		os.Exit(1)
+	}
+}
+
+func run(ctx context.Context, cmd *cli.Command) error {
+
+	// Initialize logger
+	logger := slog.New(slog.NewTextHandler(os.Stderr, nil))
+
+	// Connect to Firebolt
+	err := os.Setenv("FIREBOLT_ENDPOINT", fmt.Sprintf("https://api.%s", cmd.String("environment")))
+	if err != nil {
+		return fmt.Errorf("failed to set FIREBOLT_ENDPOINT environment variable: %w", err)
+	}
+	clientID := cmd.String("client-id")
+	clientSecret := cmd.String("client-secret")
+	dbPool, dbPoolClose := database.NewPool(logger, clientID, clientSecret)
+	defer dbPoolClose()
+	discoveryClient, err := discovery.NewClient(
+		ctx, logger,
+		clientID, clientSecret,
+		fmt.Sprintf("https://id.%s", cmd.String("environment")),
+		fmt.Sprintf("https://api.%s/web/v3", cmd.String("environment")),
+	)
+	if err != nil {
+		return fmt.Errorf("failed to create Firebolt discovery client: %w", err)
+	}
+
+	// Initialize MCP server
+	docsProof := generateRandomSecret()
+	resourceDocs := resources.NewDocs(fireboltdocs.FS, docsProof)
+	resourceAccounts := resources.NewAccounts(discoveryClient)
+	resourceDatabases := resources.NewDatabases(dbPool)
+	resourceEngines := resources.NewEngines(dbPool)
+	srv := server.NewServer(
+		logger,
+		cmd.String("transport"),
+		cmd.String("transport-sse-listen-address"),
+		[]server.Tool{
+			tools.NewConnect(resourceAccounts, resourceDatabases, resourceEngines, docsProof),
+			tools.NewDocs(resourceDocs),
+			tools.NewQuery(dbPool),
+		},
+		[]server.Prompt{
+			prompts.NewFireboltExpert(),
+		},
+		[]server.ResourceTemplate{
+			resourceDocs,
+			resourceAccounts,
+			resourceDatabases,
+			resourceEngines,
+		},
+	)
+
+	// Start the server
+	logger.Info("Welcome to Firebolt MCP Server!", "version", version.GetFullVersion())
+	if err = srv.Serve(ctx); err != nil {
+		return fmt.Errorf("failed to start server: %w", err)
+	}
+
+	return nil
+}
+
+// generateRandomSecret generates a random 32-character alphanumeric string.
+func generateRandomSecret() string {
+	const charset = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789"
+	b := make([]byte, 32)
+	for i := range b {
+		b[i] = charset[rand.Intn(len(charset))]
+	}
+	return string(b)
+}
diff --git a/go.mod b/go.mod
new file mode 100644
index 0000000..25d712b
--- /dev/null
+++ b/go.mod
@@ -0,0 +1,48 @@
+module github.com/firebolt-db/mcp-server
+
+go 1.24.1
+
+require (
+	github.com/JohannesKaufmann/html-to-markdown/v2 v2.3.1
+	github.com/firebolt-db/firebolt-go-sdk v1.6.2
+	github.com/gocolly/colly/v2 v2.2.0
+	github.com/mark3labs/mcp-go v0.17.0
+	github.com/neilotoole/slogt v1.1.0
+	github.com/pkg/errors v0.9.1
+	github.com/stretchr/testify v1.10.0
+	github.com/urfave/cli/v3 v3.1.1
+	golang.org/x/oauth2 v0.28.0
+	golang.org/x/sync v0.12.0
+)
+
+require (
+	github.com/JohannesKaufmann/dom v0.2.0 // indirect
+	github.com/PuerkitoBio/goquery v1.10.2 // indirect
+	github.com/andybalholm/cascadia v1.3.3 // indirect
+	github.com/antchfx/htmlquery v1.3.4 // indirect
+	github.com/antchfx/xmlquery v1.4.4 // indirect
+	github.com/antchfx/xpath v1.3.3 // indirect
+	github.com/astaxie/beego v1.12.3 // indirect
+	github.com/bits-and-blooms/bitset v1.22.0 // indirect
+	github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc // indirect
+	github.com/gobwas/glob v0.2.3 // indirect
+	github.com/golang/groupcache v0.0.0-20241129210726-2c02b8208cf8 // indirect
+	github.com/golang/protobuf v1.5.4 // indirect
+	github.com/google/go-cmp v0.7.0 // indirect
+	github.com/google/uuid v1.6.0 // indirect
+	github.com/kennygrant/sanitize v1.2.4 // indirect
+	github.com/matishsiao/goInfo v0.0.0-20210923090445-da2e3fa8d45f // indirect
+	github.com/nlnwa/whatwg-url v0.6.1 // indirect
+	github.com/pmezard/go-difflib v1.0.1-0.20181226105442-5d4384ee4fb2 // indirect
+	github.com/saintfish/chardet v0.0.0-20230101081208-5e3ef4b5456d // indirect
+	github.com/shopspring/decimal v1.4.0 // indirect
+	github.com/stretchr/objx v0.5.2 // indirect
+	github.com/temoto/robotstxt v1.1.2 // indirect
+	github.com/xwb1989/sqlparser v0.0.0-20180606152119-120387863bf2 // indirect
+	github.com/yosida95/uritemplate/v3 v3.0.2 // indirect
+	golang.org/x/net v0.37.0 // indirect
+	golang.org/x/text v0.23.0 // indirect
+	google.golang.org/appengine v1.6.8 // indirect
+	google.golang.org/protobuf v1.36.6 // indirect
+	gopkg.in/yaml.v3 v3.0.1 // indirect
+)
diff --git a/go.sum b/go.sum
new file mode 100644
index 0000000..7726391
--- /dev/null
+++ b/go.sum
@@ -0,0 +1,310 @@
+github.com/BurntSushi/toml v0.3.1/go.mod h1:xHWCNGjB5oqiDr8zfno3MHue2Ht5sIBksp03qcyfWMU=
+github.com/JohannesKaufmann/dom v0.2.0 h1:1bragmEb19K8lHAqgFgqCpiPCFEZMTXzOIEjuxkUfLQ=
+github.com/JohannesKaufmann/dom v0.2.0/go.mod h1:57iSUl5RKric4bUkgos4zu6Xt5LMHUnw3TF1l5CbGZo=
+github.com/JohannesKaufmann/html-to-markdown/v2 v2.3.1 h1:aCUWTMxMrxNr7IWnHiZK6Cn9/ebEAmEp5RfsLiGAFOM=
+github.com/JohannesKaufmann/html-to-markdown/v2 v2.3.1/go.mod h1:GELm/VaOL/CGXFPH32mw//nXiMNiEQgtMnLNr4QK/Y8=
+github.com/Knetic/govaluate v3.0.0+incompatible/go.mod h1:r7JcOSlj0wfOMncg0iLm8Leh48TZaKVeNIfJntJ2wa0=
+github.com/PuerkitoBio/goquery v1.10.2 h1:7fh2BdHcG6VFZsK7toXBT/Bh1z5Wmy8Q9MV9HqT2AM8=
+github.com/PuerkitoBio/goquery v1.10.2/go.mod h1:0guWGjcLu9AYC7C1GHnpysHy056u9aEkUHwhdnePMCU=
+github.com/alecthomas/template v0.0.0-20160405071501-a0175ee3bccc/go.mod h1:LOuyumcjzFXgccqObfd/Ljyb9UuFJ6TxHnclSeseNhc=
+github.com/alecthomas/template v0.0.0-20190718012654-fb15b899a751/go.mod h1:LOuyumcjzFXgccqObfd/Ljyb9UuFJ6TxHnclSeseNhc=
+github.com/alecthomas/units v0.0.0-20151022065526-2efee857e7cf/go.mod h1:ybxpYRFXyAe+OPACYpWeL0wqObRcbAqCMya13uyzqw0=
+github.com/alecthomas/units v0.0.0-20190717042225-c3de453c63f4/go.mod h1:ybxpYRFXyAe+OPACYpWeL0wqObRcbAqCMya13uyzqw0=
+github.com/alicebob/gopher-json v0.0.0-20180125190556-5a6b3ba71ee6/go.mod h1:SGnFV6hVsYE877CKEZ6tDNTjaSXYUk6QqoIK6PrAtcc=
+github.com/alicebob/miniredis v2.5.0+incompatible/go.mod h1:8HZjEj4yU0dwhYHky+DxYx+6BMjkBbe5ONFIF1MXffk=
+github.com/andybalholm/cascadia v1.3.3 h1:AG2YHrzJIm4BZ19iwJ/DAua6Btl3IwJX+VI4kktS1LM=
+github.com/andybalholm/cascadia v1.3.3/go.mod h1:xNd9bqTn98Ln4DwST8/nG+H0yuB8Hmgu1YHNnWw0GeA=
+github.com/antchfx/htmlquery v1.3.4 h1:Isd0srPkni2iNTWCwVj/72t7uCphFeor5Q8nCzj1jdQ=
+github.com/antchfx/htmlquery v1.3.4/go.mod h1:K9os0BwIEmLAvTqaNSua8tXLWRWZpocZIH73OzWQbwM=
+github.com/antchfx/xmlquery v1.4.4 h1:mxMEkdYP3pjKSftxss4nUHfjBhnMk4imGoR96FRY2dg=
+github.com/antchfx/xmlquery v1.4.4/go.mod h1:AEPEEPYE9GnA2mj5Ur2L5Q5/2PycJ0N9Fusrx9b12fc=
+github.com/antchfx/xpath v1.3.3 h1:tmuPQa1Uye0Ym1Zn65vxPgfltWb/Lxu2jeqIGteJSRs=
+github.com/antchfx/xpath v1.3.3/go.mod h1:i54GszH55fYfBmoZXapTHN8T8tkcHfRgLyVwwqzXNcs=
+github.com/astaxie/beego v1.12.3 h1:SAQkdD2ePye+v8Gn1r4X6IKZM1wd28EyUOVQ3PDSOOQ=
+github.com/astaxie/beego v1.12.3/go.mod h1:p3qIm0Ryx7zeBHLljmd7omloyca1s4yu1a8kM1FkpIA=
+github.com/beego/goyaml2 v0.0.0-20130207012346-5545475820dd/go.mod h1:1b+Y/CofkYwXMUU0OhQqGvsY2Bvgr4j6jfT699wyZKQ=
+github.com/beego/x2j v0.0.0-20131220205130-a0352aadc542/go.mod h1:kSeGC/p1AbBiEp5kat81+DSQrZenVBZXklMLaELspWU=
+github.com/beorn7/perks v0.0.0-20180321164747-3a771d992973/go.mod h1:Dwedo/Wpr24TaqPxmxbtue+5NUziq4I4S80YR8gNf3Q=
+github.com/beorn7/perks v1.0.0/go.mod h1:KWe93zE9D1o94FZ5RNwFwVgaQK1VOXiVxmqh+CedLV8=
+github.com/beorn7/perks v1.0.1/go.mod h1:G2ZrVWU2WbWT9wwq4/hrbKbnv/1ERSJQ0ibhJ6rlkpw=
+github.com/bits-and-blooms/bitset v1.20.0/go.mod h1:7hO7Gc7Pp1vODcmWvKMRA9BNmbv6a/7QIWpPxHddWR8=
+github.com/bits-and-blooms/bitset v1.22.0 h1:Tquv9S8+SGaS3EhyA+up3FXzmkhxPGjQQCkcs2uw7w4=
+github.com/bits-and-blooms/bitset v1.22.0/go.mod h1:7hO7Gc7Pp1vODcmWvKMRA9BNmbv6a/7QIWpPxHddWR8=
+github.com/bradfitz/gomemcache v0.0.0-20180710155616-bc664df96737/go.mod h1:PmM6Mmwb0LSuEubjR8N7PtNe1KxZLtOUHtbeikc5h60=
+github.com/casbin/casbin v1.7.0/go.mod h1:c67qKN6Oum3UF5Q1+BByfFxkwKvhwW57ITjqwtzR1KE=
+github.com/cespare/xxhash/v2 v2.1.1/go.mod h1:VGX0DQ3Q6kWi7AoAeZDth3/j3BFtOZR5XLFGgcrjCOs=
+github.com/cloudflare/golz4 v0.0.0-20150217214814-ef862a3cdc58/go.mod h1:EOBUe0h4xcZ5GoxqC5SDxFQ8gwyZPKQoEzownBlhI80=
+github.com/couchbase/go-couchbase v0.0.0-20200519150804-63f3cdb75e0d/go.mod h1:TWI8EKQMs5u5jLKW/tsb9VwauIrMIxQG1r5fMsswK5U=
+github.com/couchbase/gomemcached v0.0.0-20200526233749-ec430f949808/go.mod h1:srVSlQLB8iXBVXHgnqemxUXqN6FCvClgCMPCsjBDR7c=
+github.com/couchbase/goutils v0.0.0-20180530154633-e865a1461c8a/go.mod h1:BQwMFlJzDjFDG3DJUdU0KORxn88UlsOULuxLExMh3Hs=
+github.com/cupcake/rdb v0.0.0-20161107195141-43ba34106c76/go.mod h1:vYwsqCOLxGiisLwp9rITslkFNpZD5rz43tf41QFkTWY=
+github.com/davecgh/go-spew v1.1.0/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
+github.com/davecgh/go-spew v1.1.1/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
+github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc h1:U9qPSI2PIWSS1VwoXQT9A3Wy9MM3WgvqSxFWenqJduM=
+github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
+github.com/edsrzf/mmap-go v0.0.0-20170320065105-0bce6a688712/go.mod h1:YO35OhQPt3KJa3ryjFM5Bs14WD66h8eGKpfaBNrHW5M=
+github.com/elastic/go-elasticsearch/v6 v6.8.5/go.mod h1:UwaDJsD3rWLM5rKNFzv9hgox93HoX8utj1kxD9aFUcI=
+github.com/elazarl/go-bindata-assetfs v1.0.0/go.mod h1:v+YaWX3bdea5J/mo8dSETolEo7R71Vk1u8bnjau5yw4=
+github.com/firebolt-db/firebolt-go-sdk v1.6.2 h1:gq6Ob/q9TU4/mMqj3FzLndMIAZNHJSEYUfvgjIZ8kag=
+github.com/firebolt-db/firebolt-go-sdk v1.6.2/go.mod h1:jes3f/uon4qPDx94SM4cwnVZy1/Sld4ermfS9G+LY9k=
+github.com/fsnotify/fsnotify v1.4.7/go.mod h1:jwhsz4b93w/PPRr/qN1Yymfu8t87LnFCMoQvtojpjFo=
+github.com/glendc/gopher-json v0.0.0-20170414221815-dc4743023d0c/go.mod h1:Gja1A+xZ9BoviGJNA2E9vFkPjjsl+CoJxSXiQM1UXtw=
+github.com/go-kit/kit v0.8.0/go.mod h1:xBxKIO96dXMWWy0MnWVtmwkA9/13aqxPnvrjFYMA2as=
+github.com/go-kit/kit v0.9.0/go.mod h1:xBxKIO96dXMWWy0MnWVtmwkA9/13aqxPnvrjFYMA2as=
+github.com/go-logfmt/logfmt v0.3.0/go.mod h1:Qt1PoO58o5twSAckw1HlFXLmHsOX5/0LbT9GBnD5lWE=
+github.com/go-logfmt/logfmt v0.4.0/go.mod h1:3RMwSq7FuexP4Kalkev3ejPJsZTpXXBr9+V4qmtdjCk=
+github.com/go-redis/redis v6.14.2+incompatible/go.mod h1:NAIEuMOZ/fxfXJIrKDQDz8wamY7mA7PouImQ2Jvg6kA=
+github.com/go-sql-driver/mysql v1.5.0/go.mod h1:DCzpHaOWr8IXmIStZouvnhqoel9Qv2LBy8hT2VhHyBg=
+github.com/go-stack/stack v1.8.0/go.mod h1:v0f6uXyyMGvRgIKkXu+yp6POWl0qKG85gN/melR3HDY=
+github.com/gobwas/glob v0.2.3 h1:A4xDbljILXROh+kObIiy5kIaPYD8e96x1tgBhUI5J+Y=
+github.com/gobwas/glob v0.2.3/go.mod h1:d3Ez4x06l9bZtSvzIay5+Yzi0fmZzPgnTbPcKjJAkT8=
+github.com/gocolly/colly/v2 v2.2.0 h1:FQGxcqvTdFAvOpMRhk52o20Qsf6KtRU5HSf0bITS38I=
+github.com/gocolly/colly/v2 v2.2.0/go.mod h1:YOQwv1ofoQOzJiELnkThDd6ObOfl6odUk2i6Czbx3Ws=
+github.com/gogo/protobuf v1.1.1/go.mod h1:r8qH/GZQm5c6nD/R0oafs1akxWv10x8SbQlK7atdtwQ=
+github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da/go.mod h1:cIg4eruTrX1D+g88fzRXU5OdNfaM+9IcxsU14FzY7Hc=
+github.com/golang/groupcache v0.0.0-20241129210726-2c02b8208cf8 h1:f+oWsMOmNPc8JmEHVZIycC7hBoQxHH9pNKQORJNozsQ=
+github.com/golang/groupcache v0.0.0-20241129210726-2c02b8208cf8/go.mod h1:wcDNUvekVysuuOpQKo3191zZyTpiI6se1N1ULghS0sw=
+github.com/golang/protobuf v1.2.0/go.mod h1:6lQm79b+lXiMfvg/cZm0SGofjICqVBUtrP5yJMmIC1U=
+github.com/golang/protobuf v1.3.1/go.mod h1:6lQm79b+lXiMfvg/cZm0SGofjICqVBUtrP5yJMmIC1U=
+github.com/golang/protobuf v1.3.2/go.mod h1:6lQm79b+lXiMfvg/cZm0SGofjICqVBUtrP5yJMmIC1U=
+github.com/golang/protobuf v1.4.0-rc.1/go.mod h1:ceaxUfeHdC40wWswd/P6IGgMaK3YpKi5j83Wpe3EHw8=
+github.com/golang/protobuf v1.4.0-rc.1.0.20200221234624-67d41d38c208/go.mod h1:xKAWHe0F5eneWXFV3EuXVDTCmh+JuBKY0li0aMyXATA=
+github.com/golang/protobuf v1.4.0-rc.2/go.mod h1:LlEzMj4AhA7rCAGe4KMBDvJI+AwstrUpVNzEA03Pprs=
+github.com/golang/protobuf v1.4.0-rc.4.0.20200313231945-b860323f09d0/go.mod h1:WU3c8KckQ9AFe+yFwt9sWVRKCVIyN9cPHBJSNnbL67w=
+github.com/golang/protobuf v1.4.0/go.mod h1:jodUvKwWbYaEsadDk5Fwe5c77LiNKVO9IDvqG2KuDX0=
+github.com/golang/protobuf v1.4.2/go.mod h1:oDoupMAO8OvCJWAcko0GGGIgR6R6ocIYbsSw735rRwI=
+github.com/golang/protobuf v1.5.0/go.mod h1:FsONVRAS9T7sI+LIUmWTfcYkHO4aIWwzhcaSAoJOfIk=
+github.com/golang/protobuf v1.5.2/go.mod h1:XVQd3VNwM+JqD3oG2Ue2ip4fOMUkwXdXDdiuN0vRsmY=
+github.com/golang/protobuf v1.5.4 h1:i7eJL8qZTpSEXOPTxNKhASYpMn+8e5Q6AdndVa1dWek=
+github.com/golang/protobuf v1.5.4/go.mod h1:lnTiLA8Wa4RWRcIUkrtSVa5nRhsEGBg48fD6rSs7xps=
+github.com/golang/snappy v0.0.0-20170215233205-553a64147049/go.mod h1:/XxbfmMg8lxefKM7IXC3fBNl/7bRcc72aCRzEWrmP2Q=
+github.com/golang/snappy v0.0.0-20180518054509-2e65f85255db/go.mod h1:/XxbfmMg8lxefKM7IXC3fBNl/7bRcc72aCRzEWrmP2Q=
+github.com/gomodule/redigo v2.0.0+incompatible/go.mod h1:B4C85qUVwatsJoIUNIfCRsp7qO0iAmpGFZ4EELWSbC4=
+github.com/google/go-cmp v0.3.0/go.mod h1:8QqcDgzrUqlUb/G2PQTWiueGozuR1884gddMywk6iLU=
+github.com/google/go-cmp v0.3.1/go.mod h1:8QqcDgzrUqlUb/G2PQTWiueGozuR1884gddMywk6iLU=
+github.com/google/go-cmp v0.4.0/go.mod h1:v8dTdLbMG2kIc/vJvl+f65V22dbkXbowE6jgT/gNBxE=
+github.com/google/go-cmp v0.5.5/go.mod h1:v8dTdLbMG2kIc/vJvl+f65V22dbkXbowE6jgT/gNBxE=
+github.com/google/go-cmp v0.6.0/go.mod h1:17dUlkBOakJ0+DkrSSNjCkIjxS6bF9zb3elmeNGIjoY=
+github.com/google/go-cmp v0.7.0 h1:wk8382ETsv4JYUZwIsn6YpYiWiBsYLSJiTsyBybVuN8=
+github.com/google/go-cmp v0.7.0/go.mod h1:pXiqmnSA92OHEEa9HXL2W4E7lf9JzCmGVUdgjX3N/iU=
+github.com/google/gofuzz v1.0.0/go.mod h1:dBl0BpW6vV/+mYPU4Po3pmUjxk6FQPldtuIdl/M65Eg=
+github.com/google/uuid v1.6.0 h1:NIvaJDMOsjHA8n1jAhLSgzrAzy1Hgr+hNrb57e+94F0=
+github.com/google/uuid v1.6.0/go.mod h1:TIyPZe4MgqvfeYDBFedMoGGpEw/LqOeaOT+nhxU+yHo=
+github.com/hashicorp/golang-lru v0.5.4/go.mod h1:iADmTwqILo4mZ8BN3D2Q6+9jd8WM5uGBxy+E8yxSoD4=
+github.com/hpcloud/tail v1.0.0/go.mod h1:ab1qPbhIpdTxEkNHXyeSf5vhxWSCs/tWer42PpOxQnU=
+github.com/json-iterator/go v1.1.6/go.mod h1:+SdeFBvtyEkXs7REEP0seUULqWtbJapLOCVDaaPEHmU=
+github.com/json-iterator/go v1.1.10/go.mod h1:KdQUCv79m/52Kvf8AW2vK1V8akMuk1QjK/uOdHXbAo4=
+github.com/julienschmidt/httprouter v1.2.0/go.mod h1:SYymIcj16QtmaHHD7aYtjjsJG7VTCxuUUipMqKk8s4w=
+github.com/kennygrant/sanitize v1.2.4 h1:gN25/otpP5vAsO2djbMhF/LQX6R7+O1TB4yv8NzpJ3o=
+github.com/kennygrant/sanitize v1.2.4/go.mod h1:LGsjYYtgxbetdg5owWB2mpgUL6e2nfw2eObZ0u0qvak=
+github.com/konsorten/go-windows-terminal-sequences v1.0.1/go.mod h1:T0+1ngSBFLxvqU3pZ+m/2kptfBszLMUkC4ZK/EgS/cQ=
+github.com/kr/logfmt v0.0.0-20140226030751-b84e30acd515/go.mod h1:+0opPa2QZZtGFBFZlji/RkVcI2GknAs/DXo4wKdlNEc=
+github.com/kr/pretty v0.1.0/go.mod h1:dAy3ld7l9f0ibDNOQOHHMYYIIbhfbHSm3C4ZsoJORNo=
+github.com/kr/pty v1.1.1/go.mod h1:pFQYn66WHrOpPYNljwOMqo10TkYh1fy3cYio2l3bCsQ=
+github.com/kr/text v0.1.0 h1:45sCR5RtlFHMR4UwH9sdQ5TC8v0qDQCHnXt+kaKSTVE=
+github.com/kr/text v0.1.0/go.mod h1:4Jbv+DJW3UT/LiOwJeYQe1efqtUx/iVham/4vfdArNI=
+github.com/ledisdb/ledisdb v0.0.0-20200510135210-d35789ec47e6/go.mod h1:n931TsDuKuq+uX4v1fulaMbA/7ZLLhjc85h7chZGBCQ=
+github.com/lib/pq v1.0.0/go.mod h1:5WUZQaWbwv1U+lTReE5YruASi9Al49XbQIvNi/34Woo=
+github.com/mark3labs/mcp-go v0.17.0 h1:5Ps6T7qXr7De/2QTqs9h6BKeZ/qdeUeGrgM5lPzi930=
+github.com/mark3labs/mcp-go v0.17.0/go.mod h1:KmJndYv7GIgcPVwEKJjNcbhVQ+hJGJhrCCB/9xITzpE=
+github.com/matishsiao/goInfo v0.0.0-20210923090445-da2e3fa8d45f h1:B0OD7nYl2FPQEVrw8g2uyc1lGEzNbvrKh7fspGZcbvY=
+github.com/matishsiao/goInfo v0.0.0-20210923090445-da2e3fa8d45f/go.mod h1:aEt7p9Rvh67BYApmZwNDPpgircTO2kgdmDUoF/1QmwA=
+github.com/mattn/go-sqlite3 v2.0.3+incompatible/go.mod h1:FPy6KqzDD04eiIsT53CuJW3U88zkxoIYsOqkbpncsNc=
+github.com/matttproud/golang_protobuf_extensions v1.0.1/go.mod h1:D8He9yQNgCq6Z5Ld7szi9bcBfOoFv/3dc6xSMkL2PC0=
+github.com/modern-go/concurrent v0.0.0-20180228061459-e0a39a4cb421/go.mod h1:6dJC0mAP4ikYIbvyc7fijjWJddQyLn8Ig3JB5CqoB9Q=
+github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd/go.mod h1:6dJC0mAP4ikYIbvyc7fijjWJddQyLn8Ig3JB5CqoB9Q=
+github.com/modern-go/reflect2 v0.0.0-20180701023420-4b7aa43c6742/go.mod h1:bx2lNnkwVCuqBIxFjflWJWanXIb3RllmbCylyMrvgv0=
+github.com/modern-go/reflect2 v1.0.1/go.mod h1:bx2lNnkwVCuqBIxFjflWJWanXIb3RllmbCylyMrvgv0=
+github.com/mwitkow/go-conntrack v0.0.0-20161129095857-cc309e4a2223/go.mod h1:qRWi+5nqEBWmkhHvq77mSJWrCKwh8bxhgT7d/eI7P4U=
+github.com/neilotoole/slogt v1.1.0 h1:c7qE92sq+V0yvCuaxph+RQ2jOKL61c4hqS1Bv9W7FZE=
+github.com/neilotoole/slogt v1.1.0/go.mod h1:RCrGXkPc/hYybNulqQrMHRtvlQ7F6NktNVLuLwk6V+w=
+github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e h1:fD57ERR4JtEqsWbfPhv4DMiApHyliiK5xCTNVSPiaAs=
+github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e/go.mod h1:zD1mROLANZcx1PVRCS0qkT7pwLkGfwJo4zjcN/Tysno=
+github.com/nlnwa/whatwg-url v0.6.1 h1:Zlefa3aglQFHF/jku45VxbEJwPicDnOz64Ra3F7npqQ=
+github.com/nlnwa/whatwg-url v0.6.1/go.mod h1:x0FPXJzzOEieQtsBT/AKvbiBbQ46YlL6Xa7m02M1ECk=
+github.com/onsi/ginkgo v1.6.0/go.mod h1:lLunBs/Ym6LB5Z9jYTR76FiuTmxDTDusOGeTQH+WWjE=
+github.com/onsi/ginkgo v1.12.0/go.mod h1:oUhWkIvk5aDxtKvDDuw8gItl8pKl42LzjC9KZE0HfGg=
+github.com/onsi/gomega v1.7.1/go.mod h1:XdKZgCCFLUoM/7CFJVPcG8C1xQ1AJ0vpAezJrB7JYyY=
+github.com/pelletier/go-toml v1.0.1/go.mod h1:5z9KED0ma1S8pY6P1sdut58dfprrGBbd/94hg7ilaic=
+github.com/pelletier/go-toml v1.2.0/go.mod h1:5z9KED0ma1S8pY6P1sdut58dfprrGBbd/94hg7ilaic=
+github.com/peterh/liner v1.0.1-0.20171122030339-3681c2a91233/go.mod h1:xIteQHvHuaLYG9IFj6mSxM0fCKrs34IrEQUhOYuGPHc=
+github.com/pkg/errors v0.8.0/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0=
+github.com/pkg/errors v0.8.1/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0=
+github.com/pkg/errors v0.9.1 h1:FEBLx1zS214owpjy7qsBeixbURkuhQAwrK5UwLGTwt4=
+github.com/pkg/errors v0.9.1/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0=
+github.com/pmezard/go-difflib v1.0.0/go.mod h1:iKH77koFhYxTK1pcRnkKkqfTogsbg7gZNVY4sRDYZ/4=
+github.com/pmezard/go-difflib v1.0.1-0.20181226105442-5d4384ee4fb2 h1:Jamvg5psRIccs7FGNTlIRMkT8wgtp5eCXdBlqhYGL6U=
+github.com/pmezard/go-difflib v1.0.1-0.20181226105442-5d4384ee4fb2/go.mod h1:iKH77koFhYxTK1pcRnkKkqfTogsbg7gZNVY4sRDYZ/4=
+github.com/prometheus/client_golang v0.9.1/go.mod h1:7SWBe2y4D6OKWSNQJUaRYU/AaXPKyh/dDVn+NZz0KFw=
+github.com/prometheus/client_golang v1.0.0/go.mod h1:db9x61etRT2tGnBNRi70OPL5FsnadC4Ky3P0J6CfImo=
+github.com/prometheus/client_golang v1.7.0/go.mod h1:PY5Wy2awLA44sXw4AOSfFBetzPP4j5+D6mVACh+pe2M=
+github.com/prometheus/client_model v0.0.0-20180712105110-5c3871d89910/go.mod h1:MbSGuTsp3dbXC40dX6PRTWyKYBIrTGTE9sqQNg2J8bo=
+github.com/prometheus/client_model v0.0.0-20190129233127-fd36f4220a90/go.mod h1:xMI15A0UPsDsEKsMN9yxemIoYk6Tm2C1GtYGdfGttqA=
+github.com/prometheus/client_model v0.2.0/go.mod h1:xMI15A0UPsDsEKsMN9yxemIoYk6Tm2C1GtYGdfGttqA=
+github.com/prometheus/common v0.4.1/go.mod h1:TNfzLD0ON7rHzMJeJkieUDPYmFC7Snx/y86RQel1bk4=
+github.com/prometheus/common v0.10.0/go.mod h1:Tlit/dnDKsSWFlCLTWaA1cyBgKHSMdTB80sz/V91rCo=
+github.com/prometheus/procfs v0.0.0-20181005140218-185b4288413d/go.mod h1:c3At6R/oaqEKCNdg8wHV1ftS6bRYblBhIjjI8uT2IGk=
+github.com/prometheus/procfs v0.0.2/go.mod h1:TjEm7ze935MbeOT/UhFTIMYKhuLP4wbCsTZCD3I8kEA=
+github.com/prometheus/procfs v0.1.3/go.mod h1:lV6e/gmhEcM9IjHGsFOCxxuZ+z1YqCvr4OA4YeYWdaU=
+github.com/saintfish/chardet v0.0.0-20230101081208-5e3ef4b5456d h1:hrujxIzL1woJ7AwssoOcM/tq5JjjG2yYOc8odClEiXA=
+github.com/saintfish/chardet v0.0.0-20230101081208-5e3ef4b5456d/go.mod h1:uugorj2VCxiV1x+LzaIdVa9b4S4qGAcH6cbhh4qVxOU=
+github.com/sebdah/goldie/v2 v2.5.5 h1:rx1mwF95RxZ3/83sdS4Yp7t2C5TCokvWP4TBRbAyEWY=
+github.com/sebdah/goldie/v2 v2.5.5/go.mod h1:oZ9fp0+se1eapSRjfYbsV/0Hqhbuu3bJVvKI/NNtssI=
+github.com/sergi/go-diff v1.3.1 h1:xkr+Oxo4BOQKmkn/B9eMK0g5Kg/983T9DqqPHwYqD+8=
+github.com/sergi/go-diff v1.3.1/go.mod h1:aMJSSKb2lpPvRNec0+w3fl7LP9IOFzdc9Pa4NFbPK1I=
+github.com/shiena/ansicolor v0.0.0-20151119151921-a422bbe96644/go.mod h1:nkxAfR/5quYxwPZhyDxgasBMnRtBZd0FCEpawpjMUFg=
+github.com/shopspring/decimal v1.4.0 h1:bxl37RwXBklmTi0C79JfXCEBD1cqqHt0bbgBAGFp81k=
+github.com/shopspring/decimal v1.4.0/go.mod h1:gawqmDU56v4yIKSwfBSFip1HdCCXN8/+DMd9qYNcwME=
+github.com/siddontang/go v0.0.0-20170517070808-cb568a3e5cc0/go.mod h1:3yhqj7WBBfRhbBlzyOC3gUxftwsU0u8gqevxwIHQpMw=
+github.com/siddontang/goredis v0.0.0-20150324035039-760763f78400/go.mod h1:DDcKzU3qCuvj/tPnimWSsZZzvk9qvkvrIL5naVBPh5s=
+github.com/siddontang/rdb v0.0.0-20150307021120-fc89ed2e418d/go.mod h1:AMEsy7v5z92TR1JKMkLLoaOQk++LVnOKL3ScbJ8GNGA=
+github.com/sirupsen/logrus v1.2.0/go.mod h1:LxeOpSwHxABJmUn/MG1IvRgCAasNZTLOkJPxbbu5VWo=
+github.com/sirupsen/logrus v1.4.2/go.mod h1:tLMulIdttU9McNUspp0xgXVQah82FyeX6MwdIuYE2rE=
+github.com/ssdb/gossdb v0.0.0-20180723034631-88f6b59b84ec/go.mod h1:QBvMkMya+gXctz3kmljlUCu/yB3GZ6oee+dUozsezQE=
+github.com/stretchr/objx v0.1.0/go.mod h1:HFkY916IF+rwdDfMAkV7OtwuqBVzrE8GR6GFx+wExME=
+github.com/stretchr/objx v0.1.1/go.mod h1:HFkY916IF+rwdDfMAkV7OtwuqBVzrE8GR6GFx+wExME=
+github.com/stretchr/objx v0.5.2 h1:xuMeJ0Sdp5ZMRXx/aWO6RZxdr3beISkG5/G/aIRr3pY=
+github.com/stretchr/objx v0.5.2/go.mod h1:FRsXN1f5AsAjCGJKqEizvkpNtU+EGNCLh3NxZ/8L+MA=
+github.com/stretchr/testify v1.2.2/go.mod h1:a8OnRcib4nhh0OaRAV+Yts87kKdq0PP7pXfy6kDkUVs=
+github.com/stretchr/testify v1.3.0/go.mod h1:M5WIy9Dh21IEIfnGCwXGc5bZfKNJtfHm1UVUgZn+9EI=
+github.com/stretchr/testify v1.4.0/go.mod h1:j7eGeouHqKxXV5pUuKE4zz7dFj8WfuZ+81PSLYec5m4=
+github.com/stretchr/testify v1.10.0 h1:Xv5erBjTwe/5IxqUQTdXv5kgmIvbHo3QQyRwhJsOfJA=
+github.com/stretchr/testify v1.10.0/go.mod h1:r2ic/lqez/lEtzL7wO/rwa5dbSLXVDPFyf8C91i36aY=
+github.com/syndtr/goleveldb v0.0.0-20160425020131-cfa635847112/go.mod h1:Z4AUp2Km+PwemOoO/VB5AOx9XSsIItzFjoJlOSiYmn0=
+github.com/syndtr/goleveldb v0.0.0-20181127023241-353a9fca669c/go.mod h1:Z4AUp2Km+PwemOoO/VB5AOx9XSsIItzFjoJlOSiYmn0=
+github.com/temoto/robotstxt v1.1.2 h1:W2pOjSJ6SWvldyEuiFXNxz3xZ8aiWX5LbfDiOFd7Fxg=
+github.com/temoto/robotstxt v1.1.2/go.mod h1:+1AmkuG3IYkh1kv0d2qEB9Le88ehNO0zwOr3ujewlOo=
+github.com/ugorji/go v0.0.0-20171122102828-84cb69a8af83/go.mod h1:hnLbHMwcvSihnDhEfx2/BzKp2xb0Y+ErdfYcrs9tkJQ=
+github.com/urfave/cli/v3 v3.1.1 h1:bNnl8pFI5dxPOjeONvFCDFoECLQsceDG4ejahs4Jtxk=
+github.com/urfave/cli/v3 v3.1.1/go.mod h1:FJSKtM/9AiiTOJL4fJ6TbMUkxBXn7GO9guZqoZtpYpo=
+github.com/wendal/errors v0.0.0-20130201093226-f66c77a7882b/go.mod h1:Q12BUT7DqIlHRmgv3RskH+UCM/4eqVMgI0EMmlSpAXc=
+github.com/xwb1989/sqlparser v0.0.0-20180606152119-120387863bf2 h1:zzrxE1FKn5ryBNl9eKOeqQ58Y/Qpo3Q9QNxKHX5uzzQ=
+github.com/xwb1989/sqlparser v0.0.0-20180606152119-120387863bf2/go.mod h1:hzfGeIUDq/j97IG+FhNqkowIyEcD88LrW6fyU3K3WqY=
+github.com/yosida95/uritemplate/v3 v3.0.2 h1:Ed3Oyj9yrmi9087+NczuL5BwkIc4wvTb5zIM+UJPGz4=
+github.com/yosida95/uritemplate/v3 v3.0.2/go.mod h1:ILOh0sOhIJR3+L/8afwt/kE++YT040gmv5BQTMR2HP4=
+github.com/yuin/goldmark v1.4.13/go.mod h1:6yULJ656Px+3vBD8DxQVa3kxgyrAnzto9xy5taEt/CY=
+github.com/yuin/goldmark v1.7.8 h1:iERMLn0/QJeHFhxSt3p6PeN9mGnvIKSpG9YYorDMnic=
+github.com/yuin/goldmark v1.7.8/go.mod h1:uzxRWxtg69N339t3louHJ7+O03ezfj6PlliRlaOzY1E=
+github.com/yuin/gopher-lua v0.0.0-20171031051903-609c9cd26973/go.mod h1:aEV29XrmTYFr3CiRxZeGHpkvbwq+prZduBqMaascyCU=
+golang.org/x/crypto v0.0.0-20180904163835-0709b304e793/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
+golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
+golang.org/x/crypto v0.0.0-20191011191535-87dc89f01550/go.mod h1:yigFU9vqHzYiE8UmvKecakEJjdnWj3jj499lnFckfCI=
+golang.org/x/crypto v0.0.0-20210921155107-089bfa567519/go.mod h1:GvvjBRRGRdwPK5ydBHafDWAxML/pGHZbMvKqRZ5+Abc=
+golang.org/x/crypto v0.13.0/go.mod h1:y6Z2r+Rw4iayiXXAIxJIDAJ1zMW4yaTpebo8fPOliYc=
+golang.org/x/crypto v0.19.0/go.mod h1:Iy9bg/ha4yyC70EfRS8jz+B6ybOBKMaSxLj6P6oBDfU=
+golang.org/x/crypto v0.23.0/go.mod h1:CKFgDieR+mRhux2Lsu27y0fO304Db0wZe70UKqHu0v8=
+golang.org/x/crypto v0.31.0/go.mod h1:kDsLvtWBEx7MV9tJOj9bnXsPbxwJQ6csT/x4KIN4Ssk=
+golang.org/x/crypto v0.32.0/go.mod h1:ZnnJkOaASj8g0AjIduWNlq2NRxL0PlBrbKVyZ6V/Ugc=
+golang.org/x/mod v0.6.0-dev.0.20220419223038-86c51ed26bb4/go.mod h1:jJ57K6gSWd91VN4djpZkiMVwK6gcyfeH4XE8wZrZaV4=
+golang.org/x/mod v0.8.0/go.mod h1:iBbtSCu2XBx23ZKBPSOrRkjjQPZFPuis4dIYUhu/chs=
+golang.org/x/mod v0.12.0/go.mod h1:iBbtSCu2XBx23ZKBPSOrRkjjQPZFPuis4dIYUhu/chs=
+golang.org/x/mod v0.15.0/go.mod h1:hTbmBsO62+eylJbnUtE2MGJUyE7QWk4xUqPFrRgJ+7c=
+golang.org/x/mod v0.17.0/go.mod h1:hTbmBsO62+eylJbnUtE2MGJUyE7QWk4xUqPFrRgJ+7c=
+golang.org/x/net v0.0.0-20180906233101-161cd47e91fd/go.mod h1:mL1N/T3taQHkDXs73rZJwtUhF3w3ftmwwsq0BUmARs4=
+golang.org/x/net v0.0.0-20181114220301-adae6a3d119a/go.mod h1:mL1N/T3taQHkDXs73rZJwtUhF3w3ftmwwsq0BUmARs4=
+golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
+golang.org/x/net v0.0.0-20190613194153-d28f0bde5980/go.mod h1:z5CRVTTTmAJ677TzLLGU+0bjPO0LkuOLi4/5GtJWs/s=
+golang.org/x/net v0.0.0-20190620200207-3b0461eec859/go.mod h1:z5CRVTTTmAJ677TzLLGU+0bjPO0LkuOLi4/5GtJWs/s=
+golang.org/x/net v0.0.0-20210226172049-e18ecbb05110/go.mod h1:m0MpNAwzfU5UDzcl9v0D8zg8gWTRqZa9RBIspLL5mdg=
+golang.org/x/net v0.0.0-20220722155237-a158d28d115b/go.mod h1:XRhObCWvk6IyKnWLug+ECip1KBveYUHfp+8e9klMJ9c=
+golang.org/x/net v0.6.0/go.mod h1:2Tu9+aMcznHK/AK1HMvgo6xiTLG5rD5rZLDS+rp2Bjs=
+golang.org/x/net v0.10.0/go.mod h1:0qNGK6F8kojg2nk9dLZ2mShWaEBan6FAoqfSigmmuDg=
+golang.org/x/net v0.15.0/go.mod h1:idbUs1IY1+zTqbi8yxTbhexhEEk5ur9LInksu6HrEpk=
+golang.org/x/net v0.21.0/go.mod h1:bIjVDfnllIU7BJ2DNgfnXvpSvtn8VRwhlsaeUTyUS44=
+golang.org/x/net v0.25.0/go.mod h1:JkAGAh7GEvH74S6FOH42FLoXpXbE/aqXSrIQjXgsiwM=
+golang.org/x/net v0.33.0/go.mod h1:HXLR5J+9DxmrqMwG9qjGCxZ+zKXxBru04zlTvWlWuN4=
+golang.org/x/net v0.34.0/go.mod h1:di0qlW3YNM5oh6GqDGQr92MyTozJPmybPK4Ev/Gm31k=
+golang.org/x/net v0.37.0 h1:1zLorHbz+LYj7MQlSf1+2tPIIgibq2eL5xkrGk6f+2c=
+golang.org/x/net v0.37.0/go.mod h1:ivrbrMbzFq5J41QOQh0siUuly180yBYtLp+CKbEaFx8=
+golang.org/x/oauth2 v0.28.0 h1:CrgCKl8PPAVtLnU3c+EDw6x11699EWlsDeWNWKdIOkc=
+golang.org/x/oauth2 v0.28.0/go.mod h1:onh5ek6nERTohokkhCD/y2cV4Do3fxFHFuAejCkRWT8=
+golang.org/x/sync v0.0.0-20180314180146-1d60e4601c6f/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
+golang.org/x/sync v0.0.0-20181108010431-42b317875d0f/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
+golang.org/x/sync v0.0.0-20181221193216-37e7f081c4d4/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
+golang.org/x/sync v0.0.0-20190423024810-112230192c58/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
+golang.org/x/sync v0.0.0-20190911185100-cd5d95a43a6e/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
+golang.org/x/sync v0.0.0-20220722155255-886fb9371eb4/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
+golang.org/x/sync v0.1.0/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
+golang.org/x/sync v0.3.0/go.mod h1:FU7BRWz2tNW+3quACPkgCx/L+uEAv1htQ0V83Z9Rj+Y=
+golang.org/x/sync v0.6.0/go.mod h1:Czt+wKu1gCyEFDUtn0jG5QVvpJ6rzVqr5aXyt9drQfk=
+golang.org/x/sync v0.7.0/go.mod h1:Czt+wKu1gCyEFDUtn0jG5QVvpJ6rzVqr5aXyt9drQfk=
+golang.org/x/sync v0.10.0/go.mod h1:Czt+wKu1gCyEFDUtn0jG5QVvpJ6rzVqr5aXyt9drQfk=
+golang.org/x/sync v0.12.0 h1:MHc5BpPuC30uJk597Ri8TV3CNZcTLu6B6z4lJy+g6Jw=
+golang.org/x/sync v0.12.0/go.mod h1:1dzgHSNfp02xaA81J2MS99Qcpr2w7fw1gpm99rleRqA=
+golang.org/x/sys v0.0.0-20180905080454-ebe1bf3edb33/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
+golang.org/x/sys v0.0.0-20180909124046-d0be0721c37e/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
+golang.org/x/sys v0.0.0-20181116152217-5ac8a444bdc5/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
+golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
+golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
+golang.org/x/sys v0.0.0-20190422165155-953cdadca894/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
+golang.org/x/sys v0.0.0-20191120155948-bd437916bb0e/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
+golang.org/x/sys v0.0.0-20200106162015-b016eb3dc98e/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
+golang.org/x/sys v0.0.0-20200615200032-f1bc736245b1/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
+golang.org/x/sys v0.0.0-20201119102817-f84b799fce68/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
+golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
+golang.org/x/sys v0.0.0-20220520151302-bc2c85ada10a/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
+golang.org/x/sys v0.0.0-20220722155257-8c9f86f7a55f/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
+golang.org/x/sys v0.5.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
+golang.org/x/sys v0.8.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
+golang.org/x/sys v0.12.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
+golang.org/x/sys v0.17.0/go.mod h1:/VUhepiaJMQUp4+oa/7Zr1D23ma6VTLIYjOOTFZPUcA=
+golang.org/x/sys v0.20.0/go.mod h1:/VUhepiaJMQUp4+oa/7Zr1D23ma6VTLIYjOOTFZPUcA=
+golang.org/x/sys v0.28.0/go.mod h1:/VUhepiaJMQUp4+oa/7Zr1D23ma6VTLIYjOOTFZPUcA=
+golang.org/x/sys v0.29.0/go.mod h1:/VUhepiaJMQUp4+oa/7Zr1D23ma6VTLIYjOOTFZPUcA=
+golang.org/x/telemetry v0.0.0-20240228155512-f48c80bd79b2/go.mod h1:TeRTkGYfJXctD9OcfyVLyj2J3IxLnKwHJR8f4D8a3YE=
+golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1/go.mod h1:bj7SfCRtBDWHUb9snDiAeCFNEtKQo2Wmx5Cou7ajbmo=
+golang.org/x/term v0.0.0-20210927222741-03fcf44c2211/go.mod h1:jbD1KX2456YbFQfuXm/mYQcufACuNUgVhRMnK/tPxf8=
+golang.org/x/term v0.5.0/go.mod h1:jMB1sMXY+tzblOD4FWmEbocvup2/aLOaQEp7JmGp78k=
+golang.org/x/term v0.8.0/go.mod h1:xPskH00ivmX89bAKVGSKKtLOWNx2+17Eiy94tnKShWo=
+golang.org/x/term v0.12.0/go.mod h1:owVbMEjm3cBLCHdkQu9b1opXd4ETQWc3BhuQGKgXgvU=
+golang.org/x/term v0.17.0/go.mod h1:lLRBjIVuehSbZlaOtGMbcMncT+aqLLLmKrsjNrUguwk=
+golang.org/x/term v0.20.0/go.mod h1:8UkIAJTvZgivsXaD6/pH6U9ecQzZ45awqEOzuCvwpFY=
+golang.org/x/term v0.27.0/go.mod h1:iMsnZpn0cago0GOrHO2+Y7u7JPn5AylBrcoWkElMTSM=
+golang.org/x/term v0.28.0/go.mod h1:Sw/lC2IAUZ92udQNf3WodGtn4k/XoLyZoh8v/8uiwek=
+golang.org/x/text v0.3.0/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ=
+golang.org/x/text v0.3.3/go.mod h1:5Zoc/QRtKVWzQhOtBMvqHzDpF6irO9z98xDceosuGiQ=
+golang.org/x/text v0.3.7/go.mod h1:u+2+/6zg+i71rQMx5EYifcz6MCKuco9NR6JIITiCfzQ=
+golang.org/x/text v0.3.8/go.mod h1:E6s5w1FMmriuDzIBO73fBruAKo1PCIq6d2Q6DHfQ8WQ=
+golang.org/x/text v0.7.0/go.mod h1:mrYo+phRRbMaCq/xk9113O4dZlRixOauAjOtrjsXDZ8=
+golang.org/x/text v0.9.0/go.mod h1:e1OnstbJyHTd6l/uOt8jFFHp6TRDWZR/bV3emEE/zU8=
+golang.org/x/text v0.13.0/go.mod h1:TvPlkZtksWOMsz7fbANvkp4WM8x/WCo/om8BMLbz+aE=
+golang.org/x/text v0.14.0/go.mod h1:18ZOQIKpY8NJVqYksKHtTdi31H5itFRjB5/qKTNYzSU=
+golang.org/x/text v0.15.0/go.mod h1:18ZOQIKpY8NJVqYksKHtTdi31H5itFRjB5/qKTNYzSU=
+golang.org/x/text v0.21.0/go.mod h1:4IBbMaMmOPCJ8SecivzSH54+73PCFmPWxNTLm+vZkEQ=
+golang.org/x/text v0.23.0 h1:D71I7dUrlY+VX0gQShAThNGHFxZ13dGLBHQLVl1mJlY=
+golang.org/x/text v0.23.0/go.mod h1:/BLNzu4aZCJ1+kcD0DNRotWKage4q2rGVAg4o22unh4=
+golang.org/x/tools v0.0.0-20180917221912-90fa682c2a6e/go.mod h1:n7NCudcB/nEzxVGmLbDWY5pfWTLqBcC2KZ6jyYvM4mQ=
+golang.org/x/tools v0.0.0-20191119224855-298f0cb1881e/go.mod h1:b+2E5dAYhXwXZwtnZ6UAqBI28+e2cm9otk0dWdXHAEo=
+golang.org/x/tools v0.1.12/go.mod h1:hNGJHUnrk76NpqgfD5Aqm5Crs+Hm0VOH/i9J2+nxYbc=
+golang.org/x/tools v0.6.0/go.mod h1:Xwgl3UAJ/d3gWutnCtw505GrjyAbvKui8lOU390QaIU=
+golang.org/x/tools v0.13.0/go.mod h1:HvlwmtVNQAhOuCjW7xxvovg8wbNq7LwfXh/k7wXUl58=
+golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d/go.mod h1:aiJjzUbINMkxbQROHiO6hDPo2LHcIPhhQsa9DLh0yGk=
+golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
+golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
+google.golang.org/appengine v1.6.8 h1:IhEN5q69dyKagZPYMSdIjS2HqprW324FRQZJcGqPAsM=
+google.golang.org/appengine v1.6.8/go.mod h1:1jJ3jBArFh5pcgW8gCtRJnepW8FzD1V44FJffLiz/Ds=
+google.golang.org/protobuf v0.0.0-20200109180630-ec00e32a8dfd/go.mod h1:DFci5gLYBciE7Vtevhsrf46CRTquxDuWsQurQQe4oz8=
+google.golang.org/protobuf v0.0.0-20200221191635-4d8936d0db64/go.mod h1:kwYJMbMJ01Woi6D6+Kah6886xMZcty6N08ah7+eCXa0=
+google.golang.org/protobuf v0.0.0-20200228230310-ab0ca4ff8a60/go.mod h1:cfTl7dwQJ+fmap5saPgwCLgHXTUD7jkjRqWcaiX5VyM=
+google.golang.org/protobuf v1.20.1-0.20200309200217-e05f789c0967/go.mod h1:A+miEFZTKqfCUM6K7xSMQL9OKL/b6hQv+e19PK+JZNE=
+google.golang.org/protobuf v1.21.0/go.mod h1:47Nbq4nVaFHyn7ilMalzfO3qCViNmqZ2kzikPIcrTAo=
+google.golang.org/protobuf v1.23.0/go.mod h1:EGpADcykh3NcUnDUJcl1+ZksZNG86OlYog2l/sGQquU=
+google.golang.org/protobuf v1.26.0-rc.1/go.mod h1:jlhhOSvTdKEhbULTjvd4ARK9grFBp09yW+WbY/TyQbw=
+google.golang.org/protobuf v1.26.0/go.mod h1:9q0QmTI4eRPtz6boOQmLYwt+qCgq0jsYwAQnmE0givc=
+google.golang.org/protobuf v1.36.6 h1:z1NpPI8ku2WgiWnf+t9wTPsn6eP1L7ksHUlkfLvd9xY=
+google.golang.org/protobuf v1.36.6/go.mod h1:jduwjTPXsFjZGTmRluh+L6NjiWu7pchiJ2/5YcXBHnY=
+gopkg.in/alecthomas/kingpin.v2 v2.2.6/go.mod h1:FMv+mEhP44yOT+4EoQTLFTRgOQ1FBLkstjWtayDeSgw=
+gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
+gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
+gopkg.in/check.v1 v1.0.0-20200227125254-8fa46927fb4f h1:BLraFXnmrev5lT+xlilqcH8XK9/i0At2xKjWk4p6zsU=
+gopkg.in/check.v1 v1.0.0-20200227125254-8fa46927fb4f/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
+gopkg.in/fsnotify.v1 v1.4.7/go.mod h1:Tz8NjZHkW78fSQdbUxIjBTcgA1z1m8ZHf0WmKUhAMys=
+gopkg.in/mgo.v2 v2.0.0-20190816093944-a6b53ec6cb22/go.mod h1:yeKp02qBN3iKW1OzL3MGk2IdtZzaj7SFntXj72NppTA=
+gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7/go.mod h1:dt/ZhP58zS4L8KSrWDmTeBkI65Dw0HsyUHuEVlX15mw=
+gopkg.in/yaml.v2 v2.2.1/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
+gopkg.in/yaml.v2 v2.2.2/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
+gopkg.in/yaml.v2 v2.2.4/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
+gopkg.in/yaml.v2 v2.2.5/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
+gopkg.in/yaml.v2 v2.2.8/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
+gopkg.in/yaml.v3 v3.0.1 h1:fxVm/GzAzEWqLHuvctI91KS9hhNmmWOoWu0XTYJS7CA=
+gopkg.in/yaml.v3 v3.0.1/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM=
diff --git a/pkg/clients/database/connection.go b/pkg/clients/database/connection.go
new file mode 100644
index 0000000..98878e2
--- /dev/null
+++ b/pkg/clients/database/connection.go
@@ -0,0 +1,149 @@
+package database
+
+import (
+	"context"
+	"database/sql"
+	"fmt"
+	"log/slog"
+	"sync/atomic"
+
+	_ "github.com/firebolt-db/firebolt-go-sdk" // Register the Firebolt driver
+)
+
+// ErrConnectionClosed is returned when an operation is attempted on a closed connection.
+var ErrConnectionClosed = fmt.Errorf("connection is closed")
+
+// Connection defines the methods for interacting with Firebolt via SQL.
+//
+// It provides a standardized interface to execute queries against a Firebolt database instance
+// while abstracting away the underlying implementation details of the connection.
+type Connection interface {
+
+	// Query executes a SQL query against Firebolt and returns the result.
+	// The sql parameter can be any valid Firebolt SQL statement, including
+	// SELECT, INSERT, UPDATE, DELETE, etc.
+	Query(ctx context.Context, sql string, args ...any) ([]map[string]any, error)
+}
+
+// ConnectionCloser extends the Connection interface to include a method for closing the connection.
+type ConnectionCloser interface {
+	Connection
+
+	// Close terminates the underlying database connection and releases
+	// all associated resources.
+	Close()
+}
+
+// NewConnection creates a new Firebolt connection using the provided parameters.
+// It returns a ConnectionCloser interface, a function to close the connection, and an error
+// if any occurred during the connection setup.
+func NewConnection(
+	logger *slog.Logger,
+	params DSNProvider,
+) (ConnectionCloser, func(), error) {
+
+	db, err := sql.Open(params.DriverName(), params.DSN())
+	if err != nil {
+		return nil, nil, fmt.Errorf("failed to open Firebolt connection: %w", err)
+	}
+
+	conn := &connectionImpl{
+		db:       db,
+		logger:   logger,
+		isClosed: &atomic.Bool{},
+	}
+
+	return conn, conn.Close, nil
+}
+
+type connectionImpl struct {
+	db       *sql.DB
+	logger   *slog.Logger
+	isClosed *atomic.Bool
+}
+
+func (c *connectionImpl) Query(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+
+	// Check if the connection is closed
+	if c.isClosed.Load() {
+		return nil, ErrConnectionClosed
+	}
+
+	// Query the database
+	rows, err := c.db.QueryContext(ctx, sql, args...)
+	if err != nil {
+		return nil, fmt.Errorf("failed to execute query: %w", err)
+	}
+	defer func() {
+		if err := rows.Close(); err != nil {
+			c.logger.Warn(
+				"failed to close database result rows",
+				"error", err,
+				"sql", sql,
+			)
+		}
+	}()
+
+	// Retrieve column names
+	columns, err := rows.Columns()
+	if err != nil {
+		return nil, fmt.Errorf("failed to get columns: %w", err)
+	}
+
+	// Iterate over the rows and scan the results into a slice of maps
+	var results []map[string]any
+	for rows.Next() {
+
+		// Create containers for the row data
+		values := make([]any, len(columns))
+		valuePtrs := make([]any, len(columns))
+		for i := range values {
+			valuePtrs[i] = &values[i]
+		}
+
+		// Scan the row into the value pointers
+		if err := rows.Scan(valuePtrs...); err != nil {
+			return nil, fmt.Errorf("failed to scan row: %w", err)
+		}
+
+		// Map column names to their values
+		rowMap := make(map[string]any)
+		for i, col := range columns {
+			rowMap[col] = values[i]
+		}
+
+		results = append(results, rowMap)
+	}
+
+	// Check for errors during iteration
+	if err := rows.Err(); err != nil {
+		return nil, fmt.Errorf("rows iteration error: %w", err)
+	}
+
+	return results, nil
+}
+
+func (c *connectionImpl) Close() {
+
+	if c.isClosed.Load() {
+		return
+	}
+
+	if err := c.db.Close(); err != nil {
+		c.logger.Warn("failed to close database connection", "error", err)
+	}
+
+	c.isClosed.Store(true)
+}
+
+// DSNProvider defines the interface for providing a Data Source Name (DSN).
+// The only DSNProvider implementation is ConnectionParams, but this interface
+// allows to write mock implementations for testing purposes.
+type DSNProvider interface {
+
+	// DriverName returns the name of the database driver.
+	DriverName() string
+
+	// DSN returns the Data Source Name (DSN) for the connection.
+	DSN() string
+}
diff --git a/pkg/clients/database/connection_test.go b/pkg/clients/database/connection_test.go
new file mode 100644
index 0000000..11d02f2
--- /dev/null
+++ b/pkg/clients/database/connection_test.go
@@ -0,0 +1,215 @@
+package database_test
+
+import (
+	"database/sql"
+	"database/sql/driver"
+	"errors"
+	"io"
+	"testing"
+
+	"github.com/neilotoole/slogt"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+)
+
+func TestNewConnection(t *testing.T) {
+
+	t.Run("successful connection", func(t *testing.T) {
+		conn, closer, err := database.NewConnection(slogt.New(t), mockParams{})
+		require.NoError(t, err)
+		require.NotNil(t, conn)
+		require.NotNil(t, closer)
+		closer()
+	})
+}
+
+func TestConnectionQuery(t *testing.T) {
+
+	t.Run("successful query", func(t *testing.T) {
+
+		conn, closer, err := database.NewConnection(slogt.New(t), mockParams{})
+		require.NoError(t, err)
+		t.Cleanup(closer)
+
+		results, err := conn.Query(t.Context(), "SELECT col1, col2 FROM test")
+		require.NoError(t, err)
+		require.Len(t, results, 2)
+
+		// Verify first row
+		assert.Equal(t, "value1", results[0]["col1"])
+		assert.Equal(t, 1, results[0]["col2"])
+
+		// Verify second row
+		assert.Equal(t, "value2", results[1]["col1"])
+		assert.Equal(t, 2, results[1]["col2"])
+	})
+
+	t.Run("empty result set", func(t *testing.T) {
+
+		conn, closer, err := database.NewConnection(slogt.New(t), mockParams{})
+		require.NoError(t, err)
+		t.Cleanup(closer)
+
+		results, err := conn.Query(t.Context(), "SELECT * FROM empty")
+		require.NoError(t, err)
+		assert.Empty(t, results)
+	})
+
+	t.Run("query error", func(t *testing.T) {
+
+		conn, closer, err := database.NewConnection(slogt.New(t), mockParams{})
+		require.NoError(t, err)
+		t.Cleanup(closer)
+
+		results, err := conn.Query(t.Context(), "ERROR")
+		require.Error(t, err)
+		assert.Nil(t, results)
+	})
+
+	t.Run("closed connection", func(t *testing.T) {
+
+		conn, closer, err := database.NewConnection(slogt.New(t), mockParams{})
+		require.NoError(t, err)
+
+		// Close the connection
+		closer()
+
+		// Try to query on a closed connection
+		results, err := conn.Query(t.Context(), "SELECT col1, col2 FROM test")
+		require.Error(t, err)
+		assert.ErrorIs(t, err, database.ErrConnectionClosed)
+		assert.Nil(t, results)
+	})
+}
+
+func TestConnectionClose(t *testing.T) {
+
+	t.Run("multiple close calls", func(t *testing.T) {
+
+		conn, closer, err := database.NewConnection(slogt.New(t), mockParams{})
+		require.NoError(t, err)
+
+		// First close
+		closer()
+
+		// Second close should not panic
+		closer()
+
+		// Should still return error for operations
+		results, err := conn.Query(t.Context(), "SELECT col1, col2 FROM test")
+		require.Error(t, err)
+		assert.ErrorIs(t, err, database.ErrConnectionClosed)
+		assert.Nil(t, results)
+	})
+}
+
+// Mock SQL driver implementation for testing
+type mockDriver struct{}
+
+type mockConn struct {
+	closed bool
+}
+
+type mockStmt struct {
+	query  string
+	closed bool
+}
+
+type mockRows struct {
+	columns []string
+	data    [][]driver.Value
+	closed  bool
+	rowIdx  int
+}
+
+// Register the mock driver
+func init() {
+	sql.Register("fireboltmock", &mockDriver{})
+}
+
+func (d *mockDriver) Open(name string) (driver.Conn, error) {
+	return &mockConn{}, nil
+}
+
+func (c *mockConn) Prepare(query string) (driver.Stmt, error) {
+	if c.closed {
+		return nil, driver.ErrBadConn
+	}
+	return &mockStmt{query: query}, nil
+}
+
+func (c *mockConn) Close() error {
+	c.closed = true
+	return nil
+}
+
+func (c *mockConn) Begin() (driver.Tx, error) {
+	return nil, errors.New("transactions not supported")
+}
+
+func (s *mockStmt) Close() error {
+	s.closed = true
+	return nil
+}
+
+func (s *mockStmt) NumInput() int {
+	return 0
+}
+
+func (s *mockStmt) Exec(args []driver.Value) (driver.Result, error) {
+	return nil, errors.New("exec not implemented")
+}
+
+func (s *mockStmt) Query(args []driver.Value) (driver.Rows, error) {
+
+	if s.query == "ERROR" {
+		return nil, errors.New("query error")
+	}
+
+	if s.query == "SELECT col1, col2 FROM test" {
+		return &mockRows{
+			columns: []string{"col1", "col2"},
+			data: [][]driver.Value{
+				{"value1", 1},
+				{"value2", 2},
+			},
+		}, nil
+	}
+
+	return &mockRows{
+		columns: []string{},
+		data:    [][]driver.Value{},
+	}, nil
+}
+
+func (r *mockRows) Columns() []string {
+	return r.columns
+}
+
+func (r *mockRows) Close() error {
+	r.closed = true
+	return nil
+}
+
+func (r *mockRows) Next(dest []driver.Value) error {
+	if r.rowIdx >= len(r.data) {
+		return io.EOF
+	}
+
+	copy(dest, r.data[r.rowIdx])
+	r.rowIdx++
+	return nil
+}
+
+type mockParams struct {
+}
+
+func (m mockParams) DriverName() string {
+	return "fireboltmock"
+}
+
+func (m mockParams) DSN() string {
+	return "fireboltmock://test"
+}
diff --git a/pkg/clients/database/databasemock/connection.go b/pkg/clients/database/databasemock/connection.go
new file mode 100644
index 0000000..2d35f92
--- /dev/null
+++ b/pkg/clients/database/databasemock/connection.go
@@ -0,0 +1,57 @@
+package databasemock
+
+import (
+	"context"
+	"sync/atomic"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+)
+
+var _ database.ConnectionCloser = &ConnectionMock{}
+
+func NewConnectionMock() *ConnectionMock {
+	return &ConnectionMock{
+		QueryFunc: func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+			return []map[string]any{}, nil
+		},
+		CloseFunc: func() {},
+		IsClosed:  &atomic.Bool{},
+	}
+}
+
+type ConnectionMock struct {
+	QueryFunc  func(ctx context.Context, sql string, args ...any) ([]map[string]any, error)
+	CloseFunc  func()
+	CloseCount int
+	IsClosed   *atomic.Bool
+}
+
+func (c *ConnectionMock) Query(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+	if c.IsClosed.Load() {
+		return nil, database.ErrConnectionClosed
+	}
+	return c.QueryFunc(ctx, sql, args...)
+}
+
+func (c *ConnectionMock) Close() {
+	c.CloseCount++
+	c.IsClosed.Store(true)
+	c.CloseFunc()
+}
+
+// WithQueryFunc allows setting a custom query function for testing
+func (c *ConnectionMock) WithQueryFunc(fn func(ctx context.Context, sql string, args ...any) ([]map[string]any, error)) *ConnectionMock {
+	c.QueryFunc = fn
+	return c
+}
+
+// WithCloseFunc allows setting a custom close function for testing
+func (c *ConnectionMock) WithCloseFunc(fn func()) *ConnectionMock {
+	c.CloseFunc = fn
+	return c
+}
+
+// IsConnectionClosed returns the status of the connection
+func (c *ConnectionMock) IsConnectionClosed() bool {
+	return c.IsClosed.Load()
+}
diff --git a/pkg/clients/database/databasemock/pool.go b/pkg/clients/database/databasemock/pool.go
new file mode 100644
index 0000000..7f4e688
--- /dev/null
+++ b/pkg/clients/database/databasemock/pool.go
@@ -0,0 +1,115 @@
+package databasemock
+
+import (
+	"fmt"
+	"sync"
+	"sync/atomic"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+)
+
+var _ database.Pool = &PoolMock{}
+
+func NewPoolMock() *PoolMock {
+	return &PoolMock{
+		GetConnectionFunc: func(params database.PoolParams) (database.Connection, error) {
+			return NewConnectionMock(), nil
+		},
+		CloseFunc:       func() {},
+		IsClosed:        &atomic.Bool{},
+		connections:     make(map[string]database.Connection),
+		connectionCalls: make(map[string]int),
+	}
+}
+
+type PoolMock struct {
+	GetConnectionFunc func(params database.PoolParams) (database.Connection, error)
+	CloseFunc         func()
+	IsClosed          *atomic.Bool
+	CloseCount        int
+
+	mu              sync.RWMutex
+	connections     map[string]database.Connection
+	connectionCalls map[string]int
+}
+
+func (p *PoolMock) GetConnection(params database.PoolParams) (database.Connection, error) {
+	p.mu.Lock()
+	defer p.mu.Unlock()
+
+	if p.IsClosed.Load() {
+		return nil, database.ErrPoolClosed
+	}
+
+	key := keyForPoolParams(params)
+	p.connectionCalls[key]++
+
+	return p.GetConnectionFunc(params)
+}
+
+func (p *PoolMock) Close() {
+	p.mu.Lock()
+	defer p.mu.Unlock()
+
+	p.CloseCount++
+	p.IsClosed.Store(true)
+	p.CloseFunc()
+}
+
+// WithGetConnectionFunc allows setting a custom GetConnection function for testing
+func (p *PoolMock) WithGetConnectionFunc(fn func(params database.PoolParams) (database.Connection, error)) *PoolMock {
+	p.GetConnectionFunc = fn
+	return p
+}
+
+// WithCloseFunc allows setting a custom close function for testing
+func (p *PoolMock) WithCloseFunc(fn func()) *PoolMock {
+	p.CloseFunc = fn
+	return p
+}
+
+// IsPoolClosed returns the status of the pool
+func (p *PoolMock) IsPoolClosed() bool {
+	return p.IsClosed.Load()
+}
+
+// GetConnectionCallCount returns the number of times GetConnection was called with the given parameters
+func (p *PoolMock) GetConnectionCallCount(params database.PoolParams) int {
+	p.mu.RLock()
+	defer p.mu.RUnlock()
+
+	key := keyForPoolParams(params)
+	return p.connectionCalls[key]
+}
+
+// RegisterConnection allows registering a specific connection for specific parameters
+func (p *PoolMock) RegisterConnection(params database.PoolParams, conn database.Connection) {
+	p.mu.Lock()
+	defer p.mu.Unlock()
+
+	key := keyForPoolParams(params)
+	p.connections[key] = conn
+
+	originalFunc := p.GetConnectionFunc
+	p.GetConnectionFunc = func(reqParams database.PoolParams) (database.Connection, error) {
+		reqKey := keyForPoolParams(params)
+		if conn, ok := p.connections[reqKey]; ok {
+			return conn, nil
+		}
+		return originalFunc(reqParams)
+	}
+}
+
+// keyForPoolParams generates a key by using the underlying string values
+// for the optional parameters.
+func keyForPoolParams(params database.PoolParams) string {
+	db := ""
+	if params.DatabaseName != nil {
+		db = *params.DatabaseName
+	}
+	engine := ""
+	if params.EngineName != nil {
+		engine = *params.EngineName
+	}
+	return fmt.Sprintf("%s-%s-%s", params.AccountName, db, engine)
+}
diff --git a/pkg/clients/database/params.go b/pkg/clients/database/params.go
new file mode 100644
index 0000000..9d679f5
--- /dev/null
+++ b/pkg/clients/database/params.go
@@ -0,0 +1,67 @@
+package database
+
+import (
+	"crypto/sha512"
+	"encoding/hex"
+	"fmt"
+	"strings"
+)
+
+const secretMask = "xxxxx"
+
+// PoolParams holds the parameters required to create a connection in the pool.
+// The pool will convert these parameters into a ConnectionParams struct by adding the ClientID and ClientSecret.
+type PoolParams struct {
+	AccountName  string
+	DatabaseName *string
+	EngineName   *string
+}
+
+// ConnectionParams holds the parameters required to establish a connection to Firebolt.
+// It contains authentication credentials, account information, and optional database and engine specifications.
+type ConnectionParams struct {
+	ClientID     string
+	ClientSecret string
+	AccountName  string
+	DatabaseName *string
+	EngineName   *string
+}
+
+// String returns a string representation of the connection parameters.
+// The format is similar to a DSN, but sensitive information (ClientID and ClientSecret) is masked,
+// making this string safe to log or display.
+func (c ConnectionParams) String() string {
+	return strings.NewReplacer(c.ClientID, secretMask, c.ClientSecret, secretMask).Replace(c.DSN())
+}
+
+// DriverName returns the name of the database driver.
+// In this case, it returns "firebolt", which is the driver name used by the Firebolt Go SDK.
+func (c ConnectionParams) DriverName() string {
+	return "firebolt"
+}
+
+// DSN returns the Data Source Name expected by the Firebolt Go SDK.
+// This is a connection string that contains all the necessary information to connect to the Firebolt database.
+// The format follows the pattern: firebolt://[database]?account_name=[account]&client_id=[id]&client_secret=[secret]&engine=[engine]
+func (c ConnectionParams) DSN() string {
+
+	dbName := ""
+	if c.DatabaseName != nil {
+		dbName = "/" + *c.DatabaseName
+	}
+
+	engineName := ""
+	if c.EngineName != nil {
+		engineName = "&engine=" + *c.EngineName
+	}
+
+	return fmt.Sprintf("firebolt://%s?account_name=%s&client_id=%s&client_secret=%s%s", dbName, c.AccountName, c.ClientID, c.ClientSecret, engineName)
+}
+
+// Hash returns a SHA-512/256 hash of the connection parameters.
+// This is useful for caching connections or comparing parameter sets without exposing sensitive information.
+// The hash is computed from the full DSN string and returned as a hex-encoded string.
+func (c ConnectionParams) Hash() string {
+	sum := sha512.Sum512_256([]byte(c.DSN()))
+	return hex.EncodeToString(sum[:])
+}
diff --git a/pkg/clients/database/params_test.go b/pkg/clients/database/params_test.go
new file mode 100644
index 0000000..d371f18
--- /dev/null
+++ b/pkg/clients/database/params_test.go
@@ -0,0 +1,161 @@
+package database_test
+
+import (
+	"crypto/sha512"
+	"encoding/hex"
+	"testing"
+
+	"github.com/stretchr/testify/assert"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+)
+
+func TestConnectionParams_DriverName(t *testing.T) {
+	params := database.ConnectionParams{}
+	assert.Equal(t, "firebolt", params.DriverName(), "DriverName should return 'firebolt'")
+}
+
+func TestConnectionParams_DSN(t *testing.T) {
+	tests := []struct {
+		name     string
+		params   database.ConnectionParams
+		expected string
+	}{
+		{
+			name: "full params",
+			params: database.ConnectionParams{
+				ClientID:     "test-client",
+				ClientSecret: "test-secret",
+				AccountName:  "test-account",
+				DatabaseName: strPtr("test-db"),
+				EngineName:   strPtr("test-engine"),
+			},
+			expected: "firebolt:///test-db?account_name=test-account&client_id=test-client&client_secret=test-secret&engine=test-engine",
+		},
+		{
+			name: "nil database",
+			params: database.ConnectionParams{
+				ClientID:     "test-client",
+				ClientSecret: "test-secret",
+				AccountName:  "test-account",
+				DatabaseName: nil,
+				EngineName:   strPtr("test-engine"),
+			},
+			expected: "firebolt://?account_name=test-account&client_id=test-client&client_secret=test-secret&engine=test-engine",
+		},
+		{
+			name: "nil engine name",
+			params: database.ConnectionParams{
+				ClientID:     "test-client",
+				ClientSecret: "test-secret",
+				AccountName:  "test-account",
+				DatabaseName: strPtr("test-db"),
+				EngineName:   nil,
+			},
+			expected: "firebolt:///test-db?account_name=test-account&client_id=test-client&client_secret=test-secret",
+		},
+		{
+			name: "nil database and engine name",
+			params: database.ConnectionParams{
+				ClientID:     "test-client",
+				ClientSecret: "test-secret",
+				AccountName:  "test-account",
+				DatabaseName: nil,
+				EngineName:   nil,
+			},
+			expected: "firebolt://?account_name=test-account&client_id=test-client&client_secret=test-secret",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			assert.Equal(t, tt.expected, tt.params.DSN(), "DSN should match expected value")
+		})
+	}
+}
+
+func TestConnectionParams_String(t *testing.T) {
+	tests := []struct {
+		name     string
+		params   database.ConnectionParams
+		expected string
+	}{
+		{
+			name: "masks sensitive information",
+			params: database.ConnectionParams{
+				ClientID:     "sensitive-client-id",
+				ClientSecret: "sensitive-secret",
+				AccountName:  "test-account",
+				DatabaseName: strPtr("test-db"),
+				EngineName:   strPtr("test-engine"),
+			},
+			expected: "firebolt:///test-db?account_name=test-account&client_id=xxxxx&client_secret=xxxxx&engine=test-engine",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			assert.Equal(t, tt.expected, tt.params.String(), "String should mask sensitive information")
+		})
+	}
+}
+
+func TestConnectionParams_Hash(t *testing.T) {
+	params := database.ConnectionParams{
+		ClientID:     "test-client",
+		ClientSecret: "test-secret",
+		AccountName:  "test-account",
+		DatabaseName: strPtr("test-db"),
+		EngineName:   strPtr("test-engine"),
+	}
+
+	// Calculate expected hash manually
+	dsn := params.DSN()
+	sum := sha512.Sum512_256([]byte(dsn))
+	expected := hex.EncodeToString(sum[:])
+
+	assert.Equal(t, expected, params.Hash(), "Hash should match expected value")
+}
+
+func TestConnectionParams_HashConsistency(t *testing.T) {
+	params := database.ConnectionParams{
+		ClientID:     "test-client",
+		ClientSecret: "test-secret",
+		AccountName:  "test-account",
+		DatabaseName: strPtr("test-db"),
+		EngineName:   strPtr("test-engine"),
+	}
+
+	hash1 := params.Hash()
+	hash2 := params.Hash()
+
+	assert.Equal(t, hash1, hash2, "Hash should be consistent across calls")
+}
+
+func TestConnectionParams_HashDifference(t *testing.T) {
+	params1 := database.ConnectionParams{
+		ClientID:     "test-client",
+		ClientSecret: "test-secret",
+		AccountName:  "test-account",
+		DatabaseName: strPtr("test-db"),
+		EngineName:   strPtr("test-engine"),
+	}
+
+	params2 := database.ConnectionParams{
+		ClientID:     "different-client",
+		ClientSecret: "test-secret",
+		AccountName:  "test-account",
+		DatabaseName: strPtr("test-db"),
+		EngineName:   strPtr("test-engine"),
+	}
+
+	hash1 := params1.Hash()
+	hash2 := params2.Hash()
+
+	assert.NotEqual(t, hash1, hash2, "Different parameters should have different hashes")
+}
+
+// Helper function to create a string pointer
+func strPtr(s string) *string {
+	return &s
+}
diff --git a/pkg/clients/database/pool.go b/pkg/clients/database/pool.go
new file mode 100644
index 0000000..4ab7065
--- /dev/null
+++ b/pkg/clients/database/pool.go
@@ -0,0 +1,132 @@
+package database
+
+import (
+	"fmt"
+	"log/slog"
+	"sync"
+)
+
+// ErrPoolClosed is returned when an operation is attempted on a closed pool.
+var ErrPoolClosed = fmt.Errorf("pool is closed")
+
+// Pool implements a thread-safe connection pool for Firebolt database connections.
+//
+// This MCP server is designed to provide access to multiple Firebolt accounts
+// and databases simultaneously, which the current identity has access to.
+// Since the Firebolt Go SDK creates connections to a single account only,
+// we need to maintain a pool of connections to different accounts.
+//
+// The implementation creates a pool of connections for different combinations of:
+// - Accounts
+// - Databases
+// - Engines
+//
+// This approach helps LLMs switch between different databases and engines
+// with fewer mistakes, trading some connection efficiency for improved reliability.
+type Pool interface {
+
+	// GetConnection returns a connection for the specified parameters.
+	// It first checks if a matching connection exists in the pool.
+	// If not found, it creates a new connection, adds it to the pool, and returns it.
+	GetConnection(params PoolParams) (Connection, error)
+
+	// Close closes all connections in the pool and releases associated resources.
+	Close()
+}
+
+// NewPool creates a new connection pool with the provided logger.
+// It returns the pool implementation and a function to close all connections.
+func NewPool(logger *slog.Logger, clientID, clientSecret string) (Pool, func()) {
+	return NewPoolWithConnectionFactory(logger, clientID, clientSecret, NewConnection)
+}
+
+// NewConnectionFunc defines a function type for creating new connections.
+type NewConnectionFunc func(*slog.Logger, DSNProvider) (ConnectionCloser, func(), error)
+
+// NewPoolWithConnectionFactory creates a new connection pool with a custom connection factory.
+// It allows you to provide a custom function to create connections which can be useful for testing.
+func NewPoolWithConnectionFactory(
+	logger *slog.Logger,
+	clientID, clientSecret string,
+	newConnectionFunc NewConnectionFunc,
+) (Pool, func()) {
+
+	pool := &poolImpl{
+		logger:            logger,
+		connections:       make(map[string]Connection),
+		newConnectionFunc: newConnectionFunc,
+		clientID:          clientID,
+		clientSecret:      clientSecret,
+	}
+
+	return pool, pool.Close
+}
+
+type poolImpl struct {
+	sync.RWMutex
+	isClosed          bool
+	logger            *slog.Logger
+	closers           []func()
+	connections       map[string]Connection
+	newConnectionFunc NewConnectionFunc
+	clientID          string
+	clientSecret      string
+}
+
+func (p *poolImpl) GetConnection(params PoolParams) (Connection, error) {
+
+	connectionParams := ConnectionParams{
+		ClientID:     p.clientID,
+		ClientSecret: p.clientSecret,
+		AccountName:  params.AccountName,
+		DatabaseName: params.DatabaseName,
+		EngineName:   params.EngineName,
+	}
+	hash := connectionParams.Hash()
+
+	// First, try to get an existing connection with a read lock
+	p.RLock()
+	if p.isClosed {
+		p.RUnlock()
+		return nil, ErrPoolClosed
+	}
+	if conn, ok := p.connections[hash]; ok {
+		p.RUnlock()
+		return conn, nil
+	}
+	p.RUnlock()
+
+	// Create a new connection if one doesn't exist
+	conn, closer, err := p.newConnectionFunc(p.logger, connectionParams)
+	if err != nil {
+		return nil, fmt.Errorf("failed to create connection: %w", err)
+	}
+
+	// Store the new connection in the pool with a write lock
+	p.Lock()
+	p.connections[hash] = conn
+	p.closers = append(p.closers, closer)
+	p.Unlock()
+
+	return conn, nil
+}
+
+func (p *poolImpl) Close() {
+
+	p.Lock()
+	defer p.Unlock()
+
+	if p.isClosed {
+		return
+	}
+
+	// Close all connections
+	for _, closer := range p.closers {
+		closer()
+	}
+
+	// Reset the pool state
+	p.closers = nil
+	p.connections = make(map[string]Connection)
+	p.isClosed = true
+}
diff --git a/pkg/clients/database/pool_test.go b/pkg/clients/database/pool_test.go
new file mode 100644
index 0000000..2a2be6a
--- /dev/null
+++ b/pkg/clients/database/pool_test.go
@@ -0,0 +1,225 @@
+package database_test
+
+import (
+	"log/slog"
+	"sync/atomic"
+	"testing"
+
+	"github.com/neilotoole/slogt"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+	"github.com/firebolt-db/mcp-server/pkg/clients/database/databasemock"
+)
+
+func TestNewPool(t *testing.T) {
+
+	t.Run("create new pool", func(t *testing.T) {
+		pool, closer := database.NewPool(slogt.New(t), "", "")
+		require.NotNil(t, pool, "Pool should not be nil")
+		require.NotNil(t, closer, "Closer function should not be nil")
+		closer()
+	})
+
+	t.Run("create pool with custom connection factory", func(t *testing.T) {
+
+		factoryCalled := false
+		customFactory := func(logger *slog.Logger, params database.DSNProvider) (database.ConnectionCloser, func(), error) {
+			factoryCalled = true
+			conn := databasemock.NewConnectionMock()
+			return conn, conn.Close, nil
+		}
+
+		pool, closer := database.NewPoolWithConnectionFactory(slogt.New(t), "", "", customFactory)
+		require.NotNil(t, pool, "Pool should not be nil")
+		require.NotNil(t, closer, "Closer function should not be nil")
+
+		// Get a connection to trigger the factory
+		conn, err := pool.GetConnection(database.PoolParams{
+			AccountName: "test-account",
+		})
+		require.NoError(t, err, "GetConnection should not return an error")
+		require.NotNil(t, conn, "Connection should not be nil")
+		assert.True(t, factoryCalled, "Custom connection factory should be called")
+
+		closer()
+	})
+}
+
+func TestPoolGetConnection(t *testing.T) {
+
+	t.Run("get connection", func(t *testing.T) {
+
+		factoryCallCount := 0
+		customFactory := func(logger *slog.Logger, params database.DSNProvider) (database.ConnectionCloser, func(), error) {
+			factoryCallCount++
+			conn := databasemock.NewConnectionMock()
+			return conn, conn.Close, nil
+		}
+
+		pool, closer := database.NewPoolWithConnectionFactory(slogt.New(t), "", "", customFactory)
+		t.Cleanup(closer)
+
+		params := database.PoolParams{
+			AccountName: "test-account",
+		}
+
+		// First request should create a new connection
+		conn1, err := pool.GetConnection(params)
+		require.NoError(t, err, "GetConnection should not return an error")
+		require.NotNil(t, conn1, "Connection should not be nil")
+		assert.Equal(t, 1, factoryCallCount, "Connection factory should be called once")
+
+		// Second request with same params should reuse the connection
+		conn2, err := pool.GetConnection(params)
+		require.NoError(t, err, "GetConnection should not return an error")
+		require.NotNil(t, conn2, "Connection should not be nil")
+		assert.Equal(t, 1, factoryCallCount, "Connection factory should still be called only once")
+
+		// Connection objects should be the same instance
+		assert.Same(t, conn1, conn2, "Both connections should be the same instance")
+	})
+
+	t.Run("get different connections", func(t *testing.T) {
+
+		factoryCallCount := 0
+		customFactory := func(logger *slog.Logger, params database.DSNProvider) (database.ConnectionCloser, func(), error) {
+			factoryCallCount++
+			conn := databasemock.NewConnectionMock()
+			return conn, conn.Close, nil
+		}
+
+		pool, poolCloser := database.NewPoolWithConnectionFactory(slogt.New(t), "", "", customFactory)
+		t.Cleanup(poolCloser)
+
+		// Create connections with different parameters
+		params1 := database.PoolParams{
+			AccountName: "account1",
+		}
+
+		params2 := database.PoolParams{
+			AccountName: "account2",
+		}
+
+		conn1, err := pool.GetConnection(params1)
+		require.NoError(t, err, "GetConnection with params1 should not return an error")
+
+		conn2, err := pool.GetConnection(params2)
+		require.NoError(t, err, "GetConnection with params2 should not return an error")
+
+		assert.NotSame(t, conn1, conn2, "Connections with different params should be different instances")
+		assert.Equal(t, 2, factoryCallCount, "Connection factory should create 2 connections")
+	})
+}
+
+func TestPoolClose(t *testing.T) {
+
+	t.Run("close all connections", func(t *testing.T) {
+
+		closeCount := 0
+		customFactory := func(logger *slog.Logger, params database.DSNProvider) (database.ConnectionCloser, func(), error) {
+			conn := databasemock.NewConnectionMock().WithCloseFunc(func() {
+				closeCount++
+			})
+			return conn, conn.Close, nil
+		}
+
+		pool, poolCloser := database.NewPoolWithConnectionFactory(slogt.New(t), "", "", customFactory)
+
+		// Create several connections
+		params1 := database.PoolParams{AccountName: "account1"}
+		params2 := database.PoolParams{AccountName: "account2"}
+
+		_, err := pool.GetConnection(params1)
+		require.NoError(t, err)
+
+		_, err = pool.GetConnection(params2)
+		require.NoError(t, err)
+
+		// Close the pool - should close all connections
+		poolCloser()
+		assert.Equal(t, 2, closeCount, "All connections should be closed")
+
+		// Verify pool is closed by trying to get a connection again
+		conn3, err := pool.GetConnection(params1)
+		require.Error(t, err, "GetConnection should return error after pool is closed")
+		assert.Nil(t, conn3, "Connection should be nil after pool is closed")
+		assert.ErrorIs(t, err, database.ErrPoolClosed, "Error should be ErrPoolClosed")
+	})
+
+	t.Run("multiple close calls", func(t *testing.T) {
+
+		closeCount := 0
+		customFactory := func(logger *slog.Logger, params database.DSNProvider) (database.ConnectionCloser, func(), error) {
+			conn := databasemock.NewConnectionMock().WithCloseFunc(func() {
+				closeCount++
+			})
+			return conn, conn.Close, nil
+		}
+
+		pool, poolCloser := database.NewPoolWithConnectionFactory(slogt.New(t), "", "", customFactory)
+
+		// Create a connection
+		params := database.PoolParams{AccountName: "account"}
+		_, err := pool.GetConnection(params)
+		require.NoError(t, err)
+
+		// Close the pool multiple times - should be safe
+		poolCloser()
+		assert.Equal(t, 1, closeCount, "Connection should be closed once")
+
+		poolCloser() // Second close call
+		assert.Equal(t, 1, closeCount, "Connections should not be closed again")
+
+		// Getting a new connection after closing should fail
+		conn, err := pool.GetConnection(params)
+		require.Error(t, err, "GetConnection should return error after pool is closed")
+		assert.Nil(t, conn, "Connection should be nil after pool is closed")
+		assert.ErrorIs(t, err, database.ErrPoolClosed, "Error should be ErrPoolClosed")
+	})
+}
+
+func TestPoolConcurrency(t *testing.T) {
+
+	t.Run("concurrent connection requests", func(t *testing.T) {
+
+		var factoryCallCount atomic.Int32
+
+		customFactory := func(logger *slog.Logger, params database.DSNProvider) (database.ConnectionCloser, func(), error) {
+			factoryCallCount.Add(1)
+
+			conn := databasemock.NewConnectionMock()
+			return conn, conn.Close, nil
+		}
+
+		pool, closer := database.NewPoolWithConnectionFactory(slogt.New(t), "", "", customFactory)
+		t.Cleanup(closer)
+
+		params := database.PoolParams{
+			AccountName: "test-account",
+		}
+
+		// Run concurrent goroutines all requesting the same connection parameters
+		const numGoroutines = 100
+		done := make(chan bool, numGoroutines)
+
+		for i := 0; i < numGoroutines; i++ {
+			go func() {
+				conn, err := pool.GetConnection(params)
+				assert.NoError(t, err)
+				assert.NotNil(t, conn)
+				done <- true
+			}()
+		}
+
+		// Wait for all goroutines to complete
+		for i := 0; i < numGoroutines; i++ {
+			<-done
+		}
+
+		// Should only create one connection despite concurrent requests
+		assert.Equal(t, int32(1), factoryCallCount.Load(),
+			"Connection factory should be called exactly once despite concurrent requests")
+	})
+}
diff --git a/pkg/clients/discovery/client.go b/pkg/clients/discovery/client.go
new file mode 100644
index 0000000..2a58406
--- /dev/null
+++ b/pkg/clients/discovery/client.go
@@ -0,0 +1,132 @@
+package discovery
+
+import (
+	"context"
+	"encoding/json"
+	"fmt"
+	"io"
+	"log/slog"
+	"net/http"
+	"net/url"
+
+	"golang.org/x/oauth2"
+	"golang.org/x/oauth2/clientcredentials"
+)
+
+const (
+	authTokenEndpoint  = "/oauth/token"
+	myAccountsEndpoint = "/myAccounts"
+)
+
+// Client represents a Firebolt API client that can be used to discover a list of accounts accessible by the identity
+// on behalf of which the MCP server runs.
+// The standard Firebolt Go SDK requires an account to be specified in the connection string.
+// This client allows the MCP to work with multiple accounts within an organization and switch between them as needed.
+type Client interface {
+
+	// ListAccounts retrieves a list of accounts that the current identity has access to.
+	// It returns a slice of Account or an error if the operation fails.
+	ListAccounts(ctx context.Context) ([]Account, error)
+}
+
+// NewClient creates a new instance of the Firebolt API client.
+// It initializes the client with the provided OAuth2 credentials and base URLs for authentication and API access.
+// Returns an instance of Client or an error if the initialization fails.
+func NewClient(
+	ctx context.Context,
+	logger *slog.Logger,
+	clientID, clientSecret,
+	authBaseURL, apiBaseURL string,
+) (Client, error) {
+
+	// Prepare config for OAuth2 client credentials authentication
+	tokenURL, err := url.JoinPath(authBaseURL, authTokenEndpoint)
+	if err != nil {
+		return nil, fmt.Errorf("could not create token URL: %w", err)
+	}
+	authConfig := &clientcredentials.Config{
+		ClientID:     clientID,
+		ClientSecret: clientSecret,
+		TokenURL:     tokenURL,
+		AuthStyle:    oauth2.AuthStyleInParams,
+		EndpointParams: url.Values{
+			"audience": []string{"https://api.firebolt.io"},
+		},
+	}
+
+	// Return a new client implementation with the configured HTTP client
+	return &clientImpl{
+		apiBaseURL: apiBaseURL,
+		logger:     logger,
+		httpClient: authConfig.Client(ctx),
+	}, nil
+}
+
+type clientImpl struct {
+	apiBaseURL string
+	logger     *slog.Logger
+	httpClient *http.Client
+}
+
+func (c *clientImpl) ListAccounts(ctx context.Context) ([]Account, error) {
+
+	// Construct the URL for the myAccounts endpoint
+	myAccountsURL, err := url.JoinPath(c.apiBaseURL, myAccountsEndpoint)
+	if err != nil {
+		return nil, fmt.Errorf("could not create list accounts URL: %w", err)
+	}
+
+	// Create a new HTTP request with the constructed URL
+	request, err := http.NewRequestWithContext(ctx, http.MethodGet, myAccountsURL, nil)
+	if err != nil {
+		return nil, fmt.Errorf("failed to create HTTP request: %w", err)
+	}
+
+	// Perform the HTTP request
+	response, err := c.httpClient.Do(request)
+	if err != nil {
+		return nil, fmt.Errorf("failed to perform HTTP request: %w", err)
+	}
+	defer func() {
+
+		// Ensure the response body is fully read and closed
+		if _, err := io.Copy(io.Discard, response.Body); err != nil {
+			c.logger.Warn("failed to discard HTTP response body", "error", err)
+		}
+		if err := response.Body.Close(); err != nil {
+			c.logger.Warn("failed to close HTTP response body", "error", err)
+		}
+	}()
+
+	// Check if the response status code is OK
+	if response.StatusCode != http.StatusOK {
+		var responseText string
+		responseData, err := io.ReadAll(response.Body)
+		if err == nil {
+			responseText = string(responseData)
+		}
+		return nil, fmt.Errorf(
+			"unexpected response status code returned from Firebolt API: code - %d, responseText - %s",
+			response.StatusCode, responseText,
+		)
+	}
+
+	// Decode the response body JSON into a myAccountsResponse struct
+	var result myAccountsResponse
+	if err = json.NewDecoder(response.Body).Decode(&result); err != nil {
+		return nil, fmt.Errorf("failed to decode response body JSON: %w", err)
+	}
+
+	// Map the account names from the response
+	return result.Accounts, nil
+}
+
+// Account represents a Firebolt account with its name and region.
+type Account struct {
+	Name   string `json:"name"`
+	Region string `json:"region"`
+}
+
+type myAccountsResponse struct {
+	Accounts []Account `json:"accounts"`
+}
diff --git a/pkg/clients/discovery/client_test.go b/pkg/clients/discovery/client_test.go
new file mode 100644
index 0000000..eab5899
--- /dev/null
+++ b/pkg/clients/discovery/client_test.go
@@ -0,0 +1,284 @@
+package discovery_test
+
+import (
+	"context"
+	"encoding/json"
+	"net/http"
+	"net/http/httptest"
+	"testing"
+
+	"github.com/neilotoole/slogt"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+	"golang.org/x/oauth2"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/discovery"
+)
+
+const (
+	authTokenEndpoint  = "/oauth/token"
+	myAccountsEndpoint = "/myAccounts"
+)
+
+type myAccountsResponse struct {
+	Accounts []discovery.Account `json:"accounts"`
+}
+
+func TestListAccounts(t *testing.T) {
+
+	t.Run("successful response", func(t *testing.T) {
+
+		// Mock server
+		mockServer := newMockServer(t, nil, nil)
+		t.Cleanup(mockServer.Close)
+
+		// Create client
+		client, err := discovery.NewClient(
+			context.WithValue(t.Context(), oauth2.HTTPClient, mockServer.Client()),
+			slogt.New(t),
+			"test-client-id",
+			"test-client-secret",
+			mockServer.URL,
+			mockServer.URL,
+		)
+		require.NoError(t, err)
+
+		// Call ListAccounts
+		accounts, err := client.ListAccounts(t.Context())
+		require.NoError(t, err)
+
+		// Verify result
+		expectedAccounts := []discovery.Account{
+			{Name: "Account 1", Region: "us-east-1"},
+			{Name: "Account 2", Region: "eu-west-1"},
+		}
+		assert.Equal(t, expectedAccounts, accounts)
+	})
+
+	t.Run("error response", func(t *testing.T) {
+
+		// Mock server with error response for myAccounts endpoint
+		errorHandler := func(w http.ResponseWriter, r *http.Request) {
+			w.WriteHeader(http.StatusInternalServerError)
+			_, err := w.Write([]byte(`{"error": "server error"}`))
+			require.NoError(t, err)
+		}
+		mockServer := newMockServer(t, nil, errorHandler)
+		t.Cleanup(mockServer.Close)
+
+		// Create client
+		client, err := discovery.NewClient(
+			context.WithValue(t.Context(), oauth2.HTTPClient, mockServer.Client()),
+			slogt.New(t),
+			"test-client-id",
+			"test-client-secret",
+			mockServer.URL,
+			mockServer.URL,
+		)
+		require.NoError(t, err)
+
+		// Call ListAccounts - should fail
+		accounts, err := client.ListAccounts(t.Context())
+		assert.Error(t, err)
+		assert.Nil(t, accounts)
+		assert.Contains(t, err.Error(), "unexpected response status code")
+	})
+
+	t.Run("authentication error", func(t *testing.T) {
+
+		// Mock server with authentication error
+		authErrorHandler := func(w http.ResponseWriter, r *http.Request) {
+			w.WriteHeader(http.StatusUnauthorized)
+			_, err := w.Write([]byte(`{"error": "invalid_client", "error_description": "Client authentication failed"}`))
+			require.NoError(t, err)
+		}
+		mockServer := newMockServer(t, authErrorHandler, nil)
+		t.Cleanup(mockServer.Close)
+
+		// Create client
+		client, err := discovery.NewClient(
+			context.WithValue(t.Context(), oauth2.HTTPClient, mockServer.Client()),
+			slogt.New(t),
+			"invalid-client-id",
+			"invalid-client-secret",
+			mockServer.URL,
+			mockServer.URL,
+		)
+		require.NoError(t, err)
+
+		// Call ListAccounts - should fail due to authentication error
+		accounts, err := client.ListAccounts(t.Context())
+		assert.Error(t, err)
+		assert.Nil(t, accounts)
+		// oauth2 could have various error messages, so we don't check the exact error content
+	})
+
+	t.Run("invalid JSON response", func(t *testing.T) {
+
+		// Mock server with invalid JSON response
+		invalidJSONHandler := func(w http.ResponseWriter, r *http.Request) {
+			w.Header().Set("Content-Type", "application/json")
+			w.WriteHeader(http.StatusOK)
+			_, err := w.Write([]byte(`{"accounts": [{"name": "Account 1"`)) // Incomplete JSON
+			require.NoError(t, err)
+		}
+		mockServer := newMockServer(t, nil, invalidJSONHandler)
+		t.Cleanup(mockServer.Close)
+
+		// Create client
+		client, err := discovery.NewClient(
+			context.WithValue(t.Context(), oauth2.HTTPClient, mockServer.Client()),
+			slogt.New(t),
+			"test-client-id",
+			"test-client-secret",
+			mockServer.URL,
+			mockServer.URL,
+		)
+		require.NoError(t, err)
+
+		// Call ListAccounts - should fail due to invalid JSON
+		accounts, err := client.ListAccounts(t.Context())
+		assert.Error(t, err)
+		assert.Nil(t, accounts)
+		assert.Contains(t, err.Error(), "failed to decode response body JSON")
+	})
+
+	t.Run("context cancellation", func(t *testing.T) {
+
+		// Mock server with delay
+		slowHandler := func(w http.ResponseWriter, r *http.Request) {
+			// This handler deliberately does nothing and doesn't respond,
+			// which will cause the request to wait until context cancellation
+			select {
+			case <-r.Context().Done():
+				// Context was cancelled, we can return now
+				return
+			}
+		}
+		mockServer := newMockServer(t, nil, slowHandler)
+		t.Cleanup(mockServer.Close)
+
+		// Create client
+		client, err := discovery.NewClient(
+			context.WithValue(t.Context(), oauth2.HTTPClient, mockServer.Client()),
+			slogt.New(t),
+			"test-client-id",
+			"test-client-secret",
+			mockServer.URL,
+			mockServer.URL,
+		)
+		require.NoError(t, err)
+
+		// Create a context that is already cancelled
+		ctx, cancel := context.WithCancel(t.Context())
+		cancel() // Cancel immediately
+
+		// Call ListAccounts with cancelled context
+		accounts, err := client.ListAccounts(ctx)
+		assert.Error(t, err)
+		assert.Nil(t, accounts)
+		assert.Contains(t, err.Error(), "context canceled")
+	})
+
+	t.Run("server not available", func(t *testing.T) {
+
+		// Create a server and immediately close it to ensure the URL is unreachable
+		mockServer := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {}))
+		mockServer.Close() // Close immediately to make server unavailable
+
+		// Create client with URL that points to the closed server
+		client, err := discovery.NewClient(
+			t.Context(),
+			slogt.New(t),
+			"test-client-id",
+			"test-client-secret",
+			mockServer.URL,
+			mockServer.URL,
+		)
+		require.NoError(t, err)
+
+		// Call ListAccounts - should fail because server is not available
+		accounts, err := client.ListAccounts(t.Context())
+		assert.Error(t, err)
+		assert.Nil(t, accounts)
+		// Error message may vary based on system/network, so we don't check exact text
+	})
+}
+
+func TestNewClient(t *testing.T) {
+
+	t.Run("valid configuration", func(t *testing.T) {
+		client, err := discovery.NewClient(
+			t.Context(),
+			slogt.New(t),
+			"client-id",
+			"client-secret",
+			"https://auth.example.com",
+			"https://api.example.com",
+		)
+		require.NoError(t, err)
+		assert.NotNil(t, client)
+	})
+
+	t.Run("invalid auth URL", func(t *testing.T) {
+		client, err := discovery.NewClient(
+			t.Context(),
+			slogt.New(t),
+			"client-id",
+			"client-secret",
+			"://invalid-url", // Invalid URL
+			"https://api.example.com",
+		)
+		assert.Error(t, err)
+		assert.Nil(t, client)
+		assert.Contains(t, err.Error(), "could not create token URL")
+	})
+}
+
+func newMockServer(
+	t *testing.T,
+	customAuthHandler http.HandlerFunc,
+	customAccountsHandler http.HandlerFunc,
+) *httptest.Server {
+
+	return httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
+
+		// /auth/token endpoint
+		if r.Method == http.MethodPost && r.URL.Path == authTokenEndpoint {
+
+			if customAuthHandler != nil {
+				customAuthHandler(w, r)
+				return
+			}
+
+			// Return a successful response
+			w.Header().Set("Content-Type", "application/json")
+			_, err := w.Write([]byte(`{"access_token":"test-token","token_type":"bearer","expires_in":3600}`))
+			require.NoError(t, err)
+			return
+		}
+
+		// /myAccounts endpoint
+		if r.Method == http.MethodGet && r.URL.Path == myAccountsEndpoint {
+
+			if customAccountsHandler != nil {
+				customAccountsHandler(w, r)
+				return
+			}
+
+			// Return a successful response
+			response := myAccountsResponse{
+				Accounts: []discovery.Account{
+					{Name: "Account 1", Region: "us-east-1"},
+					{Name: "Account 2", Region: "eu-west-1"},
+				},
+			}
+			w.Header().Set("Content-Type", "application/json")
+			w.WriteHeader(http.StatusOK)
+			require.NoError(t, json.NewEncoder(w).Encode(response))
+			return
+		}
+
+		http.NotFound(w, r)
+	}))
+}
diff --git a/pkg/clients/discovery/discoverymock/client.go b/pkg/clients/discovery/discoverymock/client.go
new file mode 100644
index 0000000..f07bd72
--- /dev/null
+++ b/pkg/clients/discovery/discoverymock/client.go
@@ -0,0 +1,36 @@
+package discoverymock
+
+import (
+	"context"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/discovery"
+)
+
+var _ discovery.Client = &ClientMock{}
+
+// ClientMock is a mock implementation of the discovery.Client interface
+type ClientMock struct {
+	ListAccountsFunc  func(ctx context.Context) ([]discovery.Account, error)
+	ListAccountsCount int
+}
+
+// NewClientMock creates a new instance of ClientMock with default implementations
+func NewClientMock() *ClientMock {
+	return &ClientMock{
+		ListAccountsFunc: func(ctx context.Context) ([]discovery.Account, error) {
+			return []discovery.Account{}, nil
+		},
+	}
+}
+
+// ListAccounts implements the discovery.Client interface
+func (c *ClientMock) ListAccounts(ctx context.Context) ([]discovery.Account, error) {
+	c.ListAccountsCount++
+	return c.ListAccountsFunc(ctx)
+}
+
+// WithListAccountsFunc allows setting a custom ListAccounts function for testing
+func (c *ClientMock) WithListAccountsFunc(fn func(ctx context.Context) ([]discovery.Account, error)) *ClientMock {
+	c.ListAccountsFunc = fn
+	return c
+}
diff --git a/pkg/helpers/args/args.go b/pkg/helpers/args/args.go
new file mode 100644
index 0000000..6c099d9
--- /dev/null
+++ b/pkg/helpers/args/args.go
@@ -0,0 +1,70 @@
+package args
+
+import (
+	"errors"
+	"fmt"
+)
+
+// String retrieves a required string argument from the provided map.
+func String(arguments map[string]any, name string) (string, error) {
+
+	val, ok := arguments[name]
+	if !ok || val == nil {
+		return "", fmt.Errorf("required argument %s not provided", name)
+	}
+
+	str, ok := val.(string)
+	if !ok {
+		return "", fmt.Errorf("argument %s is not a string", name)
+	}
+
+	return str, nil
+}
+
+// MaybeString retrieves an optional string argument from the provided map.
+func MaybeString(arguments map[string]any, name string) (*string, error) {
+
+	val, ok := arguments[name]
+	if !ok || val == nil {
+		return nil, nil
+	}
+
+	str, ok := val.(string)
+	if !ok {
+		return nil, fmt.Errorf("argument %s is not a string", name)
+	}
+
+	return &str, nil
+}
+
+// Strings retrieves multiple required string arguments from the provided map.
+func Strings(arguments map[string]any, names ...string) ([]string, error) {
+
+	values := make([]string, len(names))
+	errs := make([]error, len(names))
+
+	for i, name := range names {
+		values[i], errs[i] = String(arguments, name)
+	}
+	if err := errors.Join(errs...); err != nil {
+		return nil, err
+	}
+
+	return values, nil
+}
+
+// MaybeStrings retrieves multiple optional string arguments from the provided map.
+func MaybeStrings(arguments map[string]any, names ...string) ([]*string, error) {
+
+	values := make([]*string, len(names))
+	errs := make([]error, len(names))
+
+	for i, name := range names {
+		values[i], errs[i] = MaybeString(arguments, name)
+	}
+	if err := errors.Join(errs...); err != nil {
+		return nil, err
+	}
+
+	return values, nil
+}
diff --git a/pkg/helpers/args/args_test.go b/pkg/helpers/args/args_test.go
new file mode 100644
index 0000000..797ffb9
--- /dev/null
+++ b/pkg/helpers/args/args_test.go
@@ -0,0 +1,89 @@
+package args
+
+import (
+	"testing"
+)
+
+func TestString(t *testing.T) {
+	args := map[string]any{
+		"key1": "value1",
+	}
+
+	val, err := String(args, "key1")
+	if err != nil {
+		t.Errorf("unexpected error: %v", err)
+	}
+	if val != "value1" {
+		t.Errorf("expected 'value1', got '%s'", val)
+	}
+
+	_, err = String(args, "key2")
+	if err == nil {
+		t.Errorf("expected error, got nil")
+	}
+}
+
+func TestMaybeString(t *testing.T) {
+	args := map[string]any{
+		"key1": "value1",
+	}
+
+	val, err := MaybeString(args, "key1")
+	if err != nil {
+		t.Errorf("unexpected error: %v", err)
+	}
+	if val == nil || *val != "value1" {
+		t.Errorf("expected 'value1', got '%v'", val)
+	}
+
+	val, err = MaybeString(args, "key2")
+	if err != nil {
+		t.Errorf("unexpected error: %v", err)
+	}
+	if val != nil {
+		t.Errorf("expected nil, got '%v'", val)
+	}
+}
+
+func TestStrings(t *testing.T) {
+	args := map[string]any{
+		"key1": "value1",
+		"key2": "value2",
+	}
+
+	vals, err := Strings(args, "key1", "key2")
+	if err != nil {
+		t.Errorf("unexpected error: %v", err)
+	}
+	if len(vals) != 2 || vals[0] != "value1" || vals[1] != "value2" {
+		t.Errorf("expected ['value1', 'value2'], got '%v'", vals)
+	}
+
+	_, err = Strings(args, "key1", "key3")
+	if err == nil {
+		t.Errorf("expected error, got nil")
+	}
+}
+
+func TestMaybeStrings(t *testing.T) {
+	args := map[string]any{
+		"key1": "value1",
+		"key2": "value2",
+	}
+
+	vals, err := MaybeStrings(args, "key1", "key2")
+	if err != nil {
+		t.Errorf("unexpected error: %v", err)
+	}
+	if len(vals) != 2 || *vals[0] != "value1" || *vals[1] != "value2" {
+		t.Errorf("expected ['value1', 'value2'], got '%v'", vals)
+	}
+
+	vals, err = MaybeStrings(args, "key1", "key3")
+	if err != nil {
+		t.Errorf("unexpected error: %v", err)
+	}
+	if len(vals) != 2 || *vals[0] != "value1" || vals[1] != nil {
+		t.Errorf("expected ['value1', nil], got '%v'", vals)
+	}
+}
diff --git a/pkg/helpers/itertools/map.go b/pkg/helpers/itertools/map.go
new file mode 100644
index 0000000..f1a068d
--- /dev/null
+++ b/pkg/helpers/itertools/map.go
@@ -0,0 +1,25 @@
+package itertools
+
+// Map transforms each element of a slice by applying a converter function to it.
+func Map[I, O any](inputs []I, converter func(I) O) []O {
+	outputs := make([]O, len(inputs))
+	for i, input := range inputs {
+		outputs[i] = converter(input)
+	}
+	return outputs
+}
+
+// MapWithFailure is the same as Map but takes a converter function which can return an error.
+// In the case that conversion returns an error the conversion process will be short circuited
+// and the error and an empty slice will be returned
+func MapWithFailure[I, O any](inputs []I, converter func(I) (O, error)) ([]O, error) {
+	outputs := make([]O, 0, len(inputs))
+	for _, input := range inputs {
+		o, err := converter(input)
+		if err != nil {
+			return nil, err
+		}
+		outputs = append(outputs, o)
+	}
+	return outputs, nil
+}
diff --git a/pkg/helpers/itertools/map_test.go b/pkg/helpers/itertools/map_test.go
new file mode 100644
index 0000000..0213c57
--- /dev/null
+++ b/pkg/helpers/itertools/map_test.go
@@ -0,0 +1,47 @@
+package itertools
+
+import (
+	"errors"
+	"testing"
+
+	"github.com/stretchr/testify/assert"
+)
+
+func TestMap(t *testing.T) {
+	inputs := []int{1, 2, 3, 4}
+	expected := []int{2, 4, 6, 8}
+	outputs := Map(inputs, func(i int) int {
+		return i * 2
+	})
+	assert.Equal(t, expected, outputs)
+}
+
+func TestMapWithFailure(t *testing.T) {
+	t.Run("successful conversion", func(t *testing.T) {
+		inputs := []int{1, 2, 3, 4}
+		expected := []string{"1", "2", "3", "4"}
+
+		outputs, err := MapWithFailure(inputs, func(i int) (string, error) {
+			return string(rune('0' + i)), nil
+		})
+
+		assert.NoError(t, err)
+		assert.Equal(t, expected, outputs)
+	})
+
+	t.Run("failed conversion", func(t *testing.T) {
+		inputs := []int{1, 2, 0, 4}
+		expectedErr := errors.New("cannot convert zero")
+
+		outputs, err := MapWithFailure(inputs, func(i int) (string, error) {
+			if i == 0 {
+				return "", expectedErr
+			}
+			return string(rune('0' + i)), nil
+		})
+
+		assert.Error(t, err)
+		assert.Equal(t, expectedErr, err)
+		assert.Nil(t, outputs)
+	})
+}
diff --git a/pkg/helpers/mimetype/mime_type.go b/pkg/helpers/mimetype/mime_type.go
new file mode 100644
index 0000000..471441c
--- /dev/null
+++ b/pkg/helpers/mimetype/mime_type.go
@@ -0,0 +1,6 @@
+package mimetype
+
+const (
+	JSON     = "application/json"
+	Markdown = "text/markdown"
+)
diff --git a/pkg/prompts/firebolt.go b/pkg/prompts/firebolt.go
new file mode 100644
index 0000000..eb06eb7
--- /dev/null
+++ b/pkg/prompts/firebolt.go
@@ -0,0 +1,38 @@
+package prompts
+
+import (
+	"context"
+	_ "embed"
+
+	"github.com/mark3labs/mcp-go/mcp"
+)
+
+//go:embed firebolt.md
+var fireboltMD string
+
+const fireboltPromptDescription = "Expert that can provide any assistance with Firebolt cloud data warehouse"
+
+type FireboltExpert struct {
+}
+
+func NewFireboltExpert() *FireboltExpert {
+	return &FireboltExpert{}
+}
+
+func (p *FireboltExpert) Prompt() mcp.Prompt {
+	return mcp.NewPrompt(
+		"Firebolt Expert",
+		mcp.WithPromptDescription(fireboltPromptDescription),
+	)
+}
+
+func (p *FireboltExpert) Handler(_ context.Context, _ mcp.GetPromptRequest) (*mcp.GetPromptResult, error) {
+
+	var messages []mcp.PromptMessage
+	messages = append(messages, mcp.NewPromptMessage(
+		mcp.RoleAssistant,
+		mcp.NewTextContent(fireboltMD),
+	))
+
+	return mcp.NewGetPromptResult(fireboltPromptDescription, messages), nil
+}
diff --git a/pkg/prompts/firebolt.md b/pkg/prompts/firebolt.md
new file mode 100644
index 0000000..dc072f3
--- /dev/null
+++ b/pkg/prompts/firebolt.md
@@ -0,0 +1,35 @@
+You are a helpful and knowledgeable assistant specializing in the Firebolt cloud data warehouse. Your goal is to help users with SQL queries, optimization, data modeling, and analytics. You are also an expert in Firebolt’s architecture, best practices, and core concepts. When answering user queries, your highest priority is correctness.
+
+**Guidelines:**
+
+1. **Accuracy and Correctness:**
+    - Always base your answers on the official Firebolt documentation and the provided overview context.
+    - If you are not completely sure about an answer or if the available information is insufficient, clearly suggest that the user consult Firebolt’s official documentation at [https://docs.firebolt.io](https://docs.firebolt.io).
+
+2. **Use of MCP Tools:**
+    - When users need detailed documentation or explanations, utilize the available MCP tools:
+        - **firebolt_docs**: Use this tool to get detailed articles about Firebolt’s architecture, concepts, and features.
+        - **firebolt_connect, firebolt_query**: Use these tools to interact with Firebolt and to execute SQL queries.
+    - Make sure to confirm the user’s request by checking whether you have sufficient documentation details before generating SQL or optimization advice.
+
+3. **SQL Generation and Optimization:**
+    - When generating SQL queries, follow best practices and Firebolt’s SQL guidelines.
+    - Provide explanations along with the generated SQL.
+    - If any assumptions are made in the query, clearly indicate them and invite the user to verify against the official docs.
+
+4. **Documentation and Explanation:**
+    - When explaining Firebolt concepts, use clear language and reference specific parts of the Firebolt documentation.
+    - If a user asks for more detail on a topic, fetch the relevant article using the **firebolt_docs** tool and provide a summary.
+    - Always encourage users to consult the full documentation for more in-depth information.
+
+5. **Handling Insufficient Information:**
+    - If the provided context or documentation is not sufficient to answer the query fully, notify the user and recommend visiting the Firebolt documentation for further details.
+
+6. **General Style:**
+    - Be concise, clear, and professional.
+    - Always prioritize correctness and factual accuracy over completeness if there is any risk of generating incorrect or “hallucinated” information.
+    - When in doubt, state that more detailed or updated information is available in the official Firebolt documentation.
+
+**Example Opening:**
+
+_"Hello, I'm your expert on Firebolt cloud data warehousing. I can help you with SQL query generation, optimization strategies, data modeling advice, and more. My responses are based on the latest Firebolt documentation and best practices."_
diff --git a/pkg/resources/accounts.go b/pkg/resources/accounts.go
new file mode 100644
index 0000000..679b3e9
--- /dev/null
+++ b/pkg/resources/accounts.go
@@ -0,0 +1,90 @@
+package resources
+
+import (
+	"context"
+	"encoding/json"
+	"fmt"
+
+	"github.com/mark3labs/mcp-go/mcp"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/discovery"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/args"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/itertools"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+)
+
+// AccountURI creates a formatted Firebolt account URI for a given account name.
+func AccountURI(name string) string {
+	return fmt.Sprintf("firebolt://accounts/%s", name)
+}
+
+// Accounts is a resource template handler for serving Firebolt account information.
+// It interacts with the discovery client to retrieve account data from the Firebolt service.
+type Accounts struct {
+	discoveryClient discovery.Client
+}
+
+// NewAccounts creates and returns a new instance of the Accounts resource handler
+// with the provided discovery client.
+func NewAccounts(discoveryClient discovery.Client) *Accounts {
+	return &Accounts{
+		discoveryClient: discoveryClient,
+	}
+}
+
+// ResourceTemplate defines the template for account resources.
+// It specifies the URI format, content type, description, and suggested usage.
+func (r *Accounts) ResourceTemplate() mcp.ResourceTemplate {
+	return mcp.NewResourceTemplate(
+		AccountURI("{account}"),
+		"Account",
+		mcp.WithTemplateMIMEType(mimetype.JSON),
+		mcp.WithTemplateAnnotations([]mcp.Role{mcp.RoleUser, mcp.RoleAssistant}, 0.9),
+		mcp.WithTemplateDescription("Brief information about the account in the Firebolt organization."),
+	)
+}
+
+// Handler processes resource requests for account information.
+// It extracts the account parameter and fetches the appropriate account data.
+func (r *Accounts) Handler(ctx context.Context, request mcp.ReadResourceRequest) ([]mcp.ResourceContents, error) {
+
+	accountName, err := args.String(request.Params.Arguments, "account")
+	if err != nil {
+		return nil, fmt.Errorf("bad request: %w", err)
+	}
+
+	return r.FetchAccountResources(ctx, accountName)
+}
+
+// FetchAccountResources retrieves account information from the Firebolt service.
+// If a specific account name is specified, it filters for that account; otherwise, it returns all accounts.
+func (r *Accounts) FetchAccountResources(ctx context.Context, accountName string) ([]mcp.ResourceContents, error) {
+
+	// Fetch the list of accounts from the discovery client
+	accounts, err := r.discoveryClient.ListAccounts(ctx)
+	if err != nil {
+		return nil, fmt.Errorf("failed to discover accounts: %w", err)
+	}
+
+	// Filter the accounts by name if needed
+	var filteredAccounts []discovery.Account
+	for _, account := range accounts {
+		if accountName == "" || accountName == account.Name {
+			filteredAccounts = append(filteredAccounts, account)
+		}
+	}
+
+	return itertools.MapWithFailure(filteredAccounts, func(i discovery.Account) (mcp.ResourceContents, error) {
+
+		data, err := json.Marshal(i)
+		if err != nil {
+			return mcp.TextResourceContents{}, fmt.Errorf("failed to marshal row data to JSON: %w", err)
+		}
+
+		return mcp.TextResourceContents{
+			URI:      AccountURI(i.Name),
+			MIMEType: mimetype.JSON,
+			Text:     string(data),
+		}, nil
+	})
+}
diff --git a/pkg/resources/accounts_test.go b/pkg/resources/accounts_test.go
new file mode 100644
index 0000000..3f644fc
--- /dev/null
+++ b/pkg/resources/accounts_test.go
@@ -0,0 +1,298 @@
+package resources_test
+
+import (
+	"context"
+	"encoding/json"
+	"errors"
+	"testing"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/discovery"
+	"github.com/firebolt-db/mcp-server/pkg/clients/discovery/discoverymock"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+	"github.com/firebolt-db/mcp-server/pkg/resources"
+)
+
+func TestAccountURI(t *testing.T) {
+	tests := []struct {
+		name     string
+		account  string
+		expected string
+	}{
+		{
+			name:     "basic case",
+			account:  "test-account",
+			expected: "firebolt://accounts/test-account",
+		},
+		{
+			name:     "with special characters",
+			account:  "test.account",
+			expected: "firebolt://accounts/test.account",
+		},
+		{
+			name:     "empty value",
+			account:  "",
+			expected: "firebolt://accounts/",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			result := resources.AccountURI(tt.account)
+			assert.Equal(t, tt.expected, result)
+		})
+	}
+}
+
+func TestNewAccounts(t *testing.T) {
+	client := discoverymock.NewClientMock()
+	accounts := resources.NewAccounts(client)
+	assert.NotNil(t, accounts)
+}
+
+func TestAccounts_ResourceTemplate(t *testing.T) {
+
+	client := discoverymock.NewClientMock()
+	accounts := resources.NewAccounts(client)
+	template := accounts.ResourceTemplate()
+
+	assert.NotEmpty(t, template.Name)
+	assert.NotEmpty(t, template.URITemplate)
+	assert.NotEmpty(t, template.MIMEType)
+	assert.NotEmpty(t, template.Description)
+}
+
+func TestAccounts_Handler(t *testing.T) {
+	tests := []struct {
+		name          string
+		params        map[string]any
+		mockSetup     func(*discoverymock.ClientMock)
+		expected      []discovery.Account
+		expectedError string
+	}{
+		{
+			name: "successful request",
+			params: map[string]any{
+				"account": "test-account",
+			},
+			mockSetup: func(client *discoverymock.ClientMock) {
+				client.WithListAccountsFunc(func(ctx context.Context) ([]discovery.Account, error) {
+					return []discovery.Account{
+						{
+							Name:   "test-account",
+							Region: "us-east-1",
+						},
+					}, nil
+				})
+			},
+			expected: []discovery.Account{
+				{
+					Name:   "test-account",
+					Region: "us-east-1",
+				},
+			},
+		},
+		{
+			name:   "missing account parameter",
+			params: map[string]any{
+				// No account parameter
+			},
+			expectedError: "bad request: required argument account not provided",
+		},
+		{
+			name: "discovery client error",
+			params: map[string]any{
+				"account": "test-account",
+			},
+			mockSetup: func(client *discoverymock.ClientMock) {
+				client.WithListAccountsFunc(func(ctx context.Context) ([]discovery.Account, error) {
+					return nil, errors.New("discovery error")
+				})
+			},
+			expectedError: "failed to discover accounts: discovery error",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			client := discoverymock.NewClientMock()
+
+			if tt.mockSetup != nil {
+				tt.mockSetup(client)
+			}
+
+			accounts := resources.NewAccounts(client)
+
+			request := mcp.ReadResourceRequest{}
+			request.Params.Arguments = tt.params
+
+			result, err := accounts.Handler(t.Context(), request)
+
+			if tt.expectedError != "" {
+				assert.Error(t, err)
+				assert.Contains(t, err.Error(), tt.expectedError)
+				return
+			}
+
+			require.NoError(t, err)
+			require.Len(t, result, len(tt.expected))
+
+			for i, res := range result {
+				textRes, ok := res.(mcp.TextResourceContents)
+				require.True(t, ok, "Expected TextResourceContents")
+
+				var data discovery.Account
+				err := json.Unmarshal([]byte(textRes.Text), &data)
+				require.NoError(t, err)
+
+				assert.Equal(t, tt.expected[i], data)
+				assert.Equal(t, resources.AccountURI(data.Name), textRes.URI)
+				assert.Equal(t, mimetype.JSON, textRes.MIMEType)
+			}
+
+			assert.Equal(t, 1, client.ListAccountsCount, "ListAccounts should be called exactly once")
+		})
+	}
+}
+
+func TestAccounts_FetchAccountResources(t *testing.T) {
+	tests := []struct {
+		name          string
+		accountName   string
+		mockSetup     func(*discoverymock.ClientMock)
+		expected      []discovery.Account
+		expectedError string
+	}{
+		{
+			name:        "fetch specific account",
+			accountName: "test-account",
+			mockSetup: func(client *discoverymock.ClientMock) {
+				client.WithListAccountsFunc(func(ctx context.Context) ([]discovery.Account, error) {
+					return []discovery.Account{
+						{
+							Name:   "test-account",
+							Region: "us-east-1",
+						},
+						{
+							Name:   "other-account",
+							Region: "eu-west-1",
+						},
+					}, nil
+				})
+			},
+			expected: []discovery.Account{
+				{
+					Name:   "test-account",
+					Region: "us-east-1",
+				},
+			},
+		},
+		{
+			name:        "fetch all accounts",
+			accountName: "",
+			mockSetup: func(client *discoverymock.ClientMock) {
+				client.WithListAccountsFunc(func(ctx context.Context) ([]discovery.Account, error) {
+					return []discovery.Account{
+						{
+							Name:   "account-1",
+							Region: "us-east-1",
+						},
+						{
+							Name:   "account-2",
+							Region: "eu-west-1",
+						},
+					}, nil
+				})
+			},
+			expected: []discovery.Account{
+				{
+					Name:   "account-1",
+					Region: "us-east-1",
+				},
+				{
+					Name:   "account-2",
+					Region: "eu-west-1",
+				},
+			},
+		},
+		{
+			name:        "no matching accounts",
+			accountName: "non-existent-account",
+			mockSetup: func(client *discoverymock.ClientMock) {
+				client.WithListAccountsFunc(func(ctx context.Context) ([]discovery.Account, error) {
+					return []discovery.Account{
+						{
+							Name:   "account-1",
+							Region: "us-east-1",
+						},
+					}, nil
+				})
+			},
+			expected: []discovery.Account{}, // Empty result since no accounts match
+		},
+		{
+			name:        "json marshaling error test",
+			accountName: "test-account",
+			mockSetup: func(client *discoverymock.ClientMock) {
+				client.WithListAccountsFunc(func(ctx context.Context) ([]discovery.Account, error) {
+					// Create a custom type that will cause JSON marshaling to fail
+					// This is a bit tricky to test directly in Go, so we'll simulate by returning accounts
+					// and rely on test coverage for the error path
+					return []discovery.Account{
+						{
+							Name:   "test-account",
+							Region: "us-east-1",
+						},
+					}, nil
+				})
+			},
+			expected: []discovery.Account{
+				{
+					Name:   "test-account",
+					Region: "us-east-1",
+				},
+			},
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			client := discoverymock.NewClientMock()
+
+			if tt.mockSetup != nil {
+				tt.mockSetup(client)
+			}
+
+			accounts := resources.NewAccounts(client)
+
+			result, err := accounts.FetchAccountResources(t.Context(), tt.accountName)
+
+			if tt.expectedError != "" {
+				assert.Error(t, err)
+				assert.Contains(t, err.Error(), tt.expectedError)
+				return
+			}
+
+			require.NoError(t, err)
+			require.Len(t, result, len(tt.expected))
+
+			for i, res := range result {
+				textRes, ok := res.(mcp.TextResourceContents)
+				require.True(t, ok, "Expected TextResourceContents")
+
+				var data discovery.Account
+				err := json.Unmarshal([]byte(textRes.Text), &data)
+				require.NoError(t, err)
+
+				assert.Equal(t, tt.expected[i], data)
+				assert.Equal(t, resources.AccountURI(data.Name), textRes.URI)
+				assert.Equal(t, mimetype.JSON, textRes.MIMEType)
+			}
+
+			assert.Equal(t, 1, client.ListAccountsCount, "ListAccounts should be called exactly once")
+		})
+	}
+}
diff --git a/pkg/resources/databases.go b/pkg/resources/databases.go
new file mode 100644
index 0000000..0a3efa5
--- /dev/null
+++ b/pkg/resources/databases.go
@@ -0,0 +1,100 @@
+package resources
+
+import (
+	"context"
+	"encoding/json"
+	"fmt"
+
+	"github.com/mark3labs/mcp-go/mcp"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/args"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/itertools"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+)
+
+// DatabaseURI creates a formatted Firebolt database URI for a given account and database name.
+func DatabaseURI(account, database string) string {
+	return fmt.Sprintf("firebolt://accounts/%s/databases/%s", account, database)
+}
+
+// Databases is a resource template handler for serving Firebolt database information.
+type Databases struct {
+	dbPool database.Pool
+}
+
+// NewDatabases creates and returns a new instance of the Databases resource handler.
+func NewDatabases(dbPool database.Pool) *Databases {
+	return &Databases{
+		dbPool: dbPool,
+	}
+}
+
+// ResourceTemplate defines the template for database resources.
+// It specifies the URI format, content type, description, and suggested usage.
+func (r *Databases) ResourceTemplate() mcp.ResourceTemplate {
+	return mcp.NewResourceTemplate(
+		DatabaseURI("{account}", "{database}"),
+		"Database",
+		mcp.WithTemplateMIMEType(mimetype.JSON),
+		mcp.WithTemplateAnnotations([]mcp.Role{mcp.RoleUser, mcp.RoleAssistant}, 0.8),
+		mcp.WithTemplateDescription("Brief information about the database in the Firebolt account."),
+	)
+}
+
+// Handler processes resource requests for database information.
+// It extracts account and database parameters and fetches the appropriate database data.
+func (r *Databases) Handler(ctx context.Context, request mcp.ReadResourceRequest) ([]mcp.ResourceContents, error) {
+
+	values, err := args.Strings(request.Params.Arguments, "account", "database")
+	if err != nil {
+		return nil, fmt.Errorf("bad request: %w", err)
+	}
+
+	return r.FetchDatabaseResources(ctx, values[0], values[1])
+}
+
+// FetchDatabaseResources retrieves database information from the Firebolt service.
+// If a specific database is specified, it filters for that database; otherwise, it returns all databases.
+func (r *Databases) FetchDatabaseResources(ctx context.Context, account, dbName string) ([]mcp.ResourceContents, error) {
+
+	// Acquire a connection to the database
+	conn, err := r.dbPool.GetConnection(database.PoolParams{
+		AccountName: account,
+	})
+	if err != nil {
+		return nil, fmt.Errorf("failed to acquire database connection: %w", err)
+	}
+
+	// Prepare the SQL query
+	var (
+		sql  = "SELECT database_name, description FROM information_schema.databases"
+		args []any
+	)
+	if dbName != "" {
+		sql += " WHERE database_name = ?"
+		args = append(args, dbName)
+	}
+
+	// Query database
+	rows, err := conn.Query(ctx, sql, args...)
+	if err != nil {
+		return nil, fmt.Errorf("failed to query database: %w", err)
+	}
+
+	// Convert rows to resources
+	return itertools.MapWithFailure(rows, func(i map[string]any) (mcp.ResourceContents, error) {
+
+		i["account_name"] = account
+		data, err := json.Marshal(i)
+		if err != nil {
+			return mcp.TextResourceContents{}, fmt.Errorf("failed to marshal row data to JSON: %w", err)
+		}
+
+		return mcp.TextResourceContents{
+			URI:      DatabaseURI(account, i["database_name"].(string)),
+			MIMEType: mimetype.JSON,
+			Text:     string(data),
+		}, nil
+	})
+}
diff --git a/pkg/resources/databases_test.go b/pkg/resources/databases_test.go
new file mode 100644
index 0000000..fd13037
--- /dev/null
+++ b/pkg/resources/databases_test.go
@@ -0,0 +1,307 @@
+package resources_test
+
+import (
+	"context"
+	"encoding/json"
+	"errors"
+	"testing"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+	"github.com/firebolt-db/mcp-server/pkg/clients/database/databasemock"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+	"github.com/firebolt-db/mcp-server/pkg/resources"
+)
+
+func TestDatabaseURI(t *testing.T) {
+	tests := []struct {
+		name     string
+		account  string
+		database string
+		expected string
+	}{
+		{
+			name:     "basic case",
+			account:  "test-account",
+			database: "test-database",
+			expected: "firebolt://accounts/test-account/databases/test-database",
+		},
+		{
+			name:     "with special characters",
+			account:  "test.account",
+			database: "test-database-123",
+			expected: "firebolt://accounts/test.account/databases/test-database-123",
+		},
+		{
+			name:     "empty values",
+			account:  "",
+			database: "",
+			expected: "firebolt://accounts//databases/",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			result := resources.DatabaseURI(tt.account, tt.database)
+			assert.Equal(t, tt.expected, result)
+		})
+	}
+}
+
+func TestNewDatabases(t *testing.T) {
+	pool := databasemock.NewPoolMock()
+	databases := resources.NewDatabases(pool)
+	assert.NotNil(t, databases)
+}
+
+func TestDatabases_ResourceTemplate(t *testing.T) {
+	pool := databasemock.NewPoolMock()
+	databases := resources.NewDatabases(pool)
+	assert.NotEmpty(t, databases.ResourceTemplate())
+}
+
+func TestDatabases_Handler(t *testing.T) {
+	tests := []struct {
+		name          string
+		params        map[string]any
+		mockSetup     func(*databasemock.PoolMock, *databasemock.ConnectionMock)
+		expected      []map[string]any
+		expectedError string
+	}{
+		{
+			name: "successful request",
+			params: map[string]any{
+				"account":  "test-account",
+				"database": "test-database",
+			},
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					assert.Equal(t, "SELECT database_name, description FROM information_schema.databases WHERE database_name = ?", sql)
+					assert.Equal(t, []any{"test-database"}, args)
+					return []map[string]any{
+						{
+							"database_name": "test-database",
+							"description":   "Test database description",
+						},
+					}, nil
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expected: []map[string]any{
+				{
+					"account_name":  "test-account",
+					"database_name": "test-database",
+					"description":   "Test database description",
+				},
+			},
+		},
+		{
+			name: "missing account parameter",
+			params: map[string]any{
+				"database": "test-database",
+			},
+			expectedError: "bad request: required argument account not provided",
+		},
+		{
+			name: "missing database parameter",
+			params: map[string]any{
+				"account": "test-account",
+			},
+			expectedError: "bad request: required argument database not provided",
+		},
+		{
+			name: "database connection error",
+			params: map[string]any{
+				"account":  "test-account",
+				"database": "test-database",
+			},
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				pool.WithGetConnectionFunc(func(params database.PoolParams) (database.Connection, error) {
+					return nil, errors.New("connection error")
+				})
+			},
+			expectedError: "failed to acquire database connection: connection error",
+		},
+		{
+			name: "query execution error",
+			params: map[string]any{
+				"account":  "test-account",
+				"database": "test-database",
+			},
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					return nil, errors.New("query error")
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expectedError: "failed to query database: query error",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			pool := databasemock.NewPoolMock()
+			conn := databasemock.NewConnectionMock()
+
+			if tt.mockSetup != nil {
+				tt.mockSetup(pool, conn)
+			}
+
+			databases := resources.NewDatabases(pool)
+
+			request := mcp.ReadResourceRequest{}
+			request.Params.Arguments = tt.params
+
+			result, err := databases.Handler(t.Context(), request)
+
+			if tt.expectedError != "" {
+				assert.Error(t, err)
+				assert.Contains(t, err.Error(), tt.expectedError)
+				return
+			}
+
+			require.NoError(t, err)
+			require.Len(t, result, len(tt.expected))
+
+			for i, res := range result {
+				textRes, ok := res.(mcp.TextResourceContents)
+				require.True(t, ok, "Expected TextResourceContents")
+
+				var data map[string]any
+				err := json.Unmarshal([]byte(textRes.Text), &data)
+				require.NoError(t, err)
+
+				assert.Equal(t, tt.expected[i], data)
+				assert.Equal(t, resources.DatabaseURI("test-account", data["database_name"].(string)), textRes.URI)
+				assert.Equal(t, mimetype.JSON, textRes.MIMEType)
+			}
+		})
+	}
+}
+
+func TestDatabases_FetchDatabaseResources(t *testing.T) {
+	tests := []struct {
+		name          string
+		account       string
+		database      string
+		mockSetup     func(*databasemock.PoolMock, *databasemock.ConnectionMock)
+		expected      []map[string]any
+		expectedError string
+	}{
+		{
+			name:     "fetch specific database",
+			account:  "test-account",
+			database: "test-database",
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					assert.Equal(t, "SELECT database_name, description FROM information_schema.databases WHERE database_name = ?", sql)
+					assert.Equal(t, []any{"test-database"}, args)
+					return []map[string]any{
+						{
+							"database_name": "test-database",
+							"description":   "Production database",
+						},
+					}, nil
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expected: []map[string]any{
+				{
+					"account_name":  "test-account",
+					"database_name": "test-database",
+					"description":   "Production database",
+				},
+			},
+		},
+		{
+			name:     "fetch all databases",
+			account:  "test-account",
+			database: "",
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					assert.Equal(t, "SELECT database_name, description FROM information_schema.databases", sql)
+					assert.Empty(t, args)
+					return []map[string]any{
+						{
+							"database_name": "database-1",
+							"description":   "First database",
+						},
+						{
+							"database_name": "database-2",
+							"description":   "Second database",
+						},
+					}, nil
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expected: []map[string]any{
+				{
+					"account_name":  "test-account",
+					"database_name": "database-1",
+					"description":   "First database",
+				},
+				{
+					"account_name":  "test-account",
+					"database_name": "database-2",
+					"description":   "Second database",
+				},
+			},
+		},
+		{
+			name:     "json marshaling error",
+			account:  "test-account",
+			database: "test-database",
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					return []map[string]any{
+						{
+							"database_name": make(chan int), // Channels are not JSON-serializable
+						},
+					}, nil
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expectedError: "failed to marshal row data to JSON",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			pool := databasemock.NewPoolMock()
+			conn := databasemock.NewConnectionMock()
+
+			if tt.mockSetup != nil {
+				tt.mockSetup(pool, conn)
+			}
+
+			databases := resources.NewDatabases(pool)
+
+			result, err := databases.FetchDatabaseResources(t.Context(), tt.account, tt.database)
+
+			if tt.expectedError != "" {
+				assert.Error(t, err)
+				assert.Contains(t, err.Error(), tt.expectedError)
+				return
+			}
+
+			require.NoError(t, err)
+			require.Len(t, result, len(tt.expected))
+
+			for i, res := range result {
+				textRes, ok := res.(mcp.TextResourceContents)
+				require.True(t, ok, "Expected TextResourceContents")
+
+				var data map[string]any
+				err := json.Unmarshal([]byte(textRes.Text), &data)
+				require.NoError(t, err)
+
+				assert.Equal(t, tt.expected[i], data)
+				assert.Equal(t, resources.DatabaseURI(tt.account, data["database_name"].(string)), textRes.URI)
+				assert.Equal(t, mimetype.JSON, textRes.MIMEType)
+			}
+		})
+	}
+}
diff --git a/pkg/resources/docs.go b/pkg/resources/docs.go
new file mode 100644
index 0000000..9ee601a
--- /dev/null
+++ b/pkg/resources/docs.go
@@ -0,0 +1,137 @@
+package resources
+
+import (
+	"context"
+	_ "embed"
+	"fmt"
+	"io/fs"
+	"strings"
+
+	"github.com/mark3labs/mcp-go/mcp"
+
+	"github.com/firebolt-db/mcp-server/pkg/helpers/args"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+)
+
+// Special articles used by this MCP server.
+const (
+	DocsArticleOverview  = "mcp/overview.md"
+	DocsArticleProof     = "mcp/proof.md"
+	DocsArticleReference = "mcp/reference.md"
+)
+
+//go:embed docs_overview.md
+var docsOverviewMD string
+
+//go:embed docs_proof.md
+var docsProofMD string
+
+//go:embed docs_reference.md
+var docsReferenceMD string
+
+// DocsURI creates a formatted Firebolt documentation URI for a given article.
+func DocsURI(article string) string {
+	return fmt.Sprintf("firebolt://docs/%s", article)
+}
+
+// DocsFS is an interface that combines the ReadDirFS and ReadFileFS interfaces.
+type DocsFS interface {
+	fs.ReadDirFS
+	fs.ReadFileFS
+}
+
+// Docs is a resource template handler for serving Firebolt documentation articles.
+type Docs struct {
+	docsFS      DocsFS
+	proofSecret string
+}
+
+// NewDocs creates and returns a new instance of the Docs.
+func NewDocs(docsFS DocsFS, proofSecret string) *Docs {
+	return &Docs{
+		docsFS:      docsFS,
+		proofSecret: proofSecret,
+	}
+}
+
+// ResourceTemplate defines the template for documentation resources.
+// It specifies the URI format, content type, description, and suggested usage.
+func (r *Docs) ResourceTemplate() mcp.ResourceTemplate {
+	return mcp.NewResourceTemplate(
+		DocsURI("{article}"),
+		"Documentation article",
+		mcp.WithTemplateMIMEType(mimetype.Markdown),
+		mcp.WithTemplateDescription("An article that offers insights into a particular topic related to Firebolt."),
+		mcp.WithTemplateAnnotations([]mcp.Role{mcp.RoleUser, mcp.RoleAssistant}, 0.5),
+	)
+}
+
+// Handler processes resource requests for documentation articles.
+// It extracts the article parameter and fetches the appropriate documentation content.
+func (r *Docs) Handler(ctx context.Context, request mcp.ReadResourceRequest) ([]mcp.ResourceContents, error) {
+
+	// Extract the article name from the request parameters
+	value, err := args.String(request.Params.Arguments, "article")
+	if err != nil {
+		return nil, fmt.Errorf("bad request: %w", err)
+	}
+
+	return r.FetchDocsResources(ctx, value)
+}
+
+// FetchDocsResources retrieves the content for a specified documentation article.
+// It handles special articles (overview, reference) and regular documentation files.
+func (r *Docs) FetchDocsResources(_ context.Context, article string) ([]mcp.ResourceContents, error) {
+
+	switch article {
+
+	case DocsArticleOverview:
+
+		// Return the pre-embedded overview markdown content
+		return r.newResource(article, docsOverviewMD)
+
+	case DocsArticleProof:
+
+		// Return the pre-embedded proof markdown content
+		return r.newResource(article, fmt.Sprintf(docsProofMD, r.proofSecret))
+
+	case DocsArticleReference:
+
+		// Retrieve a list of available docs files
+		entries, err := r.docsFS.ReadDir(".")
+		if err != nil {
+			return nil, fmt.Errorf("failed to read docs directory: %w", err)
+		}
+
+		// Build a Markdown list of available files
+		b := &strings.Builder{}
+		for _, entry := range entries {
+			if entry.IsDir() || !strings.HasSuffix(entry.Name(), ".md") {
+				continue
+			}
+			b.WriteString("- " + entry.Name() + "\n")
+		}
+
+		// Combine the reference template with the generated file list
+		return r.newResource(article, docsReferenceMD+b.String())
+
+	default:
+
+		// For other articles, read the file directly from the filesystem
+		fileData, err := r.docsFS.ReadFile(article)
+		if err != nil {
+			return nil, fmt.Errorf("failed to read file %s: %w", article, err)
+		}
+
+		return r.newResource(article, string(fileData))
+	}
+}
+
+// newResource creates a properly formatted resource contents object for a documentation article.
+func (r *Docs) newResource(article, content string) ([]mcp.ResourceContents, error) {
+	return []mcp.ResourceContents{&mcp.TextResourceContents{
+		URI:      DocsURI(article),
+		MIMEType: mimetype.Markdown,
+		Text:     content,
+	}}, nil
+}
diff --git a/pkg/resources/docs_overview.md b/pkg/resources/docs_overview.md
new file mode 100644
index 0000000..d97af80
--- /dev/null
+++ b/pkg/resources/docs_overview.md
@@ -0,0 +1,208 @@
+# Firebolt Foundational Knowledge Layer
+
+This document provides a foundational overview of Firebolt, designed to help an LLM learn its core concepts and capabilities effectively and responsibly. The focus is on *how to learn* Firebolt, leveraging its introspection capabilities and official documentation, rather than memorizing static details.
+
+**Model Behavior Guidelines:**
+
+* If you lack sufficient information to answer a user's question with high confidence, state: *"Please consult the official Firebolt documentation at https://docs.firebolt.io for more details."*
+* **Never** hallucinate function names, table structures, SQL syntax, or other technical details. When unsure, refer to the official documentation or indicate the need for it.
+
+---
+
+## 1. Firebolt Architecture Overview
+
+Firebolt is a cloud data warehouse optimized for high performance, low latency, and scalability, particularly for data-intensive applications.
+
+* **Key Differentiator:** Efficiency and low cost at scale.
+* **Designed For:** Addressing high latency, poor concurrency performance, and scaling challenges in data processing and retrieval.
+* **Core Principles:** High efficiency (price-to-performance), concurrency at scale, elasticity, and SQL simplicity.
+
+*(To understand the detailed architecture, consult the Firebolt documentation sections on Architecture Overview.)*
+
+## 2. Decoupled Storage and Compute
+
+Firebolt's architecture separates storage from compute resources.
+
+* **Storage:** Managed via cloud storage (Amazon S3 supported), optimized for large datasets using techniques like compression and sparse indexing. Data is organized within **Databases** (also referred to as Catalogs), which logically contain schemas, tables, views, and indexes.
+* **Compute (Engines):** Independent compute clusters (Engines) process queries. Engines can be started, stopped, and resized dynamically.
+  * **Database Access:** Any active engine can access data from any database within the same account, highlighting the decoupling. This allows different engines (perhaps sized differently for specific workloads) to operate on the same underlying data.
+  * **Multi-dimensional Elasticity:** Engines can scale independently:
+    * **Vertically:** Increase node capacity (e.g., S, M, L, XL node types).
+    * **Horizontally:** Increase the number of nodes within a cluster.
+    * **Concurrently:** Increase the number of clusters within an engine (auto-scaling is supported in Enterprise editions).
+  * **Workload Isolation:** Compute resources are isolated per engine, preventing interference between different workloads (e.g., ELT vs. BI) even when accessing the same database.
+
+*(To learn more about engine configuration and operation, query `information_schema.engines` or refer to the Engine Fundamentals and Operate Engines guides in the docs. To list databases, query `information_schema.databases` or `information_schema.catalogs`.)*
+
+## 3. Organizations, Accounts, Logins & Service Accounts, Users
+
+Firebolt uses a hierarchical model for managing access and resources.
+
+* **Organization:** The top-level entity, typically representing a company. Organization names are globally unique and based on the domain name used during registration. Manages billing and global settings like Logins and Service Accounts.
+* **Account:** A container within an Organization, often used to isolate environments (dev, staging, prod) or departments. Each account exists in a specific AWS region. Holds regional resources like Databases, Engines, Users, and Roles.
+  *(To list accounts, query `information_schema.accounts`. To manage accounts, use `CREATE ACCOUNT`, `ALTER ACCOUNT`, `DROP ACCOUNT`.)*
+* **Login:** Represents a human person, identified by an email address. Used for authentication via credentials or SSO. Managed at the Organization level. Must be associated with a User at the Account level.
+  *(To list logins, query `information_schema.logins`. To manage logins, use `CREATE LOGIN`, `ALTER LOGIN`, `DROP LOGIN`.)*
+* **Service Account:** Represents a machine or application for programmatic access. Uses an ID and Secret for authentication. Managed at the Organization level. Must be associated with a User at the Account level.
+  *(To list service accounts, query `information_schema.service_accounts`. To manage service accounts, use `CREATE SERVICE ACCOUNT`, `ALTER SERVICE ACCOUNT`, `DROP SERVICE ACCOUNT`. Use `CALL fb_GENERATESERVICEACCOUNTKEY` to manage secrets.)*
+* **User:** An identity within a specific Account that interacts with Firebolt. Must be linked to **either** a Login or a Service Account. Roles are assigned to Users to grant permissions. Managed at the Account level.
+  *(To list users, query `information_schema.users`. To manage users, use `CREATE USER`, `ALTER USER`, `DROP USER`.)*
+
+## 4. Security and Access Control
+
+Firebolt employs a multi-layered security approach.
+
+* **Network Security:**
+  * End-to-end encryption using TLS 1.2.
+  * Network Policies allow defining allowed/blocked IP ranges at the organization, login, or service account level.
+    *(To manage network policies, use `CREATE NETWORK POLICY`, `ALTER NETWORK POLICY`, `DROP NETWORK POLICY`. Query `information_schema.network_policies` to view.)*
+  * Supports AWS PrivateLink for secure connections without exposing traffic to the public internet.
+* **Identity Management:**
+  * Uses Auth0 for identity management.
+  * Supports username/password authentication, Single Sign-On (SSO), and Multi-Factor Authentication (MFA).
+* **Access Control (RBAC):**
+  * Permissions are managed via Roles assigned to Users.
+  * Follows the principle of least privilege.
+  * Includes system roles (`public`, `account_admin`, `organization_admin`) and allows creation of custom roles.
+  * Permissions are hierarchical (e.g., database USAGE grants access to objects within).
+  * Supports object Ownership, where the creator gains full control.
+    *(Use `GRANT` and `REVOKE` to manage permissions. Query `information_schema.object_privileges`, `information_schema.enabled_roles`, `information_schema.applicable_roles` to view.)*
+* **Data Protection:**
+  * Data at rest is encrypted using Amazon S3-managed keys or AWS KMS keys.
+  * Data in motion is encrypted end-to-end (TLS 1.2).
+  * Supports HIPAA compliance.
+
+## 5. Data Modeling and Performance Optimization
+
+Firebolt stores data in a compressed columnar format within internal objects called tablets. Effective data modeling is crucial for performance.
+
+* **Table Types:**
+  * **Fact Tables:** Store large volumes of quantitative/event data. Distributed across engine nodes. (Default type for `CREATE TABLE`)
+  * **Dimension Tables:** Store descriptive attributes. Often smaller and replicated across engine nodes for faster joins. Use `CREATE DIMENSION TABLE`.
+  * **External Tables:** Reference data in S3 without loading it into Firebolt. Used primarily for ingestion. Use `CREATE EXTERNAL TABLE`.
+* **Partitioning:** Tables can be partitioned (e.g., by date) to improve query performance by allowing the engine to scan only relevant partitions (partition pruning). Use `PARTITION BY` in `CREATE TABLE`.
+  *(Use functions like `DATE_TRUNC`, `TO_YYYYMM`, `TO_YYYYMMDD`, `EXTRACT` for partition keys.)*
+* **Optimization:**
+  * **VACUUM:** Reclaims storage from deleted/updated rows and optimizes tablet structure. Can be run manually or occurs automatically in the background.
+  * **Data Pruning:** Firebolt uses index metadata to skip scanning irrelevant data ranges (data pruning) and tablets (tablet pruning). Partitioning adds partition pruning.
+
+*(To learn how to design tables and indexes, refer to the Data Modeling and Using Indexes sections in the documentation.)*
+
+## 6. Indexes and Best Practices
+
+Indexes are critical for query performance in Firebolt.
+
+* **Primary Index:**
+  * Sorts data within tablets based on specified columns. Essential for efficient data pruning.
+  * Defined at table creation using `PRIMARY INDEX <col1>, [<col2>...]`. Cannot be altered later.
+  * **Best Practices:** Order columns by selectivity (highest cardinality first); include columns frequently used in `WHERE`, `JOIN`, `GROUP BY` clauses; use columns directly in filters without transformations.
+  * *(Refer to the Primary Index documentation for details.)*
+* **Aggregating Index:**
+  * Precomputes and stores results of aggregate functions (`SUM`, `COUNT`, `AVG`, etc.).
+  * Defined using `CREATE AGGREGATING INDEX ... ON ... (<grouping_cols...>, <aggregations...>)`. Can be added/dropped after table creation.
+  * Automatically maintained upon data changes (`INSERT`, `UPDATE`, `DELETE`).
+  * Queries automatically use the index if the `GROUP BY` clause and aggregations match the index definition.
+  * **Best Practices:** Define for frequently run aggregation queries; include all necessary grouping columns and measures; place low-cardinality columns first in the grouping key definition.
+  * *(Use `EXPLAIN` to verify index usage. Refer to the Aggregating Index documentation for details.)*
+* **Index Granularity:** Advanced setting (`index_granularity` in `CREATE TABLE WITH (...)`) controls the number of rows per index range (default 8192). Smaller values may improve highly selective queries but increase memory usage.
+* **Recommendation Engine:** Use `CALL recommend_ddl(<table_name>, (<select_query_workload>))` to get suggestions for primary index and partitioning based on query history.
+
+## 7. Available Views in `information_schema`
+
+The `information_schema` database provides read-only views containing metadata about your Firebolt organization and accounts. Query these views to understand your environment.
+
+* **Organization Level:**
+  * `information_schema.accounts`: Lists accounts within the organization.
+  * `information_schema.logins`: Lists logins (human users) in the organization.
+  * `information_schema.service_accounts`: Lists service accounts (programmatic access).
+  * `information_schema.network_policies`: Lists defined network policies.
+* **Account Level (Context Dependent):**
+  * `information_schema.databases` / `information_schema.catalogs`: Lists databases in the current account.
+  * `information_schema.engines`: Lists engines in the current account.
+  * `information_schema.users`: Lists users defined within the current account.
+  * `information_schema.applicable_roles`: Lists roles and their direct grantees within the account.
+  * `information_schema.transitive_applicable_roles`: Lists roles and all direct/indirect grantees.
+  * `information_schema.enabled_roles`: Lists roles accessible by the current user session.
+  * `information_schema.object_privileges`: Shows permissions granted on objects. Context-dependent (account or database level).
+* **Database Level (Requires specific database context):**
+  * `information_schema.schemata`: Lists schemas within the current database.
+  * `information_schema.tables`: Lists tables (Fact, Dimension, External) and views in the current database.
+  * `information_schema.views`: Lists views specifically in the current database.
+  * `information_schema.columns`: Lists columns for tables/views in the current database.
+  * `information_schema.indexes`: Lists primary and aggregating indexes in the current database.
+* **Monitoring & History:**
+  * `information_schema.engine_query_history`: Contains history of queries executed on engines (up to 10k per cluster).
+  * `information_schema.engine_user_query_history`: Filtered query history showing only user-initiated queries.
+  * `information_schema.engine_running_queries`: Shows queries currently executing or queued on engines (up to 10k per cluster).
+  * `information_schema.engine_history`: Shows engine lifecycle events (create, start, stop, alter).
+  * `information_schema.engine_metering_history`: Hourly engine FBU consumption.
+  * `information_schema.engine_metrics_history`: Engine resource utilization snapshots (CPU, RAM, cache, disk) taken every 30s, retained for 30 days.
+  * `information_schema.storage_billing`: Daily storage costs per account/region.
+  * `information_schema.engines_billing`: Daily engine compute costs per engine/account/region.
+  * `information_schema.storage_history`: Detailed daily storage consumption per database.
+  * `information_schema.storage_metering_history`: Aggregated daily storage consumption per account.
+  * `information_schema.routines`: Lists available SQL functions.
+
+*(To explore the specific columns available in each view, query the view directly or consult the `information_schema` documentation section.)*
+
+## 8. SQL Syntax Overview
+
+Firebolt uses a SQL dialect largely compatible with PostgreSQL. Key operations include:
+
+* **Data Definition Language (DDL):**
+  * `CREATE`, `ALTER`, `DROP` for `DATABASE`, `TABLE`, `VIEW`, `INDEX`, `ENGINE`, `ROLE`, `USER`, `LOGIN`, `SERVICE ACCOUNT`, `NETWORK POLICY`, `ACCOUNT`, `ORGANIZATION`.
+* **Data Manipulation Language (DML):**
+  * `INSERT INTO ... VALUES ...`: For inserting individual rows.
+  * `INSERT INTO ... SELECT ...`: For inserting results of a query.
+  * `UPDATE ... SET ... WHERE ...`: For modifying existing rows.
+  * `DELETE FROM ... WHERE ...`: For removing rows.
+  * `TRUNCATE TABLE ...`: For removing all rows quickly.
+  * `COPY FROM ...`: Bulk load data from S3 into a Firebolt table. Supports schema inference and various file types (CSV, Parquet, JSON, etc.).
+  * `COPY (...) TO ...`: Export query results to S3. Supports CSV, TSV, JSON, Parquet.
+  * `VACUUM ...`: Optimize table storage and remove deleted rows.
+* **Data Query Language (DQL):**
+  * `SELECT ... FROM ... WHERE ... GROUP BY ... HAVING ... ORDER BY ... LIMIT ... OFFSET ...`: Standard query structure.
+  * Supports `JOIN` types (`INNER`, `LEFT`, `RIGHT`, `FULL`, `CROSS`).
+  * Supports `UNION [ALL]`.
+  * Supports Common Table Expressions (`WITH ... AS ...`). Materialized CTEs available via `WITH ... AS MATERIALIZED ...`.
+  * Supports Window Functions (`... OVER (PARTITION BY ... ORDER BY ...)`).
+  * Supports Table-Valued Functions like `UNNEST` and `GENERATE_SERIES`.
+* **Pipe Syntax:** Alternative syntax for chaining transformations (`FROM table |> WHERE ... |> SELECT ...`).
+
+*(For detailed syntax of any command or function, query `information_schema.routines` or consult the SQL Reference section of the documentation.)*
+
+## 9. Supported Functions (List by Category)
+
+Firebolt provides a wide range of SQL functions. Query `information_schema.routines` for a full list or refer to the documentation. Categories include:
+
+* **Aggregation:** `AVG`, `COUNT`, `SUM`, `MIN`, `MAX`, `BOOL_AND`, `BOOL_OR`, `BIT_AND`, `BIT_OR`, `BIT_XOR`, `ARRAY_AGG`, `HASH_AGG` (CHECKSUM), `MEDIAN`, `PERCENTILE_CONT`, `HLL_COUNT_BUILD`, `HLL_COUNT_MERGE`, `MIN_BY`, `MAX_BY`, `STDDEV_POP`, `STDDEV_SAMP`, `VAR_POP`, `VAR_SAMP`, `APACHE_DATASKETCHES_HLL_BUILD`, `APACHE_DATASKETCHES_HLL_MERGE`.
+* **Array:** `ARRAY_CONCAT`, `ARRAY_CONTAINS`, `ARRAY_COUNT_DISTINCT`, `ARRAY_DISTINCT`, `ARRAY_ENUMERATE`, `ARRAY_LENGTH`, `ARRAY_MAX`, `ARRAY_MIN`, `ARRAY_REVERSE`, `ARRAY_TO_STRING`, `FLATTEN`, `INDEX_OF`.
+* **Lambda (for Arrays):** `ARRAY_ALL_MATCH`, `ARRAY_ANY_MATCH`, `ARRAY_COUNT`, `ARRAY_FILTER`, `ARRAY_FIRST`, `ARRAY_REVERSE_SORT`, `ARRAY_SORT`, `ARRAY_SUM`, `ARRAY_TRANSFORM`.
+* **Binary:** `CONVERT_FROM`, `DECODE`, `ENCODE`, `OCTET_LENGTH`.
+* **Conditional/Misc:** `CASE`, `CAST`, `TRY_CAST`, `COALESCE`, `IF`, `IFNULL`, `NULLIF`, `GREATEST`, `LEAST`, `CITY_HASH`, `HASH`, `TYPEOF`, `VERSION`.
+* **Date & Time:** `CURRENT_DATE`, `CURRENT_TIMESTAMP` (NOW), `LOCALTIMESTAMP`, `DATE`, `DATE_ADD`, `DATE_DIFF`, `DATE_TRUNC`, `EXTRACT`, `TO_DATE`, `TO_TIMESTAMP` (FROM_UNIXTIME), `TO_YYYYMM`, `TO_YYYYMMDD`, `TO_CHAR`.
+* **JSON:** `JSON_EXTRACT` (JSON_POINTER_EXTRACT), `JSON_EXTRACT_ARRAY` (JSON_POINTER_EXTRACT_ARRAY), `JSON_VALUE`, `JSON_VALUE_ARRAY`, `JSON_POINTER_EXTRACT_KEYS`, `JSON_POINTER_EXTRACT_VALUES`, `JSON_POINTER_EXTRACT_TEXT`.
+* **Numeric:** `ABS`, `ACOS`, `ASIN`, `ATAN`, `ATAN2`, `CEIL` (CEILING), `COS`, `COT`, `DEGREES`, `FLOOR`, `IS_FINITE`, `IS_INFINITE`, `LN`, `LOG` (LOG10), `MOD`, `PI`, `POW` (POWER), `RADIANS`, `RANDOM`, `ROUND`, `SIGN`, `SIN`, `SQRT`, `TAN`, `BIT_SHIFT_LEFT`, `BIT_SHIFT_RIGHT`, `HLL_COUNT_ESTIMATE`, `APACHE_DATASKETCHES_HLL_ESTIMATE`.
+* **String:** `CONCAT` (||), `LOWER`, `UPPER`, `LENGTH`, `LPAD`, `RPAD`, `LTRIM`, `RTRIM`, `BTRIM` (TRIM), `POSITION`, `STRPOS`, `REPLACE`, `SUBSTRING` (SUBSTR), `SPLIT_PART`, `STRING_TO_ARRAY`, `LIKE`, `ILIKE`, `REGEXP_LIKE`, `REGEXP_LIKE_ANY`, `REGEXP_EXTRACT`, `REGEXP_EXTRACT_ALL`, `REGEXP_REPLACE`, `REGEXP_REPLACE_ALL`, `URL_ENCODE`, `URL_DECODE`.
+* **Vector:** `VECTOR_ADD`, `VECTOR_SUBTRACT`, `VECTOR_COSINE_DISTANCE`, `VECTOR_COSINE_SIMILARITY`, `VECTOR_EUCLIDEAN_DISTANCE`, `VECTOR_SQUARED_EUCLIDEAN_DISTANCE`, `VECTOR_INNER_PRODUCT`, `VECTOR_MANHATTAN_DISTANCE`.
+* **Window:** `AVG`, `COUNT`, `SUM`, `MIN`, `MAX`, `ROW_NUMBER`, `RANK`, `DENSE_RANK`, `PERCENT_RANK`, `LEAD`, `LAG`, `FIRST_VALUE`.
+* **Table-Valued:** `GENERATE_SERIES`, `LIST_OBJECTS`, `READ_CSV`, `READ_PARQUET`, `UNNEST`.
+* **Geospatial:** `ST_ASBINARY`, `ST_ASEWKB`, `ST_ASGEOJSON`, `ST_ASTEXT`, `ST_CONTAINS`, `ST_COVERS`, `ST_DISTANCE`, `ST_GEOGFROMGEOJSON`, `ST_GEOGFROMTEXT`, `ST_GEOGFROMWKB`, `ST_GEOGPOINT`, `ST_INTERSECTS`, `ST_S2CELLIDFROMPOINT`, `ST_X`, `ST_Y`.
+
+*(To learn about a specific function's syntax, parameters, and behavior, search for its name in the Firebolt documentation.)*
+
+## 10. Supported Data Types
+
+Firebolt supports standard SQL data types.
+
+* **Numeric:** `INTEGER` (INT), `BIGINT` (LONG), `NUMERIC` (DECIMAL), `REAL` (FLOAT4), `DOUBLE PRECISION` (FLOAT, DOUBLE).
+* **Boolean:** `BOOLEAN` (BOOL).
+* **String:** `TEXT`. Uses UTF-8 encoding.
+* **Binary:** `BYTEA`.
+* **Date/Time:** `DATE`, `TIMESTAMP` (Timestamp without time zone), `TIMESTAMPTZ` (Timestamp with time zone).
+* **Composite:** `ARRAY(<type>)`. Can be nested.
+* **Spatial:** `GEOGRAPHY`. Represents points, linestrings, polygons on the WGS84 spheroid.
+
+*(For details on range, precision, storage size, literal formats, and casting rules, consult the Data Types section in the documentation.)*
+
+---
\ No newline at end of file
diff --git a/pkg/resources/docs_proof.md b/pkg/resources/docs_proof.md
new file mode 100644
index 0000000..b3918b8
--- /dev/null
+++ b/pkg/resources/docs_proof.md
@@ -0,0 +1,3 @@
+# Documentation Read Proof
+
+Pass the following value to the `docs_proof` parameter of the `firebolt_connect` tool to confirm that you have read the documentation: `%s`.
diff --git a/pkg/resources/docs_reference.md b/pkg/resources/docs_reference.md
new file mode 100644
index 0000000..6fa7e38
--- /dev/null
+++ b/pkg/resources/docs_reference.md
@@ -0,0 +1,6 @@
+# Firebolt Documentation Reference
+
+The Firebolt MCP server offers comprehensive documentation covering various aspects of Firebolt's architecture, features, and best practices.
+
+Below is a complete list of available documentation articles.
+To retrieve the full content of any article, provide its identifier(s) to the `firebolt_docs` tool.
diff --git a/pkg/resources/docs_test.go b/pkg/resources/docs_test.go
new file mode 100644
index 0000000..286b093
--- /dev/null
+++ b/pkg/resources/docs_test.go
@@ -0,0 +1,144 @@
+package resources_test
+
+import (
+	"io/fs"
+	"testing"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/mock"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+	"github.com/firebolt-db/mcp-server/pkg/resources"
+)
+
+func TestDocs_ResourceTemplate(t *testing.T) {
+
+	docs := resources.NewDocs(nil, "")
+	template := docs.ResourceTemplate()
+
+	assert.NotEmpty(t, template.Name)
+	assert.NotEmpty(t, template.URITemplate)
+	assert.NotEmpty(t, template.MIMEType)
+	assert.NotEmpty(t, template.Description)
+}
+
+func TestDocs_Handler(t *testing.T) {
+
+	mockFS := newMockDocsFS()
+	docs := resources.NewDocs(mockFS, "test-proof")
+
+	t.Run("fetch overview article", func(t *testing.T) {
+
+		request := mcp.ReadResourceRequest{}
+		request.Params.Arguments = map[string]any{
+			"article": resources.DocsArticleOverview,
+		}
+
+		contents, err := docs.Handler(t.Context(), request)
+		assert.NoError(t, err)
+		require.Len(t, contents, 1)
+		resource, ok := contents[0].(*mcp.TextResourceContents)
+		require.True(t, ok)
+		assert.Equal(t, resources.DocsURI(resources.DocsArticleOverview), resource.URI)
+		assert.Equal(t, mimetype.Markdown, resource.MIMEType)
+		assert.Contains(t, resource.Text, "Foundational Knowledge Layer", "should contain the Foundational Knowledge Layer")
+	})
+
+	t.Run("fetch proof article", func(t *testing.T) {
+
+		request := mcp.ReadResourceRequest{}
+		request.Params.Arguments = map[string]any{
+			"article": resources.DocsArticleProof,
+		}
+
+		contents, err := docs.Handler(t.Context(), request)
+		assert.NoError(t, err)
+		require.Len(t, contents, 1)
+		resource, ok := contents[0].(*mcp.TextResourceContents)
+		require.True(t, ok)
+		assert.Equal(t, resources.DocsURI(resources.DocsArticleProof), resource.URI)
+		assert.Equal(t, mimetype.Markdown, resource.MIMEType)
+		assert.Contains(t, resource.Text, "test-proof", "should contain the proof value")
+	})
+
+	t.Run("fetch reference article", func(t *testing.T) {
+
+		mockFS.On("ReadDir", ".").Return([]fs.DirEntry{
+			newMockDirEntry("file1.md", false),
+			newMockDirEntry("file2.md", false),
+		}, nil)
+
+		request := mcp.ReadResourceRequest{}
+		request.Params.Arguments = map[string]any{
+			"article": resources.DocsArticleReference,
+		}
+
+		contents, err := docs.Handler(t.Context(), request)
+		assert.NoError(t, err)
+		require.Len(t, contents, 1)
+		resource, ok := contents[0].(*mcp.TextResourceContents)
+		require.True(t, ok)
+		assert.Equal(t, resources.DocsURI(resources.DocsArticleReference), resource.URI)
+		assert.Equal(t, mimetype.Markdown, resource.MIMEType)
+		assert.Contains(t, resource.Text, "file1.md")
+		assert.Contains(t, resource.Text, "file2.md")
+	})
+
+	t.Run("fetch file-based article", func(t *testing.T) {
+
+		mockFS.On("ReadFile", "file1.md").Return([]byte("# File 1 Content"), nil)
+
+		request := mcp.ReadResourceRequest{}
+		request.Params.Arguments = map[string]any{
+			"article": "file1.md",
+		}
+
+		contents, err := docs.Handler(t.Context(), request)
+		assert.NoError(t, err)
+		require.Len(t, contents, 1)
+		resource, ok := contents[0].(*mcp.TextResourceContents)
+		require.True(t, ok)
+		assert.Equal(t, resources.DocsURI("file1.md"), resource.URI)
+		assert.Equal(t, mimetype.Markdown, resource.MIMEType)
+		assert.Equal(t, "# File 1 Content", resource.Text)
+	})
+}
+
+func newMockDocsFS() *mockDocsFS {
+	return &mockDocsFS{}
+}
+
+type mockDocsFS struct {
+	mock.Mock
+}
+
+func (m *mockDocsFS) Open(name string) (fs.File, error) {
+	args := m.Called(name)
+	return args.Get(0).(fs.File), args.Error(1)
+}
+
+func (m *mockDocsFS) ReadDir(name string) ([]fs.DirEntry, error) {
+	args := m.Called(name)
+	return args.Get(0).([]fs.DirEntry), args.Error(1)
+}
+
+func (m *mockDocsFS) ReadFile(name string) ([]byte, error) {
+	args := m.Called(name)
+	return args.Get(0).([]byte), args.Error(1)
+}
+
+func newMockDirEntry(name string, isDir bool) *mockDirEntry {
+	return &mockDirEntry{name: name, isDir: isDir}
+}
+
+type mockDirEntry struct {
+	name  string
+	isDir bool
+}
+
+func (m *mockDirEntry) Name() string               { return m.name }
+func (m *mockDirEntry) IsDir() bool                { return m.isDir }
+func (m *mockDirEntry) Type() fs.FileMode          { return 0 }
+func (m *mockDirEntry) Info() (fs.FileInfo, error) { return nil, nil }
diff --git a/pkg/resources/engines.go b/pkg/resources/engines.go
new file mode 100644
index 0000000..2c909f3
--- /dev/null
+++ b/pkg/resources/engines.go
@@ -0,0 +1,100 @@
+package resources
+
+import (
+	"context"
+	"encoding/json"
+	"fmt"
+
+	"github.com/mark3labs/mcp-go/mcp"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/args"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/itertools"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+)
+
+// EngineURI creates a formatted Firebolt engine URI for a given account and engine name.
+func EngineURI(account, engine string) string {
+	return fmt.Sprintf("firebolt://accounts/%s/engines/%s", account, engine)
+}
+
+// Engines is a resource template handler for serving Firebolt engine information.
+type Engines struct {
+	dbPool database.Pool
+}
+
+// NewEngines creates and returns a new instance of the Engines resource handler.
+func NewEngines(dbPool database.Pool) *Engines {
+	return &Engines{
+		dbPool: dbPool,
+	}
+}
+
+// ResourceTemplate defines the template for engine resources.
+// It specifies the URI format, content type, description, and suggested usage.
+func (r *Engines) ResourceTemplate() mcp.ResourceTemplate {
+	return mcp.NewResourceTemplate(
+		EngineURI("{account}", "{engine}"),
+		"Engine",
+		mcp.WithTemplateMIMEType(mimetype.JSON),
+		mcp.WithTemplateAnnotations([]mcp.Role{mcp.RoleUser, mcp.RoleAssistant}, 0.8),
+		mcp.WithTemplateDescription("Brief information about the engine in the Firebolt account."),
+	)
+}
+
+// Handler processes resource requests for engine information.
+// It extracts account and engine parameters and fetches the appropriate engine data.
+func (r *Engines) Handler(ctx context.Context, request mcp.ReadResourceRequest) ([]mcp.ResourceContents, error) {
+
+	params, err := args.Strings(request.Params.Arguments, "account", "engine")
+	if err != nil {
+		return nil, fmt.Errorf("bad request: %w", err)
+	}
+
+	return r.FetchEngineResources(ctx, params[0], params[1])
+}
+
+// FetchEngineResources retrieves engine information from the database.
+// If a specific engine is specified, it filters for that engine; otherwise, it returns all engines.
+func (r *Engines) FetchEngineResources(ctx context.Context, account, engine string) ([]mcp.ResourceContents, error) {
+
+	// Acquire a connection to the database
+	conn, err := r.dbPool.GetConnection(database.PoolParams{
+		AccountName: account,
+	})
+	if err != nil {
+		return nil, fmt.Errorf("failed to acquire database connection: %w", err)
+	}
+
+	// Prepare the SQL query
+	var (
+		sql  = "SELECT engine_name, description, status, version, type, family, nodes, clusters, auto_start FROM information_schema.engines"
+		args []any
+	)
+	if engine != "" {
+		sql += " WHERE engine_name = ?"
+		args = append(args, engine)
+	}
+
+	// Query database
+	rows, err := conn.Query(ctx, sql, args...)
+	if err != nil {
+		return nil, fmt.Errorf("failed to query database: %w", err)
+	}
+
+	// Convert rows to resources
+	return itertools.MapWithFailure(rows, func(i map[string]any) (mcp.ResourceContents, error) {
+
+		i["account_name"] = account
+		data, err := json.Marshal(i)
+		if err != nil {
+			return mcp.TextResourceContents{}, fmt.Errorf("failed to marshal row data to JSON: %w", err)
+		}
+
+		return mcp.TextResourceContents{
+			URI:      EngineURI(account, i["engine_name"].(string)),
+			MIMEType: mimetype.JSON,
+			Text:     string(data),
+		}, nil
+	})
+}
diff --git a/pkg/resources/engines_test.go b/pkg/resources/engines_test.go
new file mode 100644
index 0000000..845a27a
--- /dev/null
+++ b/pkg/resources/engines_test.go
@@ -0,0 +1,313 @@
+package resources_test
+
+import (
+	"context"
+	"encoding/json"
+	"errors"
+	"testing"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+	"github.com/firebolt-db/mcp-server/pkg/clients/database/databasemock"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+	"github.com/firebolt-db/mcp-server/pkg/resources"
+)
+
+func TestEngineURI(t *testing.T) {
+	tests := []struct {
+		name     string
+		account  string
+		engine   string
+		expected string
+	}{
+		{
+			name:     "basic case",
+			account:  "test-account",
+			engine:   "test-engine",
+			expected: "firebolt://accounts/test-account/engines/test-engine",
+		},
+		{
+			name:     "with special characters",
+			account:  "test.account",
+			engine:   "test-engine-123",
+			expected: "firebolt://accounts/test.account/engines/test-engine-123",
+		},
+		{
+			name:     "empty values",
+			account:  "",
+			engine:   "",
+			expected: "firebolt://accounts//engines/",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			result := resources.EngineURI(tt.account, tt.engine)
+			assert.Equal(t, tt.expected, result)
+		})
+	}
+}
+
+func TestNewEngines(t *testing.T) {
+	pool := databasemock.NewPoolMock()
+	engines := resources.NewEngines(pool)
+	assert.NotNil(t, engines)
+}
+
+func TestEngines_ResourceTemplate(t *testing.T) {
+	pool := databasemock.NewPoolMock()
+	engines := resources.NewEngines(pool)
+	assert.NotEmpty(t, engines.ResourceTemplate())
+}
+
+func TestEngines_Handler(t *testing.T) {
+	tests := []struct {
+		name          string
+		params        map[string]any
+		mockSetup     func(*databasemock.PoolMock, *databasemock.ConnectionMock)
+		expected      []map[string]any
+		expectedError string
+	}{
+		{
+			name: "successful request",
+			params: map[string]any{
+				"account": "test-account",
+				"engine":  "test-engine",
+			},
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					assert.Equal(t, "SELECT engine_name, description, status, version, type, family, nodes, clusters, auto_start FROM information_schema.engines WHERE engine_name = ?", sql)
+					assert.Equal(t, []any{"test-engine"}, args)
+					return []map[string]any{
+						{
+							"engine_name": "test-engine",
+							"status":      "running",
+							"version":     "3.0",
+						},
+					}, nil
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expected: []map[string]any{
+				{
+					"account_name": "test-account",
+					"engine_name":  "test-engine",
+					"status":       "running",
+					"version":      "3.0",
+				},
+			},
+		},
+		{
+			name: "missing account parameter",
+			params: map[string]any{
+				"engine": "test-engine",
+			},
+			expectedError: "bad request: required argument account not provided",
+		},
+		{
+			name: "missing engine parameter",
+			params: map[string]any{
+				"account": "test-account",
+			},
+			expectedError: "bad request: required argument engine not provided",
+		},
+		{
+			name: "database connection error",
+			params: map[string]any{
+				"account": "test-account",
+				"engine":  "test-engine",
+			},
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				pool.WithGetConnectionFunc(func(params database.PoolParams) (database.Connection, error) {
+					return nil, errors.New("connection error")
+				})
+			},
+			expectedError: "failed to acquire database connection: connection error",
+		},
+		{
+			name: "query execution error",
+			params: map[string]any{
+				"account": "test-account",
+				"engine":  "test-engine",
+			},
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					return nil, errors.New("query error")
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expectedError: "failed to query database: query error",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			pool := databasemock.NewPoolMock()
+			conn := databasemock.NewConnectionMock()
+
+			if tt.mockSetup != nil {
+				tt.mockSetup(pool, conn)
+			}
+
+			engines := resources.NewEngines(pool)
+
+			request := mcp.ReadResourceRequest{}
+			request.Params.Arguments = tt.params
+
+			result, err := engines.Handler(t.Context(), request)
+
+			if tt.expectedError != "" {
+				assert.Error(t, err)
+				assert.Contains(t, err.Error(), tt.expectedError)
+				return
+			}
+
+			require.NoError(t, err)
+			require.Len(t, result, len(tt.expected))
+
+			for i, res := range result {
+				textRes, ok := res.(mcp.TextResourceContents)
+				require.True(t, ok, "Expected TextResourceContents")
+
+				var data map[string]any
+				err := json.Unmarshal([]byte(textRes.Text), &data)
+				require.NoError(t, err)
+
+				assert.Equal(t, tt.expected[i], data)
+				assert.Equal(t, resources.EngineURI("test-account", data["engine_name"].(string)), textRes.URI)
+				assert.Equal(t, mimetype.JSON, textRes.MIMEType)
+			}
+		})
+	}
+}
+
+func TestEngines_FetchEngineResources(t *testing.T) {
+	tests := []struct {
+		name          string
+		account       string
+		engine        string
+		mockSetup     func(*databasemock.PoolMock, *databasemock.ConnectionMock)
+		expected      []map[string]any
+		expectedError string
+	}{
+		{
+			name:    "fetch specific engine",
+			account: "test-account",
+			engine:  "test-engine",
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					assert.Equal(t, "SELECT engine_name, description, status, version, type, family, nodes, clusters, auto_start FROM information_schema.engines WHERE engine_name = ?", sql)
+					assert.Equal(t, []any{"test-engine"}, args)
+					return []map[string]any{
+						{
+							"engine_name": "test-engine",
+							"status":      "running",
+							"version":     "3.0",
+							"type":        "general_purpose",
+						},
+					}, nil
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expected: []map[string]any{
+				{
+					"account_name": "test-account",
+					"engine_name":  "test-engine",
+					"status":       "running",
+					"version":      "3.0",
+					"type":         "general_purpose",
+				},
+			},
+		},
+		{
+			name:    "fetch all engines",
+			account: "test-account",
+			engine:  "",
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					assert.Equal(t, "SELECT engine_name, description, status, version, type, family, nodes, clusters, auto_start FROM information_schema.engines", sql)
+					assert.Empty(t, args)
+					return []map[string]any{
+						{
+							"engine_name": "engine-1",
+							"status":      "running",
+						},
+						{
+							"engine_name": "engine-2",
+							"status":      "stopped",
+						},
+					}, nil
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expected: []map[string]any{
+				{
+					"account_name": "test-account",
+					"engine_name":  "engine-1",
+					"status":       "running",
+				},
+				{
+					"account_name": "test-account",
+					"engine_name":  "engine-2",
+					"status":       "stopped",
+				},
+			},
+		},
+		{
+			name:    "json marshaling error",
+			account: "test-account",
+			engine:  "test-engine",
+			mockSetup: func(pool *databasemock.PoolMock, conn *databasemock.ConnectionMock) {
+				conn.WithQueryFunc(func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+					return []map[string]any{
+						{
+							"engine_name": make(chan int), // Channels are not JSON-serializable
+						},
+					}, nil
+				})
+				pool.RegisterConnection(database.PoolParams{AccountName: "test-account"}, conn)
+			},
+			expectedError: "failed to marshal row data to JSON",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			pool := databasemock.NewPoolMock()
+			conn := databasemock.NewConnectionMock()
+
+			if tt.mockSetup != nil {
+				tt.mockSetup(pool, conn)
+			}
+
+			engines := resources.NewEngines(pool)
+
+			result, err := engines.FetchEngineResources(t.Context(), tt.account, tt.engine)
+
+			if tt.expectedError != "" {
+				assert.Error(t, err)
+				assert.Contains(t, err.Error(), tt.expectedError)
+				return
+			}
+
+			require.NoError(t, err)
+			require.Len(t, result, len(tt.expected))
+
+			for i, res := range result {
+				textRes, ok := res.(mcp.TextResourceContents)
+				require.True(t, ok, "Expected TextResourceContents")
+
+				var data map[string]any
+				err := json.Unmarshal([]byte(textRes.Text), &data)
+				require.NoError(t, err)
+
+				assert.Equal(t, tt.expected[i], data)
+				assert.Equal(t, resources.EngineURI(tt.account, data["engine_name"].(string)), textRes.URI)
+				assert.Equal(t, mimetype.JSON, textRes.MIMEType)
+			}
+		})
+	}
+}
diff --git a/pkg/server/server.go b/pkg/server/server.go
new file mode 100644
index 0000000..7c1356e
--- /dev/null
+++ b/pkg/server/server.go
@@ -0,0 +1,211 @@
+// Package server provides the core MCP server implementation for the Firebolt MCP.
+// It defines interfaces for tools, prompts, and resource templates that can be registered
+// with the server, as well as methods for serving the MCP over different transports.
+package server
+
+import (
+	"context"
+	"errors"
+	"log"
+	"log/slog"
+	"os"
+	"time"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	mcpserver "github.com/mark3labs/mcp-go/server"
+
+	"github.com/firebolt-db/mcp-server/pkg/version"
+)
+
+// Server represents the interface for the MCP server functionality.
+// It defines the method to start the server and handle MCP requests.
+type Server interface {
+	// Serve starts the server with the provided context and handles MCP requests
+	// until the context is canceled or an error occurs.
+	Serve(ctx context.Context) error
+}
+
+// Tool represents a callable tool that can be registered with the MCP server.
+// It provides methods to define the tool metadata and handle tool calls.
+type Tool interface {
+	// Tool returns the MCP tool definition with its name, description, parameters, etc.
+	Tool() mcp.Tool
+	// Handler processes tool call requests and returns results.
+	Handler(ctx context.Context, request mcp.CallToolRequest) (*mcp.CallToolResult, error)
+}
+
+// Prompt represents a prompt that can be registered with the MCP server.
+// It provides methods to define the prompt metadata and handle prompt requests.
+type Prompt interface {
+	// Prompt returns the MCP prompt definition.
+	Prompt() mcp.Prompt
+	// Handler processes prompt requests and returns results.
+	Handler(ctx context.Context, request mcp.GetPromptRequest) (*mcp.GetPromptResult, error)
+}
+
+// ResourceTemplate represents a resource template that can be registered with the MCP server.
+// It provides methods to define the resource template metadata and handle resource requests.
+type ResourceTemplate interface {
+	// ResourceTemplate returns the MCP resource template definition.
+	ResourceTemplate() mcp.ResourceTemplate
+	// Handler processes resource read requests and returns resource contents.
+	Handler(ctx context.Context, request mcp.ReadResourceRequest) ([]mcp.ResourceContents, error)
+}
+
+// NewServer creates a new MCP server with the provided configuration.
+// It registers the provided tools, prompts, and resource templates with the server.
+//
+// Parameters:
+//   - logger: The structured logger to use for logging.
+//   - transport: The transport type to use ("stdio" or "sse").
+//   - transportSSEAddress: The address to listen on when using SSE transport.
+//   - tools: The list of tools to register with the server.
+//   - prompts: The list of prompts to register with the server.
+//   - resourceTemplates: The list of resource templates to register with the server.
+//
+// Returns a Server that can be used to start handling MCP requests.
+func NewServer(
+	logger *slog.Logger,
+	transport string,
+	transportSSEAddress string,
+	tools []Tool,
+	prompts []Prompt,
+	resourceTemplates []ResourceTemplate,
+) Server {
+
+	// Configure logging hooks to track tool calls and errors
+	hooks := &mcpserver.Hooks{}
+	hooks.AddBeforeCallTool(func(id any, message *mcp.CallToolRequest) {
+		logger.Debug(
+			"received tool call request",
+			slog.Any("id", id),
+			slog.String("tool", message.Params.Name),
+			slog.Any("arguments", message.Params.Arguments),
+		)
+	})
+	hooks.AddAfterCallTool(func(id any, message *mcp.CallToolRequest, result *mcp.CallToolResult) {
+		logger.Info(
+			"tool call finished",
+			slog.Any("id", id),
+			slog.String("tool", message.Params.Name),
+			slog.Any("any", result.Result),
+		)
+	})
+	hooks.AddOnError(func(id any, method mcp.MCPMethod, message any, err error) {
+		logger.Error(
+			"error occurred",
+			slog.Any("id", id),
+			slog.String("method", string(method)),
+			slog.Any("message", message),
+			slog.String("error", err.Error()),
+		)
+	})
+
+	// Initialize the MCP server with Firebolt-specific configuration
+	mcpSrv := mcpserver.NewMCPServer(
+		"Firebolt MCP Server",
+		version.GetFullVersion(),
+		mcpserver.WithInstructions(`
+			This MCP makes you a Firebolt cloud data warehouse expert with access to specialized tools and resources.
+			You can assist with SQL queries, data modeling, performance optimization, and analytics for Firebolt.
+			
+			Use available tools and resources to:
+			- Access Firebolt documentation for reference
+			- Execute SQL queries against Firebolt databases
+		`),
+		mcpserver.WithHooks(hooks),
+		mcpserver.WithToolCapabilities(true),
+		mcpserver.WithPromptCapabilities(false),
+		mcpserver.WithResourceCapabilities(false, false),
+	)
+
+	// Register the tools, prompts, and resource templates with the server
+	mcpSrv.AddTools(transform(tools, func(i Tool) mcpserver.ServerTool {
+		return mcpserver.ServerTool{
+			Tool:    i.Tool(),
+			Handler: i.Handler,
+		}
+	})...)
+	for _, prompt := range prompts {
+		mcpSrv.AddPrompt(prompt.Prompt(), prompt.Handler)
+	}
+	for _, resourceTemplate := range resourceTemplates {
+		mcpSrv.AddResourceTemplate(resourceTemplate.ResourceTemplate(), resourceTemplate.Handler)
+	}
+
+	// Initialize the server implementation with the configured MCP server
+	s := &serverImpl{
+		logger:              logger,
+		inner:               mcpSrv,
+		transport:           transport,
+		transportSSEAddress: transportSSEAddress,
+	}
+
+	return s
+}
+
+// serverImpl is the implementation of the Server interface.
+// It wraps an MCP server and provides methods to serve it over different transports.
+type serverImpl struct {
+	logger              *slog.Logger
+	inner               *mcpserver.MCPServer
+	transport           string
+	transportSSEAddress string
+}
+
+// Serve starts the server with the provided context and handles MCP requests
+// until the context is canceled or an error occurs.
+// It selects the appropriate transport (stdio or SSE) based on the server configuration.
+func (s *serverImpl) Serve(ctx context.Context) error {
+	switch s.transport {
+	case "stdio":
+		return s.serveStdio(ctx)
+	case "sse":
+		return s.serveSSE(ctx)
+	default:
+		return errors.New("unsupported transport type: " + s.transport)
+	}
+}
+
+// serveStdio starts the server using the stdio transport.
+// It reads MCP requests from stdin and writes responses to stdout.
+func (s *serverImpl) serveStdio(ctx context.Context) error {
+	s.logger.Info("Using stdio transport")
+
+	srv := mcpserver.NewStdioServer(s.inner)
+	srv.SetErrorLogger(log.New(os.Stderr, "", log.LstdFlags))
+
+	return srv.Listen(ctx, os.Stdin, os.Stdout)
+}
+
+// serveSSE starts the server using the SSE transport.
+// It listens for HTTP requests on the configured address and serves MCP requests over SSE.
+// The server will shut down gracefully when the context is canceled.
+func (s *serverImpl) serveSSE(ctx context.Context) error {
+	s.logger.Info("Using sse transport", "listen_address", s.transportSSEAddress)
+
+	srv := mcpserver.NewSSEServer(s.inner)
+
+	// Setup graceful shutdown when context is canceled
+	go func() {
+		<-ctx.Done()
+		ctx, cancel := context.WithTimeout(context.WithoutCancel(ctx), 5*time.Second)
+		defer cancel()
+		if err := srv.Shutdown(ctx); err != nil {
+			s.logger.Warn("error shutting down server gracefully", "error", err)
+		}
+	}()
+
+	return srv.Start(s.transportSSEAddress)
+}
+
+// transform is a utility function that applies a transformation function to each element
+// of the input slice and returns a new slice containing the transformed elements.
+// It's a generic function that works with any input and output types.
+func transform[I, O any](inputs []I, transformer func(I) O) []O {
+	outputs := make([]O, len(inputs))
+	for i, input := range inputs {
+		outputs[i] = transformer(input)
+	}
+	return outputs
+}
diff --git a/pkg/server/server_test.go b/pkg/server/server_test.go
new file mode 100644
index 0000000..2adb323
--- /dev/null
+++ b/pkg/server/server_test.go
@@ -0,0 +1,130 @@
+package server_test
+
+import (
+	"context"
+	"io"
+	"log/slog"
+	"strings"
+	"testing"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	"github.com/neilotoole/slogt"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/mock"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/server"
+)
+
+// TestNewServer checks that NewServer registers tools, prompts, and resource templates correctly.
+func TestNewServer(t *testing.T) {
+	// Create test logger
+	logger := slog.New(slog.NewTextHandler(io.Discard, nil))
+
+	// Setup mocks
+	mockTool1 := new(mockTool)
+	mockTool1.On("Tool").Return(mcp.Tool{
+		Name:        "testTool1",
+		Description: "Test tool 1",
+	})
+
+	mockPrompt1 := new(mockPrompt)
+	mockPrompt1.On("Prompt").Return(mcp.Prompt{
+		Name:        "testPrompt1",
+		Description: "Test prompt 1",
+	})
+
+	mockResource1 := new(mockResourceTemplate)
+	mockResource1.On("ResourceTemplate").Return(
+		mcp.NewResourceTemplate(
+			"test",
+			"testResource1",
+			mcp.WithTemplateDescription("Test resource 1"),
+		),
+	)
+
+	// Create server
+	srv := server.NewServer(
+		logger,
+		"stdio",
+		"localhost:8080",
+		[]server.Tool{mockTool1},
+		[]server.Prompt{mockPrompt1},
+		[]server.ResourceTemplate{mockResource1},
+	)
+
+	// Assertions
+	require.NotNil(t, srv, "Server should not be nil")
+
+	// Verify that mocks were called as expected
+	mockTool1.AssertCalled(t, "Tool")
+	mockPrompt1.AssertCalled(t, "Prompt")
+	mockResource1.AssertCalled(t, "ResourceTemplate")
+}
+
+// TestServeUnsupportedTransport checks that Serve returns an error for unsupported transports.
+func TestServeUnsupportedTransport(t *testing.T) {
+
+	// Create server with unsupported transport
+	srv := server.NewServer(slogt.New(t), "test", "", nil, nil, nil)
+
+	// Call Serve and check error
+	err := srv.Serve(t.Context())
+	assert.Error(t, err, "Serve should return an error for unsupported transport")
+	assert.True(t, strings.Contains(err.Error(), "unsupported transport type"),
+		"Error message should mention unsupported transport type")
+}
+
+// mockTool is a mock implementation of the Tool interface for testing.
+type mockTool struct {
+	mock.Mock
+}
+
+func (m *mockTool) Tool() mcp.Tool {
+	args := m.Called()
+	return args.Get(0).(mcp.Tool)
+}
+
+func (m *mockTool) Handler(ctx context.Context, request mcp.CallToolRequest) (*mcp.CallToolResult, error) {
+	args := m.Called(ctx, request)
+	if args.Get(0) == nil {
+		return nil, args.Error(1)
+	}
+	return args.Get(0).(*mcp.CallToolResult), args.Error(1)
+}
+
+// mockPrompt is a mock implementation of the Prompt interface for testing.
+type mockPrompt struct {
+	mock.Mock
+}
+
+func (m *mockPrompt) Prompt() mcp.Prompt {
+	args := m.Called()
+	return args.Get(0).(mcp.Prompt)
+}
+
+func (m *mockPrompt) Handler(ctx context.Context, request mcp.GetPromptRequest) (*mcp.GetPromptResult, error) {
+	args := m.Called(ctx, request)
+	if args.Get(0) == nil {
+		return nil, args.Error(1)
+	}
+	return args.Get(0).(*mcp.GetPromptResult), args.Error(1)
+}
+
+// mockResourceTemplate is a mock implementation of the ResourceTemplate interface for testing.
+type mockResourceTemplate struct {
+	mock.Mock
+}
+
+func (m *mockResourceTemplate) ResourceTemplate() mcp.ResourceTemplate {
+	args := m.Called()
+	return args.Get(0).(mcp.ResourceTemplate)
+}
+
+func (m *mockResourceTemplate) Handler(ctx context.Context, request mcp.ReadResourceRequest) ([]mcp.ResourceContents, error) {
+	args := m.Called(ctx, request)
+	if args.Get(0) == nil {
+		return nil, args.Error(1)
+	}
+	return args.Get(0).([]mcp.ResourceContents), args.Error(1)
+}
diff --git a/pkg/tools/connect.go b/pkg/tools/connect.go
new file mode 100644
index 0000000..3eda081
--- /dev/null
+++ b/pkg/tools/connect.go
@@ -0,0 +1,188 @@
+package tools
+
+import (
+	"context"
+	"encoding/json"
+	"fmt"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	"github.com/pkg/errors"
+	"golang.org/x/sync/errgroup"
+
+	"github.com/firebolt-db/mcp-server/pkg/helpers/args"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/itertools"
+)
+
+// AccountResourcesFetcher defines the interface for retrieving account resources.
+// Implementations should provide methods to fetch Firebolt account information.
+type AccountResourcesFetcher interface {
+	// FetchAccountResources retrieves account information for a specified account name.
+	// If accountName is empty, all accessible accounts should be returned.
+	FetchAccountResources(ctx context.Context, accountName string) ([]mcp.ResourceContents, error)
+}
+
+// DatabaseResourcesFetcher defines the interface for retrieving database resources.
+// Implementations should provide methods to fetch Firebolt database information within an account.
+type DatabaseResourcesFetcher interface {
+	// FetchDatabaseResources retrieves database information for a specified account and database name.
+	// If databaseName is empty, all databases in the account should be returned.
+	FetchDatabaseResources(ctx context.Context, accountName, databaseName string) ([]mcp.ResourceContents, error)
+}
+
+// EngineResourcesFetcher defines the interface for retrieving engine resources.
+// Implementations should provide methods to fetch Firebolt engine information within an account.
+type EngineResourcesFetcher interface {
+	// FetchEngineResources retrieves engine information for a specified account and engine name.
+	// If engineName is empty, all engines in the account should be returned.
+	FetchEngineResources(ctx context.Context, accountName, engineName string) ([]mcp.ResourceContents, error)
+}
+
+// Connect represents a tool for fetching and returning Firebolt resource information.
+// It provides hierarchical access to accounts, databases, and engines in the Firebolt system.
+type Connect struct {
+	accountsFetcher  AccountResourcesFetcher  // Fetches account resources
+	databasesFetcher DatabaseResourcesFetcher // Fetches database resources
+	enginesFetcher   EngineResourcesFetcher   // Fetches engine resources
+	docsProof        string                   // Shared with the docs resources
+}
+
+// NewConnect creates a new instance of the Connect tool with the provided resource fetchers.
+// It requires implementations for fetching accounts, databases, and engines.
+func NewConnect(
+	accountsFetcher AccountResourcesFetcher,
+	databasesFetcher DatabaseResourcesFetcher,
+	enginesFetcher EngineResourcesFetcher,
+	docsProof string,
+) *Connect {
+	return &Connect{
+		accountsFetcher:  accountsFetcher,
+		databasesFetcher: databasesFetcher,
+		enginesFetcher:   enginesFetcher,
+		docsProof:        docsProof,
+	}
+}
+
+// Tool returns the mcp.Tool definition for the Connect tool.
+// This defines how the tool is represented in the MCP system.
+func (t *Connect) Tool() mcp.Tool {
+	return mcp.NewTool(
+		"firebolt_connect",
+		mcp.WithDescription(
+			"Returns a list of Firebolt accounts, databases, and engines you have access to. "+
+				"This information is required before using the `firebolt_query` tool.",
+		),
+		mcp.WithString(
+			"docs_proof",
+			mcp.Required(),
+			mcp.Title("Documentation Read Proof"),
+			mcp.Description(
+				"This parameter is used to confirm that the essential documentation has been reviewed before connecting to Firebolt. "+
+					"The correct value will be returned by the `firebolt_docs` tool when it is called without any parameters.",
+			),
+		),
+	)
+}
+
+// Handler processes tool invocation requests and returns a comprehensive view of
+// Firebolt resources. It fetches accounts and then concurrently retrieves the
+// databases and engines for each account.
+func (t *Connect) Handler(ctx context.Context, request mcp.CallToolRequest) (*mcp.CallToolResult, error) {
+
+	// Verify docs read proof
+	proof, err := args.String(request.Params.Arguments, "docs_proof")
+	if err != nil {
+		return nil, fmt.Errorf("bad request: %w", err)
+	}
+	if proof != t.docsProof {
+		return nil, errors.New(
+			"invalid documentation proof, " +
+				"you need to call `firebolt_docs` tool first and extract value from this parameter from the response",
+		)
+	}
+
+	// Fetch all accounts
+	accounts, err := t.accountsFetcher.FetchAccountResources(ctx, "")
+	if err != nil {
+		return nil, fmt.Errorf("failed to discover resources: %w", err)
+	}
+
+	// Results collection
+	var results []mcp.ResourceContents
+	done := make(chan struct{}, 1)
+	resourcesCh := make(chan mcp.ResourceContents, len(accounts))
+
+	// Start a goroutine to collect results from the channel
+	go func() {
+		for resource := range resourcesCh {
+			results = append(results, resource)
+		}
+		done <- struct{}{}
+	}()
+
+	// For every account, concurrently fetch databases and engines
+	group, groupCtx := errgroup.WithContext(ctx)
+	for _, account := range accounts {
+		account := account // Capture variable for goroutine
+		group.Go(func() error {
+
+			// Add the account resource to results
+			resourcesCh <- account
+
+			// Extract the account information from the resource
+			accountTextResource, ok := account.(mcp.TextResourceContents)
+			if !ok {
+				return fmt.Errorf("failed to convert account resource to text resource")
+			}
+			var ar accountResource
+			err = json.Unmarshal([]byte(accountTextResource.Text), &ar)
+			if err != nil {
+				return fmt.Errorf("failed to unmarshal account resource: %w", err)
+			}
+
+			// Fetch all databases for the account
+			databases, err := t.databasesFetcher.FetchDatabaseResources(groupCtx, ar.Name, "")
+			if err != nil {
+				return fmt.Errorf("failed to discover database resources: %w", err)
+			}
+			for _, db := range databases {
+				resourcesCh <- db
+			}
+
+			// Fetch all engines for the account
+			engines, err := t.enginesFetcher.FetchEngineResources(groupCtx, ar.Name, "")
+			if err != nil {
+				return fmt.Errorf("failed to discover engine resources: %w", err)
+			}
+			for _, engine := range engines {
+				resourcesCh <- engine
+			}
+
+			return nil
+		})
+	}
+
+	// Wait for all fetches to complete
+	err = group.Wait()
+	close(resourcesCh)
+	if err != nil {
+		return nil, fmt.Errorf("failed to fetch resources: %w", err)
+	}
+
+	// Wait for all results to be collected
+	<-done
+
+	// Return the results as embedded resources
+	return &mcp.CallToolResult{
+		Result: mcp.Result{},
+		Content: itertools.Map(results, func(i mcp.ResourceContents) mcp.Content {
+			return mcp.NewEmbeddedResource(i)
+		}),
+		IsError: false,
+	}, nil
+}
+
+// accountResource represents the minimal structure needed to extract
+// the account name from an account resource.
+type accountResource struct {
+	Name string `json:"name"`
+}
diff --git a/pkg/tools/connect_test.go b/pkg/tools/connect_test.go
new file mode 100644
index 0000000..3738ba1
--- /dev/null
+++ b/pkg/tools/connect_test.go
@@ -0,0 +1,311 @@
+package tools_test
+
+import (
+	"context"
+	"encoding/json"
+	"errors"
+	"testing"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+	"github.com/firebolt-db/mcp-server/pkg/tools"
+)
+
+const validProof = "valid_proof"
+
+// MockResourceFetcher is a test implementation of the resource fetcher interfaces
+type MockResourceFetcher struct {
+	AccountsFunc  func(ctx context.Context, accountName string) ([]mcp.ResourceContents, error)
+	DatabasesFunc func(ctx context.Context, accountName, databaseName string) ([]mcp.ResourceContents, error)
+	EnginesFunc   func(ctx context.Context, accountName, engineName string) ([]mcp.ResourceContents, error)
+}
+
+func (m *MockResourceFetcher) FetchAccountResources(ctx context.Context, accountName string) ([]mcp.ResourceContents, error) {
+	return m.AccountsFunc(ctx, accountName)
+}
+
+func (m *MockResourceFetcher) FetchDatabaseResources(ctx context.Context, accountName, databaseName string) ([]mcp.ResourceContents, error) {
+	return m.DatabasesFunc(ctx, accountName, databaseName)
+}
+
+func (m *MockResourceFetcher) FetchEngineResources(ctx context.Context, accountName, engineName string) ([]mcp.ResourceContents, error) {
+	return m.EnginesFunc(ctx, accountName, engineName)
+}
+
+// Helpers to create resource mocks
+func createAccountResource(name string) mcp.ResourceContents {
+	account := map[string]string{
+		"name":   name,
+		"region": "us-east-1",
+	}
+	data, _ := json.Marshal(account)
+	return mcp.TextResourceContents{
+		URI:      "firebolt://accounts/" + name,
+		MIMEType: mimetype.JSON,
+		Text:     string(data),
+	}
+}
+
+func createDatabaseResource(accountName, databaseName string) mcp.ResourceContents {
+	database := map[string]string{
+		"account_name":  accountName,
+		"database_name": databaseName,
+		"description":   "Description for " + databaseName,
+	}
+	data, _ := json.Marshal(database)
+	return mcp.TextResourceContents{
+		URI:      "firebolt://accounts/" + accountName + "/databases/" + databaseName,
+		MIMEType: mimetype.JSON,
+		Text:     string(data),
+	}
+}
+
+func createEngineResource(accountName, engineName string) mcp.ResourceContents {
+	engine := map[string]string{
+		"account_name": accountName,
+		"engine_name":  engineName,
+		"status":       "running",
+		"description":  "Description for " + engineName,
+	}
+	data, _ := json.Marshal(engine)
+	return mcp.TextResourceContents{
+		URI:      "firebolt://accounts/" + accountName + "/engines/" + engineName,
+		MIMEType: mimetype.JSON,
+		Text:     string(data),
+	}
+}
+
+func TestNewConnect(t *testing.T) {
+	mock := &MockResourceFetcher{}
+	connectTool := tools.NewConnect(mock, mock, mock, validProof)
+	assert.NotNil(t, connectTool)
+}
+
+func TestConnect_Tool(t *testing.T) {
+	mock := &MockResourceFetcher{}
+	connectTool := tools.NewConnect(mock, mock, mock, validProof)
+
+	tool := connectTool.Tool()
+	assert.Equal(t, "firebolt_connect", tool.Name)
+	assert.Contains(t, tool.Description, "Returns a list of Firebolt accounts")
+}
+
+func TestConnect_Handler_Success(t *testing.T) {
+	// Create test data
+	accounts := []string{"account1", "account2"}
+	databases := map[string][]string{
+		"account1": {"db1", "db2"},
+		"account2": {"db3"},
+	}
+	engines := map[string][]string{
+		"account1": {"engine1"},
+		"account2": {"engine2", "engine3"},
+	}
+
+	// Create mock fetcher
+	mock := &MockResourceFetcher{
+		AccountsFunc: func(ctx context.Context, accountName string) ([]mcp.ResourceContents, error) {
+			var resources []mcp.ResourceContents
+			for _, acc := range accounts {
+				resources = append(resources, createAccountResource(acc))
+			}
+			return resources, nil
+		},
+		DatabasesFunc: func(ctx context.Context, accountName, databaseName string) ([]mcp.ResourceContents, error) {
+			var resources []mcp.ResourceContents
+			for _, db := range databases[accountName] {
+				resources = append(resources, createDatabaseResource(accountName, db))
+			}
+			return resources, nil
+		},
+		EnginesFunc: func(ctx context.Context, accountName, engineName string) ([]mcp.ResourceContents, error) {
+			var resources []mcp.ResourceContents
+			for _, eng := range engines[accountName] {
+				resources = append(resources, createEngineResource(accountName, eng))
+			}
+			return resources, nil
+		},
+	}
+
+	// Create the tool
+	connectTool := tools.NewConnect(mock, mock, mock, validProof)
+
+	// Execute the handler
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"docs_proof": validProof,
+	}
+	result, err := connectTool.Handler(t.Context(), request)
+
+	// Assertions
+	require.NoError(t, err)
+	require.NotNil(t, result)
+	assert.False(t, result.IsError)
+
+	// Calculate expected total resources
+	expectedCount := len(accounts) // accounts
+	for _, dbs := range databases {
+		expectedCount += len(dbs) // databases
+	}
+	for _, engs := range engines {
+		expectedCount += len(engs) // engines
+	}
+
+	// Check if we got the expected number of resources
+	assert.Len(t, result.Content, expectedCount)
+
+	// Verify the content contains all expected resources
+	resourceMap := make(map[string]bool)
+	for _, content := range result.Content {
+		embeddedResource, ok := content.(mcp.EmbeddedResource)
+		require.True(t, ok, "Expected EmbeddedResource")
+
+		textResource, ok := embeddedResource.Resource.(mcp.TextResourceContents)
+		require.True(t, ok, "Expected TextResourceContents")
+
+		resourceMap[textResource.URI] = true
+	}
+
+	// Check if all accounts are present
+	for _, acc := range accounts {
+		uri := "firebolt://accounts/" + acc
+		assert.True(t, resourceMap[uri], "Missing account resource: "+uri)
+	}
+
+	// Check if all databases are present
+	for acc, dbs := range databases {
+		for _, db := range dbs {
+			uri := "firebolt://accounts/" + acc + "/databases/" + db
+			assert.True(t, resourceMap[uri], "Missing database resource: "+uri)
+		}
+	}
+
+	// Check if all engines are present
+	for acc, engs := range engines {
+		for _, eng := range engs {
+			uri := "firebolt://accounts/" + acc + "/engines/" + eng
+			assert.True(t, resourceMap[uri], "Missing engine resource: "+uri)
+		}
+	}
+}
+
+func TestConnect_Handler_AccountFetchFailure(t *testing.T) {
+	mock := &MockResourceFetcher{
+		AccountsFunc: func(ctx context.Context, accountName string) ([]mcp.ResourceContents, error) {
+			return nil, errors.New("failed to fetch accounts")
+		},
+	}
+
+	connectTool := tools.NewConnect(mock, mock, mock, validProof)
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"docs_proof": validProof,
+	}
+	result, err := connectTool.Handler(t.Context(), request)
+
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "failed to discover resources")
+	assert.Nil(t, result)
+}
+
+func TestConnect_Handler_InvalidAccountResource(t *testing.T) {
+	mock := &MockResourceFetcher{
+		AccountsFunc: func(ctx context.Context, accountName string) ([]mcp.ResourceContents, error) {
+			// Return a non-text resource to trigger the type assertion failure
+			return []mcp.ResourceContents{
+				mcp.BlobResourceContents{
+					URI:      "firebolt://accounts/test-account",
+					MIMEType: "application/octet-stream",
+					Blob:     "binary data",
+				},
+			}, nil
+		},
+	}
+
+	connectTool := tools.NewConnect(mock, mock, mock, validProof)
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"docs_proof": validProof,
+	}
+	result, err := connectTool.Handler(t.Context(), request)
+
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "failed to convert account resource to text resource")
+	assert.Nil(t, result)
+}
+
+func TestConnect_Handler_InvalidAccountJSON(t *testing.T) {
+	mock := &MockResourceFetcher{
+		AccountsFunc: func(ctx context.Context, accountName string) ([]mcp.ResourceContents, error) {
+			// Return invalid JSON to trigger unmarshal error
+			return []mcp.ResourceContents{
+				mcp.TextResourceContents{
+					URI:      "firebolt://accounts/test-account",
+					MIMEType: mimetype.JSON,
+					Text:     "invalid json",
+				},
+			}, nil
+		},
+	}
+
+	connectTool := tools.NewConnect(mock, mock, mock, validProof)
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"docs_proof": validProof,
+	}
+	result, err := connectTool.Handler(t.Context(), request)
+
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "failed to unmarshal account resource")
+	assert.Nil(t, result)
+}
+
+func TestConnect_Handler_DatabasesFetchFailure(t *testing.T) {
+	mock := &MockResourceFetcher{
+		AccountsFunc: func(ctx context.Context, accountName string) ([]mcp.ResourceContents, error) {
+			return []mcp.ResourceContents{createAccountResource("test-account")}, nil
+		},
+		DatabasesFunc: func(ctx context.Context, accountName, databaseName string) ([]mcp.ResourceContents, error) {
+			return nil, errors.New("failed to fetch databases")
+		},
+	}
+
+	connectTool := tools.NewConnect(mock, mock, mock, validProof)
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"docs_proof": validProof,
+	}
+	result, err := connectTool.Handler(t.Context(), request)
+
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "failed to discover database resources")
+	assert.Nil(t, result)
+}
+
+func TestConnect_Handler_EnginesFetchFailure(t *testing.T) {
+	mock := &MockResourceFetcher{
+		AccountsFunc: func(ctx context.Context, accountName string) ([]mcp.ResourceContents, error) {
+			return []mcp.ResourceContents{createAccountResource("test-account")}, nil
+		},
+		DatabasesFunc: func(ctx context.Context, accountName, databaseName string) ([]mcp.ResourceContents, error) {
+			return []mcp.ResourceContents{}, nil
+		},
+		EnginesFunc: func(ctx context.Context, accountName, engineName string) ([]mcp.ResourceContents, error) {
+			return nil, errors.New("failed to fetch engines")
+		},
+	}
+
+	connectTool := tools.NewConnect(mock, mock, mock, validProof)
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"docs_proof": validProof,
+	}
+	result, err := connectTool.Handler(t.Context(), request)
+
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "failed to discover engine resources")
+	assert.Nil(t, result)
+}
diff --git a/pkg/tools/docs.go b/pkg/tools/docs.go
new file mode 100644
index 0000000..b387a7d
--- /dev/null
+++ b/pkg/tools/docs.go
@@ -0,0 +1,110 @@
+package tools
+
+import (
+	"context"
+	"fmt"
+
+	"github.com/mark3labs/mcp-go/mcp"
+
+	"github.com/firebolt-db/mcp-server/pkg/helpers/itertools"
+	"github.com/firebolt-db/mcp-server/pkg/resources"
+)
+
+// DocsResourcesFetcher defines the interface for retrieving documentation resources.
+// Implementations should provide methods to fetch Firebolt documentation.
+type DocsResourcesFetcher interface {
+	// FetchDocsResources retrieves documentation content for a specified article.
+	// If article is empty, the implementation should determine an appropriate default behavior.
+	FetchDocsResources(_ context.Context, article string) ([]mcp.ResourceContents, error)
+}
+
+// Docs represents a tool for fetching and returning Firebolt documentation.
+// It provides access to documentation articles that explain Firebolt concepts and functionality.
+type Docs struct {
+	docsFetcher DocsResourcesFetcher // Fetches documentation resources
+}
+
+// NewDocs creates a new instance of the Docs tool with the provided documentation fetcher.
+// It requires an implementation for fetching documentation articles.
+func NewDocs(docsFetcher DocsResourcesFetcher) *Docs {
+	return &Docs{
+		docsFetcher: docsFetcher,
+	}
+}
+
+// Tool returns the mcp.Tool definition for the Docs tool.
+// This defines how the tool is represented in the MCP system, including its name, description,
+// and parameters it accepts.
+func (t *Docs) Tool() mcp.Tool {
+	return mcp.NewTool(
+		"firebolt_docs",
+		mcp.WithDescription(
+			"Returns Firebolt documentation articles. "+
+				"Use this tool whenever you asked a question about Firebolt or need to connect to and use Firebolt. "+
+				"Firebolt differs significantly from other databases, so it's important to gather some initial information before providing accurate answers. "+
+				"Calling this tool without any parameters will return an overview document containing essential Firebolt fundamentals, "+
+				"an index of detailed documentation articles, and a secret value expected by `firebolt_connect` tool that confirms you have read the documentation. "+
+				"To retrieve specific articles, call this tool with their corresponding IDs using the `articles` parameter.",
+		),
+		mcp.WithArray(
+			"articles",
+			mcp.Title("Article IDs"),
+			mcp.Description("Identifiers of the articles to fetch from Firebolt documentation"),
+			mcp.MinItems(1),
+			mcp.Items(map[string]any{
+				"type": "string",
+			}),
+		),
+	)
+}
+
+// Handler processes tool invocation requests and returns Firebolt documentation articles.
+// If no specific articles are requested, it returns a set of default articles including an overview,
+// a proof of documentation reading (needed for the connect tool), and a reference article.
+// If specific articles are requested via the "articles" parameter, it fetches and returns those.
+func (t *Docs) Handler(ctx context.Context, request mcp.CallToolRequest) (*mcp.CallToolResult, error) {
+
+	var (
+		articleIDs []any                  // List of article IDs to fetch
+		results    []mcp.ResourceContents // Collection of fetched documentation resources
+	)
+
+	// Extract article IDs from request parameters if provided
+	val, ok := request.Params.Arguments["articles"]
+	if ok && val != nil {
+		articleIDs = val.([]any)
+	} else {
+		// Default articles to return if none specified
+		articleIDs = append(
+			articleIDs,
+			resources.DocsArticleOverview,  // General Firebolt overview
+			resources.DocsArticleProof,     // Contains proof value for connect tool
+			resources.DocsArticleReference, // Reference documentation
+		)
+	}
+
+	// Fetch each requested article
+	for _, value := range articleIDs {
+		// Ensure value is a string
+		strValue, ok := value.(string)
+		if !ok {
+			return nil, fmt.Errorf("invalid type for article ID: %T", value)
+		}
+
+		// Fetch the article resources
+		articleResources, err := t.docsFetcher.FetchDocsResources(ctx, strValue)
+		if err != nil {
+			return nil, fmt.Errorf("failed to discover resources: %w", err)
+		}
+		results = append(results, articleResources...)
+	}
+
+	// Return the results as embedded resources
+	return &mcp.CallToolResult{
+		Result: mcp.Result{},
+		Content: itertools.Map(results, func(i mcp.ResourceContents) mcp.Content {
+			return mcp.NewEmbeddedResource(i)
+		}),
+		IsError: false,
+	}, nil
+}
diff --git a/pkg/tools/docs_test.go b/pkg/tools/docs_test.go
new file mode 100644
index 0000000..53245af
--- /dev/null
+++ b/pkg/tools/docs_test.go
@@ -0,0 +1,246 @@
+package tools_test
+
+import (
+	"context"
+	"errors"
+	"testing"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/helpers/mimetype"
+	"github.com/firebolt-db/mcp-server/pkg/resources"
+	"github.com/firebolt-db/mcp-server/pkg/tools"
+)
+
+func TestNewDocs(t *testing.T) {
+	mock := &MockDocsFetcher{}
+	docsTool := tools.NewDocs(mock)
+	assert.NotNil(t, docsTool)
+}
+
+func TestDocs_Tool(t *testing.T) {
+	mock := &MockDocsFetcher{}
+	docsTool := tools.NewDocs(mock)
+
+	tool := docsTool.Tool()
+	assert.Equal(t, "firebolt_docs", tool.Name)
+	assert.Contains(t, tool.Description, "Returns Firebolt documentation articles")
+}
+
+func TestDocs_Handler_DefaultArticles(t *testing.T) {
+	// Create test data for default articles
+	mockArticles := map[string]string{
+		resources.DocsArticleOverview:  "# Firebolt Overview\nThis is an overview of Firebolt.",
+		resources.DocsArticleProof:     "# Proof Document\nSecret proof: proof_value_123",
+		resources.DocsArticleReference: "# Reference\nThis is the reference documentation.",
+	}
+
+	// Create mock fetcher that returns the mock articles
+	mock := &MockDocsFetcher{
+		FetchDocsFunc: func(ctx context.Context, article string) ([]mcp.ResourceContents, error) {
+			content, exists := mockArticles[article]
+			if !exists {
+				return nil, errors.New("article not found")
+			}
+			return []mcp.ResourceContents{createDocResource(article, content)}, nil
+		},
+	}
+
+	// Create the tool
+	docsTool := tools.NewDocs(mock)
+
+	// Execute the handler with empty request (should return default articles)
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{}
+	result, err := docsTool.Handler(t.Context(), request)
+
+	// Assertions
+	require.NoError(t, err)
+	require.NotNil(t, result)
+	assert.False(t, result.IsError)
+
+	// Should return 3 default articles
+	assert.Len(t, result.Content, 3)
+
+	// Verify the content contains all expected resources
+	resourceMap := make(map[string]string)
+	for _, content := range result.Content {
+		embeddedResource, ok := content.(mcp.EmbeddedResource)
+		require.True(t, ok, "Expected EmbeddedResource")
+
+		textResource, ok := embeddedResource.Resource.(mcp.TextResourceContents)
+		require.True(t, ok, "Expected TextResourceContents")
+
+		resourceMap[textResource.URI] = textResource.Text
+	}
+
+	// Check if all default articles are present
+	for articleID, expectedContent := range mockArticles {
+		uri := "firebolt://docs/" + articleID
+		assert.Contains(t, resourceMap, uri)
+		assert.Equal(t, expectedContent, resourceMap[uri])
+	}
+}
+
+func TestDocs_Handler_SpecificArticles(t *testing.T) {
+	// Create test data for specific articles
+	mockArticles := map[string]string{
+		"article1": "# Article 1\nContent for article 1",
+		"article2": "# Article 2\nContent for article 2",
+	}
+
+	// Create mock fetcher that returns the mock articles
+	mock := &MockDocsFetcher{
+		FetchDocsFunc: func(ctx context.Context, article string) ([]mcp.ResourceContents, error) {
+			content, exists := mockArticles[article]
+			if !exists {
+				return nil, errors.New("article not found")
+			}
+			return []mcp.ResourceContents{createDocResource(article, content)}, nil
+		},
+	}
+
+	// Create the tool
+	docsTool := tools.NewDocs(mock)
+
+	// Execute the handler with specific articles
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"articles": []any{"article1", "article2"},
+	}
+	result, err := docsTool.Handler(t.Context(), request)
+
+	// Assertions
+	require.NoError(t, err)
+	require.NotNil(t, result)
+	assert.False(t, result.IsError)
+
+	// Should return the 2 requested articles
+	assert.Len(t, result.Content, 2)
+
+	// Verify the content contains all expected resources
+	resourceMap := make(map[string]string)
+	for _, content := range result.Content {
+		embeddedResource, ok := content.(mcp.EmbeddedResource)
+		require.True(t, ok, "Expected EmbeddedResource")
+
+		textResource, ok := embeddedResource.Resource.(mcp.TextResourceContents)
+		require.True(t, ok, "Expected TextResourceContents")
+
+		resourceMap[textResource.URI] = textResource.Text
+	}
+
+	// Check if all requested articles are present
+	for articleID, expectedContent := range mockArticles {
+		uri := "firebolt://docs/" + articleID
+		assert.Contains(t, resourceMap, uri)
+		assert.Equal(t, expectedContent, resourceMap[uri])
+	}
+}
+
+func TestDocs_Handler_FetchError(t *testing.T) {
+	// Create mock fetcher that returns an error
+	mock := &MockDocsFetcher{
+		FetchDocsFunc: func(ctx context.Context, article string) ([]mcp.ResourceContents, error) {
+			return nil, errors.New("failed to fetch article")
+		},
+	}
+
+	// Create the tool
+	docsTool := tools.NewDocs(mock)
+
+	// Execute the handler
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{}
+	result, err := docsTool.Handler(t.Context(), request)
+
+	// Assertions
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "failed to discover resources")
+	assert.Nil(t, result)
+}
+
+func TestDocs_Handler_InvalidArticleID(t *testing.T) {
+	// Create the tool with any mock
+	mock := &MockDocsFetcher{}
+	docsTool := tools.NewDocs(mock)
+
+	// Execute the handler with an invalid article ID type
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"articles": []any{123}, // Not a string
+	}
+	result, err := docsTool.Handler(t.Context(), request)
+
+	// Assertions
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "invalid type for article ID")
+	assert.Nil(t, result)
+}
+
+func TestDocs_Handler_MultipleFetchedResources(t *testing.T) {
+	// Create mock fetcher that returns multiple resources for a single article ID
+	mock := &MockDocsFetcher{
+		FetchDocsFunc: func(ctx context.Context, article string) ([]mcp.ResourceContents, error) {
+			if article == "multi-resource" {
+				return []mcp.ResourceContents{
+					createDocResource("multi-resource-1", "# Part 1\nContent part 1"),
+					createDocResource("multi-resource-2", "# Part 2\nContent part 2"),
+				}, nil
+			}
+			return nil, errors.New("article not found")
+		},
+	}
+
+	// Create the tool
+	docsTool := tools.NewDocs(mock)
+
+	// Execute the handler
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"articles": []any{"multi-resource"},
+	}
+	result, err := docsTool.Handler(t.Context(), request)
+
+	// Assertions
+	require.NoError(t, err)
+	require.NotNil(t, result)
+	assert.False(t, result.IsError)
+
+	// Should return both resources
+	assert.Len(t, result.Content, 2)
+
+	// Verify both parts are present
+	resourceMap := make(map[string]bool)
+	for _, content := range result.Content {
+		embeddedResource, ok := content.(mcp.EmbeddedResource)
+		require.True(t, ok, "Expected EmbeddedResource")
+
+		textResource, ok := embeddedResource.Resource.(mcp.TextResourceContents)
+		require.True(t, ok, "Expected TextResourceContents")
+
+		resourceMap[textResource.URI] = true
+	}
+
+	assert.True(t, resourceMap["firebolt://docs/multi-resource-1"])
+	assert.True(t, resourceMap["firebolt://docs/multi-resource-2"])
+}
+
+type MockDocsFetcher struct {
+	FetchDocsFunc func(ctx context.Context, article string) ([]mcp.ResourceContents, error)
+}
+
+func (m *MockDocsFetcher) FetchDocsResources(ctx context.Context, article string) ([]mcp.ResourceContents, error) {
+	return m.FetchDocsFunc(ctx, article)
+}
+
+// Helper to create a doc resource
+func createDocResource(articleID, content string) mcp.ResourceContents {
+	return mcp.TextResourceContents{
+		URI:      "firebolt://docs/" + articleID,
+		MIMEType: mimetype.Markdown,
+		Text:     content,
+	}
+}
diff --git a/pkg/tools/query.go b/pkg/tools/query.go
new file mode 100644
index 0000000..e1d1c8e
--- /dev/null
+++ b/pkg/tools/query.go
@@ -0,0 +1,113 @@
+package tools
+
+import (
+	"context"
+	"encoding/json"
+	"errors"
+	"fmt"
+
+	"github.com/mark3labs/mcp-go/mcp"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+	"github.com/firebolt-db/mcp-server/pkg/helpers/args"
+)
+
+// Query represents a tool for executing SQL queries against Firebolt databases.
+// It handles connecting to the appropriate account, database, and engine before
+// executing the query and returning results.
+type Query struct {
+	dbPool database.Pool
+}
+
+// NewQuery creates a new instance of the Query tool with the provided database connection pool.
+// The connection pool is responsible for managing connections to different Firebolt
+// account/database/engine combinations.
+func NewQuery(dbPool database.Pool) *Query {
+	return &Query{
+		dbPool: dbPool,
+	}
+}
+
+// Tool returns the mcp.Tool definition for the Query tool.
+// This defines how the tool is represented in the MCP system, including:
+// - The tool's name and description
+// - Required and optional parameters with their descriptions
+func (t *Query) Tool() mcp.Tool {
+	return mcp.NewTool(
+		"firebolt_query",
+		mcp.WithDescription("Execute an SQL query against Firebolt."),
+		mcp.WithString(
+			"query",
+			mcp.Required(),
+			mcp.Title("Query"),
+			mcp.Description("SQL query to execute"),
+		),
+		mcp.WithString(
+			"account",
+			mcp.Required(),
+			mcp.Title("Account name"),
+			mcp.Description("Name of the account to connect to"),
+		),
+		mcp.WithString(
+			"database",
+			mcp.Title("Database name"),
+			mcp.Description(`
+				Name of the database to send the query to.
+				If not provided, no database will be specified.
+				This still allows you to manage Firebolt organization and account metadata.
+			`),
+		),
+		mcp.WithString(
+			"engine",
+			mcp.Title("Engine name"),
+			mcp.Description(`
+				Name of the engine to use for query execution.
+				If not provided, the system engine will be used.
+				Please note that the system engine can only be used for metadata queries and operations (DDL and DCL).
+				Metadata queries are those that configure your Firebolt organization and account, or define the schema of your data.
+				It will reject any queries that affect actual data stored in database.
+			`),
+		),
+	)
+}
+
+// Handler processes tool invocation requests and executes SQL queries against Firebolt.
+// It performs the following steps:
+// 1. Extracts and validates required/optional parameters from the request
+// 2. Acquires a database connection from the pool using the specified parameters
+// 3. Executes the query against the database
+// 4. Returns the query results as JSON
+func (t *Query) Handler(ctx context.Context, request mcp.CallToolRequest) (*mcp.CallToolResult, error) {
+
+	// Extract the required and optional arguments from the request
+	requireds, err1 := args.Strings(request.Params.Arguments, "query", "account")
+	optionals, err2 := args.MaybeStrings(request.Params.Arguments, "database", "engine")
+	if err := errors.Join(err1, err2); err != nil {
+		return nil, fmt.Errorf("bad request: %w", err)
+	}
+
+	// Acquire a connection to the database using the provided parameters
+	conn, err := t.dbPool.GetConnection(database.PoolParams{
+		AccountName:  requireds[1],
+		DatabaseName: optionals[0],
+		EngineName:   optionals[1],
+	})
+	if err != nil {
+		return nil, fmt.Errorf("failed to obtain database connection: %w", err)
+	}
+
+	// Execute the query using the connection
+	result, err := conn.Query(ctx, requireds[0])
+	if err != nil {
+		return nil, fmt.Errorf("failed to query database: %w", err)
+	}
+
+	// Convert the query result to JSON format
+	resultJSON, err := json.Marshal(result)
+	if err != nil {
+		return nil, fmt.Errorf("failed to marshal query result: %w", err)
+	}
+
+	// Create a new tool result with the JSON data and return it
+	return mcp.NewToolResultText(string(resultJSON)), nil
+}
diff --git a/pkg/tools/query_test.go b/pkg/tools/query_test.go
new file mode 100644
index 0000000..1049378
--- /dev/null
+++ b/pkg/tools/query_test.go
@@ -0,0 +1,270 @@
+package tools_test
+
+import (
+	"context"
+	"encoding/json"
+	"errors"
+	"testing"
+
+	"github.com/mark3labs/mcp-go/mcp"
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+
+	"github.com/firebolt-db/mcp-server/pkg/clients/database"
+	"github.com/firebolt-db/mcp-server/pkg/clients/database/databasemock"
+	"github.com/firebolt-db/mcp-server/pkg/tools"
+)
+
+func TestNewQuery(t *testing.T) {
+	mockPool := databasemock.NewPoolMock()
+	queryTool := tools.NewQuery(mockPool)
+	assert.NotNil(t, queryTool)
+}
+
+func TestQuery_Tool(t *testing.T) {
+	mockPool := databasemock.NewPoolMock()
+	queryTool := tools.NewQuery(mockPool)
+
+	tool := queryTool.Tool()
+	assert.Equal(t, "firebolt_query", tool.Name)
+	assert.Contains(t, tool.Description, "Execute an SQL query against Firebolt")
+}
+
+func TestQuery_Handler_Success(t *testing.T) {
+
+	// Create mock query result
+	mockResult := []map[string]any{
+		{
+			"id":   1,
+			"name": "test",
+		},
+		{
+			"id":   2,
+			"name": "test2",
+		},
+	}
+
+	mockConnection := databasemock.NewConnectionMock().WithQueryFunc(
+		func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+			assert.Equal(t, "SELECT * FROM test", sql)
+			return mockResult, nil
+		},
+	)
+
+	mockPool := databasemock.NewPoolMock()
+	mockPool.RegisterConnection(database.PoolParams{
+		AccountName:  "test-account",
+		DatabaseName: ptrTo("test-db"),
+		EngineName:   ptrTo("test-engine"),
+	}, mockConnection)
+
+	queryTool := tools.NewQuery(mockPool)
+
+	// Create a request with all parameters
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"query":    "SELECT * FROM test",
+		"account":  "test-account",
+		"database": "test-db",
+		"engine":   "test-engine",
+	}
+
+	// Execute the handler
+	result, err := queryTool.Handler(t.Context(), request)
+
+	// Assertions
+	require.NoError(t, err)
+	require.NotNil(t, result)
+	assert.False(t, result.IsError)
+
+	// Check the connection was requested with the right parameters
+	callCount := mockPool.GetConnectionCallCount(database.PoolParams{
+		AccountName:  "test-account",
+		DatabaseName: ptrTo("test-db"),
+		EngineName:   ptrTo("test-engine"),
+	})
+	assert.Equal(t, 1, callCount)
+
+	// Verify the result contains the expected JSON data
+	expectedJSON, _ := json.Marshal(mockResult)
+	assert.Equal(t, string(expectedJSON), result.Content[0].(mcp.TextContent).Text)
+}
+
+func TestQuery_Handler_MinimalParameters(t *testing.T) {
+	// Create mock query result
+	mockResult := []map[string]any{
+		{
+			"success": true,
+		},
+	}
+
+	mockConnection := databasemock.NewConnectionMock().WithQueryFunc(
+		func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+			assert.Equal(t, "SHOW ENGINES", sql)
+			return mockResult, nil
+		},
+	)
+
+	mockPool := databasemock.NewPoolMock()
+	mockPool.RegisterConnection(database.PoolParams{
+		AccountName: "test-account",
+		// No database or engine specified
+	}, mockConnection)
+
+	queryTool := tools.NewQuery(mockPool)
+
+	// Create a request with only required parameters
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"query":   "SHOW ENGINES",
+		"account": "test-account",
+		// No database or engine
+	}
+
+	// Execute the handler
+	result, err := queryTool.Handler(t.Context(), request)
+
+	// Assertions
+	require.NoError(t, err)
+	require.NotNil(t, result)
+	assert.False(t, result.IsError)
+
+	// Check the connection was requested with the right parameters
+	callCount := mockPool.GetConnectionCallCount(database.PoolParams{
+		AccountName: "test-account",
+		// No database or engine
+	})
+	assert.Equal(t, 1, callCount)
+
+	// Verify the result contains the expected JSON data
+	expectedJSON, _ := json.Marshal(mockResult)
+	assert.Equal(t, string(expectedJSON), result.Content[0].(mcp.TextContent).Text)
+}
+
+func TestQuery_Handler_MissingRequiredParameters(t *testing.T) {
+	mockPool := databasemock.NewPoolMock()
+	queryTool := tools.NewQuery(mockPool)
+
+	testCases := []struct {
+		name      string
+		arguments map[string]any
+		errSubstr string
+	}{
+		{
+			name:      "missing query",
+			arguments: map[string]any{"account": "test-account"},
+			errSubstr: "query",
+		},
+		{
+			name:      "missing account",
+			arguments: map[string]any{"query": "SELECT 1"},
+			errSubstr: "account",
+		},
+		{
+			name:      "empty request",
+			arguments: map[string]any{},
+			errSubstr: "bad request",
+		},
+	}
+
+	for _, tc := range testCases {
+		t.Run(tc.name, func(t *testing.T) {
+			request := mcp.CallToolRequest{}
+			request.Params.Arguments = tc.arguments
+
+			result, err := queryTool.Handler(t.Context(), request)
+
+			assert.Error(t, err)
+			assert.Contains(t, err.Error(), tc.errSubstr)
+			assert.Nil(t, result)
+		})
+	}
+}
+
+func TestQuery_Handler_ConnectionError(t *testing.T) {
+	mockPool := databasemock.NewPoolMock().WithGetConnectionFunc(
+		func(params database.PoolParams) (database.Connection, error) {
+			return nil, errors.New("connection error")
+		},
+	)
+
+	queryTool := tools.NewQuery(mockPool)
+
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"query":   "SELECT 1",
+		"account": "test-account",
+	}
+
+	result, err := queryTool.Handler(t.Context(), request)
+
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "failed to obtain database connection")
+	assert.Nil(t, result)
+}
+
+func TestQuery_Handler_QueryError(t *testing.T) {
+	mockConnection := databasemock.NewConnectionMock().WithQueryFunc(
+		func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+			return nil, errors.New("query execution error")
+		},
+	)
+
+	mockPool := databasemock.NewPoolMock()
+	mockPool.RegisterConnection(database.PoolParams{
+		AccountName: "test-account",
+	}, mockConnection)
+
+	queryTool := tools.NewQuery(mockPool)
+
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"query":   "SELECT * FROM nonexistent_table",
+		"account": "test-account",
+	}
+
+	result, err := queryTool.Handler(t.Context(), request)
+
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "failed to query database")
+	assert.Nil(t, result)
+}
+
+func TestQuery_Handler_JSONMarshalError(t *testing.T) {
+	// Create a value that can't be marshaled to JSON (a function)
+	unmarshalableValue := func() {}
+	mockResult := []map[string]any{
+		{
+			"unmarshalable": unmarshalableValue,
+		},
+	}
+
+	mockConnection := databasemock.NewConnectionMock().WithQueryFunc(
+		func(ctx context.Context, sql string, args ...any) ([]map[string]any, error) {
+			return mockResult, nil
+		},
+	)
+
+	mockPool := databasemock.NewPoolMock()
+	mockPool.RegisterConnection(database.PoolParams{
+		AccountName: "test-account",
+	}, mockConnection)
+
+	queryTool := tools.NewQuery(mockPool)
+
+	request := mcp.CallToolRequest{}
+	request.Params.Arguments = map[string]any{
+		"query":   "SELECT problematic_data()",
+		"account": "test-account",
+	}
+
+	result, err := queryTool.Handler(t.Context(), request)
+
+	assert.Error(t, err)
+	assert.Contains(t, err.Error(), "failed to marshal query result")
+	assert.Nil(t, result)
+}
+
+func ptrTo[T any](v T) *T {
+	return &v
+}
diff --git a/pkg/version/version.go b/pkg/version/version.go
new file mode 100644
index 0000000..d793112
--- /dev/null
+++ b/pkg/version/version.go
@@ -0,0 +1,27 @@
+package version
+
+import (
+	"fmt"
+	"runtime"
+	"runtime/debug"
+)
+
+// Version is set during build time to the current version of the application.
+var Version = "0.0.0-dev"
+
+// GetFullVersion returns the version of the application along with the Go version
+func GetFullVersion() string {
+
+	buildInfo, ok := debug.ReadBuildInfo()
+	if ok {
+		return fmt.Sprintf(
+			"%s (%s, %s/%s)",
+			Version,
+			buildInfo.GoVersion,
+			runtime.GOOS,
+			runtime.GOARCH,
+		)
+	}
+
+	return Version
+}

From dd1a115005dafcac053dd115143ed34aced3a971 Mon Sep 17 00:00:00 2001
From: Ivan Koptiev <ivan@firebolt.io>
Date: Mon, 7 Apr 2025 23:47:51 +0300
Subject: [PATCH 2/4] chore: changes

---
 .goreleaser.yaml | 3 ---
 .legitignore     | 1 +
 2 files changed, 1 insertion(+), 3 deletions(-)
 create mode 100644 .legitignore

diff --git a/.goreleaser.yaml b/.goreleaser.yaml
index a5938bf..0bc6b97 100644
--- a/.goreleaser.yaml
+++ b/.goreleaser.yaml
@@ -77,6 +77,3 @@ docker_manifests:
       - ghcr.io/firebolt-db/mcp-server:{{ .Version }}-arm64v8
 
 release: {}
-
-npm:
-  - name: "@firebolt-db/mcp-server"
diff --git a/.legitignore b/.legitignore
new file mode 100644
index 0000000..f767cfc
--- /dev/null
+++ b/.legitignore
@@ -0,0 +1 @@
+cmd/docs-scrapper/fireboltdocs/**

From 801ad8968a1d012c39d9c8ca3fa50bbc0cef83ab Mon Sep 17 00:00:00 2001
From: Ivan Koptiev <ivan@firebolt.io>
Date: Mon, 7 Apr 2025 23:51:46 +0300
Subject: [PATCH 3/4] chore: changes

---
 .github/workflows/release.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
index 530c603..5619a99 100644
--- a/.github/workflows/release.yaml
+++ b/.github/workflows/release.yaml
@@ -32,7 +32,7 @@ jobs:
         uses: goreleaser/goreleaser-action@v6
         with:
           version: "~> v2"
-          args: release --clean
+          args: release --clean --snapshot
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 

From bc136fc88f892875aa1020832c992e4724762765 Mon Sep 17 00:00:00 2001
From: Ivan Koptiev <ivan@firebolt.io>
Date: Tue, 8 Apr 2025 00:02:02 +0300
Subject: [PATCH 4/4] chore: changes

---
 .github/workflows/release.yaml | 2 +-
 .goreleaser.yaml               | 2 --
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
index 5619a99..530c603 100644
--- a/.github/workflows/release.yaml
+++ b/.github/workflows/release.yaml
@@ -32,7 +32,7 @@ jobs:
         uses: goreleaser/goreleaser-action@v6
         with:
           version: "~> v2"
-          args: release --clean --snapshot
+          args: release --clean
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
diff --git a/.goreleaser.yaml b/.goreleaser.yaml
index 0bc6b97..45aa84f 100644
--- a/.goreleaser.yaml
+++ b/.goreleaser.yaml
@@ -39,7 +39,6 @@ dockers:
   - use: buildx
     image_templates:
       - "ghcr.io/firebolt-db/mcp-server:{{ .Version }}-amd64"
-    skip_push: true
     build_flag_templates:
       - --platform=linux/amd64
       - --label=org.opencontainers.image.title={{ .ProjectName }}
@@ -54,7 +53,6 @@ dockers:
     image_templates:
       - "ghcr.io/firebolt-db/mcp-server:{{ .Version }}-arm64v8"
     goarch: arm64
-    skip_push: true
     build_flag_templates:
       - --platform=linux/arm64/v8
       - --label=org.opencontainers.image.title={{ .ProjectName }}