I have SQL Server 2005 Developer edition installed.  I use Windows
Authentication and the user is an admin on this box.  For whatever
reason, I was recently locked out of SQL Server.  So I uninstalled and
reinstalled then I could get back in.  Then once again, I became locked

I see these events in the logs of my SBS R2 server running SQL 2005:
Event Type:    Failure Audit
Event Source:    MSSQLSERVER
Event Category:    (4)

I am new to SQL security.
Some days ago I happened to open my event log and found lots of attacks have
been going on to my SQL server 2005. Maybe for some months. I have been
using firewall and Windows integrated authentication. The attacks might be

I am looking at the sys.dm_exec_connections view and notice some connections
are Kerberos and others NTLM.  All the users are on XP SP2.
It seems the kerberos connections are getting  the "Cannot generate SSPI
context" every day or so, would this be the case/

How would one make SQL SERVER Log the IP on failed login attempt ?

The preblem has been already discussed but none of answers help me.
I have a SQL Server 2000 SP4. Users that are not sysadmins create jobs for
SQL Server Agent. These jobs consist of a single CmdExec step.
As advised in many posts I created a Proxy SQL Server Agent account

I need to audit any  access to table (example table creditcards)
profiler work fine  if table  creditcards referenced
by select/ upadate/delete or procedure
but if I create view

I logged into SQL Server 2005 Developer edition as an admin through
Windows Auth.  I created a very basic user and login.  I then changed
the authentication to mixed and logged in as the basic user.  I log out
and now I'm stuck.  Windows Auth is turned off so I can't get in as the

We have a brand new out-of-the-box SQL Server 2005 Workgroup Edition install.
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain.  We've given those logins the appropriate
permissions on the databases they're supposed to be ...

Our database section is relatively new.  The SQL Servers were setup
before our creation and the security is our first area of concern.
Currently, there is a .NET 1.1 COM layer that handles all database
access.  It is using a single NT domain account with read/write to all

I am experiencing strange success of authentication.
I have two boxes, one xp-pro and another windows 2003, both have SQL2005.
Two boxes have no relationships except that they are in same network. Really
nothing such as account and trusted relationship.

Hi, this could be an ASP, IIS or SQL server question so please bear with me!
We have an sql server 2000 machine and our IIS 6 machine running seperately
but on the same domain.  I can connect fine to the database without using
impersonation, but when it's enabled I get the error:

I have a SQL Server 2005 database that is used by an Access ADP program. What
I'd like to do with my SQL Server 2005 database is secure it with a UserName
and Password that is only known to my program. Any other use who logs in to
SQL Server, even the SA User, should not be able ...

I'm a newby to SQL and I would like to create a SQL stored proc to drop a
given user from all databases, and the drop the login.
So if any given server has 10 or 12 databases, I was hoping the proc would
loop through whatever the databases are :  Select name from

Weird question, but hey!!
We have mixed-mode authentication on one of our databases.
Is there any way of avoiding the users seeing the "Use trusted connection"
option when in the connection dialog (eg from Excel Import Data)