I am a Microsoft SQL Server programmer who is a bit out of practice. I have been asked to assist on a new project. The overall purpose is to organize a large number of recordings so that they can be searched. I have an enormous music library but my songs are several hours long. I need to include things like time, date and location of the recording. I don't have a problem with the general database design. I have two primary questions:

1. I need to use either @{MySQL}|tool:1025| or @{PostgreSQL}|tool:1028| on a @{Linux}|tool:10483| based OS. Which would be better for this application?
2. I have not dealt with a sound based data type before. How do I store that and put it in a table? Thank you.

We have chosen Tibero over Oracle because we want to offer a PL/SQL-as-a-Service that the users can deploy in any Cloud without concerns from our website at some standard cost. With Oracle Database, developers would have to worry about what they implement and the related costs of each feature but the licensing model from Tibero is just 1 price and we have all features included, so we don't have to worry and developers using our SQLaaS neither. PostgreSQL would be open source. We have chosen Tibero over Oracle because we want to offer a PL/SQL that you can deploy in any Cloud without concerns. PostgreSQL would be the open source option but we need to offer an SQLaaS with encryption and more enterprise features in the background and best value option we have found, it was Tibero Database for PL/SQL-based applications.

There'd be a couple of thousands of customers with a similar data structure and a medium number of transactions per day, but the data volume is pretty high (Each customer has around 1 or 2 GB so it would sum up to roughly 2TB). The usage pattern is both read and write-heavy (writes are mostly made through a Windows app, but read operations are made by the user), and I need the historical data for analysis and aggregation. The data model is not join-heavy as is not join-free. If the solution is fully ACID, the better, but must be Highly Available and Horizontally Scalable.

Also, the budget is not so high, and I'd rather be using a handful (at most 5) of cheap to medium-sized servers (2 CPU cores and 4GB RAM).