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 - 2002-05-10 : 11:23:10
|
| John writes "Hello,My subject is a little unclear to myself, but I'll try to explain. I recenlty set up SQL Server Software on a network. The IT guy that manages the network had issue with the fact that the database tables reside on the c:\ of the server. He strongly suggested to me that I figure out how to basically 'save' the database tables to a partitioned section of the hard drive which is mapped as an 'e:\' drive. Is it possible?...to run the software from the c:\ drive and write the data to a separate e:\ drive (for example)? Thanks in advance.-John" |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-05-10 : 11:31:53
|
| Sure! That's very easy to do. When you create the database, make sure to indicate the path and file name on the E: drive instead of the default C: drive.You *might* see a drop in performance though, since the E: drive is a partition and not a separate drive. If you can add another physical drive to the computer, then you can put the data on that drive, and the performance should improve.Read Books Online under "filegroups" and check out the scenarios they describe, it'll give you more background on the most effective way to utilize the drives you have. |
 |
|
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2002-05-10 : 11:34:37
|
| Yes, it is advisable that you don't put the database files on the c/system drive of the server; for performance and storage reasons.Lookup CREATE DATABASE in BOL.When you create the databases specify the desired location:USE masterGOCREATE DATABASE SalesON ( NAME = Sales_dat, FILENAME = 'e:\mssql\data\saledat.mdf', SIZE = .... |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2002-05-10 : 11:50:00
|
| I've attached a database using UNC across the network, but it was very slow...DanielSQL Server DBA |
|
|
|
RobMarsh
Starting Member
28 Posts |
Posted - 2002-05-10 : 14:16:08
|
| This is the layout for most servers I set up:C: system files and programsD: Data filesE: Log FilesIf you have extra disks, you can stick your intermediary backups up that to... :)Rob |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-05-10 : 15:41:45
|
quote:
John writes "Hello...He strongly suggested to me that I figure out how to basically 'save' the database tables to a partitioned section of the hard drive which is mapped as an 'e:\' drive."
Assuming you do not allow unrestricted filegrowth on your data and log files, I see no advantage* to partioning a single disk and moving data files around like this. The reason to have OS and Data/Logs on different spindles is mainly twofold: (1)Reduce read/write head contention and increase I/O throughput and (2) allow database filegrowth and OS disk needs to be mutually exclusive. Partitioning a single disk accomplishes neither of these (assuming my assumption ;)). If you do not restrict filegrowth, you datafile could potential grow and choke out your OS. Tell you Network guy to buy you some more disks.*Footnote: OK, one may be if you are mirroring another servers drive mappings for easy backup/restore action . . .<O> |
|
|
|
|
|
|
|
|
Can Data be stored on a non-'C' Drive?