Solved! Go to Solution.
There could be several suggestions for you:
1. Shrink the database.
in SQL Server management Studio-->R-Click on the database-->Tasks--> Shrink
Shrinking the Transaction Log:
2. rebuild indexes
http://support.esri.com/cn/knowledgebase/techarticles/detail/24518 (the link is valid for new SQL Server versions as well)
3. Reconcile/Post all versions and compress to state 0
Give these a try and check whether this helps!
Is the �??compress�?� tool does compress to state 0?
does the �??analyze�?� tool help improving the performance as the �??analyze dataset�?� does?
The compress tool trims the state lineage of your versioned geodatabase. Depending on how much of your edits have been reconciled and posted from child versions up to parent versions, compress will move records from the delta tables to the base tables. Compressing to state 0 essentially means that all records have been moved from the delta tables to the base tables. You can compress all you want, but you will only achieve state 0 if: (1) ALL edits have been reconciled / posted, and (2) all versions are either deleted or their state IDs are set to the same state ID of SDE.DEFAULT prior to compress (although this happens as you successfully reconcile and post, anyways). Compressing on a consistent basis is recommended, even if state 0 isn't your end goal.
The analyze tool and the analyze dataset tool both essentially do the same thing; however the analyze dataset tool will perform an analyze for all object classes within the entire input workspace (e.g., a feature dataset). The analyze tool only targets one specific object class at a time.