Settings and activity
13 results found
-
5 votes
An error occurred while saving the comment 
Dan W
supported this idea
·
-
19 votesDan W
supported this idea
·
-
6 votes
An error occurred while saving the comment Dan W
commented
DIY manual work-around without all the fancy automatic actions:
-- /*
code to use or hide
-- */Remove the -- before /* to hide the section; Re-add -- before /* to enable the section. Leave "-- */" as-is because it's always valid
-
6 votesDan W
supported this idea
·
-
4 votesDan W
supported this idea
·
-
6 votesDan W
supported this idea
·
-
3 votesDan W
supported this idea
·
-
1 voteDan W
shared this idea
·
-
13 votes
An error occurred while saving the comment Dan W
commented
I think this is a great idea! That would add so much freedom to let SQL Source Control do it's thing while I go about my work!
Dan W
supported this idea
·
-
24 votesDan W
supported this idea
·
-
5 votes
An error occurred while saving the comment Dan W
commented
I have an implementation option to recommend. In keeping with the rest of the error handling, simply put the IF @@ERROR <> 0 SET NOEXEC ON after the USE [my_database] statement in the synchronization script, such as:
USE [my_database]
GO
IF @@ERROR <> 0 SET NOEXEC ON
GOThis doesn't protect against scripts from being run against the right database on the wrong server, but it at least it prevents scripts from being applied if the change to the expected target database fails.
Dan W
supported this idea
·
-
14 votesDan W
supported this idea
·
-
9 votesDan W
supported this idea
·
It sounds like this would also make it easier to deal with our elevated user situation where I need to run SSMS as an elevated user account for any database updates, but it's difficult to keep Excel activated for that elevated user account (that gets used for Excel when selecting the "Open in Excel" option. If the "Open in Excel" feature allowed a copy-paste option, it would be easier to bridge that gap and still benefit from the wonderful Excel formatting that SQL Prompt does.