Hi,

You may find the following reference to be of use - Disaster Recovery Planning - Getting Started[/url]

Cheers,

Hi,

When you say that you did everything to enable AWE, what 'exactly' did you do?

Some quick points that may assist you.

1.Have you restarted the SQL Server Service since making the...

Hi,

Have you enabled remote procedure calls (RPC) for your Linked Server?

You're welcome, glad to help.

I have a reference to one of the best index defrag scripts, in my opinion, on my blog[/url]. It was written by SQLFool.

http://www.johnsansom.com/index.php/2009/03/automate-sql-server-index-defragmentationoptimisation/%5B/url%5D

An essential move not having your Reporting Server database on the C:\ Drive (which I assume is where your OS is intalled).

Hopefully your system database are also not sitting there...

One further consideration, I notice you state that you believe Reporting Services to be the source of your performance issues.

Before going ahead with any changes, I would suggest establishing with...

I would really not bother moving the installation files from one drive to another as, unless someone has evidence to the contrary, it will provide no noticeable performance benifit in...

What is the deadlock error message produced from your scenario?

It will identify for you the resources that are in contention with one another, and the lock types that are both...

You should find what you are looking for here.

http://msdn.microsoft.com/en-us/library/ms143518(SQL.90).aspx

Hi,

A common solution is to use SQL Server Replication to create a publication made up of a subset of your production database data.

The publication can then be scubscribed to by...

Yes, an INSERT can indeed be involved in a deadlock if another transaction either has or requires an exclusive lock on the object in question i.e. a particular data page.

It is quite common to not have antivirus software running on your sql server box provided the box itself is secured adequately within a securely configured network.

This requires that your...

One point that immediately comes to mind is have you configured your antivirus software to not scan your SQL Server data files?

What type of storage is being used on each instance? Are they identicial?