How realize Windows Authentication in small networks?

Hello,

In SQL Servern Books is written:
SQL Server Authentication is provided for backward compatibility only. When possible, use Windows Authentication.

How can Windows Authentication be realized in small networks from two ore more computers running Windows XP?

Having all a application written in VB Net 2005 for example, which connects to a central database on one computer. Where the cost and afford for a domain controller running Windows Server is not necessary.

If Windows Authentication can't be realized or can't be realized easy in such a scenario, and SQL Server Authentication is not supported any more, then SQL Server can't be taken as database server for this scenario, where the focus is at simplicity and low cost.

Regards,
Markus

I think that is a a bit confusing from the BOL. Backward means those machines that can not use Windows authentication, like workgroup machines, other platforms etc. I Don′t think they will deprecate that in the future. Perhaps that might be the help to your costly problems, don′t now if that applies to you, haven′t tried it yet (ADAM) http://www.microsoft.com/downloads/details.aspx?FamilyId=9688F8B9-1034-4EF6-A3E5-2A2A57B5C8E4&displaylang=en

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

> costly problems

i think simplicity and low cost need not be a problem. When possible, it should be a great advantage :-)

|||

We still support SQL Authentication, use it in good health.

BOL is just trying to encourage folks on larger networks who have Windows Auth available to them to use it as it offers several advantages from a management point of view. For small Workgroup networks such as that you describe, SQL Auth is your answer.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||Thank you, Mike. Then it was a misunderstanding of "SQL Server Authentication is provided for backward compatibility only." in the documentation. How already Jens expected.