Comments
Sort by recent activity
I'd love to switch back - V4 is a step backwards. However, like an idiot I deleted my previous installs - I didn't expect V4 to be this level of a re-write. I with they would put 3.9 up for download. / comments
I'd love to switch back - V4 is a step backwards. However, like an idiot I deleted my previous installs - I didn't expect V4 to be this level of a re-write. I with they would put 3.9 up for dow...
This is a pretty big issue guys - I thought SQL Compare was hanging. I recommend you make this issue more prominent in the UI - even showing a popup when first accessing a 2005/2008 DB with a new install.
I am working over a VPN so it was even worse. We have no encrypted objects so this was really slowing me down - and in the case of a large DB I just assumed something else was wrong and it was hanging until I found this. / comments
This is a pretty big issue guys - I thought SQL Compare was hanging. I recommend you make this issue more prominent in the UI - even showing a popup when first accessing a 2005/2008 DB with a new...
Oops - I need to learn to search better - thanks! / comments
Oops - I need to learn to search better - thanks!
Thanks David - I had no idea that was there. / comments
Thanks David - I had no idea that was there.
Yes the v3.9 installer would help immensely.
Thank you,
Nick / comments
Yes the v3.9 installer would help immensely.
Thank you,
Nick
Ok guys, this product cost far too much for the basics to still be non-functioning. The level of frustration I am dealing with EVERYDAY is starting to get to me.
Please post the latest 3.x version for download - I need a version that works. (NOLOCK) pretty much rendering it inoperative is making sql prompt useless for me. 90% of our stored procesdures use nolock. This is a serious problem for me. I am very dependent on SQL Prompt - I'm a contractor and I regularly work with large databases with what amounts to random fieldnames. So EVERYDAY I get more and more angry as SQL Prompt fails to work. This isn't something I use once a week - it's something I use all day long.
I apologize for the tone of this post but I really feel like I am beta testing an application at this point and I didn't sign up for that. I want to revert to 3.x until this thing is working.
As it stands, I feel like we all deserve an extension on our support. For me, it's nearly unusable with the current bugs. If it weren't part of the package I purchased, I'd be returning it for a refund. THAT is how frustrated I am at this point.
This post is a product of the last two days of SQL Prompt 4 constantly failing due to the fact I am debugging stored procedures that contain NOLOCK. 4 is certainly faster than 3 - but that speed doesn't help when it constantly fails to function.
Regards,
Nick Hustak / comments
Ok guys, this product cost far too much for the basics to still be non-functioning. The level of frustration I am dealing with EVERYDAY is starting to get to me.
Please post the latest 3.x versio...
I have gone back into the procs and reset them. Unfortunately (?), it works though I do have to manually invoke.
For what it's worth, I do always hit manual invoke when nothing pops up and that usually works (I also am very quick to rebuild the cache via hotkey). If I'm having problems, it will show a list of internal function calls. From my memory, what is intersting is it shows none of the variables. I say that because the first time it happened, I immediately went into the options to change the 'look behind' distance to all - except that option has been removed in 4.0. I assume it's look at all code now always.
The next time this happens, I will be sure to manually invoke per your request and gather information.
Regards,
Nick / comments
I have gone back into the procs and reset them. Unfortunately (?), it works though I do have to manually invoke.
For what it's worth, I do always hit manual invoke when nothing pops up and that us...
First off, please put the release numbers in the posts about new versions.
Second - version 4.0.2.53 - it is still erratically picking up declared variables. ALTER proc [dbo].[Matcher_PostBuildingKeyAndScore]
@Matcher_Output_pk INT = null,
@Building_fk INT = NULL,
@BuildingMatchScore INT = NULL,
@BuildingPass VARCHAR(5)
as
set nocount on;
if @Matcher_Output_pk is not null
UPDATE
dbo.Matcher_Output
SET
Building_fk = @Building_fk,
BuildingMatchScore = @BuildingMatchScore,
BuildingPass = @BuildingPass
WHERE
Matcher_Output_pk = @Matcher_Output_pk
@BuildingPass did not pick up when I typed it.
I hit refresh cache and suddenly it picked it up. I duplicated this in another window and nothing makes it work.
Here's the other proc - I have refreshed the cache, backed up and retyped the @ several times. Nothing. ALTER proc [dbo].[Matcher_PostBusinessKeyAndScore]
@Matcher_Output_pk int = null,
@Business_fk INT = NULL,
@BusinessMatchScore INT = NULL,
@BusinessPass VARCHAR(5)
as
set nocount on;
if @Matcher_Output_pk is not null
UPDATE
dbo.Matcher_Output
SET
Business_fk = @Business_fk,
BusinessMatchScore = @BusinessMatchScore,
BusinessPass = @
WHERE
Matcher_Output_pk = @Matcher_Output_pk
return(@@rowcount)
Is it possible to get the install for version 3.x? I really feel llike 4.x was released too early - some of the core functionality isn't working correctly. I like where it's headed, but I'd rather wait until the bugs are ironed out. / comments
First off, please put the release numbers in the posts about new versions.
Second - version 4.0.2.53 - it is still erratically picking up declared variables.ALTER proc [dbo].[Matcher_Po...
Extremly disappointed this was not fixed in latest release. This is causing me all kinds of problems as we use NOLOCK on a consistent basis and the databases I work with have a huge number of tables and fields. One of the MAJOR things it helps me with is my joins - which of course is broken with a (NOLOCK).
I have really come to rely on this product so you can imagine the impact of not having this work. / comments
Extremly disappointed this was not fixed in latest release. This is causing me all kinds of problems as we use NOLOCK on a consistent basis and the databases I work with have a huge number of tabl...
After some fooling around with the latest version I have found the intellisense to be much less 'intelligent'. I mean that it requires the preceding code to be 100% complete or it suggest nothing.
It wasn't this way before. Here's an example I ran into that convinced me of it. I regularly do the return type last. My lack of a return definition is keeping it from deducing the declare statement. CREATE FUNCTION dbo.fn_get_active_game_guid
(
@user_guid UNIQUEIDENTIFIER
)
RETURNS <Function_Data_Type, ,int> <---- the lack of a definition here prevents the code below from popping the intellisense
AS
BEGIN
DECLARE @instance_guid <--- I'm right here trying to get 'UNIQUEIDENTIFIER' from intellisense.
{some valid sql code}
END
/ comments
After some fooling around with the latest version I have found the intellisense to be much less 'intelligent'. I mean that it requires the preceding code to be 100% complete or it suggest nothing...