SQL Failure Audits

A few pointers:

- Never have a blank 'sa' password
- Use NT Authentication only, not SQL authentication
- Don't use localsystem for the SQL Server startup account, create a restricted user account
- Put SQL behind a firewall or use Proxy Server/ISA Server to protect /limit who can connect to it
- Apply the latest security patches to your system.

With SQL Server 2000 if you're only using it locally, you can unbind TCP/IP and named pipes, local access can be done via Shared Memory. I take it you're using SQL Server Express 2005? I'm not familiar with that, have a look at the documentation: http://www.microsoft.com/sql/editions/express/default.mspx

If your SQL is only accessed by the local machine then simply don't allow connections other than local:

 First Launch SQL Computer Manager

     Then Expand "Server Network Configuration"

     > Expand Protocols for "SQLEXPRESS"

     > Enable Np (for local access only)

     > Enable TCP (for local access only)

    Lastly Restart SQL Express

This should solve that problem 100%

-D-

Thanks for your reply,
dimante:- I can not find where it says (for local access only) when enabled Np or TCP
Can you please let me know what I should be seeing.

when I enable Np or TCP the only option it gives me is enable or disable

How about as a test disable TCP and see if your app still works.  If it does that will solve the issue.

no this did not work, i am guessing I will need to change my sql connection string ?

Are you using a DSN or DSNLess connection?

DSNLess

Provider = SQLNCLI; Data Source=IP; Initial Catalog=db_name; User ID=username; Password=password;

Nearly right,

here is the correct SQL statement for anyone read:

Provider = SQLNCLI; Data Source=\\<computer name>\pipe\MSSQL$SQLEXPRESS\sql\query; Initial Catalog=database_name; User ID=username; Password=password;

Not had a single Failure Audit since.
Many Thanks dimante

Excellent!  And most secure for your situation ;-)