- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: EVA4100 and SQL allocation unit size when form...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2008 09:44 AM
тАО09-25-2008 09:44 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2008 11:26 AM
тАО09-25-2008 11:26 AM
Re: EVA4100 and SQL allocation unit size when formatting drive.
maybe the following threads could help you:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1056062
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1251071
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 08:55 AM
тАО09-26-2008 08:55 AM
Re: EVA4100 and SQL allocation unit size when formatting drive.
http://support.microsoft.com/kb/140365/en-us
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2008 06:12 AM
тАО10-03-2008 06:12 AM
Re: EVA4100 and SQL allocation unit size when formatting drive.
From an EVA4100 standpoint do not do a disk alignment and keep the partition cluster size to default of 4kb is best practice? Reason I ask is I see so many write up's for SQL 2005 that recommend to partition a volume with cluster size larger like 64k for database.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2008 08:41 AM
тАО10-03-2008 08:41 AM
Re: EVA4100 and SQL allocation unit size when formatting drive.
A few days ago I have read that one of the analyzers (don't recall the exact name right now) complains if a data partition is not aligned. Now, if not aligning a partition does not hurt in an EVA environment, I doubt it will hurt if you _do_ align.
So, I would align the data partition(s) and run with the suggested cluster size.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2008 08:51 AM
тАО10-03-2008 08:51 AM
Re: EVA4100 and SQL allocation unit size when formatting drive.
align=16
align=32
align=64
?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2008 09:09 AM
тАО10-03-2008 09:09 AM
SolutionThe EVA chunk size is 128KB. If you use a cluster size of 64KB, I suggest you use a 64KB/128blocks offset so that NTFS clusters do not cross EVA chunks. If doing otherwise would have a negative impact on performance can only be said if it is tested.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2008 09:19 AM
тАО10-03-2008 09:19 AM
Re: EVA4100 and SQL allocation unit size when formatting drive.
CREATE PRIMARY PARTITION ALIGN=32
Which would probably be causing my issue. Also if you let windows it automatically it will set the offset to 32kb. I guess I will try 64kb and see what happens.
Our Universe database vendor recommended 16kb offset.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2008 09:33 AM
тАО10-03-2008 09:33 AM
Re: EVA4100 and SQL allocation unit size when formatting drive.
The general SQL recommendation is using a 64KB bock size during the format.
Partition alignment is also recommended.
You can use the diskpart command line as follows:
CREATE PARTITION PRIMARY ALIGN=64
and then format the disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2008 06:43 AM
тАО10-06-2008 06:43 AM
Re: EVA4100 and SQL allocation unit size when formatting drive.
"When using DISKPAR, adjust the alignment by 512 bytes, and when using DISKPART, the disk should be aligned to 64. The reason for this is due to the original master boot record design of WinTel based systems. The master boot record for all drives is 63 blocks (1 block = 512 bytes)."
Doesn't this mean that you should set align=32kb since 32kb is equal to 64 blocks? (64x1024=32,768kb.)
I do format the partition using 64k but I leave the alignment=32kb.