> ## Documentation Index > Fetch the complete documentation index at: https://docs.peopledatalabs.com/llms.txt > Use this file to discover all available pages before exploring further. # February 2024 Release Announcement **This announcement is for PDL Snowflake Customers** If you are a current PDL customer receiving data through Snowflake, please read this announcement regarding the upcoming changes to the Snowflake Table Schemas scheduled for the May 2024 release. ## ⚠️ Snowflake Schema Standardization **Change Expected In: v26.1 / May 2024**\ Previous Announcements: [v24 / October 2023](/changelog/october-2023-release-notes-v24), [v25 / January 2024](/changelog/january-2024-release-notes-v25#snowflake) As announced in our previous release notes (linked above) we will be standardizing our Snowflake Person and Company Schemas **in May 2024 (v26.1)**. This will be a breaking change to our existing Snowflake schema, and so this announcement aims to provide some additional resources and information to prepare our customers for the transition. ### Summary of Schema Changes We are migrating all Snowflake users to a common delivery schema, which represents changes to the current format that data is being received in. These changes apply to both the **Person and Company Snowflake Schema** and include: * Table and column name changes * Additions/modifications of columns within tables * Data type changes across columns The summary of these changes is as follows: **Person Schema Changes for Snowflake** * (Table Rename) “Plural” table names will now be “Singular” (i.e. `languages` is now `language`, `certifications` is now `certification`, etc) * (Column Rename) `num_sources` will now be `count_sources` * (Column Rename) `num_records` will now be `count_records` * (Column Rename) `linkedin_connections` will now be `count_linkedin_connections` * (Column Rename) `facebook_friends` will now be `count_facebook_friends` * (Column Rename) `gender` will now be `sex` * (Type Change) All `Date` types will now be `String` types **Company Schema Changes for Snowflake** * (Table Rename) “Plural” table names will now be “Singular” (i.e. `subsidiaries` is now `subsidiary`, `profiles` is now `profile`, etc) * (Table Schema Change) Table `top_us_employee_metro` now contains separate columns for `headcount` (`INT`) and `growth_rate_12_month` (`FLOAT`) * (Column Rename) `top_next_employer_by_role.employer` will be renamed to `top_next_employer_by_role.next_company_id` * (Column Rename) `top_previous_employer_by_role.employer` will be renamed to `top_previous_employer_by_role.previous_company_id` * (Column Rename) `recent_exec_departure.pdl_id` will be renamed to `recent_exec_departure.person_id` * (Column Rename) `recent_exec_departure_job_title_level.pdl_id` will be renamed to `recent_exec_departure_job_title_level.person_id` * (Column Rename) `recent_exec_departure_new_company_job_title_level.pdl_id` will be renamed to `recent_exec_departure_new_company_job_title_level.person_id` * (Column Rename) `recent_exec_hire.pdl_id` will be renamed to `recent_exec_hire.person_id` * (Column Rename) `recent_exec_hire_job_title_level.pdl_id` will be renamed to `recent_exec_hire_job_title_level.person_id` * (Column Rename) `recent_exec_hire_previous_company_job_title_level.pdl_id` will be renamed to `recent_exec_hire_previous_company_job_title_level.person_id` * (Column Rename) All columns referencing employee count metrics will be renamed to `count` * (Column Rename) More descriptive columns within tables describing growth rates (e.g. column `tenure` in table `average_tenure_by_level` and column `growth_rate` in table `headcount_12mo_growth_by_role`) * (Column Rename) Closer adherence to SQL naming conventions (e.g. `linkedin_employee_count` will now be `count_linkedin_employee` * (Type Change) All `Date` types will now be `String` types ### How to Prepare for the Transition Before the May 2024 (v26.1), we strongly suggest you: 1. Make a copy of your current data after your April 2024 delivery. This way you not only have a backup, but can also compare new to old after you switch over. 2. Go through the new standard schemas, which are included in the **Resources** section below as well as [here](/docs/data-delivery-using-snowflake#standard-schemas) 3. Prepare any script changes to your existing processes before the switch in May 2024. For any questions or help transitioning to these new schema, please reach out to your Customer Success Manager. ### Resources **Standard Schemas** We now have explicit documentation of the Person and Company Snowflake Schemas that will go into effect with the May 2024 Release (v26.1). We encourage our snowflake customers to ensure their data pipelines can support the specifications linked below. These documents are also linked in the [Data Delivery Using Snowflake](/docs/data-delivery-using-snowflake#standard-schemas) page as well. * [Person Schema for Snowflake (v26.1)](https://drive.google.com/file/d/1AFGb2CLTOUUSdC0XZzND0NDvYCyHtOQG/view?usp=sharing) * [Company Schema for Snowflake (v26.1)](https://drive.google.com/file/d/15FIv6U1O6BzLAhYvv8tmNsDDGvq30xQq/view?usp=sharing) **Snowflake Data Sample** In addition, we will also have some sample data in these new schema formats available for customers to test with to ensure their data pipelines fully support the upcoming changes. * Data Sample on Snowflake Marketplace (coming soon) ## Related topics - [May 2024 Release Notes](/changelog/may-2024-release-announcement-v26-1.md) - [February 2025 Release Notes](/changelog/february-2025-release-notes-v291.md) - [February 2026 Release Notes](/changelog/february-2026-release-notes-v331.md) - [November 2024 Release Notes](/changelog/november-2024-release-notes-v281.md) - [December 2024 Release Notes](/changelog/december-2024-release-notes-v282.md)