RE: New Server installation - Disks Setup recommendations

Hello Christian,

I personally would still put the logfiles on a separate mirror, if not for
recovery purposes, for I/O distribution. I would do the following:

c: 2 - 73gb mirrored internal disks; OS, App installation, pagefile 1
d: 2 - 73gb mirrored internal disks; logfiles; static data (data heap,
warehouse, etc)
e: 4 - 73gb raid 0+1; index data (separate filegroups for both OLTP and DW)
f: 6 - 73gb raid 0+1; data (separate filegroups for both OLTP and DW; made 2
or more for each)

If you know your hottest files, you can put them in different filegroups; in
case there is an I/O throughput problem...you can move them to lesser used
disks.

If the data is critical, you have zero loss of data requirements, or max
downtime of an hour, you can use Veritas Volume Replicator to replicate the
data real-time to a remote disaster recovery node and come up quickly if
necessary.

Hope this helps.
Kenny

--
Kenny


"Christian Hamel" wrote:

> Hello everyone,
> We have a new server that we would like to setup for SQL Server 2005
> Enterprise.
>
> The server have 6GB of Memory.
> 4 Internal Disks (73GB) on 1 controller
> 10 External Disks (73GB) on another controller (DELL PERC4)
>
> We actually have two SQL Server 2000 on distinct boxes that I'd like to
> merge into one SQL Server 2005.
> My first SQL2000 box is primarily used for Datawarehousing and replication
> with 45 reps accross the country. The second box is used for all sort of
> small Visual Basic application (Approx 100 users total).
>
> I'm planning to have two instances on my new SQL Server 2005 box to make
> sure I can split resources (Memory) to my APPS (VB) instance considering
> that some huge process can run on my datawarehouse; I do not want my VB
> users to feel the pain.
>
> I would also like to "reserved" some disks for my APPS databases.
>
> So here's the scenario I'm considering and would like any opinion as per it
> is a good setup or not.
> RAID 1+0 will be used; therefore 3 volumes will be available.
>
> C:\ 73GBx2 (Internal Disks) -> 140GB Total available
> Will be used for the OS & Tempdb
> D:\ 73GBx3 (External Disks) -> 210GB Total available
> Will be used for my Datawarehousing instance
> E:\ 73GBx2 (External Disks) -> 140GB Total available
> Will be used for my APPS instance
>
> Log & Data are going to be split accross the disks and I'm mainly using
> Simple recovery mode. So I don't see any advantage of splitting the log
> from the data for recovery. Worst case, we're restoring a backup we took
> over the night.
>
> Any recommendations/comments would be greatly appreciated as per it is the
> worst setup we ever seen or it is not that bad. Thank you very much.
>
>
>
.

Relevant Pages

  • Re: New Server installation - Disks Setup recommendations
    ... > recovery purposes, for I/O distribution. ... >> We actually have two SQL Server 2000 on distinct boxes that I'd like to ... >> that some huge process can run on my datawarehouse; I do not want my VB ... >> is a good setup or not. ...
    (microsoft.public.sqlserver.setup)
  • Re: Two Disaster Recovery Questions
    ... I support the Professional Association for SQL Server ... > recovery site ... > second restore at the recovery site. ...
    (microsoft.public.sqlserver.server)
  • Re: torn page detection and auto shrink: performance?
    ... And I have up-to-time recovery possibility. ... Curently, database size shows 18GB, but the used space shows 8GB. ... Shirinking files, will cause that by expanding files, sql server will ... There should be enough free space to permit reindexing of this table. ...
    (comp.databases.ms-sqlserver)
  • Re: Checkpointing Not Happening in Simple Recovery Model
    ... She says that she has simple recovery and that one of them is tempdb. ... Columnist, SQL Server Professional ... >> We have at least two databases on this server in simple recovery model. ...
    (microsoft.public.sqlserver.server)
  • Re: Full or Simple Recovery ?
    ... Simple recovery will not be able to recover the part of the log UNTIL ... Wayne Snyder, MCDBA, SQL Server MVP ... I support the Professional Association of SQL Server and it's community of SQL Server professionals. ...
    (microsoft.public.sqlserver.replication)
Quantcast