Moving SQL database
We are moving our RDM SQL database from one location to another. At the current location we are using a named instance on port 1435, but my dba said the new one is running on port 1433. I am trying to setup a new Data Source to test the db move but I don't see anywhere to define the port. What am I missing?
All Comments (5)
Hello,
The port 1433 is the default port for SQL Server, so you don't need to specify it in the data source configuration.
In File -> Data Sources -> New -> SQL Server, in the Server field, you have an ellipsis button on your right. Are you able to retrieve the new SQL Server using that button?
Best regards,
Jeff Dagenais
The window that pops up contains no entries.
Hello,
If you enter the server name with the appropriate username and password to connect and that you try to select the database at the bottom, is it working?
You can also consult this help topic to troubleshoot the connectivity between your computer and this new SQL Server
https://help.remotedesktopmanager.com/troubleshooting_sqlserverconnectivity.htm
Best regards,
Jeff Dagenais
To trouble shoot further if the action Jeff suggest doesn''t work:
From the computer you are running RDM perform a "telnet <databaseservername> 1433" (for example: telnet rdmhost 1433). This should clear the command line screen (success) or eventually return an error.
If you get the error something is blocking the port.
If you don't get the error you can reach the database server and sql server is listening on that port.
Now make sure (ask the dba) if the SQL Server Browser service is running. When you connect to SQL Server using the name only DATABASESERVER\INSTANCENAME for a named instance or DATABASESERVER for a non-named instance (you can actually have a named instance running on port 1433 so make sue you know if it is a named or a non-named instance - again your dba should know) you connect to port 1434 using udp. This connection returns the actual port SQL Server is running on and a new connection is setup using that port.
Let us know your findings if you are still unable to connect.
The dba just told me it was his fault, he hadn't properly configured permissions for the users. It all works now. Thanks guys and sorry for the bother. Great quick support.