So let's say you have DatabaseB running on ServerA.

Create a DNS entry called DatabaseB.db.yourdomain. Repoint your applications so that they use that DNS entry.

When you move the database to ServerC...

There's no quick fix for this unfortunately. You'll have to edit the connection strings no matter what.

You may want to get ahead of the game and create a DNS...

There are many possible reasons that it's faster on the other server such as:

- storage performance (be it DAS or SAN); you could be on faster disk on the other...

Eric, you can't move TempDB to another server. It's required for SQL Server to be able to function. All you can do...

Are you using a separate distribution server? Can you check the the login has access on that machine?

Also, look through the SQL error logs to confirm which machine is actually...

Books online is actually very helpful when it comes to proxies.

http://msdn.microsoft.com/en-us/library/ms189064.aspx

I would recommend setting up a separate account for use as the proxy. You don't want things running under the...

And the application logs? Sometimes it can be something that looks seemingly innocent that cause the problem.

Honestly, no less than 100GB for Windows 2008/R2.

You can get away with 40GB for Windows 2003, but hopefully you won't be running that.

SAS drives are to inexpensive now that there's...

Then you have no good backup.

Have you looked at the OLAP error logs? Anything useful contained within those? How about other events in the Application & System event logs around the time that the OLAP...

You would actually want your page file on another drive (for performance), although hopefully you'll have plenty of memory and limited paging.

I wouldn't (at this stage) go with anything lower...

I would recommend creating a credential on your SQL Server. This will be mapped to a domain login.

Then create a SQL Agent proxy account linked to the proxy and...

Have you been able to perform a manual distributed transaction between servers?

Such as

begin distributed transaction

select * from [ipaddress].master.sys.databases

commit distributed transaction

If not you have a DTC issue that needs to...

I would stagger your backups. Hopefully, in production, you are running in full recovery and taking regular transaction log backups meaning that you can restore to any point in time....

You could have replication scripted out and use sp_droparticle to drop the articles rather than unpublish the entire database.