User profile for Chris Auckland

Thanks for your post. I think this issues to more to do with getting used to the way SQL Prompt works, and how it tries to help you write the SQL Code with fewer keystrokes. When you get the the WHERE part of the clause, SQL Prompt already knows which table you are referencing, so there is not need to qualify the table name with the alias first. After you type WHERE<space> you will be prompted with the correct columns for the table. On completion it will insert the selected column e.g. WHERE id You can configure SQL Prompt to automatically qualify the column name on completion so that when you choose id from the list it will be inserted as c.id by enabling the option: SQL Prompt > Options > Inserted Candidates > Formatting > Qualify Column Name I hope this helps explain the situation. Let me know if you need more information. / comments

Thanks for your post. I think this issues to more to do with getting used to the way SQL Prompt works, and how it tries to help you write the SQL Code with fewer keystrokes. When you get the the WH...

0 votes

Thanks for your suggestion. It sounds like a good feature to include in a future version. I have logged the feature request as SDOC-762. Once it has been reviewed by the developers I will be able to give you a better idea if/when it will be included in the tool. I hope this will suffice for now. / comments

Thanks for your suggestion. It sounds like a good feature to include in a future version. I have logged the feature request as SDOC-762. Once it has been reviewed by the developers I will be able t...

0 votes

Thanks for your post. If you need to get hold of a copy of SQL Bundle 5, you can download it directly from our ftp site here: ftp://ftp.red-gate.com/old/SQL/SQLBundle530.exe Let me know if you have any problems. / comments

Thanks for your post. If you need to get hold of a copy of SQL Bundle 5, you can download it directly from our ftp site here:ftp://ftp.red-gate.com/old/SQL/SQLBundle530.exe Let me know if you have ...

0 votes

Thanks for your post. There is no way to set SQL Prompt to ignore certain keywords that you type, but GO should be recognised as a reserved keyword and suggested in the list of candidates. This means that you can simply type GO<space> to carry on with the rest of your coding. Are you saying that SQL Prompt trying to insert GOTO whenever you type GO<space>? / comments

Thanks for your post. There is no way to set SQL Prompt to ignore certain keywords that you type, but GO should be recognised as a reserved keyword and suggested in the list of candidates. This mea...

0 votes

Thanks for your post. You should be able to achieve what you need to do by using the command line interface to SQL Data Compare. This feature is only available with the Pro release. Here is some information on the command line functionality: http://help.red-gate.com/help/SQLDataCo ... dLine.html I hope it is useful. Let me know if you need any more information. / comments

Thanks for your post. You should be able to achieve what you need to do by using the command line interface to SQL Data Compare. This feature is only available with the Pro release. Here is some in...

0 votes

Thanks for your post. If it is a bit of SQL you don't know, then I have to admit that I don't know it either. Does this happen consistently and on every database? The only way I have managed to recreate the issue is if I create a function in my database called 'update', then type something like select dbo.update What is the SQL you are typing that is causing UPDATE to be followed by parenthesis? If you restart SQL Prompt, does the problem still occur? Are you using SQL Prompt 3.6? / comments

Thanks for your post. If it is a bit of SQL you don't know, then I have to admit that I don't know it either. Does this happen consistently and on every database? The only way I have managed to rec...

0 votes

Thanks for your post. SQL Prompt will always try and get you to type fully qualified column names in a query. This is why the top suggestions are likely to be tables/views. If you select the table then you should next get prompted for the column name. Alternatively you could skip past the default suggested candidates list and go straight to the columns list by selecting the columns tab on the pop-up (ctrl+right-right). I hope this is helpful. / comments

Thanks for your post. SQL Prompt will always try and get you to type fully qualified column names in a query. This is why the top suggestions are likely to be tables/views. If you select the table ...

0 votes

Thanks for your post. This issue is actually something that the devlopment team are aware of and have scheduled to be fixed in a future release. For your reference the bug was logged as SP-738. Thanks for taking the time to report this. / comments

Thanks for your post. This issue is actually something that the devlopment team are aware of and have scheduled to be fixed in a future release. For your reference the bug was logged as SP-738. Tha...

0 votes

Thanks for your post. Unfortunately you have encountered a known bug with SQL Prompt. The development team are ware of this issue, and it has been logged in their development database as SP-784. I have associated your support ticket number with the bug, so we will be able to update you when the status changes. The actual fix version has not yet been assigned because the fault is still under review. I'm afraid the only suggestion I can make at this point is to run SSMS with the normal user account. I have found that if you do not choose to remove the ad-in when SSMS starts, then it will not affect SQL Prompt when logging in with the other user. Thanks for taking the time to report this. / comments

Thanks for your post. Unfortunately you have encountered a known bug with SQL Prompt. The development team are ware of this issue, and it has been logged in their development database as SP-784. I ...

0 votes

Thanks for your post. Can you confirm the version of SQL prompt you are currently running? I recreated the issue you reported about the candidate list not appearing after the <> without manually pressing ctrl-space or leaving a space. I have logged this in our development database as SP-783. Thanks for letting us know. However, in the version I tested, the correct candidates were always populated in the list when I pressed ctrl-space. Do you have any other examples that might demonstrate the fault? / comments

Thanks for your post. Can you confirm the version of SQL prompt you are currently running? I recreated the issue you reported about the candidate list not appearing after the <> without manually pr...

0 votes

How can we help you today?

Chris Auckland

Comments