We want to go with SQL recommendations of seperate drives for
backups,data,log,tempdb and OS.
So we are thinking of
2*72 RAID 1 for OS
2*72 RAID 1 for Tempdb
2*72 RAID 1 for Log
4*72 RAID 10 for Data
3*72 RAID 5 for backups,etc.
So the question is should I use one RAID controller to tie all these drives
too ? Just looking at it from a price perspective. If not, then 2 and if so,
what areas should I distribute the above layout to ?
Let me know if 1 RAID controller would work.
Thanks
I would combine the tempdb and log drive and treat tempdb files like the
rest of the databases. It is better to have logs on 0+1. If the controller
is decent, one will be able to handle that spindle count.
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Hassan" <hassan@.test.com> wrote in message
news:OMbGoL8TIHA.4684@.TK2MSFTNGP06.phx.gbl...
> We want to go with SQL recommendations of seperate drives for
> backups,data,log,tempdb and OS.
> So we are thinking of
> 2*72 RAID 1 for OS
> 2*72 RAID 1 for Tempdb
> 2*72 RAID 1 for Log
> 4*72 RAID 10 for Data
> 3*72 RAID 5 for backups,etc.
> So the question is should I use one RAID controller to tie all these
> drives too ? Just looking at it from a price perspective. If not, then 2
> and if so, what areas should I distribute the above layout to ?
> Let me know if 1 RAID controller would work.
> Thanks
|||Are you saying as such ?
2*72 RAID 1 for OS
4*72 RAID 10 for Tempdb(data and log) and Log Files
4*72 RAID 10 for Data Files
3*72 RAID 5 for backups,etc.
"jason" <jason-r3move@.statisticsio.com> wrote in message
news:185DB471-3652-44A0-AAD0-33E056397B92@.microsoft.com...
>I would combine the tempdb and log drive and treat tempdb files like the
>rest of the databases. It is better to have logs on 0+1. If the controller
>is decent, one will be able to handle that spindle count.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
> "Hassan" <hassan@.test.com> wrote in message
> news:OMbGoL8TIHA.4684@.TK2MSFTNGP06.phx.gbl...
>
|||>I would combine the tempdb and log drive and treat tempdb files like the
>rest of the databases. It is better to have logs on 0+1. If the controller
>is decent, one will be able to handle that spindle count.
Logs shouldn't be shared with other files. Log writes during COMMIT are
synchronous and so response time will be negatively affected due to
competing with other file I/O.
Hope this helps.
Dan Guzman
SQL Server MVP
"jason" <jason-r3move@.statisticsio.com> wrote in message
news:185DB471-3652-44A0-AAD0-33E056397B92@.microsoft.com...
>I would combine the tempdb and log drive and treat tempdb files like the
>rest of the databases. It is better to have logs on 0+1. If the controller
>is decent, one will be able to handle that spindle count.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
> "Hassan" <hassan@.test.com> wrote in message
> news:OMbGoL8TIHA.4684@.TK2MSFTNGP06.phx.gbl...
>
|||is it best to put both the log files for the data and tempdb together ? Or
have tempdb on its own disks that include both its data files and log files
Thanks
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:7C67FDC2-4E72-4DEE-80F7-F5EEDCC44DD2@.microsoft.com...
> Logs shouldn't be shared with other files. Log writes during COMMIT are
> synchronous and so response time will be negatively affected due to
> competing with other file I/O.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "jason" <jason-r3move@.statisticsio.com> wrote in message
> news:185DB471-3652-44A0-AAD0-33E056397B92@.microsoft.com...
>
|||> is it best to put both the log files for the data and tempdb together ? Or
> have tempdb on its own disks that include both its data files and log
> files
I would place the tempdb log file to the same drive/array as the other log
files and on a controller with a lot of write cache. Tempdb data files may
be heavily used and separating data files from log files will help optimize
the sequential writes to the log.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.test.com> wrote in message
news:OqcmMl8TIHA.280@.TK2MSFTNGP03.phx.gbl...
> is it best to put both the log files for the data and tempdb together ? Or
> have tempdb on its own disks that include both its data files and log
> files
> Thanks
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:7C67FDC2-4E72-4DEE-80F7-F5EEDCC44DD2@.microsoft.com...
>
|||> 2*72 RAID 1 for OS
> 4*72 RAID 10 for Log Files
> 4*72 RAID 10 for Data Files
> 3*72 RAID 5 for backups,etc.
And treat tempdb as any other database with this spindle count. Data files
on data drive. Log files on log drive. When you don't don't have many
spindles, it is best to keep it simple.
There is even a case that could be made this config:
> 2*72 RAID 1 for OS
> 8*72 RAID 10 for Data Files and Log Files
> 3*72 RAID 5 for backups,etc.
"Hassan" <hassan@.test.com> wrote in message
news:umf6Sb8TIHA.5288@.TK2MSFTNGP04.phx.gbl...
> Are you saying as such ?
> 2*72 RAID 1 for OS
> 4*72 RAID 10 for Tempdb(data and log) and Log Files
> 4*72 RAID 10 for Data Files
> 3*72 RAID 5 for backups,etc.
> "jason" <jason-r3move@.statisticsio.com> wrote in message
> news:185DB471-3652-44A0-AAD0-33E056397B92@.microsoft.com...
>
|||Would you also do it with one controller ?
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:467C193D-BFB7-45C1-BC99-DF7084FF714C@.microsoft.com...
> I would place the tempdb log file to the same drive/array as the other log
> files and on a controller with a lot of write cache. Tempdb data files
> may be heavily used and separating data files from log files will help
> optimize the sequential writes to the log.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Hassan" <hassan@.test.com> wrote in message
> news:OqcmMl8TIHA.280@.TK2MSFTNGP03.phx.gbl...
>
|||> Would you also do it with one controller ?
It depends on budget and controller capabilities. A single controller is
probably adequate as long as it's a decent one with features like lots of
cache, configurable cache read/write ratio and battery backup.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.test.com> wrote in message
news:usb%23Wc9TIHA.1208@.TK2MSFTNGP03.phx.gbl...
> Would you also do it with one controller ?
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:467C193D-BFB7-45C1-BC99-DF7084FF714C@.microsoft.com...
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment