Compounds
Name
Compound type
Version
Size
File
Compounds (csv)
original
02.2025
64.86 MB
Compounds (csv)
standardized
02.2025
56.53 MB
Compounds (csv)
nonisomeric
02.2025
46.73 MB
Compounds (sdf)
original
02.2025
461.27 MB
Compounds (sdf)
standardized
02.2025
397.54 MB
Compounds (sdf)
nonisomeric
02.2025
349.09 MB
Targets & activities
Name
Compound type
Version
Size
File
Targets and activities (csv)
original
02.2025
101.84 MB
Targets and activities (csv)
standardized
02.2025
101.4 MB
Targets and activities (csv)
nonisomeric
02.2025
100.01 MB
Targets and activities (xlsx)
original
02.2025
91.53 MB
Targets and activities (xlsx)
standardized
02.2025
84.13 MB
Targets and activities (xlsx)
nonisomeric
02.2025
73.73 MB
Chemical probes
Name
Compound type
Version
Size
File
Chemical probes (xlsx)
standardized
02.2025
1.96 MB
Compound ID mapping
Name
Compound type
Version
Size
File
Compound ID mapping (csv)
original
02.2025
41.51 MB
Compound ID mapping (csv)
standardized
02.2025
36.96 MB
Compound ID mapping (csv)
nonisomeric
02.2025
29.38 MB
Database dump
Name
Version
Size
File
PostgreSQL database dump (zip)
02.2025
211.53 MB
SQLite database (zip)
02.2025
335.37 MB
# To restore the data from the PostgreSQL dump, first, you need to extract (unzip) the dump and create an empty database:
CREATE DATABASE database_name WITH OWNER username;
# Then you can restore the dump using:
pg_restore --no-owner -h HOST -p PORT -U USERNAME -d database_name /path/to/pd_dump.sql
Please be aware that internal database IDs are not preserved and may change from version to version. The only IDs that are consistently preserved are compounds' PDIDs, which can be used to link to P&D.