Michael Maddison
michael at ddisolutions.com.au
Sun Apr 2 22:56:05 CDT 2006
Where to begin... Try clearing the buffer on the fast db to see if it takes longer if the cache is cleared. dbcc dropcleanbuffers with no_infomsgs dbcc freeproccache with no_infomsgs Make note of any diffs in the 2 Execution plans, take note of any parallelism used by either. Add [ WITH RECOMPILE ] to sproc definition Rebuild stats read http://www.sql-server-performance.com/default.asp cheers Michael M DDI Solutions Pty Ltd michael at ddisolutions.com.au Bus: 0260400620 Mob: 0412620497 www.ddisolutions.com.au -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Monday, 3 April 2006 1:16 PM To: Access Developers discussion and problem solving; dba-SQLServer at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Optimizing Stored Procedures and Views Thanks John, I checked all the indexes and they seem to be the same. David At 3/04/2006, John Ruff wrote: >Check your indexes in the tables that make up the views on the db that >is running slow and compare them with the same tables in the db that is >running fast. I'd venture to say you don't have one or more columns >indexed in the slow db that should be indexed. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com