Settings and activity
20 results found
-
86 votesChris Luttrell supported this idea ·
-
73 votes
An error occurred while saving the comment -
47 votesChris Luttrell supported this idea ·
-
36 votesChris Luttrell supported this idea ·
-
530 votes
Thanks for this suggestion and for the many comments and upvotes. I realize that this is a pain point.
I have a few shorter-term workarounds to summarize as well as some information on the longer roadmap in this update. I know these shorter-term workarounds aren’t perfect (I summarize the pros and cons), but I’m posting them as they may help a few folks.
Workaround 1) When data changes to static data need to be made, use a “relink the table” pattern
One can “cleanly rescript” a static data table in SQL Source Control by:- Unlinking the static data table
- Committing
- Relinking the static data table
- Committing
Pro: This works with the GUI and requires no special knowledge or comfort with TSQL. This may help folks with just a few static data tables.
Con: This requires extra steps and results in extra commits in the history, which I realize can…Chris Luttrell supported this idea · -
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…
Chris Luttrell supported this idea · -
153 votesChris Luttrell supported this idea ·
-
72 votesChris Luttrell supported this idea ·
-
105 votesThomas Walsh responded
Thank you for your suggestion.
We’ve reviewed this as part of our UserVoice triage.
Due to a lack of recent interest in this request, we are no longer actively reviewing it and have removed it’s “Under Review” status.
If you feel strongly about having this feature added to Prompt, please continue to vote for and comment on this request.
Kind Regards,
The Prompt TeamChris Luttrell supported this idea · -
345 votesChris Luttrell supported this idea ·
-
103 votesChris Luttrell supported this idea ·
-
103 votesChris Luttrell supported this idea ·
-
89 votesChris Luttrell supported this idea ·
-
46 votesChris Luttrell supported this idea ·
-
215 votesChris Luttrell supported this idea ·
-
78 votesChris Luttrell supported this idea ·
-
212 votesChris Luttrell supported this idea ·
-
193 votesChris Luttrell supported this idea ·
-
58 votes
We’re going to be reviewing this over the next couple of months, which would be released via the SQL Prompt for Teams EAP (get in touch if you want to know more).
In the meantime please add any other information that you think would be useful.
Chris Luttrell supported this idea · -
18 votesChris Luttrell supported this idea ·
There is already an "Add regular expression support" request which predates this one and has more votes, shouldn't these 2 request be combined along with their votes?