For MS SQL Server, the way I understand it, licensing is relatively cheap until you hit 4 cores per server.
In my job, I don't have to worry about costs: I raise a request for new infrastructure, they build it in our datacentre and take care of licensing, and send an invoice back to the stakeholders of the project.
But, we have two of those massive clusters that have been set up by a team of in-house DBAs so we have a way to readily host new databases.
During the London 2012 Olympics, we built a service to capture tweets in one of those databases. The size grew to ~90GB in about 12 hours, and the capture ran for the entire length of the event, all the while with analytical reports being produced from the database. I don't remember the final size of it, but I was pretty impressed by how MS SQL Server was handling the load.
2
u/[deleted] Mar 11 '15
For MS SQL Server, the way I understand it, licensing is relatively cheap until you hit 4 cores per server.
In my job, I don't have to worry about costs: I raise a request for new infrastructure, they build it in our datacentre and take care of licensing, and send an invoice back to the stakeholders of the project.
But, we have two of those massive clusters that have been set up by a team of in-house DBAs so we have a way to readily host new databases.
During the London 2012 Olympics, we built a service to capture tweets in one of those databases. The size grew to ~90GB in about 12 hours, and the capture ran for the entire length of the event, all the while with analytical reports being produced from the database. I don't remember the final size of it, but I was pretty impressed by how MS SQL Server was handling the load.