Need a hand importing the MySQL dump? We can help.
Excel and Numbers can't handle files this big, here are your other options
Here are two guides from other websites which will show you how to import the MySQL dumps into your MySQL server. You can ignore the "export" sections and just concentrate on the "import" sections of these articles.
We are working on our own guides for this. In the mean time we hope these links help.
Our database contains over 69.2 million user agents. Unfortunately normal spreadsheet programs like Microsoft Excel or Apple's Numbers App simply can't handle that many records in individual CSV files and so you won't be able to use them to work with our CSV export.
We are aware of several work arounds you can use:
Opening the file with Microsoft Excel will load all the data in the CSV into your computer's memory. This is what causes the problems with loading large files - it's a huge task and most computers don't have enough memory to do it.
Instead, you can make Excel behave more like a proper database, by "connecting" it to the CSV instead of opening it. This causes Excel to only load the data you actually request from it.
There's a good tutorial on Officetuts.com to show you how to connect to CSV files with Excel. Hopefully this solves your problem.
You may find a similar approach on Windows using PowerShell.
In the event that you're not able to use a MySQL system, we've found that importing the CSV into Microsoft Access (on Windows PCs) works well. It lets you search and modify the data quite easily. You could also investigate using SQLite to import a CSV file if you don't have access to a full MySQL system.
We're sorry, there's no way to buy or download user agents for just one browser, operating system or platform. You'll need to download the whole database, import it into a database system and extract the user agents you need.
This is because the data set is so large and can be searched in so many different ways that it's really just not feasible for us to provide them all in seperate files.
It's actually pretty straight-forward to import the user agents yourself; and once you've got them in your database, you can search it again and again in as many different ways as you need.
In October 2019 we loaded a list of useragents provided to us by a customer. Unfortunately the dataset didn't include any meta data (eg the date that they first saw it) so we've had to set the day in October 2019 that we imported it as the creation date. There was also no "times seen" meta data in their dataset, so we started off setting the "times seen" as "1". Keep that in mind if you use this info for risk analysis or other types of statistics.
Our user agent parsing library detects user agents which appear abusive/malcious, restricted (swear words etc), spammy or just plain "weird" and will tell you that via the API. This feature is great to help keep your systems and users safe.
However you won't find this information in the database dumps - this is because we use this information to prevent those user agents from being included in the database dumps. In other words, our database is "clean" and doesn't contain dangerous, restricted, spammy or weird user agents.
If you need to detect dangerous or spammy user agents then use our API instead. Remember, the database isn't for detecting user agents, it's for searching and finding groups/types of user agents.
We accept MasterCard, VISA and AMEX payments for purchasing copies of the database.
We don't accept PayPal, or Bitcoin or other crypto-currencies.