User profile for PDinCA

Running 1.3.0.13... The "ridiculous monster" 163K query now successfully shows up in the Query Fragment, vs. GDI+ Exception, plus no failures on paging through over 200 entries in the Log Running Query dropdown, so a HUGE "Thank You" as the tool appears reliable again... BTW, thanks for the "Bonus" - amused for a few minutes... but work beckoned [image] / comments

Running 1.3.0.13... The "ridiculous monster" 163K query now successfully shows up in the Query Fragment, vs. GDI+ Exception, plus no failures on paging through over 200 entries in the Log Running Q...

0 votes

From Matthew: I have some more info on why the exception occurs which may help you skirt around it. It was caused by trying to display a SQL Query with a line consisting of 150,000 or more characters. I'm not sure if you know what query that is and can avoid clicking the trace info on it? Response: Well, the offending query is a ridiculous one built by "standard" Community Server .Net code but it's because the way we're using the Product is "outside the norms it was designed for", so, in effect, it's a self-inflicted wound... And it's lights-out when it runs... Apparently CS2009 addresses the way we want to use the Product... It's hard to not click the incident because there's no Database indication until I've clicked it... No worries, though, I know it happens, so I know I'll have to "recover" sometimes. / comments

From Matthew: I have some more info on why the exception occurs which may help you skirt around it. It was caused by trying to display a SQL Query with a line consisting of 150,000 or more characte...

0 votes

Could you "up" the importance of getting a fix for this, please? I just clicked on a "Blocked Process" alert, received the GDI+ Exception, and EVERY Program on my machine DIED - including Explorer.EXE (memory could not be read). So I'm dead in the water and spending some "quality time" responding to every Windows "XXX has terminated unexpectedly" dialog, and all subsequent issues... Thanks :shock: / comments

Could you "up" the importance of getting a fix for this, please? I just clicked on a "Blocked Process" alert, received the GDI+ Exception, and EVERY Program on my machine DIED - including Explorer...

0 votes

I, too, experience the strange repaint behavior with 1.2, which definitely wasn't there in 1.1 or 1.0. When using "next" to navigate through the occurrences of a certain Alert, the whole lower portion paints and shifts stuff around before it shows the detail section I asked for. It seems like it shows the collapsed sections while it's building, then realizes they are collapsed, so it hides them... Haven't had the loss of cursor/highlight, but can't say I paid attention to that as I was hovered over the "next" button the whole time. The mouse cursor didn't change position during the repaint strangeness. / comments

I, too, experience the strange repaint behavior with 1.2, which definitely wasn't there in 1.1 or 1.0. When using "next" to navigate through the occurrences of a certain Alert, the whole lower por...

0 votes

Why would one have to deal with a STANDARD key-combo? Surely RG should use a DISTINCT combo, not already assigned to an SSMS function...? / comments

Why would one have to deal with a STANDARD key-combo? Surely RG should use a DISTINCT combo, not already assigned to an SSMS function...?

0 votes

SSMS 18.2 / comments

SSMS 18.2

0 votes

Fixed - yes. Key combo does multiple things... Ctrl+Shift+E in SSMS 18.3.1 with SQP 9.5.21.11921: I do see the correct Code Analysis box... AND SSMS kindly gives me the "Resource View" pop-out... (bonus feature?) Oops? / comments

Fixed - yes. Key combo does multiple things...Ctrl+Shift+E in SSMS 18.3.1 with SQP 9.5.21.11921: I do see the correct Code Analysis box... AND SSMS kindly gives me the "Resource View" pop-out... (...

0 votes

I was referring to the highlighted lines in the lower pane - the scripts themselves. When I see that the upper list is denoting a "difference", the script pane is supposed to tell me what that is. If I'm crossing SQL Server versions, it would be good to be able to suppress cross-version "differences" so I can see the "real" differences, if there are any... By presenting STATISTICS and Extended Properties as two examples, I'd hoped to show that there are no "real" differences as far as the objects are concerned - the "differences" that SQL Compare is showing me in these cases will be automatically handled by the synchronization script so. I hope I'm among many who would regard these "differences" as "informative noise". My request in these cases would be to be able to suppress this kind of "noise" so we can see the "real" differences, as in, the wording is different in the extended property, or a column has no CREATE STATISTICS. Implementation differences across versions that generate SQL Compare differences mask and muddy the task we are trying to complete, if you get my drift. In the database that prompted this part of the original post, I had over 40 tables shown as "different" merely because SQL Server 2008 implements STATISTICS differently from 2000 - care I not! And the fact that extended properties are now implemented as SCHEMA not USER - again, care I not! It just happened that the STATISTICS differences overlapped the Extended Properties differences, and both were shown highligted in the script pane - I guess that addresses your "sematic differences" point. Other Stuff: I did clean up the registry at David Atkinson's suggestion as the Beta uninstall failed. I'll see if Alice's suggestion works out, for which I thank her. Thanks, I found the SQL "button" command - an option to show it on the script bar would be user-friendly [image] Thanks for the explanation of the "Line Differences" feature - that makes sense now. / comments

I was referring to the highlighted lines in the lower pane - the scripts themselves. When I see that the upper list is denoting a "difference", the script pane is supposed to tell me what that is....

0 votes

Thanks, Andras, I was unaware of the SS2000 issue and will turn off the ANSI NULL option in Compare. Thankfully we should be off 2000 inside 2 months [image] / comments

Thanks, Andras, I was unaware of the SS2000 issue and will turn off the ANSI NULL option in Compare. Thankfully we should be off 2000 inside 2 months

0 votes

SQL Compare 6 has never been installed on this, new, box. Do you need it to be? SSMS now generates scripts in the intensely annoying form of a text string, rather than how we code them normally - thanks MS (idiots!). However, I'll PM you the file for the first UDF differenced, along with my actual file. There's no ANSI_NULLS statement in the generated script from SSMS. UDF is very much a multistatement table-value function. / comments

SQL Compare 6 has never been installed on this, new, box. Do you need it to be? SSMS now generates scripts in the intensely annoying form of a text string, rather than how we code them normally - ...

0 votes

How can we help you today?

PDinCA

Comments