Feature request: Custom SQL port for database connection

Availability for the Always-On Enterprise

Feature request: Custom SQL port for database connection

Veeam Logoby ndolson » Thu Nov 12, 2015 8:56 pm

Our policy is to use a custom / alternate port for SQL database connections instead of the default 1433. After speaking with support, it appears it is not possible to specify an alternate port. I figure it's pretty common for people to use a non-standard port for SQL and being able to specify a custom port would make our DBA's happy.

Thanks!
ndolson
Influencer
 
Posts: 13
Liked: 2 times
Joined: Thu Jan 08, 2015 3:56 pm
Full Name: Neal

Re: Feature request: Custom SQL port for database connectio

Veeam Logoby Gostev » Thu Nov 12, 2015 9:53 pm

Hi, Neal. What functionality are you talking about here? SQL Server for configuration database our product is using? Thanks!
Gostev
Veeam Software
 
Posts: 22379
Liked: 2670 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Feature request: Custom SQL port for database connectio

Veeam Logoby 42dlx » Sun May 15, 2016 10:08 am

Hi Anton,

I have the same problem.

I'd like to use the Veeam Explorer for SQL and need to connect to a different port. In the MS SQL Server Management Studio, you can do this via ip-address, port-number (e.g 192.168.254.42, 4848).

Is this possible with the SQL Explorer?

Thanks!
42dlx
Lurker
 
Posts: 1
Liked: never
Joined: Sun May 15, 2016 10:02 am
Full Name: Andre

Re: Feature request: Custom SQL port for database connectio

Veeam Logoby scdor_bsmith » Mon Dec 11, 2017 8:29 pm

We had the same issue of not using standard SQL port numbers. First we had to address the database restore as a restore to a new database and/or server. We would list the [server name],[port #] , this was good for single node SQL servers. Our next problem was 90% of our SQL servers were clustered in Availability Groups. Even though you could direct the restore over the custom port number through the SQL Explorer Wizard, when the wizard reached the Availability Group settings, it would show "not connected" to the other nodes in the cluster. This would cause the restore not to be written into the AG setting. We found that using SQL aliases would solve this issue. You can find the it here; [color=#0000FF]https://support.microsoft.com/en-us/help/936491/after-you-install-a-64-bit-version-of-sql-server-2005-on-a-64-bit-vers.
We created a .reg file with all the aliases instead of using cliconfg.exe which looked like this;

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo]
"[Server Name]"="DBMSSOCN,[Server Name],[Port#]"


This solved our issues and allows all restore communication to talk to the restore target servers via the custom port we have designated for SQL traffic
scdor_bsmith
Lurker
 
Posts: 1
Liked: never
Joined: Fri Oct 20, 2017 2:56 pm
Full Name: Billy Smith


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Gostev and 29 guests