September 22, 2015 at 7:44 am
Hi guys.
Please, help me with this question.
Give an example of a business use case where the knowledge you need to store would be best stored in an SQL database. How large can the amount of knowledge grow to, until this solution no longer works? A rough estimate is fine but it should be some kind of number.
September 22, 2015 at 7:55 am
Alina.Sotnikova (9/22/2015)
Hi guys.Please, help me with this question.
Give an example of a business use case where the knowledge you need to store would be best stored in an SQL database. How large can the amount of knowledge grow to, until this solution no longer works? A rough estimate is fine but it should be some kind of number.
Sure sounds like an interview question. But, this one is kind of fun. I'm sure you can come up with an example based on what I'm about to say. The answer to the first question is pretty easy, when the data is itself relational it should be stored in a relational storage engine. Think of an example of business data that is relational.
As to the size where the solution no longer works, I'm not sure. I've heard of 100+ petabyte systems. The current limit on a single database is about 500 petabytes (500,000 terabytes). For the overwhelming majority of businesses you can translate that as 'infinity'. That's before we start talking about using multiple servers for sharding. In short, with a properly designed system, there really isn't a hard limit on size, just on how much you're willing to spend in order to get to the size you want.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 22, 2015 at 7:58 am
That question is horribly vague, SQL server can stores TB's or PB's of information, depending on what format that data is in that could be enough to hold all the information in all books in all the libraries in the world or a few videos.
September 22, 2015 at 8:31 am
Sounds like homework to me.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
September 22, 2015 at 8:35 am
Check this thread for large implementations of SQL databases.
http://www.sqlservercentral.com/Forums/Topic1076313-391-1.aspx
You'll realize is not about size, it's about purpose.
September 22, 2015 at 9:11 am
Thanks a lot!
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply