SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Hardware Configuration using SSD


Hardware Configuration using SSD

Author
Message
DBA by default
DBA by default
Old Hand
Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)

Group: General Forum Members
Points: 338 Visits: 727
We are in the process of ordering a new server and the hardware guys are asking about how we need to setup the arrays / drives. We are moving to Server 2012 and installing SQL 2008 R2. If we are using Solid State Drives do you get better performance having multiple arrays each with their own logical drive or is the performance about the same using one RAID10 array and split that into logical drives for the OS, data logs, etc? Everything I have found says to split it on physical drives, but most are referring to platter drives and not solid state. So if anyone can give some insight on the best setup using SSD that would be great.

Thanks,
Tracie
Elliott Whitlow
Elliott Whitlow
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10056 Visits: 5314
Keep in mind I have only a bit of experience with SSDs. But my understanding and experience is that random access and sequential access are virtually the same on an SSD because we don't have to even consider waiting for the platter to come around. Depending on how many drives you are working with there is usually some benefit to having more channels of access to the drives. If we are only talking about 4 drives then I would probably just break it down to logical drives.

I'd google: sql ssd best practices

And this URL looks promising: http://www.sqlservercentral.com/blogs/hugo/2011/06/08/notes-from-solid-state-for-sql-server-with-wes-brown-from-today-s-idera-broadcast-ssd-best-practices-for-database-servers/

CEWII
DBA by default
DBA by default
Old Hand
Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)

Group: General Forum Members
Points: 338 Visits: 727
One setup suggested is on RAID10 array with 10 drives and one RAID1 with 2 drives for the log files. The second suggested setup is Array0 RAID1 with 2 drives for OS. Array1 RAID10 4 drives data files. Array2 RAID10 4 drives log files. Array3 RAID10 4 disks tempdb and local backups.


Tracie
DBA by default
DBA by default
Old Hand
Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)

Group: General Forum Members
Points: 338 Visits: 727
Elliott Whitlow (7/9/2013)
Keep in mind I have only a bit of experience with SSDs. But my understanding and experience is that random access and sequential access are virtually the same on an SSD because we don't have to even consider waiting for the platter to come around. Depending on how many drives you are working with there is usually some benefit to having more channels of access to the drives. If we are only talking about 4 drives then I would probably just break it down to logical drives.

I'd google: sql ssd best practices

And this URL looks promising: http://www.sqlservercentral.com/blogs/hugo/2011/06/08/notes-from-solid-state-for-sql-server-with-wes-brown-from-today-s-idera-broadcast-ssd-best-practices-for-database-servers/

CEWII


Thanks for the information, I will pass it on and check out the link.

Tracie
Elliott Whitlow
Elliott Whitlow
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10056 Visits: 5314
My recommendation is to never do backups locally, always to a file server.

My rational for this is that it removes a single server failure as a mechanism of data loss. If you lose the drives you have lost not only the data but also the backups.

As well as SSD storage is still pretty expensive and I'd rather use the space for databases..

CEWII
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search