Unix Technical Forum

Physical setup: 1 data file vs multiple smaller data files

This is a discussion on Physical setup: 1 data file vs multiple smaller data files within the SQL Server forums, part of the Microsoft SQL Server category; --> Hello all. Before my arrival at my current employer, our consultants physically set up our MSSQL 7 server as ...


Go Back   Unix Technical Forum > Database Server Software > Microsoft SQL Server > SQL Server

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-28-2008, 06:34 PM
Domenico Discepola
 
Posts: n/a
Default Physical setup: 1 data file vs multiple smaller data files

Hello all. Before my arrival at my current employer, our consultants
physically set up our MSSQL 7 server as follows:
drive c: contains the mssql engine
drive d: contains the transaction log
drive e: contains the data files

No filegroups were set up and the data files consist of only 1 large
physical file. Currently, our data file is >10GB. When I was trained on
the physical aspects of sqlserver, I was told to never create physical files
> 2048MB each. If I did, I could expect inefficient physical storage of

data and slower performance (due to the OS).

Our server has 2 RAID-5 arrays. Drive c: and e: are located on the first
array and drive d: on the second. We're running Windows 4.0 NT Server SP6
with NTFS.

Can someone comment on the use of 1 single large data file vs. more smaller
data files?


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-28-2008, 06:34 PM
Greg D. Moore \(Strider\)
 
Posts: n/a
Default Re: Physical setup: 1 data file vs multiple smaller data files


"Domenico Discepola" <joeminga@yahoo.com> wrote in message
news:7OPnb.97624$PD3.5193098@nnrp1.uunet.ca...
> Hello all. Before my arrival at my current employer, our consultants
> physically set up our MSSQL 7 server as follows:
> drive c: contains the mssql engine
> drive d: contains the transaction log
> drive e: contains the data files
>
> No filegroups were set up and the data files consist of only 1 large
> physical file. Currently, our data file is >10GB. When I was trained on
> the physical aspects of sqlserver, I was told to never create physical

files
> > 2048MB each. If I did, I could expect inefficient physical storage of

> data and slower performance (due to the OS).


I've never heard that, can anyone else comment?

Prior to SQL 7.0 there was some performance gain from multiple files since
there would be one (and only one) pointer moving within a file, so multiple
files would gain you performance with multiple file pointers. But I believe
that was resolved as of SQL 7.0

>
> Our server has 2 RAID-5 arrays. Drive c: and e: are located on the first
> array and drive d: on the second. We're running Windows 4.0 NT Server SP6
> with NTFS.
>
> Can someone comment on the use of 1 single large data file vs. more

smaller
> data files?


They did the biggest bang, which was putting their data files and logs on
separate physical devices (though I'd recommend RAID 1 or 1+0 for the logs).


>
>



Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 09:33 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com