Comments
Sort by recent activity
I'm sorry that you're experiencing this issue. I've logged this in our bug tracking software and the developers will look into this. In the mean time I think you maybe able to workaround this issue by turning off the Parameter Prompt functionality. From the looks of things the exception is being thrown by the Parameter prompt function and you can disable this by going to SQL Prompt > Options > Behaviour > Information Panels > untick 'Enable parameter hints' / comments
I'm sorry that you're experiencing this issue. I've logged this in our bug tracking software and the developers will look into this. In the mean time I think you maybe able to workaround this issue...
The developers have created a patch that they hope will resolve this issue. You can email support@red-gate.com to request the patch and see if it fixes the problem. / comments
The developers have created a patch that they hope will resolve this issue. You can email support@red-gate.com to request the patch and see if it fixes the problem.
Thank you for the feedback. I was able to reproduce this bug and have raised it in our bug tracking software. / comments
Thank you for the feedback. I was able to reproduce this bug and have raised it in our bug tracking software.
It would be good if you could send us the schema (using packager) and any reproducible details so that we can try and recreate this in house. If you're able to do this could you send the information to support@red-gate.com? Once we receive the information we'll raise a support call for you and look into it. / comments
It would be good if you could send us the schema (using packager) and any reproducible details so that we can try and recreate this in house. If you're able to do this could you send the informatio...
I can't seem reproduce this issue. Could you give me an example where you are always able to reproduce this.
I've tried, for example, writing various statements with strings and I can't produce this issue e.g.
SELECT * FROM [dbo].[test] WHERE [words] LIKE 'select type join
This doesn't uppercase any of the keywords. / comments
I can't seem reproduce this issue. Could you give me an example where you are always able to reproduce this.
I've tried, for example, writing various statements with strings and I can't produce thi...
Thank you for your feedback. I've logged this as a bug and we will look to try to get a fix in for this as soon as possible. / comments
Thank you for your feedback. I've logged this as a bug and we will look to try to get a fix in for this as soon as possible.
SQL Prompt caches the databases in two different ways. It will cache the database's schema and store them on disk. This is shown in the list - 'Databases that SQL Prompt has cached'. SQL Prompt will cache as many databases, this way, as it can. They will be held on disk until you highlight the databases in the cache management window and choose to delete them.
SQL Prompt also stores a certain number of database information in memory. This is controlled by the 'Minimum number of databases to hold in memory' setting. This increases performance, for example, when running cross-database queries.
When you say that SQL Prompt holds all the databases in cache, do you mean that it keeps them all on disk? If this is the case then, I'm afraid, you'll have to manually manage the databases that it stores by deleting the one's that you don't need. / comments
SQL Prompt caches the databases in two different ways. It will cache the database's schema and store them on disk. This is shown in the list - 'Databases that SQL Prompt has cached'. SQL Prompt wil...
How are your tables set to reference each other? If you've set foreign keys then these should be picked up and the joins suggested.
If you don't have your tables set up in this way then have you tried setting the option 'Listed Candidates' > 'Join Conditions' > 'Data Types'
This will bring up join conditions based on data type. As long as your id fields share the same data type then the join you want should be selected. / comments
How are your tables set to reference each other? If you've set foreign keys then these should be picked up and the joins suggested.
If you don't have your tables set up in this way then have you tr...
At the moment SQL Prompt won't work exactly as you want in your environment. It will only pick up foreign keys, exact column name matches and matching data types. But I'll add your request as a feature request and depending on how difficult it is to implement and how much call there is for this specific Join type, hopefully the developers will consider implementing this in a future release. / comments
At the moment SQL Prompt won't work exactly as you want in your environment. It will only pick up foreign keys, exact column name matches and matching data types. But I'll add your request as a fea...
Unfortunately, the ERASEFILES_REMOTE parameter is, as you say, global. In the sense that you can only specify one instance and it will affect all of the COPYTO locations. I'll add a feature request for you requesting a way of specifying multiple ERASEFILES_REMOTE parameters.
I'm fairly sure that there isn't a limit to the amount of COPYTOs that you can use. We have customers who use multiple destinations and I've never heard of anyone reaching a 'limit'. / comments
Unfortunately, the ERASEFILES_REMOTE parameter is, as you say, global. In the sense that you can only specify one instance and it will affect all of the COPYTO locations. I'll add a feature request...