Ran out of space on C:\

[jcfrasco]

Dear anybody that can help,

I'm running SQL Server 7 on an NT machine that was previously setup before I arrived in this company. We started upgrading a DOS program that will now be using SQL Server. My problem is that as I started setting up the program for converting I found out that the C:\ drive where SQL Server is installed had been partitioned and the size is not large enough to allow me to input the data. Even if I were able to get the data in it doesn't allow any room for growth as more data is entered.

What are my options? I don't know if it's possible to re-dimension a partition or if it's possible to install SQL Server in the other partition as there is about 75% of it still available.

I appreciate any guidance on this matter.

Thanks for your time,
jcfrasco

 

[jjgraf]

Yes you have options.

Option one:
Install SQL on C: then have the default data path set to another partition. this is configured during the install or you specify a path for each database.

Option two:
go out a buy partition magic resize the partition. NT 4.0 does not allow mounting new disk to current file system or resize partitions. but partition magic lets resize the partition.

Option three:
go out and buy Drive copy then put everthing on a new harddrive and and resize the partitions when you do this.

Option four:
Install Sql on another drive.

hope this helps.

 

[jcfrasco]

Thank you jjgraf for your help.

I've decided the best, and easiest, solution is to leave SQL Server on the C drive and create the databases on the D drive. I'm still learning about SQL Server so I wasn't aware you could do that. As like everything in this career field it becomes a "I need it now" situation and there isn't much time to study all the details.

With that said, I'm very interested in any more tips, advice, recommendations, etc... that you have to offer.

Thanks again for your assistance,
jcfrasco

 

[bmclaws]

Just a quick note on partitioning software - if you choose to try it:

If you are running NT WS, then Partition Magic works great, but if you are running NT Server, you will need Server Magic instead.

I have personally used Server Magic on NT 4 Server to re-partition C: (and other partitions as well) and had absolutely no problems.

I would still recommend a back-up before trying it, just to be safe.

Barry

 

[RickCole]

jcfrasco

Just for info but you can have you databases spread around on as many disc drives as you like within the server. You can either had one database spread across more than one drive if you wish.

Lot's of people set up there databases across multiple drives from an efficiency aspect. One of the main ones is to have your database on one drive and your transaction log on another. (If it’s feasible of course)

Rick.

 

[jjgraf]

What i do:

I have a DELL server dual processor with 5 hardrives. One drive is the C: with only 4gig avaible the other 4 drives are in a RAID 5 confirguration with 27gigs avaible to data only. All binaries are stored on the C drive. I defrag the hardrives every friday and run the SQL maintenance which includes Integrity Checks, Optimization, which runs every sunday night a 12am, and Database Backup every night at 12. so far the database is approaching 2gigs


BTW you do not need to buy Server Magic if you run Partition Magic off Diskettes (this could have changed since my copy is older than dirt)

 

[RickCole]

Ensure all you databases are on the RAID 5 set-up as this will give you resilience on your data should you loose one of the disk drives.

Tempdb would be more efficient if it was on your C: drive but if you have no performance problems then also leave it on the RAID 5.

Word of warning if all your system stuff is on the C: drive and that goes then your done for.

Rick.

 

[jjgraf]

Thanks for the word of warning but i have taken care of that. All system settings and data of the Network are backup every night to tapes and moved offset, and at the end of each month a copy is put on DVD RAM disks and moved off site into Safety deposite box at a bank. The owner is nuts about bakups and keeping records forever.

The tapes are thrown away after 30 writes.

right know I backup 22 gigs of data across the network everynight, E-mails, MS office Files, Erp data, Sql Server, Active Directory, User Settings, etc.

also incremental backups are against company policy