I am working on design/testing of a large sharepoint site, on the DB
side is there any downside to using a mix of shared storage rather
than one big LUN? Is there a recommended max size for db file in a
file group? Does it even matter.?? Our best estimates are that this
will be about 4-5TB's - is there a resource I could read up on working
with SQL Db's of this size? I have some general experinece using
MSSQL, have an MCDBA from 2000 but have gotten forced into more SA
work than DBA work.....thanks for any ideas.

John

John
Is it SQL Server 2008? If I remember well db size is 16 TB maximum
http://msdn.microsoft.com/en-us/library/ms143432.aspx






"John" <jcorbin121 (AT) gmail (DOT) com> wrote

No sir it is SQL 2005 Enterprise Edition - I don't think we will go
past 6TB (I hope!!)

Is there a recommended way to break up all of that or just lay it out
it one big LUN? And can having multiple file group files be all
included on one LUN so I dont have to create another cluster resource?

John





On Jan 12, 2:47*am, "Uri Dimant" <u... (AT) iscar (DOT) co.il> wrote:

First of all, if you go over 2TB you must use GPT disks. from a LUN
perspective, I don't have any problem with large storage. I do prefer to
keep my DB file sizes down to "reasonable". In this case 500GB-1TB per
file would be good. This allows me to move files around onto new storage
without having to find another very large partition to place data.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"John" <jcorbin121 (AT) gmail (DOT) com> wrote

No sir it is SQL 2005 Enterprise Edition - I don't think we will go
past 6TB (I hope!!)

Is there a recommended way to break up all of that or just lay it out
it one big LUN? And can having multiple file group files be all
included on one LUN so I dont have to create another cluster resource?

John





On Jan 12, 2:47 am, "Uri Dimant" <u... (AT) iscar (DOT) co.il> wrote:

Thanks for the info - I will be using only GPT disks.

john


On Jan 12, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Two different sizes to be considered
- db size = total size of all db file sizes
- db file size = size of a single file, a db can be made of multiple files

I am on the same page a Geoff, keep the FILE sizes manageable, this will
allow you to move them, as well as to put them on smaller disks.
Keeping file sizes smaller will not limit your overal db size, it will just
force you to think about your db design up front.
Putting them on smaller, but more disks, will also result in spreading the
IO over more disk-spindles, which is good for performance.

Rgds,
Edwin.



"John" <jcorbin121 (AT) gmail (DOT) com> wrote

Thanks for the info - I will be using only GPT disks.

john


On Jan 12, 9:45 am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote: