Settings and activity
5 results found
-
300 votes
SQL Prompt for Azure Data Studio is now in public preview!
The aim of this public preview is to learn from the ADS community about how SQL Prompt can enhance your developer experience, adding improvements and new features based on your feedback.
With SQL Prompt, you can use an extensive collection of code snippets to write your SQL code quickly and efficiently. You can also keep your code consistent using the powerful formatting capability, with the ability to customise the applied style to suit your preferences.
We’d love to hear your feedback. You can get in touch with the team either via the new SQL Prompt in ADS forum: https://forum.red-gate.com/categories/sql-prompt-in-ads or email us at sqlprompt.in.ads@red-gate.com.
Get started with SQL Prompt for Azure Data Studio now. Download it here: https://download.red-gate.com/EAP/SQLPromptADS.zip
Sean supported this idea ·
-
22 votes
An error occurred while saving the comment -
32 votes
-
225 votes
We've had a few requests for supporting MERGE statements - https://redgate.uservoice.com/redirect/suggestions/3100622. Would MERGE help this or are you still looking for IF EXISTS on INSERTS? If you'd like to chat about this, please reply.
-
480 votes
Thank you everyone for your comments and votes on this over the years. While I don’t have a 100% full resolution for this suggestion, I can sum up our current recommendations here. Continued feedback is very welcome.
Our current recommendation is to use the post-deployment script feature of SQL Source Control (released in V6.3) to manage SQL Server Agent jobs.
An example script for this is here: https://documentation.red-gate.com/soc/common-tasks/working-with-pre-post-deployment-scripts/create-sql-server-agent-job
As some commenters in this thread have alluded to, it is possible (and sometimes very common) for SQL Agent jobs to have steps that touch multiple databases on a single SQL Server Instance. For this reason, some customers prefer to create a separate database for instance-level management and objects (sometimes named DBA or similar) and choose to manage things like linked servers and SQL Agent jobs with the post-script associated with that database.
This separate-database architecture also makes sense if the jobs…
Consider a stored procedure that has:
Exec Systemx.dbo.QueueEmail @Subject N'Failed to import from source'
Searching "Failed to import from source" with Match whole words only will fail to find the sproc in question, because it considers "N'" to be part of the whole word.