Comments
Sort by recent activity
Yep OK, I couldn't recall that from last month (I should have set a reminder in outlook) but a message box or a red x over the systray SQL Prompt icon on it wouldn't hurt. It was strange to see it continue to work in one Query Window but not another. I had to coax the exception before I knew that it had expired.
emails4me. / comments
Yep OK, I couldn't recall that from last month (I should have set a reminder in outlook) but a message box or a red x over the systray SQL Prompt icon on it wouldn't hurt. It was strange to see it ...
Same here !!
I had one Query Analyzer window open from last week and I was getting intellisense, I had opened another connected to different server database and it wasn't working. After invoking Query analyser via Enterprise Manager I finally got the exception about the expiry.
It would have been good to know via a warning a couple of days ago or a post here that it was going to expire or what the plans (if any) were going to be thereafter.
emails4me / comments
Same here !!
I had one Query Analyzer window open from last week and I was getting intellisense, I had opened another connected to different server database and it wasn't working. After invoking Qu...
I too would like to see the option available via the systray icon, instead of integrating a menu in Query Analyzer and SSMS.
Most Tray apps/utilities follow this convention. Given that there are issues with the menu removal in SSMS (see another post on this) this would be another reason to stick to the systray menu.
I often find myself right clicking on the systray icon only to find the exit option and then recalling that SQL Prompt 3 works via a menu.
emails4me / comments
I too would like to see the option available via the systray icon, instead of integrating a menu in Query Analyzer and SSMS.
Most Tray apps/utilities follow this convention. Given that there are is...
Prefer the Pop-Up: same reasons as sangha.
emails4me / comments
Prefer the Pop-Up: same reasons as sangha.
emails4me
ditto..same as sangha. / comments
ditto..same as sangha.
Got it working again without a reboot.
Selected a different database in Enterprise Manager, opened up Query Analyzer and then switched to the database I wanted. All was well again.
emails4me / comments
Got it working again without a reboot.
Selected a different database in Enterprise Manager, opened up Query Analyzer and then switched to the database I wanted. All was well again.
emails4me
Yep, second that.
I kinda like the way it works with Query Analyzer : it only appears when I invoke it. In Management studio, I often find I'm hitting the esc key to get it out of the way when I know what I want to type.
emails4me / comments
Yep, second that.
I kinda like the way it works with Query Analyzer : it only appears when I invoke it. In Management studio, I often find I'm hitting the esc key to get it out of the way when I kn...
Completely Remove SQL Prompt and restarted the PC before installing SQL Prompt 3
I had 2 separate instance of Query Analyzer and 1 instance on MS SQL Server Management Studio at the time.
HTH
emails4me / comments
Completely Remove SQL Prompt and restarted the PC before installing SQL Prompt 3
I had 2 separate instance of Query Analyzer and 1 instance on MS SQL Server Management Studio at the time.
HTH
email...
Yes, I definitely used the enter/ tab key at the time. Will try increasing the auotpopup delay as suggested and see if that helps.
emails4me / comments
Yes, I definitely used the enter/ tab key at the time. Will try increasing the auotpopup delay as suggested and see if that helps.
emails4me
Was using MS SQL Server Management Studio at the time.
Sorry can't provide the schema for the database, but the SQL script is displayed correctly in Query Analyzer and incorrectly in MS SQL Server Management Studio
It appears that SQL Prompt functions a bit differently between the two editors. / comments
Was using MS SQL Server Management Studio at the time.
Sorry can't provide the schema for the database, but the SQL script is displayed correctly in Query Analyzer and incorrectly in MS SQL Server ...