At work Friday, I used Terminal services to connect to client machine. I then started SSMS and connected to a DIFFERENT server server.
Is this called a "remote connection"? What are the rules in terms of how I am authorized to access that SQL server.The server server I connected to was in the same domain and the domain I logged into.
asked Dec 02 '12 at 10:56 AM in Default
The phrase "remote connection" could mean a lot of things, simply having SSMS installed on your Client PC and connecting to a different computer with SQL Server installed is remote, rather than local where the SSMS and the SQL Server components are on the same computer.
you could also use the term remote connection when connecting to a SQL Server via RDP or Terminal Services, as in you scenario. Whether this then connects to a SQL Server on the computer you are connected to or you then make another hop to another computer is yet another alternative.
At all times when you connect SSMS to SQL Server you have the option to connect using Windows Authentication or SQL Server authentication. This choice is what affects the authorisation process and if/how you get access.
you could connect your TS/RDP session as a windows user and then start SSMS and use SQL Server authentication (supplying the username and password of the user you want to connect as) or if you choose windows authentication then the user credentials that you are using for the TS/RDP session will be passed to the SQL Server to control your access privileges.It is your choice.
answered Dec 02 '12 at 11:26 AM