cancel
Showing results for 
Search instead for 
Did you mean: 

SQL 2005 UPDATE_STATISTICS Long runtimes

Former Member
0 Kudos

Hi All,

we've an issue with CCMS_sid_SID_UPDATE_STATISTICS SQL 2005 Job that sometimes (most of all) run for between 1 to 2 hours, but, sometimes runs for several hours (20 to 25h), we wish to know if someone experience this kind of issues and what can we do to improve this job performance.

We are in SQL 2005 and DB compatibility level is SQL 2005 (90).

someone as one clue on this issue? Shoul we schedule this job to run twice or more a week?

thanks in advance,

best regards,

Pedro H Rodrigues

Accepted Solutions (1)

Accepted Solutions (1)

former_member211576
Contributor
0 Kudos

Hi Pedro,

Please refer to note 1178916 and 1305752.

--

12.02.2009 - 20:40:18 CET - by SAP

Hello Dennis and Kenka,

The table sap_tabstats is not cleared out after the upgrade to SQL

Server 2008. The records in sap_tabstats became unusable after the

schema was switched to tcp from dbo. That is because the table

sap_tabstats has a column uid which tracks which schema a table belongs

to . Note 1305752 is being written to address this situation.

I logged into your system, and the table appears to of been populated

over the course of the last several days.

Best regards,

Dale Adams SQL Server port dev support

Former Member
0 Kudos

Hi Dennis,

that's seems to worked for me.

Thanks a lot for your help, points were rewarded.

Pedro Rodrigues

Answers (1)

Answers (1)

Former Member
0 Kudos

Check ST03/ST0N for the background. Here you will be able to check which part is taking long.