August 4, 2015 at 8:37 am
Forgive me if this is a dumb *** question, but it's a little new to me.
I have a 2 node cluster with (amongst other things), a clustered file server & a SQL instance.
When the file server is on the same node as the SQL server, the files are available to SQL (ie. during a bulk load).
When it is failed to a different node, it's unavailable.
From either node, the UNC path is available to the windows server regardless of it's host.
Where do I start with the trouble shooting / resolution?
August 4, 2015 at 8:39 am
Are you trying to access the files from SQL via the UNC as well, and that is failing?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 4, 2015 at 9:13 am
Yes so ...
BULK INSERT table
FROM '\\x\y\z\data.dat' WITH (FORMATFILE='C:\t_floatformat-c-xml.xml');
GO
Which works when the file server is on the same node as the instance, and fails when I fail the file server over to node 2.
August 4, 2015 at 3:41 pm
No inter-dependencies between the two clusters?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 5, 2015 at 1:39 am
No, the file server has just been created as a separate cluster resource.
If I had a test system, I could try a few things instead of bothering forum people! But anything I do here, (ridiculously) I do on live.
I'm guessing if I make the file server a dependency on the SQL instance, it may be available regardless of it's node ? but I'm wondering if this may create other problems. ie. if the file server is used by any other SQL instance.
It may be that I need to blatt the file server all together or move all relevant files onto a disk that can be created as a clustered resource dependent on the SQL instance.
Maybe I'm overthinking a design that wasn't particularly well thought out in the first place?
August 5, 2015 at 8:12 am
setup a new clustered fileshare resource that will make the location available regardless of which node it is on
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply