As Sara indicated, they are encrypted. They can be cracked, but usually there's not a need to see the passwords. If you want to transfer logins to another SQL Server,...

The isolation level or lock hint will allow your query to run without timing out, however there sounds to be a more serious issue. Are there transactions that are staying...

A lot of time when a create procedure code is generated, the drop procedure code is included at the top to automatically remove the procedure if it exists. Naturally, when...

I don't have any experience with DB2, so you'll want to check deeper into this yourself.

There looks to be a client that allows you to connect to DB2 via ODBC:...

It's a known bug. Switch the view to something other than Taskpad view. Then switch it back.

Does the service account which SQL Server runs under have the ability to access the network share?

You see the first screen and it doesn't go any farther? Or you are able to click through the options but nothing happens afterwards?

In either case, see if there's a...

This is an error I'm used to seeing on Windows Server 2003, but not 2000. It may be worth the money to open a case with Microsoft on it. If...

1. When a clustered index is removed is the effect immediate (I deleted the clustered index and the performace is still terrible)

While SQL Server is no longer required to physically...

SQL Server 2000 doesn't do any sort of "phone home" and I haven't run into this problem myself, even when transitioning servers like you are trying to do. In the...

You can force 8.3 (short) filenames, however, there are issues with it, as this blog points out:

Aaron Stebner's Weblog: Registry key to force Windows to use...

Using Firefox?

If John or Ann were to change settings, would the other one be affected?

A temporary table gets created in TempDB. Therefore, the CHECKIDENT would have to run against a table there. Is the login in question a dbo over TempDB?

If you're using a table variable, the table variable is going to disappear when the stored procedure that defined it ends.

From BOL:

table variables are cleaned up automatically at the end...