SQL Server accounts that aren't protected by systems administrator passwords are vulnerable to a new worm, analysts warn.

SQL Server 2008 continues to do so. The SQL Server polices that can be enforced include password complexity, password expiration, and account lockouts.

Ok, for SQL server 2000, I need to change the account it runs under. I know you need to go to the Enterprise Manager, find the database, right click, properties, choose security tab, and at the ...

They created accounts in SQL Server, and Windows was ignorant of these accounts. SQL Server has continued with this concept, largely for maintaining backward compatibility.

Security analysts are warning of a self-propagating worm targeting Microsoft Corp.'s SQL Server software.The worm scans for and attacks Internet-connected SQL server accounts that aren't protected ...

Security firms are warning of a new worm spreading fast through Internet-connected SQL Server accounts that aren't protected by administrative passwords.

I'm new at this whole DBA thing, so maybe this is totally standard practice.But we have a software vendor that wants remote access to our SQL server at an admin level to setup and install software ...

Understand SQL Server Security SQL Server grew out of the UNIX world, and administrators maintained accounts (at that time) in a fashion similar to the "no domain" scenario in Windows.