Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm onsite at a customer who's experienced a weird problem with HP PolyServe and SQL Server 2005 and I'm wondering whether anyone else has hit it.

The problem is that with default settings, a DBCC CHECKDB will fail on a database underpinned by PolyServe managed storage. This is because DBCC CHECKDB (by default) uses a hidden database snapshot which it stores in NTFS alternate streams on the existing database data files, and PolyServe by default doesn't support NTFS alternate streams.

Now - I know why this happens (I wrote DBCC CHECKDB) and I know how to work around it (create your own snapshot and check that, or restore a backup and check that, or use WITH TABLOCK as a last resort) - so I don't want answers that explain these things.

What I'd love to know is the following:

  • why does PolyServe not support NTFS alternate streams by default?
  • what functionality do you lose in PolyServe by enabling NTFS alternate stream support?
  • has anyone else experienced this?

Edit: Btw - the last upgrade to PolyServe 3.6.1 was what turned the option OFF by default, which caused the DBCC CHECKDB failure. We're trying to figure out why it went from ON to OFF by default.

I tried to find some info on this online before asking here.


PS If you want background on why DBCC CHECKDB uses a snapshot, see my long blog post on CHECKDB internals at CHECKDB From Every Angle: Complete description of all CHECKDB stages.

share|improve this question
Do you know what version of PolyServe turned that option off? We haven't encountered that issue, but maybe we're not on the latest release yet. – BradC Jun 11 '09 at 19:50
3.6.1 - just updated the question too. – Paul Randal Jun 11 '09 at 19:56


This guy seems to be running that version of Polyserve


share|improve this answer
Thanks - I wonder if he's running DBCC CHECKDBs too. – Paul Randal Jun 11 '09 at 21:37
up vote 1 down vote accepted

I found the answer. If you install 3.6.1 then you're ok. If you upgrade from an earlier version, you need to explicitly enable alternate streams via a command they call psfscheck that enables them per volume. Their support also says that you can use this command to enable 8.3 name support - which leads me to believe they're just calling the NTFS fsutil command under the covers.

Unfortunately it needs to force dismount the PS volume to do this. Nice.

Thanks to those who responded though.

PS The link to the support doc is here

share|improve this answer
And I'm glad to see that I don't get 15 points for answering my own question :-) – Paul Randal Jun 14 '09 at 14:39
Regarding accepting your own answer, see this blog entry: – BradC Jun 18 '09 at 21:41
Cool - yeah, makes sense to stop people upping their own score. – Paul Randal Jun 19 '09 at 0:56

We're running 3.6.1, and haven't had any issues with SQL 2005 DBCC jobs. Do you know where this setting is modified in Polyserve, so I can see if ours had already been enabled?

Edit: Regarding your answer. Ours was a fresh 3.6.1 install, not an upgrade, so that seems to match what you found.

share|improve this answer
I'm checking... – Paul Randal Jun 11 '09 at 21:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.