Error on newly release SQL Prompt 3.0

• 
  I keep getting intermitten errors where my Query Analyzer window will have multiple Sql-prompt menus. This doesn't happen all the time but occassionally I will have multiple windows within one QA session open, then I'll open another QA session, and that window will be normal, but my primary QA window will suddenly have as many as 6 Sql Prompt Menus.

  fhtapia January 30, 2007 14:16

  - 0 +
• 
  Hi
  
  I would really like to get to the bottom of these errors.
  
  bconlon: Could you please tell me what you were doing when you got that error? Were you creating a new window closing a window or doing something else?
  
  
  fhtapia: That sounds like a different issue If you find anyway of relyably reproducing that error please tell me. There is a similar issue where by closing and opening the tray app you can get multipule menus to appear. I will put in a fix for that problem which should fix this bug as a consiquence. I would really like to be able to reproduce that problem here so know I have definatly fixed it!
  
  Lionel

  Lionel January 31, 2007 05:41

  - 0 +
• 
  Does anybody else experience this or have any information on how we could reproduce it please?
  Thanks,
  Bart

  Bart Read February 22, 2007 11:53

  - 0 +
• 

  Bart Read wrote:

  Does anybody else experience this or have any information on how we could reproduce it please?
  Thanks,
  Bart

  Yes, I am also experiencing this error.
  
  In my case, it is always happening when I work with the "sys.dm_db_index_physical_stats" Dynamic Management View. The syntax of the command is as follows:
  
  SELECT *
  FROM sys.dm_db_index_physical_stats(DB_ID(N'<UserDatabaseName>
  ', NULL, NULL, NULL, 'LIMITED');
  
  As soon as I enter the left parenthesis, the exception is thrown. It also happens if I click or type anything inside the parentheses of an existing script of this command.
  
  My machine runs Windows XP Professional SP2 (Build 2600) and SQL Server 2005 SP1 with Cumulative Hotfix KB918222. The SQL Server build number with this hotfix is 9.0.2153. I have downloaded all current Windows updates other than SP1 for Visual Studio 2005.

  Wyatt70 March 06, 2007 14:02

  - 0 +
• 
  Thanks Wyatt, I'll give this a whirl and see what happens.

  Bart Read March 07, 2007 06:15

  - 0 +
• 
  It seems to have something to do with the DMVs, because I get the same behavior with this script that I use to monitor my SQL Backup jobs:
  
  SELECT er.session_id, program_name, er.command, er.sql_handle, er.start_time, er.status, er.percent_complete, er.blocking_session_id
  FROM sys.dm_exec_sessions es INNER JOIN sys.dm_exec_requests er
  ON es.session_id = er.session_id
  CROSS APPLY sys.dm_exec_sql_text(er.sql_handle)
  WHERE program_name like '%SQB%';

  Wyatt70 March 07, 2007 08:07

  - 0 +
• 
  Hi Wyatt,
  
  
  That's right. Actually it affects all table-valued system functions on SQL Server 2005. Rather embarrassing for us, but fortunately a very easy fix. Thanks for getting back to me with that extra information: very helpful.
  
  
  Cheers,
  Bart

  Bart Read March 07, 2007 08:27

  - 0 +
• 
  Just to add, this fix will be available in the 3.1 point release which should be out before the end of the month.
  Thanks,
  Bart

  Bart Read March 07, 2007 09:14

  - 0 +
• 
  Hi there,
  
  
  Just to let you know that an early access release of SQL Prompt 3.1 that should fix this problem is now available. See the following post for details:
  
  http://www.red-gate.com/MessageBoard/vi ... php?t=4487
  
  Hope that helps.
  
  
  Thanks,
  Bart

  Bart Read March 13, 2007 12:45

  - 0 +

Add comment

Please sign in to leave a comment.