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 |
|
DLTaylor
Posting Yak Master
136 Posts |
 Posted - 2009-01-13 : 05:35:35
|
| I have a database where the *.mdf file is 240 gb (with10% free). The db acts as an archive (and sometimes reporting db) and is continuously growing.My question is; is there a size limit where the *.mdf file might start to fail?(What’s the biggest *.mdf file anyone has used in earnest?);Should I be looking to archive the data? – is it at risk; or is it ok practice (so long as I have disk space etc…) to let the mdf file grow.(There is no unnecessary duplication of data in the database – the size is down to the volume of data we are capturing) Any advice or pointing in the right direction will be very helpful.Thanks |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2009-01-13 : 05:44:51
|
I would use multiple filegroups and/or partitioned tables if using enterprise edition.
E 12°55'05.63"N 56°04'39.26" |
 |
|
|
DLTaylor
Posting Yak Master
136 Posts |
Posted - 2009-01-13 : 05:50:03
|
| Thanks Peso I will take your advice and look into this.(i'm using enterprise edition) |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-01-13 : 10:27:12
|
| As Peso said, Create Filegroups with files and spread it accross disks to reduce I/O contention issue.Partition table is not available in SQL 2000. I think Peso meant partition views. |
|
|
|
|
|
|
is a 240gb mdf file too big?