Comments
Sort by recent activity
Anonymous wrote:
Using the version 6.0.0.441 and I have to say it is a major disappointment in performance. I'm on line 385 of a script file and significant lag is experienced when typing.
Script is made up of creation of 2 temp tables and 5 large queries that insert into real and temp tables.
I also experience similar slow performance on scripts that had a number of table valued UDF's involved.
When I get done with a production priority I can do more testing, but right now I think the team has some serious work ahead of them. I have to question the test sets redgate works with. They are obviously woefully insufficient.
p.s. that was from me... I was logged in but it didn't stick I guess. / comments
Anonymous wrote:
Using the version 6.0.0.441 and I have to say it is a major disappointment in performance. I'm on line 385 of a script file and significant lag is experienced when typing.
Scri...
Aaron Law wrote:
I've just uploaded 6.1.0.42 which includes the work I was doing with offloading the the prompt work to a thread, this should hopefully remove all of the lag you're seeing in ssms.
I will try this version when I am not having to use my system and can reinstall. Partial searching is on though I can test with it off. / comments
Aaron Law wrote:
I've just uploaded 6.1.0.42 which includes the work I was doing with offloading the the prompt work to a thread, this should hopefully remove all of the lag you're seeing in ssm...
Sounds similar to the issues documented in this thread with no comment from Red-gate. http://www.red-gate.com/MessageBoard/vi ... highlight= / comments
Sounds similar to the issues documented in this thread with no comment from Red-gate.http://www.red-gate.com/MessageBoard/vi ... highlight=
To clarify, this issue can be readily demonstrated in SQL Prompt 5.3.6.28.
Open Query window in SSMS 11.0.2100.60
Type
CREATE TABLE #Table1 (mykey INT, yourkey INT, thekey int)
CREATE TABLE #table2 (mykey INT, yourkey INT, nokey int)
Type
SELECT *
FROM #Table as T
JOIN
Now pretend you know these tables and you know how they appear in the list. As soon as you type JOIN and press the space bar, SQL Prompt will draw a selection box. As soon as you see it pop, you press the down arrow twice to select the second item from the list (#table2) and then tab to select it.
You see the highlight first highlight the first row and you expect it to highlight the 2nd row so you press tab shortly after pressing the down arrow the second time. But what happens is that a tab is entered in the screen, and the SQL Prompt selection box re-draws itself to the right slightly and you can see the selection leave the 1st row, never making it to the 2nd row.
Now if you plod along and go slow, this issue is not exposed. But if you go rapidly, it occurs.
Note this is a behavior change from previous versions (don't know when it changed) as I know that for a long time I was having no issues, and then one day I started having issues. Most often it occurs on the join condition, since you get used to the join you want is always the second one it suggests. It's almost like it is not seeing the 2nd down arrow keypress before it gets the tab or it's missing the 1st down arrow keypress and only acting on the 2nd. / comments
To clarify, this issue can be readily demonstrated in SQL Prompt 5.3.6.28.
Open Query window in SSMS 11.0.2100.60
Type
CREATE TABLE #Table1 (mykey INT, yourkey INT, thekey int)
CREATE TABLE #table2...
Paul Stephenson wrote:
There are some possibilities around avoiding too many repeat parses, but no easy solution has so far presented itself, I'm afraid. The parsing code is very complex, but we hope to be able to make some improvements in a future release without breaking any other behaviour.
Note, that in my original posting, my issue is that SQL Prompt never returned and hung the SSMS session that it was processing. I can understand things being slow, but the app shouldn't hang the UI. Note in VS2010, there was no hang, only a long delay. Thus that is what indicated to me an unexpected behavior, i.e. bug. / comments
Paul Stephenson wrote:
There are some possibilities around avoiding too many repeat parses, but no easy solution has so far presented itself, I'm afraid. The parsing code is very complex, but w...
*** Note ***
The issue below is now resolved in my environment using the August update of 5.1.8.2.
If you have a number of temp tables in a procedure and you experience hanging, I suggest updating to the 5.1.8.2 version.
Mikeh wrote:
Still manage to hang SSMS easily using SQL Prompt.
Config.
Windows 7 64bit.
SQL Server Management Studio 2008 32bit.
SQL Prompt 5.1.4.11, Professional Edition
Edit Stored Procedure with 1124 lines.
Stored Procedure works with Numerous Temporary Tables and one CTE.
Steps to duplicate.
Reboot computer. Start up SSMS with SQL Prompt Enabled. Connect to Database. find proc in object list and click modify. Press page down 8 times, to move towards the middle of the proc. Screen hangs about line 473. SSMS becomes unresponsive. Unable to open SQL Prompt 5 menu to disable SQL Prompt. Sometimes I can. If there is another window open in a tab, sometimes I can click on the tab. If the focus shifts to that tab, SSMS becomes responsive again. I can then disable SQL Prompt and then go back to the original tab. If I go back to the original tab without having disabled sql prompt, then it acts locked up again.
/ comments
*** Note ***
The issue below is now resolved in my environment using the August update of 5.1.8.2.
If you have a number of temp tables in a procedure and you experience hanging, I suggest updating ...
Still manage to hang SSMS easily using SQL Prompt.
Config.
Windows 7 64bit.
SQL Server Management Studio 2008 32bit.
SQL Prompt 5.1.4.11, Professional Edition
Edit Stored Procedure with 1124 lines.
Stored Procedure works with Numerous Temporary Tables and one CTE.
Steps to duplicate.
Reboot computer. Start up SSMS with SQL Prompt Enabled. Connect to Database. find proc in object list and click modify. Press page down 8 times, to move towards the middle of the proc. Screen hangs about line 473. SSMS becomes unresponsive. Unable to open SQL Prompt 5 menu to disable SQL Prompt. Sometimes I can. If there is another window open in a tab, sometimes I can click on the tab. If the focus shifts to that tab, SSMS becomes responsive again. I can then disable SQL Prompt and then go back to the original tab. If I go back to the original tab without having disabled sql prompt, then it acts locked up again.
Note, I don't normally use Visual Studio to edit procedures, but I gave it a shot and could also lock visual studio trying to page throught the same procedure. the main difference is that it seems Visual Studio 2010 Recovers after a few moments of sitting there. SSMS does not recover. / comments
Still manage to hang SSMS easily using SQL Prompt.
Config.
Windows 7 64bit.
SQL Server Management Studio 2008 32bit.
SQL Prompt 5.1.4.11, Professional Edition
Edit Stored Procedure with 1124 lines....