Jacqui,

the table sizes don't seem to be a problem.

Maybe I did not understand something, but: In my eyes, a Full Text catalog only makes sense if you ran queries against it, and this is not the case. So I wonder why the performance has improved because of this. Maybe the improvement was based on a cached result and/or execution plan.

I analyzed the query a bit deeper, and found that creating some indexes could help:

CREATE NONCLUSTERED INDEX IX_UserPortals_CreatedDate ON {databaseOwner}{objectQualifier}UserPortals
(
CreatedDate DESC
)
GO

CREATE NONCLUSTERED INDEX IX_UserProfile_PropertyDefinitionID ON {databaseOwner}{objectQualifier}UserProfile
(
PropertyDefinitionID ASC
)
GO

CREATE NONCLUSTERED INDEX IX_UserPortals_UserId ON {databaseOwner}{objectQualifier}UserPortals
(
UserId ASC
)
GO

After that I had 1 second instead of 4 seconds, so maybe this is helpful. But I think this is only symptom control, the real problem must be somewhere deeper. So maybe first of all you try to

EXEC sp_updatestats

and see if that helps.

Best wishes
Michael

---

Jacqui,

see here: http://msdn.microsoft.com/en-us/libra... and here: http://msdn.microsoft.com/en-us/libra...

Best wishes
Michael

---

Glad I could help.

Best wishes
Michael

---