Settings and activity
17 results found
-
4 votes
Daniel White
supported this idea
·
-
42 votes
An error occurred while saving the comment Daniel White
supported this idea
·
-
12 votesDaniel White
supported this idea
·
-
8 votes
An error occurred while saving the comment Daniel White
commented
This might help, even if it isn't a change in SQL Prompt's behavior:
ALTER VIEW [Helpers].[ObjectReferences]
AS
SELECT DISTINCT s.schema_id referencing_schema_id ,
s.name referencing_schema_name ,
o.object_id referencing_object_id ,
o.name referencing_object_name ,
o.type_desc referencing_object_type ,
re.referenced_server_name ,
re.referenced_database_name ,
re.referenced_schema_name ,
re.referenced_entity_name ,
re.referenced_id ,
re.referenced_class ,
re.referenced_class_desc ,
re.is_caller_dependent ,
re.is_ambiguous ,
re.is_selected ,re.is_updated -- this is the important line
FROM sys.schemas s
JOIN sys.objects o
ON o.schema_id = s.schema_id
LEFT JOIN sys.extended_properties ep
ON ep.class = 1
AND ep.major_id = o.object_id
AND ep.name = 'microsoft_database_tools_support'
CROSS APPLY sys.dm_sql_referenced_entities(s.name + '.' + o.name , 'object') re
WHERE ep.value IS NULL;
GO -
7 votesDaniel White
supported this idea
·
-
7 votes
An error occurred while saving the comment Daniel White
commented
I personally would like the settings to be the same for the "commit changes" and "get latest" tabs, and it would be awesome if SQL Source Control remembered them so I don't have to change them every time I start SSMS.
Daniel White
supported this idea
·
-
131 votesDaniel White
supported this idea
·
-
3 votesDaniel White
supported this idea
·
-
28 votesDaniel White
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…Daniel White
supported this idea
·
-
11 votesDaniel White
supported this idea
·
An error occurred while saving the comment Daniel White
commented
I assume you're talking about SQL Data Compare; this doesn't make much sense if you're talking about SQL Source Control. I have the same problem; I want to start SQL Data Compare, pick my databases, and have some way to automatically check just the tables that are configured as static data in SQL Source Control.
-
5 votesDaniel White
supported this idea
·
-
16 votes
An error occurred while saving the comment Daniel White
commented
or format SQL in all views in the database, or all procedures in the database, or all functions in the database, or all views in a schema, or all procedures in a schema, or all functions in a schema...
Daniel White
supported this idea
·
-
89 votes
An error occurred while saving the comment Daniel White
commented
This is a general problem not confined to just indexes. For another example, if two stored procedures are the same except for spacing and the placement of the line breaks, the differences pane highlights much code that is not actually different.
Daniel White
supported this idea
·
-
32 votes
An error occurred while saving the comment Daniel White
commented
This seems like a bad idea to me. A primary goal of these tools is to preserve data.
-
35 votesDaniel White
supported this idea
·
-
8 votesDaniel White
shared this idea
·
Oh! Do you know what would be REALLY awesome? If you could dock the Summarize Script Window, navigate around in it, and the code selected in Summarize Script is selected in the query window -- AND -- expanding or collapsing nodes in the Summarize Script tree makes them expanded or collapsed in the query window. Now THAT would be awesome.