February 25, 2013 at 3:24 pm
So I just have to ask this because I am a bit baffled and flabbergasted by this situation. In 9 years I have not come across an issue where an application built on SQL, could not work if it was set on a named instance.
We have forecasting software that we are implementing, and some functions do not work because the parameters passed to the API will not accept the servername/instance name. It really blows my mind as default/named instances aren't even remotely new, and this company is 20 years old. I can't understand how they would have never encountered this in the past.
The server we have for this is on a shared hosted solution so for obvious reasons we cannot get the default instance.
Has anyone else encountered this? If so, did you find a workaround?
Link to my blog http://notyelf.com/
February 26, 2013 at 3:09 am
Are you working with the standard port 1434? Got allow remote connections enabled :P?
Greetz
Query Shepherd
February 26, 2013 at 7:24 am
You probably know this but it is servername\instance not / (you wrote / twice so maybe thats the problem?).
Have you tried servername,portnumber instead of servername\instance?
February 26, 2013 at 9:06 am
Ah yes sorry bad habit. Yes I tried it with the backslash, I have no idea why I put the / slash but I just do that sometimes 😀
There is no where in the software that I know of to call out a port number but I will check with them to see if that is possible!
Link to my blog http://notyelf.com/
February 26, 2013 at 11:25 pm
Damn.../ only with internet protocols...never mind...my web developers also mix up / and \ very often...so it seems to be an webdev illness :-D.
You can change the port with the sql server configuration manager -> network configuration -> tcp/ip -> ip-adresses -> ports.
Greetz
Query Shepherd
February 28, 2013 at 10:47 pm
shannonjk (2/26/2013)
There is no where in the software that I know of to call out a port number but I will check with them to see if that is possible!
If it is using the SQL Native Client Drivers then you append the port to the backend of the servername with a comma separating the two, with the form:
servername,portnumber
example:
dbserver01,1733
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 1, 2013 at 1:17 am
shannonjk (2/25/2013)
In 9 years I have not come across an issue where an application built on SQL, could not work if it was set on a named instance.
It's usually because the developer hard codes port 1433 into the connection string in the app, this will then only connect to a default instance or a named instance using the default port (which never usually happens)
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 1, 2013 at 1:03 pm
You can also do server\instance,port
like
SQL01\TestInst,55001
March 1, 2013 at 1:34 pm
scogeb (3/1/2013)
You can also do server\instance,portlike
SQL01\TestInst,55001
Depending on the driver the instance name can take precedence over the port, or vice-versa. It is not consistent across drivers. I would recommend against employing something like that as a standard approach.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 1, 2013 at 2:19 pm
scogeb (3/1/2013)
You can also do server\instance,portlike
SQL01\TestInst,55001
You generally supply one or the other. Instance name or port number not both.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply