Comments
Sort by recent activity
The very latest version suddenly is back to comparing much, much faster than a previous version. Very odd. Closing issue. / comments
The very latest version suddenly is back to comparing much, much faster than a previous version. Very odd. Closing issue.
Harry,
I can confirm that the version you posted fixes the problem.
Thank you,
John
harryf wrote:
Hi jsreynolds
Sorry you're having this issue. I think this version of SQL Prompt (http://download.red-gate.com/EAP/SQLPro ... .0.205.exe) should fix the problem.
Please let me know if that works for you.
Many thanks
Harry
/ comments
Harry,
I can confirm that the version you posted fixes the problem.
Thank you,
John
harryf wrote:
Hi jsreynolds
Sorry you're having this issue. I think this version of SQL Prompt (http://download....
Thank you for letting me know. Downloading now.
Best,
John / comments
Thank you for letting me know. Downloading now.
Best,
John
Aaron,
I can confirm that the formatting problem seems to be fixed, thank you!
I'm using the beta for its extended formatting functionality. One of the big hits has been semi-colons on the next line, which makes editing existing statements so much easier.
Thank you for the continued great product and quick responses.
Best,
John / comments
Aaron,
I can confirm that the formatting problem seems to be fixed, thank you!
I'm using the beta for its extended formatting functionality. One of the big hits has been semi-colons on the next lin...
Aaron,
It's on the way via email.
Note I just found I can't edit the newer styles any longer too - throws an error as well.
--J / comments
Aaron,
It's on the way via email.
Note I just found I can't edit the newer styles any longer too - throws an error as well.
--J
version 7.2.0.241 WAIT ON THIS - I MAY BE WRONG. I will come back and edit or delete based on more findings.
Beginning of a stored procedure (nothing odd in the creation part), I get this. [image] SET NOCOUNT ON;
DECLARE @ErrorMessage NVARCHAR(2048);
-- Let's just get this awkwardness out of the way up front;
-- Is there (still) a product for the store available, or did
-- someone else on the front end rip it out from under the
-- current user?
IF NOT EXISTS ( SELECT *
FROM [Products]
WHERE [Products].[ProductID] = @ProductID )
BEGIN
SET @ErrorMessage = 'Product no longer exists.';
;
THROW 60000, @ErrorMessage, 1;
END;
But the Products table has ProductID as a column. Many squiggly red lines below this one too. Here is the start of the procedure just in case you need that. Note that everything runs fine in the proc, there are no syntax errors anywhere. SET ANSI_NULLS ON;
GO
SET QUOTED_IDENTIFIER ON;
GO
ALTER PROCEDURE [dbo].[fe_UpdateOnInventory]
@StoreNum CHAR(3),
@ProductID INTEGER,
@ProductName NVARCHAR(4000),
@PDSID INT,
@Status BIT
AS /*
/ comments
version 7.2.0.241WAIT ON THIS - I MAY BE WRONG. I will come back and edit or delete based on more findings.
Beginning of a stored procedure (nothing odd in the creation part), I get this. SET NO...
I have a good log I would like to send to someone and not post here. Any takers? / comments
I have a good log I would like to send to someone and not post here. Any takers?
Aaron,
I thought I'd try the latest beta first, and sure enough it did fix the issue with linked servers.
Also, the wavy lines under the THROW statement are gone. Things seem to be back to normal.
Thanks much,
John / comments
Aaron,
I thought I'd try the latest beta first, and sure enough it did fix the issue with linked servers.
Also, the wavy lines under the THROW statement are gone. Things seem to be back to normal.
...
Hello,
This release seems to have issues with linked servers it didn't have before. None of my linked servers seem to get intellisense and failures pop up whenever it attempts.
Also, this: -- Ensure valid store number
IF NOT EXISTS ( SELECT [tblStores].[StoreNum]
FROM [Corpmaster]..[tblStores]
WHERE [tblStores].[StoreNum] = @StoreNum )
BEGIN
THROW 60000, N'Invalid store number passed.', 1;
END;
The "THROW" statement is red wavy underlined, and the "END;" semi-colon is underlined red. After I reformat SQL it goes away, then re-appears a few seconds later.
Image: http://imgur.com/9houGbj / comments
Hello,
This release seems to have issues with linked servers it didn't have before. None of my linked servers seem to get intellisense and failures pop up whenever it attempts.
Also, this: -- Ensur...