When you delete rows from a heap, the space is not completely reclaimed.

You need to add a clustered index, rebuild, drop the index and the space should be reclaimed

How about this?

UPDATE dbsource SET softwaremanufacturer = dbref.Amended_SW_Manufacturer,

productname = dbref.Amended_Product_name,

productversion = dbref.Amended_Product_Version,

licensable = ISNULL(dbref.category,'Unknown')

FROM dbo.newtable dbsource

LEFT OUTER JOIN (

SELECT Raw_SW_Manufacturer,Amended_SW_Manufacturer,

Raw_Product_Version,Amended_Product_Version,

Raw_Product_Name,Amended_Product_Name,category

FROM datalookuptable

GROUP BY Raw_SW_Manufacturer,Amended_SW_Manufacturer,

Raw_Product_Version,Amended_Product_Version,

Raw_Product_Name,Amended_Product_Name,category

) dbref

ON dbref.Raw_SW_Manufacturer = dbsource.softwaremanufacturer

and dbref.Raw_Product_Version =...

Yes the database on ServerB should be in NORECOVERY, you can select "the secondary db is already initialized" in the wizard.

Steps here

http://www.mssqltips.com/sqlservertip/2301/step-by-step-sql-server-log-shipping/

How about this?

select max(x.row) rows, x.[800num], x.CompanyName

from (

select row_number() OVER (partition by a.CompanyName order by a.[800num]) row, a.[800num], a.CompanyName

from calldata a ) as x

group by x.[800num], x.CompanyName

What happens when you insert multiple rows? @id = ?? @type = ??

Yes threadpool shouldnt be in the top waits. I would recommend setting your Sql max mem to 68GB as per best practise.

http://sqlserverperformance.wordpress.com/2009/10/29/suggested-max-memory-settings-for-sql-server-20052008/

Try that first then investigate further.

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/f11537a5-8dc9-40a8-b2e4-17874685b074/sql-server-2008-r2-error-18056-severity-20-state29

Yes its for error state 29 but 46 is likely going to be from the same sort of resource contention.

To help understand the state 46 error, this guy...

Actually probably your best bet is to build another box with standard edition then migrate everything over to it, that way you'll know if you've missed anything.

Then you can...

There is no point adding all columns as key columns unless you have queries which use all the columns in joins/where/group by clauses.

You also have a 900 byte limit on...

Both Paul Randal and Jonathan Kehayias have blogs which include evidence that the t-logs are filled sequentially

http://www.sqlskills.com/blogs/paul/multiple-log-files-and-why-theyre-bad/

http://www.sqlskills.com/blogs/jonathan/an-xevent-a-day-23-of-31-how-it-works-multiple-transaction-log-files/

Jonathan's conclusion:

The reason that only a fraction of the log records are written...

You can't downgrade, you would need to completely uninstall and reinstall.

http://msdn.microsoft.com/en-us/library/ms143393%28v=sql.100%29.aspx

If you also have SQL on the box, you'd need to uninstall and reinstall standard edition as well:

Cross-version instances of...

Actually since you get the error with normal Powershell as well, it's not patch related.

Very unusual.. I havent seen that issue on any clustered SQL servers.

The only related...

What version and patch level of SQL are you running?

There is a connect issue related to 2008 SP3 where sqlps is not working properly in a clustered environment:

http://connect.microsoft.com/SQLServer/feedback/details/491109/subsystem-powershell-could-not-be-loaded

Could be something...

Never shrink the log file, it will have to grow again to accomodate any transaction that requires the space.

Read up some more on transaction log management, you need to understand...

From http://blogs.msdn.com/b/sqlsakthi/archive/2011/02/28/t-sql-script-to-monitor-memory-usage-by-sql-server-instance.aspx

Dynamic SQL cache is in there somewhere

/*============================================================================

Script to report Memory usage details of a SQL Server instance

Author: Sakthivel Chidambaram, Microsoft http://blogs.msdn.com/b/sqlsakthi

...