Re: SQL on its own partition
- From: "Henrik" <henrik@xxxxxxxxxxx>
- Date: Tue, 17 Apr 2007 09:28:23 +0200
Hello,
By the default installation of SBS 2003 your various different instances of
datadases are installed on C: .
That means if you havent changed It during the installation process.
When you install SQL server with SBS 2003 (Premium Ed.) you along the MSDE
instaces of WSUS, Monitoring etc. also gets a default instance in SQL
server.
You can se all your installed instances in add/remove program.
When you install SQL server (This does not automaticly means all other
instances such as WSUS, Monitoring etc) you can during setup choose where to
install it.
If you install It on D: you still have some program (SQL) files on C: but
the default databases are placed on the partition you chose. There are some
databases in SQL that comes by default and that has to be there. The chosen
partition are also the place for the primary file group in SQL where any
other database that you install also are placed. That means if you
application that uses SQL doesnt needs its own instance name. If it does you
have to run the SQL server setup an additional time and during that setup
chose to install a new NAMED instance.
Regarding performance, its vital if you want good performance, to place
datafiles on separate discs from the trans-log files.
For good performance, also separate both datafiles and trans-log files from
the system disc so it wont fight the virtual memory file for disc access.
Recomended is that you also seperate datafiles and trans-log files from the
default databases and files regarding discs so it wont have to figt them
either for disc acces.
Raid levels. When talking about Raid with SQL best practise is otften to use
Raid 10 but it costs moore disc space so the next is to use simple mirrored
Raid.
Raid 5 will give you worse performance. Its all about the amount of
spindles/disc heads.
In your case, add an additional disc so that you have 6 discs at least and
then cretae three mirrored drives. One for the system, one for SQL datafiles
and SQL default databases ,one drive for tranaction logs to all other
databases that are not default SQL databases (cant be moved easily).
There is one other BIG issue about seperating trans-log files from the
databases, that is security in case of disaster. This solution gives you a
better possibility to recover from a disaster with a minimal of data loss.
//Henrik
"Leythos" <Void@xxxxxxxxxxx> wrote in message
news:1176778038_19651@xxxxxxxxxxxxxxxxxxxxxxx
On Mon, 16 Apr 2007 19:04:03 -0700, JD wrote:
Yes, It is a Dell server with the perc 5i controller. 2 drives are raid 1
and
3 drives are raid 5 as you descrided.
The installation instruction on the SQL disk seen to imply you have to
upgrade the SHAREPOINT instance of WMSDE. You are saying it can be left
alone
if you wish?
The install defaults to the C:\Program Files\Microsoft SQL Server folder
where the MSDE desktop engine is installed. Won't it over ride that
install??
No, I'm not telling you anything about the WMSDE, I'm the wrong person to
ask about that.
I'm only talking about the SQL instance you install for your own
databases, not he default ones.
--
Leythos
spam999free@xxxxxxxxxx (remove 999 for proper email address)
.
- Follow-Ups:
- Re: SQL on its own partition
- From: Leythos
- Re: SQL on its own partition
- From: Robert Li [MSFT]
- Re: SQL on its own partition
- References:
- Re: SQL on its own partition
- From: Leythos
- Re: SQL on its own partition
- From: Leythos
- Re: SQL on its own partition
- From: Leythos
- Re: SQL on its own partition
- Prev by Date: Re: Manual WSUS sync command
- Next by Date: Re: RE: W2KSvr -> SBS2003, migration or update
- Previous by thread: Re: SQL on its own partition
- Next by thread: Re: SQL on its own partition
- Index(es):
Relevant Pages
|
