The values of the WRITELOG aren't very above the value?

Ok. What about if the index has a value page_count < 1000 you don't rebuild also? even if its near 100% of avg_fragmentation?

Ok. Let me give you an example:

nameObjectIDIndexIDPercentFragmentTotalFragsPagesPerFragNumPages

ticket_synchronization2145129316084.303417198648122509.4364444444444421232

Would you rebuild this index?

How can I see if the statiscts of other tables are ok or if they need to be updated?

Also, the sincronization started to loose performance on day 23 of october.

The logs of the SQL Server that have the Database publication and the distribution database cannot help?`

Thanks

"Set up a subscriber on your machine and subscribe to that publication."

Unfortunately I cannot , because I just have the client tools on my machine. So I cannot create a...

I understand. I will try to create a subscriver thropugh my machine.

Tell me one thing please:

I already run the query over the distribution database Which produced this results:

namecommandObjectIDIndexIDPercentFragmentTotalFragsPagesPerFragNumPages

DF__MSsubscri__nosyn__08EA5793Rebuild149575571284.543381735269472991.141663241539948333

DF__MSsubscri__nosyn__08EA5793Rebuild149575571153.157042633567218521.000539956803461853

MSmerge_historyRebuild933578364147.49687108886115732.788830715532291598

DF__MSsubscri__nosyn__08EA5793Rebuild149575571140.07064063560161522962.40001050585702365512

MSmerge_articlehistoryReOrg757577737118.29059829059835143.414396887159531755

MSmerge_historyReOrg933578364213.351443807224196664.1129733085040439756

MSmerge_historyReOrg933578364110.1303584975031920754.66726038555525429738

MSmerge_historyReOrg93357836434.1849850656106347016.3384386300787129797

DF__MSpublica__allow__014935CBReOrg2157511513.2347688033339937813.33068783068785039

IHsyscolumnsReOrg1809910512.8319697923222213611.68382352941181589

DF__MSpublica__allow__014935CBReOrg2157511512.6181649675625627515.69454545454554316

DF__MSmerge_a__delet__300424B4ReOrg80557790812.388663967611342719.114391143911442470

DF__MSmerge_s__schem__267ABA7AReOrg64557733811.451666116793143259.326153846153853031

IHpublishersReOrg142958013111.11855176981382100413.534860557768913589

UIPropertiesReOrg49810081520.08984725965858042556.51113

As you...

Or should I look at I/O Stats?

What should be the next step to investigate? maybe lock and block?

"That details what in Microsoft's eyes is a candidate for maintenance."

You are saying that because this query :

SELECT

case when avg_fragmentation_in_percent < 30 then 'ReOrg' ELSE 'Rebuild' end as command,

object_id...

Your answer, not question.

Sorry I didn't understud your question.

What are page_counts >1000

When I run your query:

SELECT

case when avg_fragmentation_in_percent < 30 then 'ReOrg' ELSE 'Rebuild' end as command,

object_id AS ObjectID,

index_id AS IndexID,

avg_fragmentation_in_percent AS PercentFragment,

fragment_count AS TotalFrags,

avg_fragment_size_in_pages AS PagesPerFrag,

page_count AS NumPages

FROM sys.dm_db_index_physical_stats(DB_ID('BMB1_Market'),

NULL,...

How can I do that trace on the server if I cannot use profiler. Any idea?

De

So, because most of the tables are above 30% in terms of indexing I should rebuid all the indexes, correct? Even from the msmerge tables?

Another question, if I rebuid the...