There are tons of articles available for SQL Server and client connections on the net which tend to be very technical with full of computer jargons.  Not much of help when you set up a local testing environment for SQL Server + client connection for a Workgroup network.  It is a little inconvenient for the testing environment with SQL Server connection from a client PC using SQL Server Authentication where you have to supply user id and password every time.

There is a simple way to avoid the inconvenience – Use Windows Authentication instead.

Normally for SQL Server PC, user id for Windows login is set to “Administrator” with an appropriate password.  SQL Server software can be installed on Windows 7, 8, 8.1 and 10 as well.  To use Windows Authentication connection instead of SQL Server Authentication connection form a client PC (running under Windows 7, 8, 8.1 or 10), all you have to do is to create Administrator account on the client PC and set user id and password exactly the same as the SQL Server PC.

Then, when you login the client PC with that user id and password, you can connect remote SQL Server with Windows Authentication (without supplying user id and password).

It make a life a little easier for the testing environment.

Your comments are welcome (subject to moderation).  Nickname is allowed for comment posting, however, you must provide a valid e-mail address (will not to be displayed).  If you fill out Website box, website address will be linked on your name appeared on the comment.  As regard to the treatment of your e-mail address, please refer to ACE PRIVACY POLICY.