Store and Change dinamically TCP Port in SQL Connection String





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I handle Sql 2014 Express and this eventually changes the TCP Dynamic Port. Since the applications of vb.net need to have a connectionString, it would be laborious to be adjusting the already compiled exe programs, each time the TCP port included in the conectionstring of my applications changes in the company network. How can I store a connectionstring in the local network in a single point so I can modify it when I change the tcp port to eventually restart the sql server? In such a way that the vbnet applications access by network to a single point where the connectionstring is stored? What is the best technique in these cases?










share|improve this question























  • Configure it to use fixed port

    – Ben
    Nov 23 '18 at 16:40











  • docs.microsoft.com/en-us/sql/tools/configuration-manager/…

    – Ben
    Nov 23 '18 at 16:42


















1















I handle Sql 2014 Express and this eventually changes the TCP Dynamic Port. Since the applications of vb.net need to have a connectionString, it would be laborious to be adjusting the already compiled exe programs, each time the TCP port included in the conectionstring of my applications changes in the company network. How can I store a connectionstring in the local network in a single point so I can modify it when I change the tcp port to eventually restart the sql server? In such a way that the vbnet applications access by network to a single point where the connectionstring is stored? What is the best technique in these cases?










share|improve this question























  • Configure it to use fixed port

    – Ben
    Nov 23 '18 at 16:40











  • docs.microsoft.com/en-us/sql/tools/configuration-manager/…

    – Ben
    Nov 23 '18 at 16:42














1












1








1








I handle Sql 2014 Express and this eventually changes the TCP Dynamic Port. Since the applications of vb.net need to have a connectionString, it would be laborious to be adjusting the already compiled exe programs, each time the TCP port included in the conectionstring of my applications changes in the company network. How can I store a connectionstring in the local network in a single point so I can modify it when I change the tcp port to eventually restart the sql server? In such a way that the vbnet applications access by network to a single point where the connectionstring is stored? What is the best technique in these cases?










share|improve this question














I handle Sql 2014 Express and this eventually changes the TCP Dynamic Port. Since the applications of vb.net need to have a connectionString, it would be laborious to be adjusting the already compiled exe programs, each time the TCP port included in the conectionstring of my applications changes in the company network. How can I store a connectionstring in the local network in a single point so I can modify it when I change the tcp port to eventually restart the sql server? In such a way that the vbnet applications access by network to a single point where the connectionstring is stored? What is the best technique in these cases?







sql-server vb.net






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 23 '18 at 16:35









Luis HLuis H

61




61













  • Configure it to use fixed port

    – Ben
    Nov 23 '18 at 16:40











  • docs.microsoft.com/en-us/sql/tools/configuration-manager/…

    – Ben
    Nov 23 '18 at 16:42



















  • Configure it to use fixed port

    – Ben
    Nov 23 '18 at 16:40











  • docs.microsoft.com/en-us/sql/tools/configuration-manager/…

    – Ben
    Nov 23 '18 at 16:42

















Configure it to use fixed port

– Ben
Nov 23 '18 at 16:40





Configure it to use fixed port

– Ben
Nov 23 '18 at 16:40













docs.microsoft.com/en-us/sql/tools/configuration-manager/…

– Ben
Nov 23 '18 at 16:42





docs.microsoft.com/en-us/sql/tools/configuration-manager/…

– Ben
Nov 23 '18 at 16:42












1 Answer
1






active

oldest

votes


















0














As long as you are running the SQL Server Browser service, you won't need to know the port number, just the instance name.






share|improve this answer
























  • The problem is: Some pc don't detect de Instance by name: SERVERINSTANCE, then in that cases we need to use instead: SERVER, PORT. So, the problem is that in some cases the only way to connect from certain PCs is to use the specific TCP port, and that is where the inconvenience of the changing port arises.

    – Luis H
    Nov 28 '18 at 20:36













  • you can use fixed port if that is the case but i would double check that the browser service is running, directing to the correct port is its main purpose

    – SqlACID
    Nov 28 '18 at 20:50












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450232%2fstore-and-change-dinamically-tcp-port-in-sql-connection-string%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














