August 2, 2016 at 12:54 pm
All,
From my research on TechNet and MSDN I have found that SQL Server 2014 can be installed on an SMB share. This installation would support system and user databases being located on the SMB share. What I have a question on is whether SMB 2.1 will support this installation.
My current problem is that I have a SQL 2014 instance installed on a Server 2008 R2 machine with system and user databases being hosted on an SMB share. The share is located on a Server 2008 R2 machine. At least once a week the application that uses this database instance becomes inoperable due to lost connectivity with the database. A restart of the SQL instance service on the host machine brings everything back up and online, but it is becoming an inconvenience to have to verify every morning that the application is still up and running. We are looking into a scheduled task to restart the service when a certain event ID is logged on the system, but we would like to figure out the root cause of this issue.
I am not a DBA but am responsible for ensuring the application stays up and running. I have enough SQL experience to be dangerous. Any help is appreciated and if you require more information please let me know.
August 2, 2016 at 1:18 pm
Please bear in mind, I've not set up a SQL instance using this method so my thoughts may be completely off-base.
That being said.
My first thought in such a situation would be a problem with the network connection between the SQL server and the SMB server. Could be from network congestion, some automated process that briefly stops network traffic, or something along those lines.
You could check in the Windows Event logs on both servers, especially the System log, looking for anything that might be network-related (especially anything that makes it look like the NIC connected.)
August 3, 2016 at 9:56 am
jasona.work (8/2/2016)
Please bear in mind, I've not set up a SQL instance using this method so my thoughts may be completely off-base.That being said.
My first thought in such a situation would be a problem with the network connection between the SQL server and the SMB server. Could be from network congestion, some automated process that briefly stops network traffic, or something along those lines.
You could check in the Windows Event logs on both servers, especially the System log, looking for anything that might be network-related (especially anything that makes it look like the NIC connected.)
Thank you for the reply.
My first thoughts leaned towards minor network issues, but I have been unable to find any type of log or evidence of an issue. I have been monitoring/working on the issue for approximately 6-8 weeks now and typically every eighth day when I come I have to restart the instance service. In regards to congestion, I find it highly unlikely. We have a small private network that the machines are running on with a very small number of users. Most of our connections are 1 GB/s and I believe the connection to the server with the share is 10 GB/s.
I have also combed through the event logs multiple times. I have looked at SQL logs as well to see if they would provide more insight with no luck. I have also reviewed the applications logs to see if there are any errors in their that might indicate an issue and have found nothing.
I have leaned towards our backup solution possibly causing issues, but if it was that I would think that it would do it every time (we run differentials daily). McAfee Antivirus was another thought but the task for full scans does not run on the same day as the disconnects.
As with you, this is my first installation of this type. So kind of learning as I go with it. Microsoft has some good information on this type of installation, but it does not answer my specific question as to whether the version of SQL or the SMB protocol being used dictates where the system databases can be installed.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply