environment alias name for server name

gudii9
gudii9 used Ask the Experts™
on
sql server 2012 when i login as below it shows some values which are unclear to me under server name

how to make sure to put server names some meaningful names to understand

instead of say
CXXXXX1234.xy.LMP.com,99999
i like to give alias name like
Production Database
or
System Test
etc

so that i do not need to refer every time when i login to check documentation to see where i am making changes etc

also how to connect multiple environments same time paralleled like production and System Test, integration etc
do i need to open microsoft sql mgmt tool multiple times or can i open separate tabs in one instance one underneath other?
Where can i refer for good usage tips and learning? any good vidoes or resources around this

what is difference between
windows authentication
and
sql server authentication
when to use which one

please advise
SQLServer2012_NAmeEnv.png
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Most Valuable Expert 2015
Distinguished Expert 2018
Commented:
CXXXXX1234.xy.LMP.com,99999

Open in new window

That's the hostname and port number.
These must be specified. The only way around could be to create ODBC DSN entries or files which holds this information, and then let the user choose between these. But that adds the trouble of creating and maintaining these entries which may present a challenge not worth the efforts.

do i need to open microsoft sql mgmt tool multiple times
Yes, except if you create code to do this. In VBA (from, say, Microsoft Access) a method is here:

Linking SQL Server

when to use which one
You will typically use Windows authentication (Trusted Connection) when server and users are in the same Active Directory as is the case in most organisations.
If outside users (not logged in to the Active Directory) will have to connect, SQL Server authentication must be used. Corporate users working in the field typically connect via a VPN connection, thus will be able to use Windows authentication.

For further into, just bing/google on the keywords - tons of info out there for the browsing.
Raja Jegan RSQL Server DBA & Architect, EE Solution Guide
Awarded 2009
Distinguished Expert 2018
Commented:
Yes, you can create Aliases for your SQL Server Instance to make it more meaningful as mentioned below..
https://dontpaniclabs.com/blog/post/2017/01/04/sql-aliasing-need/
But it has its own drawbacks as listed below:
1. You need to enable SQL Server Browser Service which will make your SQL Server instance visible across network or unauthorised people.
2. Replication can't be configured or troubleshooted with Alias names, it requires original name of the server.

>> also how to connect multiple environments same time paralleled like production and System Test, integration etc
do i need to open microsoft sql mgmt tool multiple times or can i open separate tabs in one instance one underneath other?

If your current pc has multiple network cards and have access to all environments, then you can connect all environments from a single SSMS window. otherwise you would need to open multiple SSMS from different pc or from different SSMS instance to get connected to multiple environments.

>> Where can i refer for good usage tips and learning? any good vidoes or resources around this

Above link can be a good start for you..

>> what is difference between windows authentication and sql server authentication

Windows Authentication is the default authentication method in SQL Server allowing only Windows Login users to connect to the system.
If your SQL Server should be accessed by valid users without Windows Login, then go for SQL Authentication with a SQL Login.
So, Windows or SQL Authentication usage depends upon your requirement with Windows Authentication the first recommended option..
ste5anSenior Developer
Commented:
instead of say CXXXXX1234.xy.LMP.com,99999
i like to give alias name like Production Database or System Test etc.
Naming the server Production Database is nonsense. It's a server, not a database. Also naming it System Test is suboptimal. Yeah, it's a system, but this was obvious, thus it's redundant.

You should give the host a meaningful name in the first place. Then you should use named instances. E.g then you would see e.g. in SSMS: CXXXXX1234\PRODUCTION or CXXXXX1234\TEST

Author

Commented:

You should give the host a meaningful name in the first place.
this is not in my control though

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial