I feel like every time there's a new NoSQL product both Microsoft and Oracle incorporate it into their RDBMS offerings.

I'm beginning to realize that now. If it ain't broke don't fix it Discover my world at jkirkerx.com

I didn't think of it till I replied to your post. My code runs on my boxes in the office as well. If it ain't broke don't fix it Discover my world at jkirkerx.com

"every time you use sql server for more than crud then you are married to sql serve" And that is still absolutism. Which in practical programming does not work.

This would be a database question and there is a database forum. Use code tags when you post code and anything else that should be formatted.

Code4Ever wrote: could it handle 500 read/write requests No sorry that is not a valid question based on your original post. Exactly how are 2000 users supposed to generate that many messages at one time?

Could I get some user feedback?! :) A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!

Uff, I'm so sorry for my english. It's so hard for me explain my problem in not native language. I have users, users can access to his data, and his data are students, teachers, shceduler, calendar, ... This means, every user have his own data, and this data it's for app tables. I have a mongodb, no sql. Thanks, I hope I explained better now.

So you posted this in QA[^]; reposted it in the database forum[^]; and now you've posted a third copy in the forum which explicitly forbids programming questions. Your impatience and inability to follow the rules clearly know no bounds. :doh: "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

You posted it less than 12 hours ago. Half the world won't have woken up and had a chance to to read it yet. And since questions here are answered by volunteers, nobody is under any obligation to answer it at all, let alone within a defined time limit. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

On MSFT[^] We have all asked ourselves this question when starting a new project. Should I ditch SQL and jump on the NoSQL train? If you are, go elsewhere in search of an article that might help you decide which type of database is correct for your use case. This one won't help. Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius

Previously: Spammer (madisondade123)[^] "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Hopeless Idealist wrote: I would rather type:...but all the companies demand SQL-devs. First of course because companies do not operate to please you. They operate to make money. And that comes from pleasing customers. Both in sales and in follow up support. Additionally they must keep costs low. At the end of the day technologies do not drive company success. Rather it is matter of successfully creating a product(s)/service(s) which the company can maintain and enhance. And of course then selling it in the first place. Large companies almost always have multiple persisted datastores. And I only say 'almost' because I can't be sure that there is not one company out there that only uses one. I do know that Microsoft, Oracle, Netflix, Google and Amazon all use different ones.

Imagine you load a file that has 3 sets of timeseries data: attributeA, attributeB and attributeC. Each timseries is of the form Array. There will be between 1000 and 15,000 time/value pairs in each series, so maybe 8Kb to 120Kb in each series. I will never query the data in the array. I will only ever return it as a chunk of data (meaning I could compress it into a BLOB for higher storage efficiency at a tradeoff in load speed if I needed to) A classic database such as MySQL or SQL Server seems massive overkill for this. cheers Chris Maunder