As long as you are running the SQL Server Browser service, you won't need to know the port number, just the instance name.






share|improve this answer
























  • The problem is: Some pc don't detect de Instance by name: SERVERINSTANCE, then in that cases we need to use instead: SERVER, PORT. So, the problem is that in some cases the only way to connect from certain PCs is to use the specific TCP port, and that is where the inconvenience of the changing port arises.

    – Luis H
    Nov 28 '18 at 20:36













  • you can use fixed port if that is the case but i would double check that the browser service is running, directing to the correct port is its main purpose

    – SqlACID
    Nov 28 '18 at 20:50
















0














As long as you are running the SQL Server Browser service, you won't need to know the port number, just the instance name.






share|improve this answer
























  • The problem is: Some pc don't detect de Instance by name: SERVERINSTANCE, then in that cases we need to use instead: SERVER, PORT. So, the problem is that in some cases the only way to connect from certain PCs is to use the specific TCP port, and that is where the inconvenience of the changing port arises.

    – Luis H
    Nov 28 '18 at 20:36













  • you can use fixed port if that is the case but i would double check that the browser service is running, directing to the correct port is its main purpose

    – SqlACID
    Nov 28 '18 at 20:50














0












0








0







As long as you are running the SQL Server Browser service, you won't need to know the port number, just the instance name.






share|improve this answer













As long as you are running the SQL Server Browser service, you won't need to know the port number, just the instance name.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 23 '18 at 16:44









SqlACIDSqlACID

3,9551629




3,9551629













  • The problem is: Some pc don't detect de Instance by name: SERVERINSTANCE, then in that cases we need to use instead: SERVER, PORT. So, the problem is that in some cases the only way to connect from certain PCs is to use the specific TCP port, and that is where the inconvenience of the changing port arises.

    – Luis H
    Nov 28 '18 at 20:36













  • you can use fixed port if that is the case but i would double check that the browser service is running, directing to the correct port is its main purpose

    – SqlACID
    Nov 28 '18 at 20:50



















  • The problem is: Some pc don't detect de Instance by name: SERVERINSTANCE, then in that cases we need to use instead: SERVER, PORT. So, the problem is that in some cases the only way to connect from certain PCs is to use the specific TCP port, and that is where the inconvenience of the changing port arises.

    – Luis H
    Nov 28 '18 at 20:36













  • you can use fixed port if that is the case but i would double check that the browser service is running, directing to the correct port is its main purpose

    – SqlACID
    Nov 28 '18 at 20:50

















The problem is: Some pc don't detect de Instance by name: SERVERINSTANCE, then in that cases we need to use instead: SERVER, PORT. So, the problem is that in some cases the only way to connect from certain PCs is to use the specific TCP port, and that is where the inconvenience of the changing port arises.

– Luis H
Nov 28 '18 at 20:36







The problem is: Some pc don't detect de Instance by name: SERVERINSTANCE, then in that cases we need to use instead: SERVER, PORT. So, the problem is that in some cases the only way to connect from certain PCs is to use the specific TCP port, and that is where the inconvenience of the changing port arises.

– Luis H
Nov 28 '18 at 20:36















you can use fixed port if that is the case but i would double check that the browser service is running, directing to the correct port is its main purpose

– SqlACID
Nov 28 '18 at 20:50





you can use fixed port if that is the case but i would double check that the browser service is running, directing to the correct port is its main purpose

– SqlACID
Nov 28 '18 at 20:50




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450232%2fstore-and-change-dinamically-tcp-port-in-sql-connection-string%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Paul Cézanne

UIScrollView CustomStickyHeader Resize height generates problems when scroll is too fast

Angular material date-picker (MatDatepicker) auto completes the date on focus out