Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Rafter
Starting Member
1 Post |
 Posted - 2014-03-19 : 09:35:38
|
| Hi,I have a data intensive project for which I wrote the code recently, the data and sp live in a MS SQL 2008 ENT Ed Server. My initial estimate is that the db will grow to 50TB, then it will become fairly static in growth. The final application will perform lots of row level look ups and readings, with a smaller percentile of db write backs.My piers are recommending that I abandon SQL Server for a NoSQL solution in order to handle the 50TB DB and its transactions. The questions I have are;-Would SQL Server 2008 Ent. Ed. be able to handle a 50TB db?-For physical storage my plan is to use either a SAN or DAS solution, are there any recommendations about either solution, that won't degrade performance?-Should I consider a NoSQL solution or a Hybrid (SQL Server 2012 with the Hadoop plugin)?Regards,-r |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2014-03-20 : 07:28:40
|
| SQL Server can certainly handle 50 TB. For reference here is the SQLCAT presentation on largest SQL Server deployments (PDF):http://passmedia.sqlpass.org/media/24hours/2012_fall/PDF/06.pdfSlide #4 has a nice summary. Note that this is a few years old and I believe prior to SQL Server 2012 release.I'd recommend a SAN for storage, I admit that my knowledge of DAS units is old, anything newer than 5 years I don't know about. I do know there are a number of large solid state devices with that capacity but I imagine they are a good deal more expensive.Whether a pure NoSQL or hybrid solution is best for you I can't say. If it's just a question of data capacity, SQL Server could do the job on its own. |
 |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2014-03-22 : 06:02:32
|
| there are plenty of different features to allow scaling and subsequent management of a very large database. Here are some techniques I've used in the past : http://www.sqlserver-dba.com/2011/01/sql-server-scaling-techniques.html , particuarly related to modelling environments. One big issue to consider , particuarly if the data is changing - is the maintenance of the data - dealing with large amounts may require tactical scheduling of different indexes etc.spreading tables and indices across multiple devices can assist in performance and isolating IOJack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
|
|
|
|
|
SQL Server scaling to 50TB DB