Comments
Sort by recent activity
I can definitely get it to happen inside a query as well. I have this 2800 line query that is causing all sorts of strange behavior. Joins don't always work, SELECT * doesn't always expand, brackets don't always appear around CTEs, keywords are capitalized inside strings, etc. Unfortunately, getting this exact scenario setup is quite involved. Note that the problems started appearing well before it got to 2800 lines, but that's irrelevant. / comments
I can definitely get it to happen inside a query as well. I have this 2800 line query that is causing all sorts of strange behavior. Joins don't always work, SELECT * doesn't always expand, bracket...
I can't repro it with a simple query either. The query that's doing it is extremely long (over 1000 lines) and references my large database schema. It might be worthwhile for me to send you the schema (using Packager) and this query, since it illustrates many of the issues I've been posting. Let me know if this is something you want me to do (and how to go about it). / comments
I can't repro it with a simple query either. The query that's doing it is extremely long (over 1000 lines) and references my large database schema. It might be worthwhile for me to send you the sch...
I realized this morning that one difference in this install (which is crashing) is that I had cranked the "Databases to execute against simultaneously" setting up to 7 (since I have a 7-database queue normally). I turned it down to 4 and didn't get a crash this morning. I'll keep trying to see if it crashes, but I think that was the issue. Hope it helps. / comments
I realized this morning that one difference in this install (which is crashing) is that I had cranked the "Databases to execute against simultaneously" setting up to 7 (since I have a 7-database qu...
Good catch. I'm running .NET 3.5, which includes all the latest official servicing updates to the .NET stack. However, the hotfix is dated Feb 2008, which is after the 3.5 release.
It's interesting that I never saw this issue on Vista SP0, but I recently installed a fresh copy of Vista with SP1 and that's roughly when the issue started.
Well, it's pretty annoying, but I'm okay pinning the blame on Microsoft for now. No other customers are seeing this? / comments
Good catch. I'm running .NET 3.5, which includes all the latest official servicing updates to the .NET stack. However, the hotfix is dated Feb 2008, which is after the 3.5 release.
It's interesting...
SQL version: Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
There are no open transactions, and there aren't any very often as this is a pretty isolated dev box.
System objects are not included in Prompt for me.
I'm using SQL Compare 6.2.0.271.
SELECT * FROM sys.sql_modules took 18 seconds just now (this is across the Internet, so I certainly expect Prompt to take some time to refresh -- it just seems to have suddenly started to take longer). I'm guessing that since reading the modules is taking 18 seconds, that probably explains the issue. My schema must have grown to the point where I'm really noticing the slow down. That being said, the speed change really seemed to correlate to installing Prompt 3.8 RC, and my database schema really hasn't changed much recently. I'll examine server and/or network issues as the probable cause.
Thanks for the background information! / comments
SQL version: Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition (64-bit) on Windows NT 5.2 (Build 3790: Service...
Actually, I notice that my SQL Compare now also hangs on "Reading object text" for quite a while. I don't think anything changed in my database schema or network, and it definitely happened when I installed Prompt 3.8 RC. Any thoughts, or am I doing something wrong? Thanks. / comments
Actually, I notice that my SQL Compare now also hangs on "Reading object text" for quite a while. I don't think anything changed in my database schema or network, and it definitely happened when I ...
I have to say that this was also the feature that blew my mind when I installed 3.8 RC. It's awesome -- I use it all the time. I also highly enjoy the improved INSERT functionality (in particular, I love that you now don't include the primary surrogate key in the INSERT -- woohoo!)
Red Gate's SQL Toolbelt literally paid for itself within a week in recouped labor. It's not even funny how productive this stuff makes me.
--
I was wondering something (off-topic, sorry). If SQL Prompt can't quite understand my query up to this point -- maybe I've put an extra = sign in, or put the JOIN after the WHERE on accident -- currently it starts to just behave strangely. I usually notice that it's behaving badly (like not giving me intellisense that I expect) and I go back to figure out what was wrong with my query. What would be really cool is if Prompt could actually indicate to me that there's a problem with my syntax and that it can't understand me. Maybe that's problematic, but just a little red flag would help me stop wasting time and go back to fix the query so I can keep getting intellisense properly. / comments
I have to say that this was also the feature that blew my mind when I installed 3.8 RC. It's awesome -- I use it all the time. I also highly enjoy the improved INSERT functionality (in particular, ...
I strongly second the request for scroll wheel functionality in the schema window, if this is at all possible. Also - when I select text from this window and press Ctrl-C, it doesn't seem to copy. Any way around that? I realize that this window is an overlay and probably can't respond to events properly as a result -- but it'd help. / comments
I strongly second the request for scroll wheel functionality in the schema window, if this is at all possible. Also - when I select text from this window and press Ctrl-C, it doesn't seem to copy. ...
I am receiving the same problem, even after uninstalling/reinstalling. I am also using Vista. Vista contains .Net 2.0 and 3.0 built in to the operating system, and I have additionally installed 1.1. The interesting thing is, the software worked for months and months before mysteriously stopping. I can't correlate it with anything I have done to the system, either.
I am going to try 6.0 beta, and as long as the beta doesn't corrupt my databases, that will suffice for me. However, it would be worth looking into the problem. / comments
I am receiving the same problem, even after uninstalling/reinstalling. I am also using Vista. Vista contains .Net 2.0 and 3.0 built in to the operating system, and I have additionally installed 1.1...
Jonathan,
6.0 beta definitely solved the issue. My only problem now is, the beta has expired! And since 5 doesn't work, I've hit a wall. I need a working version of this product! / comments
Jonathan,
6.0 beta definitely solved the issue. My only problem now is, the beta has expired! And since 5 doesn't work, I've hit a wall. I need a working version of this product!