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

Activity overview

Latest activity by JP7

SQL Server Management Studio slow startup times
Hi Since installing SQL Prompt 5.0.1.7 I've been experiencing extremely slow startup times of SSMS 2008 R2 and VS2010. I noticed that two entries get recorded in the logs: 07 Mar 2011 06:48:55,313 ...
3 followers 3 comments 0 votes
Add-in fails to load
Hi I'm using: SQL Prompt 4.0.2.27 Professional Edition. WindowsXP SP3 SQL 2005 VS2005 & 2008 ESET Smart Security 4.0.437.0 I've been having problems with the SQL Prompt's integration on SSMS for SQ...
3 followers 9 comments 0 votes
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... / comments
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...
0 votes
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() / comments
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 unnecessar...
0 votes
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 / comments
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
0 votes