<div>
I prefer Windows Authentication. Grant access to an Active Directory group, and then make sure that new users get put into that group.<br />
<br />
Then you don't have a hard-coded password, and you can easily control access through AD accounts.<br />
<br />
Rob<br />

</div>


I prefer Windows Authentication. Grant access to an Active Directory group, and then make sure that new users get put into that group.

Then you don't have a hard-coded password, and you can easily control access through AD accounts.

Rob


<div>
<div class="content wysiwyg-content">
I am trying to work out whether I should use windows or sql server authentication.<br />
<br />
I have an access front end application that is connecting to sql server via odbc.<br />
<br />
sql server authentication may be the easiest as when new windows users are created, they will not need to be setup in sql server. However, I am concerned abot having a hard coded userid and password.<br />
<br />
What would other developers recommend - sql or windows authentication ?
</div>
</div>


I am trying to work out whether I should use windows or sql server authentication.

I have an access front end application that is connecting to sql server via odbc.

sql server authentication may be the easiest as when new windows users are created, they will not need to be setup in sql server. However, I am concerned abot having a hard coded userid and password.

What would other developers recommend - sql or windows authentication ?

sql server connection - windows or sql server authentication

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.