76 distinct cached plans for the same stored procedure! Is that good or bad?

• Ninja's_RGR'us

  SSC Guru

  Points: 294069

  More actions

  May 4, 2011 at 11:48 am

  #1319988

  HTH.

• Jeffrey Williams

  SSC Guru

  Points: 90303

  More actions

  May 4, 2011 at 12:48 pm

  #1320035

  Here are the 2 blogs where I first saw this as a possible issue:

  http://blogs.msdn.com/b/mssqlisv/archive/2007/03/23/upgrading-to-sql-server-2005-and-default-schema-setting.aspx

  http://www.sqlskills.com/BLOGS/BOBB/category/SQL-Server-Schemas.aspx

  Jeffrey Williams
  “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

  ― Charles R. Swindoll

  How to post questions to get better answers faster
  Managing Transaction Logs

• Marios Philippopoulos

  SSC Guru

  Points: 57190

  More actions

  May 4, 2011 at 1:21 pm

  #1320058

  There is also this white paper:

  Plan Caching in SQL Server 2008

  http://msdn.microsoft.com/en-us/library/ee343986(v=sql.100).aspx

  See "Query Plan Reuse" section on factors affecting plan reuse.

  __________________________________________________________________________________
  SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
  Persisting SQL Server Index-Usage Statistics with MERGE[/url]
  Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]