No, unfortunately, as there is so much data in ChEMBL, it is not possible to store this on the FTP site as a download. It would be too big to be downloaded to users' computers. If users would like to obtain all of the bioactivity data, we urge them to install a database instance for ChEMBL using Oracle, MySQL, PostgreSQL or SQLite.
You cannot download a single SDFile of the compound information including the structure, alongside the bioactivity data. However, you can download these separately and use a program such as Pipeline Pilot or Knime to join the files together.
No there is no password set for this, so if you are asked for a password it is likely to be a local MS SQL issue and you will need to contact your database administrators to gain access.
You will need to use a tablespace with about 12GB of free space available to import the ChEMBL oracle dump file.
The SDfile contains the structures and the IDs of all the compounds currently found in the database. The MySQL/Oracle downloads contain all the compounds and associated bioactivities, but needs to be uploaded into a database to be viewed properly.
If you get an error message, please send an email to [email protected], or create an issue in our GitHub repository. We recommend that you include the full url of the page in your message, this helps us to identify the problem.
When a user generates a download from the interface, the file is kept in our servers for 7 days after the file was created. For example, if a file was generated on 17th May 2019 at 8:00 AM, it will be kept in our servers until 24th May 2019 at 8:00 AM. This means that if the same download is requested again during that period, the file will not be generated again and it will be ready to be downloaded immediately. The times shown are always based in the UTC timezone.
During the period in which we keep the downloaded file, we also keep the original query parameters required to generate the file. The parameters and the file itself are deleted after the expiration time has passed. It is important to make clear that we don't save any data that can be used to identify the user generating the file. We save just the necessary data to be able to provide the service.