Unfortunately, SQL Server 2000 doesn't have the ability to enforce password complexity. SQL Server 2005 will enforce what the OS knows if you are running on Windows Server 2003 (Windows...

This is likely not a physical memory issue... That referenced memory is the virtual memory space. As to how to uninstall it, you may have to do it manually:

The free way of doing it is to use Performance Monitor and export the data to Excel. It's pretty simple to do. If you need more details (shameless plug), I...

There is nothing specific to any technologies with respect to Microsoft, as I believe even in an NLB cluster SQL Server still only has one node servicing all clients. In...

You'll want to set up server side traces to do this. The auditing won't be obvious to a person in the datbase because it's at the server level. With that...

This should go without saying, but modifying sp_password will bring your server into a potentially unsupported state. Otherwise, piggy backing on the previous two posts by Remi, testing that specific...

If you are using SQL Server 2005, don't use syslogins. Instead use the system management view sys.sql_logins. There is a column, is_disabled, which is a flag for whether or not...

Run a Profiler trace on the server being linked to. Make sure you add in Audit Login Failure as an event. Try to use the linked server connection. If you...

Have you already taken a look at:

Troubleshooting guide for 80004005 errors in Active Server Pages and Microsoft Data Access Components

What version of the operating system, including the operating system service pack, are you running on each server? If you are running Windows Server 2003, there were fundamental changes to...

At the PASS Summit a few years ago I met the PolyServe guys and had a chance to see demos of their product. It's nice, but it's a high-availability solution......

It's not just 3rd party apps, either. Microsoft CRM 3.0 until just recently only supported default instances. You still have to jump through hoops to get a named instance working...

You shouldn't make such a change without understanding what they are trying to do security wise... this does open up the database in question and sometimes it's necessary or it's...

From a security best practices perspective, you'd want to segregate the databases accessed by your public web site from your internal (sensitive) databases and that means different servers. The risk...

Actions taken in SQL Server have no effect on the domain. If you disable a login or group in SQL Server, it only affects SQL Server. However, changes in the...