Is this abug?

• gary1

  SSC-Insane

  Points: 21152

  More actions

  September 23, 2011 at 11:26 am

  #257728

  I have enabled filestream as shown in the attachment

  and then ran the below query.

  EXEC sp_configure filestream_access_level, 2;

  GO

  RECONFIGURE;

  GO

  But when query to verify the FilestreamEffectiveLevel , it showing as 3 instead of 2.

  But in BOL, nowhere mentiond about the FilestreamEffectiveLevel 3

  From BOL,

  FILESTREAM access is controlled within SQL Server using sp_configure to set the filestream_access_level configuration option to one of three settings. The possible settings are:

  0 – disable FILESTREAM support for this instance

  1 – enable FILESTREAM for Transact-SQL access only

  2 – enable FILESTREAM for Transact-SQL and Win32 streaming access

  SELECT SERVERPROPERTY ('FilestreamEffectiveLevel')

  Is this normal? or kind of known issue? Please advise.

  Thanks

• Lowell

  SSC Guru

  Points: 323518

  More actions

  September 23, 2011 at 11:39 am

  #1385950

  don't you have to stop and start the service to change the config values into run values?

  i suspect the 3=changes pending as an undocumented status.

  Lowell

  ---

  --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

• gary1

  SSC-Insane

  Points: 21152

  More actions

  September 23, 2011 at 12:39 pm

  #1385985

  don't you have to stop and start the service to change the config values into run values?

  i suspect the 3=changes pending as an undocumented status.

  I did stop and start the service already.

  Does BOL mentioned any where about FilestreamEffectiveLevel as 3 (even as undocumented status)?

  Because, I'm implementing this in production and want to make sure some where it is documented and supported.

  Thanks

• gary1

  SSC-Insane

  Points: 21152

  More actions

  September 23, 2011 at 1:12 pm

  #1386009

  Yeah!! found it..

  From the below KB article, this behavior is normal

  http://support.microsoft.com/kb/955861

  Thanks