Ggthjy

What is the purpose of easy combat scenarios that don't need resource expenditure?

How do you funnel food off a cutting board?

Strange Sign on Lab Door

What's a good word to describe a public place that looks like it wouldn't be rough?

What is the wife of a henpecked husband called?

What is the lore-based reason that the Spectator has the Create Food and Water trait, instead of simply not requiring food and water?

It took me a lot of time to make this, pls like. (YouTube Comments #1)

How to deal with an incendiary email that was recalled

Why exactly do action photographers need high fps burst cameras?

Who is this Ant Woman character in this image alongside the Wasp?

Is it a fallacy if someone claims they need an explanation for every word of your argument to the point where they don't understand common terms?

How can I get my players to come to the game session after agreeing to a date?

Does SQL Server 2017, including older versions, support 8k disk sector sizes?

Difference between `vector<int> v;` and `vector<int> v = vector<int>();`

Traveling through the asteriod belt?

Why is working on the same position for more than 15 years not a red flag?

My cat mixes up the floors in my building. How can I help him?

Why avoid shared user accounts?

Early credit roll before the end of the film

Digits in an algebraic irrational number

How should I handle players who ignore the session zero agreement?

Explain the objections to these measures against human trafficking

Why is mind meld hard for T'pol in Star Trek: Enterprise?

Normalization for two bulk RNA-Seq samples to enable reliable fold-change estimation between genes

Does SQL Server 2017, including older versions, support 8k disk sector sizes?

Use Older Versions Of SQL Server Databases With 2012?SQL Server 2012 Availability group disk configuration optionsSQL Server 2008R2 minimum RAID/Disk configsql server disk I/o questionReplicating to Older Versions of MS SQL ServerInstalling instances of older versions of SQL ServerAre older versions of MS SQL Server DEVELOPER edition now free?Does SQL Server support custom DOMAINs?Run SQL Server 2016 side-by-side with older versions?Disk Architecture on SQL Server

13

Disk (loosely worded to include not only rotational media but non-rotational media [SSD, NVMe, etc.]) drives are continuing to evolve in their underlying formats and hardware. Part of this was an "enhancement" from 512 byte physical sector sizes to 4k physical sector sizes, which changes the on disk layout (512n, 512e, 4kn).

This next evolution is in using 8k physical sector sizes, which some manufacturers are starting to produce and setup in production. Given this next step, is the 8k sector size disk supported in Windows? Does SQL Server care about sector sizes?

sql-server hardware

share|improve this question

edited 10 hours ago

jadarnel27

5,94311938

asked 13 hours ago

Sean GallardySean Gallardy

16.5k22653

• 
  
  
  

  
  8
  

  
  
  
  
  
  

  
  
  Welcome to the site! Please take the tour and enjoy your time here!
  
  – Joe Obbish
  9 hours ago
  

  
  
  
  

add a comment | 

13

Disk (loosely worded to include not only rotational media but non-rotational media [SSD, NVMe, etc.]) drives are continuing to evolve in their underlying formats and hardware. Part of this was an "enhancement" from 512 byte physical sector sizes to 4k physical sector sizes, which changes the on disk layout (512n, 512e, 4kn).

This next evolution is in using 8k physical sector sizes, which some manufacturers are starting to produce and setup in production. Given this next step, is the 8k sector size disk supported in Windows? Does SQL Server care about sector sizes?

sql-server hardware

share|improve this question

edited 10 hours ago

jadarnel27

5,94311938

asked 13 hours ago

Sean GallardySean Gallardy

16.5k22653

• 
  
  
  

  
  8
  

  
  
  
  
  
  

  
  
  Welcome to the site! Please take the tour and enjoy your time here!
  
  – Joe Obbish
  9 hours ago
  

  
  
  
  

add a comment | 

Disk (loosely worded to include not only rotational media but non-rotational media [SSD, NVMe, etc.]) drives are continuing to evolve in their underlying formats and hardware. Part of this was an "enhancement" from 512 byte physical sector sizes to 4k physical sector sizes, which changes the on disk layout (512n, 512e, 4kn).

This next evolution is in using 8k physical sector sizes, which some manufacturers are starting to produce and setup in production. Given this next step, is the 8k sector size disk supported in Windows? Does SQL Server care about sector sizes?

sql-server hardware

share|improve this question

edited 10 hours ago

jadarnel27

5,94311938

asked 13 hours ago

Sean GallardySean Gallardy

16.5k22653

share|improve this question

edited 10 hours ago

jadarnel27

5,94311938

asked 13 hours ago

Sean GallardySean Gallardy

16.5k22653

share|improve this question

edited 10 hours ago

jadarnel27

5,94311938

asked 13 hours ago

Sean GallardySean Gallardy

16.5k22653

edited 10 hours ago

jadarnel27

5,94311938

edited 10 hours ago

jadarnel27

5,94311938

asked 13 hours ago

Sean GallardySean Gallardy

16.5k22653

asked 13 hours ago

Sean GallardySean Gallardy

16.5k22653

1 Answer
1

active

oldest

votes

12

Is the 8k sector size disk supported in Windows?

Currently, no, it is not supported by Windows and has been documented.

Does SQL Server care about sector sizes?

Yes, SQL Server does care about sector sizes. In fact, SQL Server checks the underlying physical disk information as it has data structures and algorithms that work with current disk sector sizes for various reasons (data integrity, optimizations, etc.).

If you attempt to use a physical sector size above 4k (4096) you'll receive an error:

Msg 5179, Level 16, State 1, Line 1

Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.

SQL Server supports a maximum sector size of 4096 bytes.

Move the file to a volume with a compatible sector size.

In this case, you can see that the error message is specifically telling you that the maximum sector size is 4096 (4k). This means that volume can't be used for SQL Server, and as noted above it wouldn't be supported in Windows either.

Solution

If you're receiving this error/issue, unfortunately you'll need to use a supported disk sector size such as 512 bytes or 4k. Other formats are unsupported and can't be used. You'll need to contact your hardware vendor for the Disk subsystem used and ask if there are any other options.

share|improve this answer

edited 8 hours ago

Paul White♦

52.7k14281456

answered 13 hours ago

Sean GallardySean Gallardy

16.5k22653

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  How did you get NTFS on that disk to produce the error message?
  
  – eckes
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.
  
  – jadarnel27
  7 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.
  
  – Sean Gallardy
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.
  
  – eckes
  5 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @eckes Correct! Awesome, thank you for the updated information!
  
  – Sean Gallardy
  1 hour ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f230973%2fdoes-sql-server-2017-including-older-versions-support-8k-disk-sector-sizes%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

12

Is the 8k sector size disk supported in Windows?

Currently, no, it is not supported by Windows and has been documented.

Does SQL Server care about sector sizes?

Yes, SQL Server does care about sector sizes. In fact, SQL Server checks the underlying physical disk information as it has data structures and algorithms that work with current disk sector sizes for various reasons (data integrity, optimizations, etc.).

If you attempt to use a physical sector size above 4k (4096) you'll receive an error:

Msg 5179, Level 16, State 1, Line 1

Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.

SQL Server supports a maximum sector size of 4096 bytes.

Move the file to a volume with a compatible sector size.

In this case, you can see that the error message is specifically telling you that the maximum sector size is 4096 (4k). This means that volume can't be used for SQL Server, and as noted above it wouldn't be supported in Windows either.

Solution

If you're receiving this error/issue, unfortunately you'll need to use a supported disk sector size such as 512 bytes or 4k. Other formats are unsupported and can't be used. You'll need to contact your hardware vendor for the Disk subsystem used and ask if there are any other options.

share|improve this answer

edited 8 hours ago

Paul White♦

52.7k14281456

answered 13 hours ago

Sean GallardySean Gallardy

16.5k22653

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  How did you get NTFS on that disk to produce the error message?
  
  – eckes
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.
  
  – jadarnel27
  7 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.
  
  – Sean Gallardy
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.
  
  – eckes
  5 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @eckes Correct! Awesome, thank you for the updated information!
  
  – Sean Gallardy
  1 hour ago
  

  
  
  
  

add a comment | 

12

Is the 8k sector size disk supported in Windows?

Currently, no, it is not supported by Windows and has been documented.

Does SQL Server care about sector sizes?

Yes, SQL Server does care about sector sizes. In fact, SQL Server checks the underlying physical disk information as it has data structures and algorithms that work with current disk sector sizes for various reasons (data integrity, optimizations, etc.).

If you attempt to use a physical sector size above 4k (4096) you'll receive an error:

Msg 5179, Level 16, State 1, Line 1

Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.

SQL Server supports a maximum sector size of 4096 bytes.

Move the file to a volume with a compatible sector size.

In this case, you can see that the error message is specifically telling you that the maximum sector size is 4096 (4k). This means that volume can't be used for SQL Server, and as noted above it wouldn't be supported in Windows either.

Solution

If you're receiving this error/issue, unfortunately you'll need to use a supported disk sector size such as 512 bytes or 4k. Other formats are unsupported and can't be used. You'll need to contact your hardware vendor for the Disk subsystem used and ask if there are any other options.

share|improve this answer

edited 8 hours ago

Paul White♦

52.7k14281456

answered 13 hours ago

Sean GallardySean Gallardy

16.5k22653

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  How did you get NTFS on that disk to produce the error message?
  
  – eckes
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.
  
  – jadarnel27
  7 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.
  
  – Sean Gallardy
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.
  
  – eckes
  5 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @eckes Correct! Awesome, thank you for the updated information!
  
  – Sean Gallardy
  1 hour ago
  

  
  
  
  

add a comment | 

Is the 8k sector size disk supported in Windows?

Currently, no, it is not supported by Windows and has been documented.

Does SQL Server care about sector sizes?

Yes, SQL Server does care about sector sizes. In fact, SQL Server checks the underlying physical disk information as it has data structures and algorithms that work with current disk sector sizes for various reasons (data integrity, optimizations, etc.).

If you attempt to use a physical sector size above 4k (4096) you'll receive an error:

Msg 5179, Level 16, State 1, Line 1

Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.

SQL Server supports a maximum sector size of 4096 bytes.

Move the file to a volume with a compatible sector size.

In this case, you can see that the error message is specifically telling you that the maximum sector size is 4096 (4k). This means that volume can't be used for SQL Server, and as noted above it wouldn't be supported in Windows either.

Solution

If you're receiving this error/issue, unfortunately you'll need to use a supported disk sector size such as 512 bytes or 4k. Other formats are unsupported and can't be used. You'll need to contact your hardware vendor for the Disk subsystem used and ask if there are any other options.

share|improve this answer

edited 8 hours ago

Paul White♦

52.7k14281456

answered 13 hours ago

Sean GallardySean Gallardy

16.5k22653

Msg 5179, Level 16, State 1, Line 1

Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.

SQL Server supports a maximum sector size of 4096 bytes.

Move the file to a volume with a compatible sector size.

share|improve this answer

edited 8 hours ago

Paul White♦

52.7k14281456

answered 13 hours ago

Sean GallardySean Gallardy

16.5k22653

edited 8 hours ago

Paul White♦

52.7k14281456

edited 8 hours ago

Paul White♦

52.7k14281456

answered 13 hours ago

Sean GallardySean Gallardy

16.5k22653

answered 13 hours ago

Sean GallardySean Gallardy

16.5k22653