Comments
Sort by recent activity
Thanks for all your help with this - it's now fixed in the latest beta. / comments
Thanks for all your help with this - it's now fixed in the latest beta.
Hi Jim
Glad to hear you're using the export feature already. You're right, the SQL datetimes are getting exported into Excel as strings.
It is possible to format these cells in bulk without having to click inside each one:
1. In Excel, set that column's data type to "Date" (highlight, right click > Format Cells... > select Date in the Category list).
2. With these cells still highlighted, go to DATA (in the ribbon) > Text to Columns > Finish.
Configuring your preferred date time format and then exporting to Excel as that data type is a reasonably large piece of work. If you'd like to see this functionality in SQL Prompt then please submit a UserVoice request here. This will help us gauge interest and prioritise the work.
Thanks
Ali / comments
Hi Jim
Glad to hear you're using the export feature already. You're right, the SQL datetimes are getting exported into Excel as strings.
It is possible to format these cells in bulk without having ...
Hi Jim
I spent a few hours looking into exporting datetimes directly into Excel. Unfortunately, Excel only has separate date and time column types with no native analogue of a SQL datetime object. Setting a column's type to a string or number is very simple, creating a custom cell format to display a datetime is more complex, especially when programmatically generating the Excel file from code.
If you create a UserVoice request for this alongside your original request, we will look at this again if it a lot of people are having the same problem.
Thanks
Ali / comments
Hi Jim
I spent a few hours looking into exporting datetimes directly into Excel. Unfortunately, Excel only has separate date and time column types with no native analogue of a SQL datetime object. ...
Hi
Thanks for your suggestion. We currently have a Uservoice forum for feature requests which is the best place to post this idea. It’ll allow other users that are interested to vote on it and helps us prioritise which feature to work on next (and you’ll get notified of any progress on it).
I had a quick search and there are a couple of related ideas that you might be interested in: https://redgate.uservoice.com/forums/94 ... ening-file https://redgate.uservoice.com/forums/94 ... y-of-files
Thanks
Ali / comments
Hi
Thanks for your suggestion. We currently have a Uservoice forum for feature requests which is the best place to post this idea. It’ll allow other users that are interested to vote on it and he...
We’ve just released a new version (v7.2.2) which fixes this issue. If you’ve still got the original (and incorrect) ‘curff’ snippet then it will be updated to the corrected snippet. If you’ve already modified the ‘curff’ snippet in any way then it will not overwrite your changes. New installations of SQL Prompt will use the corrected snippet.
You can get the latest build by using Check for Updates or by downloading it from here.
Thanks
Ali / comments
We’ve just released a new version (v7.2.2) which fixes this issue. If you’ve still got the original (and incorrect) ‘curff’ snippet then it will be updated to the corrected snippet. If youâ...
Hi
Thanks for letting us know this is still an issue. We made the fix when the issue was first reported but this change was overwritten during the subsequent overhaul of the snippets manager. We’ll fix the default snippet again and it’ll be in the next release.
Thanks
Ali / comments
Hi
Thanks for letting us know this is still an issue. We made the fix when the issue was first reported but this change was overwritten during the subsequent overhaul of the snippets manager. We’...
Hi Jim
Thanks for posting. You’re absolutely right and moving the $CURSOR$ placeholder as you suggested will fix the issue. We’ll make this change to the default 'curff' snippet in the product for future releases.
Thanks
Ali / comments
Hi Jim
Thanks for posting. You’re absolutely right and moving the $CURSOR$ placeholder as you suggested will fix the issue. We’ll make this change to the default 'curff' snippet in the product ...
Hi
You can attempt to free up some memory by clearing out SQL Prompt’s cache. To do this, uncheck Enable Suggestions in the SQL Prompt menu (or pressing Ctrl+Shift+P) then enable them again using the same option (or pressing Ctrl+Shift+P again).
SSMS’s native Intellisense also uses a fair bit of memory. You could try disabling it completely by going to Tools > Options > Text Editor > Transact-SQL and unchecking the Enable Intellisense checkbox.
Tab history does store its data to disk so that should not be affecting memory usage. However, if you have a lot of tabs open at once, closing some of them should also free up some memory.
Thanks
Ali / comments
Hi
You can attempt to free up some memory by clearing out SQL Prompt’s cache. To do this, uncheck Enable Suggestions in the SQL Prompt menu (or pressing Ctrl+Shift+P) then enable them again using...
Hi Tim
Unfortunately there is no setting to increase the amount of memory available to SQL Prompt. The problem is that SSMS is a 32 bit process and as SQL Prompt is an add-in for SSMS, SQL Prompt must share its memory space with SSMS.
You might be able to improve this behaviour by uninstalling any other add-ins you have for SSMS.
You can also manage which databases SQL Prompt connects to, more details here: https://documentation.red-gate.com/display/SP7/Managing+connections+and+memory
By excluding connections to the large database (or excluding connections to other databases if you still want suggestions for the large database), you’ll free up some memory.
We do have some plans to work around these memory constraints in future, but this work won’t be started for a while.
Thanks
Alasdair / comments
Hi Tim
Unfortunately there is no setting to increase the amount of memory available to SQL Prompt. The problem is that SSMS is a 32 bit process and as SQL Prompt is an add-in for SSMS, SQL Prompt m...
Hi
You can stop snippets being suggested by replacing the default snippets folder with an empty folder.
To do this, inside SSMS or VS go to SQL Prompt > Snippet Manager then change the path of the snippets folder to any empty folder (I just created a new folder at the same level as the default 'Snippets' folder, called 'NoSnippets' and used that).
Thanks
Ali / comments
Hi
You can stop snippets being suggested by replacing the default snippets folder with an empty folder.
To do this, inside SSMS or VS go to SQL Prompt > Snippet Manager then change the path of the ...