Comments
Sort by recent activity
OK thanks. So it sounds like you have a more general problem than that just the column picker isn't working. What happens when you connect to the database? Do you get any meta-data retrieval errors? And do you have dbo access or the VIEW DEFINITION permission (SQL Server 2005 only) on the database to which you're connecting?
Thanks,
Bart / comments
OK thanks. So it sounds like you have a more general problem than that just the column picker isn't working. What happens when you connect to the database? Do you get any meta-data retrieval errors...
Hi there,
You'll need to do something like this:
SELECT ^ FROM SomeTable
(^ represents the caret position)
If you hit CTRL+SPACE to bring up the completion list you should find that the column picker can be reached by pressing CTRL+LEFT. You can then select multiple columns using UP, and DOWN arrows, and SPACE to select/unselect (you can also use the mouse).
Thanks,
Bart / comments
Hi there,
You'll need to do something like this:
SELECT ^ FROM SomeTable
(^ represents the caret position)
If you hit CTRL+SPACE to bring up the completion list you should find that the column pick...
Could you post the contents of your script please? Also, do you get a list of tables after the FROM in your suggested candidates list? Could you also let me know what editor you're using and which version of SQL Prompt (go to SQL Prompt > About).
Thanks,
Bart / comments
Could you post the contents of your script please? Also, do you get a list of tables after the FROM in your suggested candidates list? Could you also let me know what editor you're using and which ...
Thanks Brian, it's much appreciated. I know how frustrating it can be when software starts misbehaving.
The only thing I can think of at the moment is that there might be some sort of race condition that means the system objects are not being fully populated before the meta-data loading and completion list population is finalised. We use a different population method on SQL Server 2000 to 2005 and above because the only way we can get the system objects on SQL Server 2000 is to actually load the meta-data for the master database. For 2005 and above we don't have to do this because it's exposed in every database.
It's a while since I wrote the code, but I suspect the reason unchecking and checking the option works is that when you check it again all the system objects will have been fully loaded, so when the completion lists are repopulated (unchecking and checking this option would force this, as long as you close the Options dialog in between) the INFORMATION_SCHEMA objects appear correctly.
For now unfortunately I can only say we'll try to get this fixed in the next release (I'm pretty sure it would still happen in 3.7, although if you fancy giving it a try there's no reason not to).
Thanks,
Bart / comments
Thanks Brian, it's much appreciated. I know how frustrating it can be when software starts misbehaving.
The only thing I can think of at the moment is that there might be some sort of race conditio...
Another thing I just thought of, only because it's just caught me out on SQL Server 2000, is that you might not have system object display enabled (it's off by default).
You can find this option in SQL Prompt > Options > Listed Candidates > Candidate Types and Filters. Under the "Candidate types" heading, ensure that "System objects" is checked.
I should add that obviously INFORMATION_SCHEMA should only appear if this *is* checked, however it could be that the bug is that some, at least, of the INFORMATION_SCHEMA objects appear when it isn't under some circumstances.
Thanks,
Bart / comments
Another thing I just thought of, only because it's just caught me out on SQL Server 2000, is that you might not have system object display enabled (it's off by default).
You can find this option in...
OK thanks, glad to hear that at least. I just wanted to be sure with that last post.
This bug is in our tracking system so hopefully it should be fixed at some point in the future.
Thanks,
Bart / comments
OK thanks, glad to hear that at least. I just wanted to be sure with that last post.
This bug is in our tracking system so hopefully it should be fixed at some point in the future.
Thanks,
Bart
Hi Brian,
It sounds like it might still have been retrieving the meta-data for the database (including system tables, views etc) when you were first typing. If you want to filter by INFORMATION_SCHEMA you should make sure that "Filter candidate list by owner/schema prefix" is checked, otherwise you'll see other database objects that don't belong to INFORMATION_SCHEMA after the dot.
Thanks,
Bart / comments
Hi Brian,
It sounds like it might still have been retrieving the meta-data for the database (including system tables, views etc) when you were first typing. If you want to filter by INFORMATION_SCH...
OK thanks, sounds like a bug to me then. I'd still recommend keeping that option checked.
Thanks,
Bart / comments
OK thanks, sounds like a bug to me then. I'd still recommend keeping that option checked.
Thanks,
Bart
Yeah, that is a bit strange. Glad it's working at any rate! Thanks for letting us know.
Bart / comments
Yeah, that is a bit strange. Glad it's working at any rate! Thanks for letting us know.
Bart
Hi there,
I'm not sure what's going on here. I've asked one of my colleagues to confirm whether or not the version of the SQL Compare back end that we use in SQL Prompt 3.6 supports compatibility mode 7 on SQL Server 2005 or not. As soon as I have an answer I'll get back to you.
Thanks,
Bart / comments
Hi there,
I'm not sure what's going on here. I've asked one of my colleagues to confirm whether or not the version of the SQL Compare back end that we use in SQL Prompt 3.6 supports compatibility m...