Microsoft has us one step closer to their hive. I can't wait to be part of their collective;-)
The cost of the CD itself is hardly anything...
on
Still More RIAA News
·
· Score: 2, Informative
The CD's themselves cost right around $0.08 each at relatively low volumes. This is for 5 color glass mastered cd's. Then, add a cover and 4 color jacket and you are around $0.80 tops. This is shrunk-wrapped, glass mastered cd's ready to go! This cost also includes the glass mastering fees and the film fees ~$750.00.
Now, keep in mind these are prices paid to a third company...I hope the recording industry owns their own replication plants.
I WILL NOT pay over $10.00 for a music CD! I also have not purchased a music CD since the RIAA started crying two years ago.
I am one of the owners of the company so I do not see this happening. Besides, our system is HIGHLY documented. Besides, we are also saving over $80,000.00/year off what Microsoft proposed for our licensing of 2000 Server. So, would I rather spend maybe 40 hours/year in extra coding time just to do things right or shell out an extra $80k for software that would protect me from my poor mistakes? It was a simple decision for me.
Anyone can screw anything up. I have seen MS SQL databases screwed up even with keys. Bottom line - if you don't know what you are doing don't touch it!
I thought I would chime in from someone that is currently using MySQL as a back-end database to a web application.
First some statistics: We have ~140 tables, 7,500,000 records and see ~100,000,000 queries monthly. We update a minimum of 300,000 records daily and are running RHLinux on a Dell 2650 Dual 2.4 with HT.
Performance: Our system performs EXTREMELY well. The database is easily handling the load we are putting on it so I wouldn't say that it falls apart under load.
Foreign Keys: Would I like to have foreign key support in MySQL? No, I would LOVE it! However, we have written apps to check database integrity throughout the day. I agree 100% that if you have unqualified programmers posting final code to a server you could quickly have a corrupt database system. This really should not be the purpose of Foreign Keys, although foreign keys do achieve this.
Database Speed: Generally, when dealing with large applications and row-level locking if speed is an issue with a MySQL database it is generally due to poor database structure. I will be the first to admit, however, that we are looking at ProstgreSQL because of row-level locking and a few other bells and whistles...who knows, MySQL 4.x may fit the bill depending on how well it performs.
My suggestion to anyone looking--try both and use what fits your needs!
Slashdot Mirror
Microsoft has us one step closer to their hive. I can't wait to be part of their collective ;-)
The CD's themselves cost right around $0.08 each at relatively low volumes. This is for 5 color glass mastered cd's. Then, add a cover and 4 color jacket and you are around $0.80 tops. This is shrunk-wrapped, glass mastered cd's ready to go! This cost also includes the glass mastering fees and the film fees ~$750.00. Now, keep in mind these are prices paid to a third company...I hope the recording industry owns their own replication plants. I WILL NOT pay over $10.00 for a music CD! I also have not purchased a music CD since the RIAA started crying two years ago.
I am one of the owners of the company so I do not see this happening. Besides, our system is HIGHLY documented. Besides, we are also saving over $80,000.00/year off what Microsoft proposed for our licensing of 2000 Server. So, would I rather spend maybe 40 hours/year in extra coding time just to do things right or shell out an extra $80k for software that would protect me from my poor mistakes? It was a simple decision for me. Anyone can screw anything up. I have seen MS SQL databases screwed up even with keys. Bottom line - if you don't know what you are doing don't touch it!
I thought I would chime in from someone that is currently using MySQL as a back-end database to a web application.
First some statistics: We have ~140 tables, 7,500,000 records and see ~100,000,000 queries monthly. We update a minimum of 300,000 records daily and are running RHLinux on a Dell 2650 Dual 2.4 with HT.
Performance: Our system performs EXTREMELY well. The database is easily handling the load we are putting on it so I wouldn't say that it falls apart under load.
Foreign Keys: Would I like to have foreign key support in MySQL? No, I would LOVE it! However, we have written apps to check database integrity throughout the day. I agree 100% that if you have unqualified programmers posting final code to a server you could quickly have a corrupt database system. This really should not be the purpose of Foreign Keys, although foreign keys do achieve this.
Database Speed: Generally, when dealing with large applications and row-level locking if speed is an issue with a MySQL database it is generally due to poor database structure. I will be the first to admit, however, that we are looking at ProstgreSQL because of row-level locking and a few other bells and whistles...who knows, MySQL 4.x may fit the bill depending on how well it performs.
My suggestion to anyone looking--try both and use what fits your needs!