How can we help you today? How can we help you today?
hansjp
Activity overview Badges (0) Posts (2) Comments (5)

Activity overview

Latest activity by hansjp

Is it correct that SQL Search does not return hits on schema name?
  1. Community
  2. SQL Search
When I search for all objects across databases with the same schema, say "qi", SQL Search only returns tables, views, stored procedures, etc. when they are referenced! That is: I only realise that ...
1 follower 1 comment 0 votes
Sounds good. [image] / comments
  1. Community
  2. SQL Prompt
  3. Code Analysis Rules
Sounds good.
0 votes
True. Making me check whether I had that, and ought to disable the rule. However, I often review legacy scripts, and in these cases it is really beneficial to have such lapses flagged! Often we only realize this sloppiness in WHERE clauses and JOINs when we augment SELECTs or alter the referenced tables so unique field names cease to be unique. I like to just maintain scripts when I work on them, instead of waiting for them to fail. / comments
  1. Community
  2. SQL Prompt
  3. Code Analysis Rules
True. Making me check whether I had that, and ought to disable the rule. However, I often review legacy scripts, and in these cases it is really beneficial to have such lapses flagged! Often we onl...
0 votes
Fully agree with Torsten. And I will add: The rule "unqualified column name" makes no sense when I use alias in ORDER BY clauses. But since SSMS understands and accepts the use of aliases (instead of very long computed statements), the rule should too. Thanks, Hans / comments
  1. Community
  2. SQL Prompt
  3. Code Analysis Rules
Fully agree with Torsten. And I will add: The rule "unqualified column name" makes no sense when I use alias in ORDER BY clauses. But since SSMS understands and accepts the use of aliases (instead ...
0 votes
hansjp wrote: When I toggle the Suggestions (CTRL+Space), I see nothing but snippets. No databases, no tables, no columns, no nothing. Strangely enough, this only happens on my SQL Server 2014 instance! I have an old SQL Server 2005 instance which behaves fine... Does anybody else experience this? Is there something, I need to do, in order to get it to work on the SQL Server 2014 instance (which is my production database now... [image] )? It is funny how asking a question can set the mind in gears... I have been troubled by this for months and finally took the time to post the question here ... only to find the solution myself a few minutes later. I decide to leave the post (and display my own error) just in case somebody else do what I did: Searching the forum in vain for addressing the root cause of this. So this is what I found: 1) The behavior of SQL Prompt is ruled by the "Options" (duh!) - so go have a look there! 2) If you have modified the Suggestions > Connections like I have (in the past, due to connecting to a really large production server where I only had read permissions to views on a single database out of hundreds), and chosen the "Only load suggestions for certain databases" option under "Databases", be very careful with the spelling! Because our new instance has had a name-change along the way... a dash was removed from the name (because dashes are visually pleasing, but really annoying in SQL Server environments, triggering the need for square brackets every time the instance is referenced). And I had not changed the name in this option window... So there you go: Correct naming of the instances and databases is crucial, if you don't use the option "Load suggestions for all databases". It has nothing to do with the SQL Server version. / comments
  1. Community
  2. SQL Prompt
  3. Suggestions don't show database content
hansjp wrote: When I toggle the Suggestions (CTRL+Space), I see nothing but snippets. No databases, no tables, no columns, no nothing. Strangely enough, this only happens on my SQL Server 2014 i...
0 votes
Suggestions don't show database content
  1. Community
  2. SQL Prompt
When I toggle the Suggestions (CTRL+Space), I see nothing but snippets. No databases, no tables, no columns, no nothing. Strangely enough, this only happens on my SQL Server 2014 instance! I have a...
2 followers 2 comments 0 votes
Aaron Law wrote: We've just released a new build (Tab Magic 0.5.0.184) which will hopefully fix your second bug: http://download.red-gate.com/EAP/SQLTab ... bMagic.zip The first time it's run it will still open the tabs so if you want to start fresh you can delete "%localappdata%\Red Gate\SQL Tab Magic\documents.db". Any further runs should only open the tabs you had open. We are aware the connection coloring in SQL Prompt is still a little unstable at the moment and it's on our todo list to stop it crashing ssms. I am currently testing SQL Prompt 6 (downloaded newest version in January 2014), and the issue persists in this program! SO: Updating SQL Tab Magic might work, but the problem isn't fixed in SQL Prompt 6... The trick of deleting the file "SavedTabs.db" (which is the only .db file on the described path) DID work as announced, though [image] / comments
  1. Community
  2. SQL Prompt Previous Versions
  3. [Bugs] SQL Tab Magic / SQL Prompt 6
Aaron Law wrote: We've just released a new build (Tab Magic 0.5.0.184) which will hopefully fix your second bug:http://download.red-gate.com/EAP/SQLTab ... bMagic.zip The first time it's run it ...
0 votes
Total activity
10
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
3