In Windows 2003 you can see user name (add "Users name" column from "View" menu). You will see difference if your instances run under different NT accounts.

We had similar problems when name server was not avaliable (check DNS or WINS settings).

Profiler also shows this information (if you need long time monitoring). Just make sure that you selected "Lock" events to monitor and selected "BinaryData" and "Mode" columns. "Mode"  describes the...

Yes, this is server name. But this does not look like error's source. It runs withour errors localy on the same server. I guess, error is because of this procedure...

If you are sure, that you restored all backups (data and logs), try to run this command in Query Analyzer:

RESTORE DATABASE DB_NAME WITH RECOVERY

Kerberos works on TCP/IP, so make sure that in protocols order (connection utilities) first protocol is TCP/IP and second - Named Pipes. When I tested accounts delegation I could not connect until...

Open "Users" folder for this database and check if this account (login) is mapped to "dbo" user. If yes - fix it with procedure sp_changedbowner.

I am not sure about clusters, but usually MS DTC installation in Windows 2003 server avaliable from "Control Panel" -> "Add or Remove Programs" -> "Add/Remove Windows Components" -> "Application...

What are SQLSEREVER and SQLSERVERAGENT services startup accounts? Local user, system or Domain account? And does this account has access to that web server? Can you give some information about...

You need to backup log more often, try to do it several times a day. It depends on frequency of modifications in your database.

If you installed samples on SQL Server installation there are samples:

C:\Program Files\Microsoft SQL Server\80\Tools\Devtools\Samples\Dts\Dtstasks\DTSCopyDatabase

Another way to run any DTS package from program or script - save package as file, then...

I used Enterprise Manager wizard to create web task and then scripted it. Here is the script and it worked fine, as well as job with SQL 2000 and Windows 2003:

EXECUTE...

Otherwise you can trace event class "Security Audit -> Audit Login" (best way to do it not with Profiler, but with stored procedures, like sp_trace_create, sp_trace_setevent etc.).

If the user is still connected to server you can find out it from login_time column from sysprocesses table.

Yes, this is the best script to fix permanenently log size. I use it as well for long time (this script is from Microsoft). Also, I suggest you to do...