Comments
5 comments
-
Hi,
if it's not doing views I'm afraid that is a bug. Could you tell me a bit more about your sytem (OS, editor, language settings, framework, sql server etc.)?
Regards,
Tilman -
Hello,
I am connecting to a SQL 200 SP4 server on Windows 2000 Server, with SQL Management Studio (2005), from an Windows XP SP2 fully patched client machine. The client machine has both .NET frameworks 1.1 and 2.0 installed.
The language settings are English on server (both Windows and SQL Service), with French (Switzerland) locale. On the client machine, the base install is English with MUI (French, German and Italian); English is the language used (for menus, etc). The regional settings on the client machine are French (Switzerland) locale, with English default for non-Unicode apps.
I hope it helps,
and thank you for this wonderful tool ;-)
With kind regards,
Emmanuel -
Hi Emmanuel,
I'm afraid I haven't got a clue what could be causing this. Version 3 will be a complete rewrite, so hopefully your problem will go away, then.
Regards,
Tilman -
Hi,
a further information: the views are essentially used for cross-database referencing, and they are written as
select * from myOtherDatabase.dbo.myInterestingTable
I haven't tried with a view referencing explicitly the columns (instead of using the * joker) though ...
With kind regards,
Emmanuel -
Sorry, I still can't get the problem. I.e. when i go 'SELECT * FROM ' I get the view in the candidate list, and when i then go 'SELECT ^ FROM View' and press Ctrl + Space i get the columns of the view.
Do you clear the cache after creating the view? SQL Prompt 2 doesn't automatically recognize when a new object has been added. But I take it those views were around before you started using SQL Prompt 2.
Regards,
Tilman
Add comment
Please sign in to leave a comment.
this is a great tool, that can potentially save quite a lot of time and effort! I say potentially, because in my current project, I work quite a lot with views (select from myView), and alas there is no intellisense for views! IMHO this feature could be very easily added (including an option: retrieve metadata from views)!
Another gotcha I found: sometimes (more often that I would like), SQL Prompt would just stop working and intellisensing. I haven't noticed anything special to reproduce this behaviour though.