Thank you mrdenny. This has highlighted the difference in the cached plans between test and production. The plans in question though are not in the cache on either machine, as far as I can tell. This may be why DBCC FLUSHPROCINDB made no difference.
Are there further factors influencing the...
I went for the brute force route of using DBCC FLUSHPROCINDB(<db_id>) but to no avail.
This is not a stored procedure that I am running.
Anything else that I can try?
Reindex did not make a difference here.
Thank you mrdenny, this looks like a fruitful avenue to pursue.
I am using SQL Server 2000 so I will need to try and get the cached plan information some other way.
Our usual weekly reindex is done with a variation on the sp by T.Pullen with the scan density threshold set to 85
http://www.sql-server-performance.com/tp_automatic_reindexing.asp
I am going to use the maintenance plan reindexing this weekend to see if it makes a difference to production.
stats are updated every morning, indexes rebuilt once a week.
What I am struggling with is what is different between the two servers that will make the execution plan look so different to begin with and then when the join is moved make them identical.
The servers are both SQL Server 2000.
Hi,
I have a production db and a restored copy of the db on two different servers.
A query on production has degraded to the point of timeout(30 seconds).
Running the same query on the restored copy produces an execution time of a couple of seconds.
The Execution plans look slightly...
Hi MarkVII,
Details as requested:
The column is of data type varchar.
I am using Enterprise Manager and trying to change the index through the design - properties window.
There are no nulls in this column.
There are relationships with six other tables, all bound to this column.
Enforce...
Hi all,
I am getting an error message when I try to make an already existing, unique index, clustered. Could anyone tell me what the error message is refering to?
Error Message:
'Tracks' table
- Unable to create index 'PK_Tracks'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.