Check the permissions of 'Public' role which may be denied to access sysobjects table.

This seems to fix your problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;323280&Product=sql2k

Good question. I don't see why not if there is no ORDER BY.

Check the option tab.

Script them out.

Try to logoff from the network and login again.

You may have to find out why they affect each other by running in one instance, possible be the TEMPDB?

If possible, I would run it on daily basis before the backup.

Could it be possible that user belongs to group which has been denied to access the SQL Server?

Are those 30 SQL Server also running on Windows 2003?

SELECT * FROM mytable WHERE Id = 1

union all

SELECT * FROM mytable WHERE Id = 3

union all

SELECT * FROM mytable WHERE Id = 2

union all

SELECT * FROM mytable WHERE Id...

Grant him as local administrator

or

Change Group Policy to give the access permissions to the MSSQLServer + MSSQLAgent Services to him.

Try to cleanup the log file with proper format before loading it with the BCP.

If SQL Server is configured to use memory dynamically, It will allocate memeory when it needs, if there is available memory for allocation.

Check Microsoft KB 244455.