Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SMB2 Corruption issue
Message
From
16/05/2014 16:01:57
Walter Meester
HoogkarspelNetherlands
 
 
To
16/05/2014 14:04:27
Mike Yearwood
Toronto, Ontario, Canada
General information
Forum:
Visual FoxPro
Category:
Installation, Setup and Configuration
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2012
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01584063
Message ID:
01600129
Views:
150
>>>Hey Al
>>>
>>>SMB2 seems to benefit single use file access, so would it not aid SQL Server?
>>
>>I might be off here, but SMB is mainly about optimizing file queries and traffic, especially when sharing files.
>>
>>Since none of that applies to SQL server I do not think there is any benefit for SQL server accessing the database, and doubt whether it has much impact on the ODBC performance over the network.
>>
>>Walter,
>
>When a single user uses FoxPro to access tables, the performance for that user is noticeably good. When the second user starts sharing the files, the first user is slowed while caches are dumped. Further access is equally slow for both. Turning off SMB2 means that neither user ever sees that initial performance boost.
>
>If SQL Server is likened to the single user, and SMB2 made the single user access good, and not having SMB2 makes single user access slow - then SQL Server might be slowed if it reaches across the LAN for its files using fle queries and traffic.
>
>I should have just googled. SQL does support SMB so turning it off could adversely affect a database server.
>
>http://blogs.msdn.com/b/sqlserverstorageengine/archive/2011/10/18/sql-databases-on-file-shares-it-s-time-to-reconsider-the-scenario.aspx

Looks like an academical discussion, only applicable when de database files are stored on a network share. That does not sound like a mainstream implementation and certainly not what I would do anyways.

If the database is stored on the same machine as SQL server itself, this is just not applicable.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform