See if this article helps:

http://www.sqlservercentral.com/articles/T-SQL/67898/

Confirmed. You don't need SP1 and SP2.

Based on your description, my vote goes to a clustered index.

Just to be sure, when you say "updated", you mean existing rows are updated or new rows are inserted?

I think you would have to use dynamic sql: (untried)

DECLARE @DatabaseName nvarchar(128)

SET @DatabaseName = 'model'

DECLARE @sql nvarchar(max)

SET @sql = '

SELECT

object_id AS objectid,

index_id AS indexid,

partition_number AS partitionnum,

avg_fragmentation_in_percent AS frag

FROM '+ @DatabaseName...

I am sure the implementation is very good, but I don't like re-inventing the wheel.

Why are you using a home maid procedure when there's Ola Hallengren's fine script[/url]?

Also,...

GilaMonster (7/7/2011)

---

Gianluca Sartori (7/7/2011)

---

If you don't want to pay for the overhead, you can disable the clustered index on the view and re-enable it with ALTER INDEX REBUILD before running...

Glad I could help.

If you don't want to pay for the overhead, you can disable the clustered index on the view and re-enable it with ALTER INDEX REBUILD before running the daily export...

Is resource governor configured?

You could:

A) Add some debug info to the stored procedure (log to a table or print and capture the output)

B) Trace the process with a server side trace

Probabyl you have...

Unfortunately they can. Take a look at...

Which provider is used by the linked server?

This is exactly what I usually do, except that I pause the node instead of removing it from possible owners.

Take a look at Gail's suggestion, then.

Any matches for the database name?