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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-01-29 : 08:59:43
|
| Daniel Wong writes "Hi there,i have a question. If one of my server running MS SQL Server,there's 3 hard disks ( C,D,E Drives )C Drive contain Systems files, program files and other binary files.D Drive contain the Data files for the MS SQL Database.E Drive contain the transaction log file for the MS SQL Database.Each hard disk is 18.2GBMy only concern is, since, D Drive contain Data file for the SQL Database. If one day, the data have grow to the near capactiy of the hard disk. I mean nearly fill up. How should we increase the size or the capacity of the database?If i not mistaken, the current Max per hard disk size is at 36.4GB. What if the Server is running Raid 1 or Raid 5. We can't possible change all the hard disk, reinstall all the OS, application and database, just to increase the size of the SQL Database.If by getting a new hard disk, plug it into the server. Can we just add another new data file in the database pointing to the new hard disk? Or there's other ways to increase the capacity of the database.Pls advise on this issue. All you guys help is greatly appreciate. Thanks in advance and have a good day ahead.RegardsDaniel" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-01-29 : 12:17:37
|
| Yes you can put a new data file on the new hard disk, but you will have to move tables over to the new data file. So you would have to figure out which ones could fit on the new hard drive and plus leave room for growth.Can't you just add another disk to the Raid array instead? |
 |
|
|
harshal_in
Aged Yak Warrior
633 Posts |
Posted - 2003-01-30 : 07:51:44
|
quote:
Yes you can put a new data file on the new hard disk, but you will have to move tables over to the new data file. So you would have to figure out which ones could fit on the new hard drive and plus leave room for growth.Can't you just add another disk to the Raid array instead?
I am not sure but would like to know if making file groups will help in this situation??Expect the UnExpected |
|
|
|
srf
Starting Member
42 Posts |
Posted - 2003-01-30 : 15:33:01
|
| Where is this max of 36.4 gigs coming from? I have some 80 gig SQL files so I'm not sure what that's in reference to.If you have RAID, just add a drive like mentioned before. If you don't have RAID, your life will be easier if you get it. If you don't want hardware RAID, Windows 2000 can do RAID 0 in hardware to "expand" the drive you already have. Also halves your MTBF.Otherwise just add another disk then add a data file. SQL automatically distributes data across data files as needed. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-01-30 : 16:02:51
|
quote:
I am not sure but would like to know if making file groups will help in this situation??
The reason why this hels is because if daniel can only add a new drive (meaning can't add the drive to the RAID array), then he can move part of his database to the other drive by using filegroups. If he can add a new disk to the RAID array, then he should just add it. |
|
|
|
|
|
|
|
|
Database Growth for SQL Server