When you say open a port, what is the network topology between the clustered and stand-alone servers? Is there a firewall in between?

Please don't cross post. I replied to your other post.

You can use server side traces. If you restrict the types of events and columns captured, you can really reduce the footprint. However, as another poster indicated, the application name...

The ./ means it is a user account on that computer (a local user account). If you look at the list of users for that system using Computer Management, you...

Yup, EXECUTE AS rocks.

When you say you gave him Windows access, does that mean you granted his Windows user account access as a login to SQL Server? Or did you mean you added...

Create two user-defined roles.

One should be for the normal company employee. GRANT that role SELECT rights against the table. Make all corresponding users a member of that role.

The second...

One issue with the -L switch is it is

a) dependendent on the SQL Server Listener Port not being blocked for a given SQL Server

b) dependent on the communications between...

If a process runs as the local System account (Windows 2000) or Network Service account (Windows XP / Server 2003), it'll connect across the network as Domain\ServerName$. Typically this is...

I think you mean SETUSER. SETUSER requires sysadmin rights to use.

Unfortunately, in SQL Server 2000 there's no way to handle this execution context switch.

Another solution, if the command...

If you have values already stored in a binary log format, you can use relog to convert them.

Description of the Windows XP Logman.exe, Relog.exe, and Typeperf.exe...

If it's a cold site (no connectivity back to the existing site) or if connectivity where name resolution comes into play is prohibited, there shouldn't be any significant issues.

However,...

Unless you had auditing via triggers or traces or a 3rd party product, unfortunately not. SQL Server does not store this type of information natively.

The trigger fires once.

It's not a named instance thing. Something else is going on. Anything in the server application, security, or system event logs which seem to correlate? What about the SQL Server...