I like this method. It is actually faster and uses less resources...

Correct. It could be simplified even more.

It comes down to coding standards, personal preference and style.

It functions and performs the same as the following.

SELECT t.c.value('.','VARCHAR(20)') AS [Name] FROM @X.nodes('//Name[1]')...

This is more elegant.

SELECT

Table1.Column1.value('.','VARCHAR(20)') AS Employee_Name

FROM

@XML_Employee_Name.nodes('/Employees/Employee/Name[1]') AS Table1(Column1)

Disabling hyper threading appears to have resolved this issue as I’m no longer receiving the warnings in the logs.  The average % processor time seems to be the same...

Thanks noeld!

I also just came accross this.

http://news.com.com/Does+hyperthreading+hurt+server+performance/2100-1006_3-5965435.html

and it links to the first item in noeld's post.

I'm going to test one node with out HT and then failor and test...

Correct me if I'm wrong but wouldn't that cut your potential processing power in half?

Microsoft makes it out to be a hardware problem or a software setting (example: Power Management set to always on) that affects the way the hardware functions.

So…

I've gone rounds with HP...

How is your index management and maintenance?

On large tables with poor indexes or poorly managed indexes you can get this type of behavior.

Your question isn't entirely clear...

SP_WHO2 or use the Activity Monitor.

What is the error message that the restore process is failing with?

Did you run DBCC CHECKDB and DBCC CHECKCATALOG Before you started this process?

If not I recomend you do...

He didn't state which replication model he was using.  He could be doing transactional which uses a snapshot.  If he is doing transactional just because the snapshot succeeded doesn’t mean...

There are a number of methods you could use to do this.

1. The simple and quick way is to right click on the publication and select the "Validate Subscriptions..." option.

2....

If you could include the Queries, table schema, and indexes etc. it would make solving this issue much easier.

Feel free to rename objects and columns if it would be a...

Spaces_are_bad.  You_should_always_use_underscores.

Your Senario is flawed.

In order to restore "Yesterday's" the way you described you would have to select "From Device:" and select a backup file.  The method you describe is restoring...