Activity overview
Latest activity by ikatsu
Is there any update on this issue or is there anything that we can do to help you track it down? / comments
Is there any update on this issue or is there anything that we can do to help you track it down?
Dave Pendleton wrote:
They do show up -- sometimes; and when they do, they only suggest user-defined functions or nothing at all.
If I recall, sp_help works with more than just udf's.
Ah so the nature of the issue is that after you type sp_help the suggestion list is restricted to only showing functions instead of stored procedures, tables, and other supported objects. I have the same issue as you. It would seem that SqlPrompt is purposfully limiting itself in this case since most procedures do not allow for passing of procedure names as parameters.
I would say that this would probably end up being a custom set of circumstances for items like sp_help, sp_helptext, sp_helpindex etc that would show specific object based on the stored procedure name instead of just a generic "Stored Procedure" acceptable list.
Would be a nice enhancement request if you ask me. / comments
Dave Pendleton wrote:
They do show up -- sometimes; and when they do, they only suggest user-defined functions or nothing at all.
If I recall, sp_help works with more than just udf's.
Ah so th...
This works on my system just fine. You may need to go into SQL Prompt options on the Listed Candidates tab, Candidate Types and Filters, then check the Show: System Objects option in order to get them to show up.
Hope this helps / comments
This works on my system just fine. You may need to go into SQL Prompt options on the Listed Candidates tab, Candidate Types and Filters, then check the Show: System Objects option in order to get t...
We now have 3 developers in our office that have reported this crash bug and they are all exhibiting the same issues reported in the first post. This is putting a slight crimp on using your tool in our development environment and is leading to some frustration as you have to constantly enable and disable sql prompt in order to use the tools we use for our normal work flow.
We do have a work around of using SSMS to work with the SQL files but the moment we go back into Visual Studio to check the files into TFS we will usually end up running into the crash bug and it is impacting our performance when using your tool. Some of our developers are disabling your tool until this bug is corrected due to the inconvenience that it is creating.
Please let me know if there is anything I can do to help you track down this issue so we can get this up and running properly. / comments
We now have 3 developers in our office that have reported this crash bug and they are all exhibiting the same issues reported in the first post. This is putting a slight crimp on using your tool in...
I have found similar errors that went into a never ending loop and found a work around. If you open a new developer environment (SSMS, VS, etc...) and then disable Sql Prompt from the menu it will stop looping and giving you errors (at least it did for me). / comments
I have found similar errors that went into a never ending loop and found a work around. If you open a new developer environment (SSMS, VS, etc...) and then disable Sql Prompt from the menu it will ...
We also have another developer at our location that is running into the same crash bug on his machine with SQL Prompt enabled. As soon as he disabled SQL Prompt he was able to open the SQL file associated with his database project.
We have also tried:
Deleting the database project off the system and re-retrieving it from TFS (Still crashes)
Deleting all cached database schemas from SQL Prompt (Still crashes).
Please let me know if there is any more information I can provide or any trouble shooting steps you would like me to attempt. / comments
We also have another developer at our location that is running into the same crash bug on his machine with SQL Prompt enabled. As soon as he disabled SQL Prompt he was able to open the SQL file ass...
VS 2k5 Team Edition Crash.
I am running SQL Prompt Version 3.6.0.109.
After applying all of the most recent hotfixes from Microsoft for Visual Studio 2k5 Team Edition for Software Developers (8.0.50727.762 (SP.050727-7600)) ...
JIT Crash in SSMS query window when using splitter.
Steps to reproduce:
Open SQL Server Management Studio.
Connect to a database server with a query window.
Grab the splitter and drag it down to show two portions of the same sql file (note you do no...
Accelerator hotkey conflict with VS 2k5 Team Edition
The SQL Prompt menu hot key, ALT-S, conflicts with the Test menu item in Visual Studio 2005 Team Edition for Software Developers.
The available hotkeys available in SQL Prompt would be: Q, L, R, O,...
# temp tables not showing up.
I have a few scripts that use # temp tables in order to hold intermediat data as it is massaged into the final form. I imagine that this is possibly caused by the #temp tables existing in tempdb ...