March 18, 2021 at 6:31 am
Hi All
I am new to SQL so please be patient. We have SQL 2017 and 2016 running on the same server (Long story as to why). We have one instance of 2017 and both a default and named instance running on 2016....however the default and named instance are one in the same in that under SQL Configuration Manager we see only 2 instances. The 2016 TCP IPALL has both a dynamic port set as well as the Port set to 1433 (See attachments).
My question is would this effect the environment in any way? What possible issues could occur? How do we go about fixing it in this situation? Is it simply removing the fixed port 1433?
Many thanks
March 19, 2021 at 7:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
March 19, 2021 at 2:33 pm
If you don't see the named instance listed, that is strange. Can you post what you see in config manager?
Typically the default instance listens on 1433. Named instances get a dynamic port. Have you checked what your 2017 instance shows? In services, do you see 3 instances running?
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply