If it's within SQL Server, use sp_password if you're looking for a T-SQL solution. You can also use Enterprise Manager.

Sorry, was in the middle of walking an admin at a remote site on troubleshooting his server's failure to register in DNS as I was typing the reply. He didn't...

Glad that snippet of code was helpful.

That article is a good start for SQL injection, but a bit on the brief side. That's because the author (a respected MVP) is concentrating more on the overall issue...

If they've installed the SQL Server client tools from the SQL Server CD, then you should apply SP3. These would be Enterprise Manager, SQL Profiler, Query Analyzer, etc.

If the client...

Is your SQL Server in an Active Directory domain? Do you know if there is a group policy set?

Attempt to log on as that username/password combo at the SQL Server itself. Also, check the event logs to ensure you don't have any "Domain Controller can't be reached" errors...

Data fault tolerance... in other words, the operating system itself does nothing specific to protect the data just because it's a cluster. You usually build fault tolerance in with the...

Have you looked at the following?

817064 - How to enable network DTC access in Windows Server 2003

329332 - PRB: You Receive Error...

That's a lot of drives. This isn't a cluster, per chance? With the drives on the other node?

IPSec policy as well. You can set a policy on the SQL Server to specifically block that IP. Defense in depth. That way if a configuration change happens on the...

If the user has granted permissions, you are correct. Same with deny. Revoke simply means to remove whatever the permissions are, be they grant or deny. Not sure why BOL...

For the domain account, check your system event logs to see if you have any errors at the same time indicating a domain controller was unavailable. The SQL Server one...

xp_fixeddrives is intended to return information on hard drives and the free space available. A CD-ROM is technically removable.

FAQ - xp_fixeddrives

Please don't crosspost. see my reply here:

SQL Injection Prevention under T-SQL