﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Andrey Shchekin commented on Schema-less databases</title><description>__In particular, making schema changes or adding indexes to a database with more than 10 - 20 million rows completely locks the database for hours at a time.
  
  
In MySql -- yes. It is the single worst performing DB I have ever worked with, especially considering index changes. Finding the workarounds for this can not be considered a breakthrough -- it would be much better if they just fixed it.
  
  
However, I do not yet see a value in having a schema-less DB2 or Sql Server (but it might be I just had no real use case).
</description><link>http://ayende.com/3896/schema-less-databases#comment4</link><guid>http://ayende.com/3896/schema-less-databases#comment4</guid><pubDate>Tue, 10 Mar 2009 10:54:35 GMT</pubDate></item><item><title>Rafal commented on Schema-less databases</title><description>Great read. RDBMS are meant to be performant and scalable, and maybe they are. But their manageability ends quickly when amount of data grows. I have very similar experience with a system built on top of SQL Server and an OR mapper. The system was meant for high availability, but upgrades are now very time consuming and dangerous because it takes hours to update database structure. You have only one chance to update database, because if something goes wrong you dont have time to retry in service time. What's worse, rollback takes the same time as completing the operation. 
  
If I were designing the software again, I'd consider a more unstructured approach with custom indexing instead of rigid relational structure.
</description><link>http://ayende.com/3896/schema-less-databases#comment3</link><guid>http://ayende.com/3896/schema-less-databases#comment3</guid><pubDate>Mon, 09 Mar 2009 18:33:08 GMT</pubDate></item><item><title>configurator commented on Schema-less databases</title><description>And now that I read the second link, I see that it does in fact speak of GData's approach. Huh.
</description><link>http://ayende.com/3896/schema-less-databases#comment2</link><guid>http://ayende.com/3896/schema-less-databases#comment2</guid><pubDate>Mon, 09 Mar 2009 00:15:04 GMT</pubDate></item><item><title>configurator commented on Schema-less databases</title><description>This is a very interesting subject. The trick is to know when to use it - on large, scalable systems, which seems counter-intuitive since normal RDBMS usage is intended for large, scalable systems.
  
  
When do you use RDBMS, then, and when do you use this approach? (Which is quite simple to google's approach with GData, I might add).
</description><link>http://ayende.com/3896/schema-less-databases#comment1</link><guid>http://ayende.com/3896/schema-less-databases#comment1</guid><pubDate>Mon, 09 Mar 2009 00:05:34 GMT</pubDate></item></channel></rss>