Did you confirm the password to start your srevices correct?

Could you give me a source showing there is no difference?

I searched the article in your link by client...

SQLCMD is for SQL 2005.

How about BCP utility?

Did you restore MSDB, where your jobs were saved?

This error may be hardware related, but not always true. See the link below.

http://support.microsoft.com/kb/828339

Check you log file size. If it is bigger than your expectation, you may try the following approaches.

1. Have transactional log backups regularly;

2. Turn the recovery mode of this database...

From Enterprise;

Right-click SQL Server Group;

Choose New SQL Server Registration ...,

...

You would not miss it.

Please provide your query. I am pretty sure some people will help you out.

VARCHAR(50) and DECIMAL(18) are not good candidates for indexing. If you cannot modify indexes, you may not have choice.

In principle, data type of column chosen to be indexed should not...

Try this, if you do not like FULLSCAN,

EXEC sp_msforeachtable 'UPDATE STATISTICS ? WITH SAMPLE 20 PERCENT'

Here are two links

http://www.devarticles.com/c/a/SQL-Server/Replication-SQL-Server-2000--Part-1/

http://www.devarticles.com/c/a/SQL-Server/Replication-SQL-Server-2000-Part-2/

Mat they help.

As far as I know, the only difference between Enterprise and Developer versions is the later has limited cocurrent users.

Did you try to grant SELECT permission to PUBLIC?

ERRORFILE can be used in SQL 2005. See the following links

http://msdn2.microsoft.com/en-us/library/ms188365.aspx

http://support.microsoft.com/kb/919775

http://www.sqlservercentral.com/Forums/Topic447601-338-1.aspx

In SQL 2000, although running BULK INSERT ... WITH (ERRORFILE ...) does not give us any error, the system ignore...

Do you mean the total cost is 99% when you wrote anything wrong in the execution plan?