How can we help you today? How can we help you today?

SQL 2005 Query Analyzer integration fails

I'm running:
- Windows XP SP3
- SQL2005 SP3
- VS2005 SP1

I just installed SQL Prompt 4 on my machine. It worked wonderfully the first time I opened Management Studio. I closed it and opened it again, and gone was my SQL Prompt integration.

The only way I can get it working again is by rebooting my notebook.

Any ideas?
JP7
0

Comments

7 comments

  • Chris George
    Hi,

    I'm sorry that you are having these problems. However, I have been unsuccessful at reproducing your issue.

    So that we can investigate this further, could you let me know the following information please?

    1. Did you already have 3.x installed? if so, which version?

    2. What exactly happens when you lose integration? Do you still get the menu in management studio? does prompting happen just without database information? Please describe the symptoms.

    3. Is management studio the only application you have open?


    Thankyou for taking the time to report this, and thankyou for trying SQL Prompt 4.0 Early Access.


    Chris
    Chris George
    0
  • JP7
    Hi Cris,

    At the moment I have some pending C# development keeping me from using SQL Prompt.

    I'll investigate the issue more thoroughly when time permits and revert with my findings.

    Thank you

    JP
    JP7
    0
  • JP7
    Hi Chris

    I had a clean installation of Windows XP, which means I did not have SQL Prompt 3 installed. V4 was the first.

    After having rebooted my notebook, I did the following:
      Closed all unnecessary programs in the system tray. Disabled Eset Smart Security 4.

    At this stage I have the bare minimum running.
      Open a new instance of SQL Management studio. Type in a query and run. Everything is working fine at this stage. Close SQL Management Studio. Open SQL Management Studio again. Type in a new query.

    Now SQL Prompt does not pop up at all. Also, the SQL Prompt 4 main menu item becomes grayed out when I try to select "Refresh Suggestions" for instance. I can mail you a screenshot if you wish.

    Usually I would have to reboot my notebook to get SQL Prompt 4 working again. However, I just tried it again a couple of times and now it's working without fail.

    Very odd. Is there any sort of debugging/tracing information or logs I can look at to try and help pinpoint the problem?

    Please note that I have VS2008 installed in addition to VS2005.

    Please let me know if I can be of any assistance in helping trace the problem.

    Just by the way, I also experienced the same problem with V3.9 before reload WinXP.

    Thanks.

    JP

    PS: I found the following error repeated in nearly all logs
    05 Jun 2009 09:02:24,843 [1] INFO  RedGate.SqlPrompt.Engine.LogService - Starting new SQL Prompt editor session
    05 Jun 2009 09:03:03,140 [5] ERROR RedGate.SqlPrompt.Engine.LogService - LogService caught unhandled exception in AppDomain: 'Thread was being aborted.'
    System.Threading.ThreadAbortException: Thread was being aborted.
       at RedGate.SQLPrompt.CommonUI.TaskExecuter.Executer.a()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    
    JP7
    0
  • Chris George
    Hi JP,

    Thanks for that information, and it's interesting it happened with 3.9 too.

    I'll pass on that information to our developers and we'll try to resolve it for the next release.

    In the meantime, we may have to contact you again to get more information, would this be ok?

    Thankyou for your continuing interest in SQL Prompt 4.0, and I hope to hear more feedback from you soon!

    Regards
    Chris
    Chris George
    0
  • JP7
    Hi Chris

    You're more than welcome to contact me at any time.

    Regards

    JP
    JP7
    0
  • JP7
    Hi Chris

    FYI, I disabled SQL Prompt 4's integration with Visual Studio 2005, and it seems to work fine in SQL Enterprise Manager now. Not sure if that's of any help to you...
    JP7
    0
  • tanya
    Hi JP,

    I will add this information to our bug report. Thank you for taking the time to post your finding.

    Regards,
    Tanya
    Project Manager
    Red Gate Software Ltd
    tanya
    0

Add comment

Please sign in to leave a comment.