Oh and then you need to restart the SQL Server service for it to take effect.

It is definitely not because of the edition. It is almost certainly because of the firewall blocking you. Even if you use a custom port, you'd still need...

I don't see how MsDtsSrvr.exe relates to the issue you are encountering.

I don't have any other ideas except that you need to contact your network administrator for assistance.

A primary key is unique. Is your one index also on FieldA or on another column? If it's on FieldA, then remove the index as it's a duplicate...

I've only ever used a domain account for the service when I've used that setting.

Yes you should. And yes it can and probably will improve performance.

Since telnet failed and since 1433 is in fact the port, you are going to need to contact your network administrator for assistance. It is likely that 1433 is...

No as the instance name must be unique on a cluster.

The 3 developers would require a license, however it does not need to be an MSDN license. They could instead just get a $50 developer edition license. It's...

There's tons of articles on it: http://www.google.com/search?rlz=1C1GPMD_enUS313US313&sourceid=chrome&ie=UTF-8&q=sql+server+audit+triggers

You can trace the queries via SQL Profiler.

If you want to audit DML operations (INSERT/UPDATE/DELETE), then you should look into auditing with triggers.

There aren't any commands that you need to run after it.

You could run update stats and a backup, but they aren't required.

VPilli, please see the link that I posted. It covers how to troubleshoot the issue including the stuff that I've posted in this topic.

We need to verify what port SQL Server is using. You can do this by viewing the SQL Server Error Log as it gets mentioned at startup, or we...

It is likely that the port is being blocked or that you aren't actually using 1433.

You need to test with telnet. On the client machine, open a cmd window...