Forum Discussion
Disk size considerations
Hello.
Could you suggest if there are any considerations regarding disk size for database files? Are there any limitations from MS SQL?
Version that we use is SQL 2014 SP1.
What we need is handling 200+ SharePoint content databases of total size about 16TB. So the question is whether it will be better from the SQL perspective to have, say, 4 x 4TB logical disks instead of one 16TB disk. Or are there only hardware considerations to take into account, but not SQL-related?
Alex
4 Replies
Hi Alex, It depends on Storage design. If you can describe what you have in terms of Storage I can help you with the desing.
Let me know the storage model, disks number and LUN + RAID used.
Based on this information I can give recomendations. I helped Dell sales to design storage for SQL and Hyper-V for many years.
Regards
Thanks Lucas. At the moment customer asks if there are any requirements/recommendations from the SQL/SharePoint side. When it comes to storage design, customer has another contractor that will prepare their suggestions. Probably they will base their suggestions on LUN/RAID, etc. that you mention.
Do you know of any recommendation to give from "software" side?
@Александр Сапожков wrote:Thanks Lucas. At the moment customer asks if there are any requirements/recommendations from the SQL/SharePoint side. When it comes to storage design, customer has another contractor that will prepare their suggestions. Probably they will base their suggestions on LUN/RAID, etc. that you mention.
Do you know of any recommendation to give from "software" side?
Good day,
This is a clasic case study mistake which a lot of complanies do
I see this wrong procedure in a lot where companies, get advice from "DBA expert" who prepares the database server, while ignoring other aspects of the system, like the storage design or the applications, which actually use the database, and latter on they take "application expert" and they probably take "storage expert" as well, and each consultant gives opposite advices, while ignoring the other aspects of the system!
A system should always we examine "as a whole" and not in parts!
Advice that fit one system can be wrong to another system even if spesific part (for example SQL/SharePoint configuration) is the same.
Now lety's go back to the original question and give you the short answer that It depends on Storage design and much more :-)
There is no way to give advice based on the information we have here. The only thing I can give you are "golden rules" and comments, which should help you or your experts to get the right decission.
>> Splitting the data should be first of all a matter of performance usually. Using single file usually in most cases (smaller DB as well) reduce performance, as SQL Server is a multi task application.
>> The question should not focus only on the size of the files but ion the storage desighn, how you splite the data between these files, and how/where you store the files...
>> In general in most cases, I recommend to split the data to files according to the way you use the data and store the data. The idea is to split the data across disk to balance the use and get better performance.
>> In general in most big databases I recommend to split the file to 6TB or less each. 16 TB is big but not huge and spliting to 4TB size make sense in first glance. Using 16TB single file is something I probably will not advice you to do. You should think about mainanence as well as "the way you use the data and store the data" which I mentioned above. The number 6TB related to several parameters including the size of backup tapes (like HP C7976A LTO 6 ) which are common in use.
Your question was only about the size of the file while you should think about the way SQL Server work regarding the data and the memeory and the entire system around it. I highly recommend to search the web for "best practice" articles and cases. In the mean time, I hope these short comments could help you and point you to the right way :-)
