How can we help you today? How can we help you today?
Matthew.Wilkerson
Activity overview Badges (0) Posts (14) Comments (17)

Comments

Sort by recent activity
FYI - This is still not fixed in the Version 3.6 Early Access Release. / comments
  1. Community
  2. SQL Prompt Previous Versions
  3. Built-in data types case setting not honored for char
FYI - This is still not fixed in the Version 3.6 Early Access Release.
0 votes
The same thing occurred for me. I couldn't just update SQL Prompt through the menu item to Check for Updates, but had to download the new version, uninstall, and then reinstall. I had been using the final beta refresh. It still says that I am using SQL Prompt version 3.0.3.0 (for both the Current and Latest Version) in the Check for Updates form. The about box says that I am using 3.0.0.868 currently. / comments
  1. Community
  2. SQL Prompt Previous Versions
  3. Check for updates not working
The same thing occurred for me. I couldn't just update SQL Prompt through the menu item to Check for Updates, but had to download the new version, uninstall, and then reinstall. I had been using ...
0 votes
thalter wrote: it no longer autocompletes in Visual Studio or the SSMS. thalter, Can you verify that installing Visual Studio SP1 breaks SQL Prompt for SSMS? We have not installed VS SP1 yet, and may hold off if this is the case until Red-Gate fixes the problem. Thanks. / comments
  1. Community
  2. SQL Prompt 3
  3. VS2005 SP1 Kills SQL Prompt
thalter wrote: it no longer autocompletes in Visual Studio or the SSMS. thalter, Can you verify that installing Visual Studio SP1 breaks SQL Prompt for SSMS? We have not installed VS SP1 yet,...
0 votes
Thanks for responding so quickly. I followed up to a couple of your replies below. V2 did not require data types (such as int, varchar, etc.) to be uppercased when keywords are. It would be nice to have the option not to, since the standards here require that the data types be lower case, but the keywords be in upper case. An intellisense box doesn't seem to make sense after a DECLARE statement Could you explain a bit more what is happening and what you would expect? (We have already fixed a bug where it didn't show data types.) One example of my statement regarding data types is when I type "declare @x int", V2 changed it to "DECLARE @x int", but V3 changes it to "DECLARE @x INT". In regards to the DECLARE statement, when I type "DECLARE ", I am getting an intellisense box, when it doesn't seem like I should be. I may be spacing out, but isn't the only thing allowed after a DECLARE keyword a new variable, cursor, etc. name? With autocomplete for the single quote turned on, sometimes after typing a single quote it would get into an endless loop adding quotes, and I would have to kill the process to get control back (MSSMS locks up). For example, typing "DECLARE @x char(3); SET @x = '" would become "DECLARE @x char(3); SET @x = '''''''''''''''''''''''''''''''''''''''''''''''''...", and would not stop adding single quotes. This does not happen all the time, and I haven't figured out what is causing it exactly. I have learned to save often, and turn off the single quote option if it happens more than twice on a given script I am editing. Come to think of it, it seems to happen when I have the window split in MSSMS. Please let us know if you can reproduce this reliably. We thought we had it fixed. The way to reproduce this is to open up a new window in MSSMS, split the window in two using the splitter, then type the following: "declare @x char(1);set @x = '". Doing that will cause the error every time. The split window seems to the cause of it. / comments
  1. Community
  2. SQL Prompt 3
  3. Current Observations/Problems/Quirks
Thanks for responding so quickly. I followed up to a couple of your replies below. V2 did not require data types (such as int, varchar, etc.) to be uppercased when keywords are. It would be ni...
0 votes
MikeGuerrieri wrote: Our development team does the vast majority of their SQL development with Visual Studio 2003 and SQL Prompt 2 works with this product. All of our SQL scripts are in database projects and checked into source control. Using Visual Studio allows our developers to use 1 IDE to both edit our scripts and manage them in source control. If this helps any, you can use database projects in SQL Management Studio (which works with versions 2 and 3) to edit scripts and manage them in source control. MikeGuerrieri wrote: Since we have not yet migrated to SQL Server 2005 this means that the only tool in our shop that is supported by SQL Prompt will be Query Analyzer which is used in our shop mainly for ad-hoc queries and analysis. You can use the SQL Management Studio IDE with SQL 2000 databases without migrating to SQL 2005 yet as well. That's what we are doing until we migrate to SQL 2005. In doing so we will be able to continue to use SQL Prompt, version 2 or 3. / comments
  1. Community
  2. SQL Prompt 2
  3. SQL Prompt 3 and Visual Studio Team 4 Database Professionals
MikeGuerrieri wrote: Our development team does the vast majority of their SQL development with Visual Studio 2003 and SQL Prompt 2 works with this product. All of our SQL scripts are in database...
0 votes
I finally got the company to upgrade me from SSMS Express to SSMS, but when I reinstalled SQL Prompt 3, I learned that it had expired [image] . Is there a reason why the beta cut off so quickly after only two weeks (especially since it was delayed in being released in the first place)? / comments
  1. Community
  2. SQL Prompt 3 Beta
  3. Beta expired
I finally got the company to upgrade me from SSMS Express to SSMS, but when I reinstalled SQL Prompt 3, I learned that it had expired . Is there a reason why the beta cut off so quickly after on...
0 votes
It appears that this does not work with the Express version of Microsoft Management Studio. Is there a reason why? / comments
  1. Community
  2. SQL Refactor Beta
  3. SQL Refactor CTP Released
It appears that this does not work with the Express version of Microsoft Management Studio. Is there a reason why?
0 votes
The file is located here for me (using Windows XP Pro), if that helps: C:\Documents and Settings\%Current User%\Local Settings\Application Data\Red Gate\SQL Prompt 5. / comments
  1. Community
  2. SQL Prompt Previous Versions
  3. Variables aren't suggested after x number of lines
The file is located here for me (using Windows XP Pro), if that helps: C:\Documents and Settings\%Current User%\Local Settings\Application Data\Red Gate\SQL Prompt 5.
0 votes
Yes, it would be nice if it were fixed. / comments
  1. Community
  2. SQL Prompt Previous Versions
  3. Feature request: show your support for XML functions.
Yes, it would be nice if it were fixed.
0 votes
It would be a huge help if SQL Prompt did this. This seems to be a big oversight, as many of our SQL queries do not just join to the previous table. Prompt SQL had provided this functionality. Thank you. / comments
  1. Community
  2. SQL Prompt Previous Versions
  3. JOIN condition limited to immediate previous table
It would be a huge help if SQL Prompt did this. This seems to be a big oversight, as many of our SQL queries do not just join to the previous table. Prompt SQL had provided this functionality. T...
0 votes
Total activity
47
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
16