586 results found
-
SourceControl occupies gigabtyes of old files
Today, my Windows C: device was 99% full. During the search of the biggest files (which were the Windows/assembly/ folder) I noticed gigabytes of SQL Source Control files! Back to Source Control Version 3.x and 4.x even though we already updated to 5.x. Source Control does not clean up old files.
Directories I found old Source Control files:
C:\Windows\Downloaded Installations\
C:\ProgrammData\Downloaded Installations\
C:\Users...\AppData\Local\Red Gate\Please provide a function do uninstall all those old files that occupy even gigabytes of disk space storage. Thank you!
16 votes -
Allow selection of which SSMS instances to install SQL Source Control
Given the size of our databases, SQL Source Control is VERY slow, frequently locking up SSMS for a minute or more.
As a result I'd like to (say) use SSMS 2014 for SQL Source Control, leaving SSMS 2017 free to work with.
Could we please have the option of choosing which SSMS instances to install it against?
1 vote -
Option to use modification date as the commit date
With SQL, when you modify an object, that object is now out there to be used or tweaked by other developers. Committing it is really just a statement of, I'm done working with this object and here's what I've done.
We have the problem of not committing objects as timely as we should. We make a modification and go our way until we realize a week later, we forgot to commit. So we commit, but the date time stamp of the commit is not helpful. That is just when the developer remembered.
I think it would be much, much more…
11 votes -
Keeping history of locked and unlocked objects
Locking feature doesn't keep history of who has locked or unlocked specific objects in database. This could become useful when a person unlocks an object locked not by him/her and would help to track historical changes.
It would require very few changes - additional history table,
[SQLSourceControl].[LockObject] and [SQLSourceControl].[UnlockObject] procedures would have to be modified.
Possibly an additional view to see that data in SQL Source Control instead of selecting raw tables.
19 votes -
Newly added objects no longer have a blue ball beside it in the object explorer unless I do a refresh from the SQL Source Control tab.
Connecting to a Subversion repository SQL Source Control used to refresh the Object Explorer and show newly added items at the bottom of the list with a blue ball next to it. Since the last version update, I have to manually refresh the Object Explorer to get the newly added item to show up and there is no blue ball next to it unless open SQL Source Control and hit refresh there.
2 votes -
Ability push database linking of database to team members
When using a shared database development model having a location which allows you see which developers have linked to the database. Also having the ability to be able to push out the linking to the database to developers from a central point
8 votes -
Find revision number of deployed database
It would be very useful if it was possible to see which revision number was last deployed to a database. Source Control 4 used to update the extended properties after deployment but version 5 no longer does this.
Not knowing the revision number makes it difficult to bring a Live db up to the same revision as a UAT db, and ensuring the required migration scripts also get executed on the Live db.
Any change this could be added somewhere? Extended properties seemed a good place to save it.
9 votes -
Separate triggers from tables
Please give option for DML trigger changes be tracked separately from tables. It's very annoying trying to support and enhance a trigger-heavy inherited database that needs an extensive trigger optimizations. It doesn't allow me to isolate and rollback my changes very easily ... and branching and integrating - ha! This was almost a big enough deal to send me to ApexSQL... alas, I am regretting my decision these days. It seems people have been requesting this feature in Source Control and Compare for a while... please stop pushing it aside - it's frustrating. Thanks
77 votes -
Cannot create migration script for selected changes in the newest version
Using the latest verrsion I cannot create a migration script for selected changes (checkins in the versioning control system).
The menu option it had in the database context menu is missing.
Why did you remove this feature?
It was nice for allowing migrating environments that you cannot connect to.30 votes -
If I exclude items from source control they should not default to be committed due to dependencies.
If I exclude items from source control they should not default to be committed due to dependencies. It would be great if there was a setting when items are excluded to never include them in the list of items that are dependencies.
13 votes -
Source control slow down
SQL Source control is slowing down my entire SSMS. This wasn't always the case, but now trying to get a context menu to show up on a table can take up to 30 seconds. Please fix!
29 votes -
make multiple git commits without a refresh in between (until after push)
When committing multiple changes with GIT it takes several extra minutes, because it has to recheck for changes between each commit.
I have a large database and sometimes 10 or more commits to make in a row.
It would speed up a lot if it did not have to refresh in between each commit.
39 votes -
git commit and push together
Add the option to push to a remote at the same time as a commit (maybe a checkbox next to the commit button - similar to sourcetree).
This would be easier than having to navigate back to the "commit changes" screen and push using the error prompt.
89 votes -
Locking/unlocking functionality
Get rid of the option for anybody to unlock an object, but instead allow to unlock only by the person that locked the object or by a group in group role in the database where only few people have access.
8 votes -
Include Ad Hoc Scripts in SQL Source Control
Whether server configuration, replication scripts, SQL agent Jobs, Powershell, or just test scripts, give me a folder in VCS that I can store and retrieve scripts from. Even if this is to/from a specific folder on my machine, make this an easy process to keep development code with my database.
82 votes -
Fix Extended Properties difference highlighting
I use extended properties on all of my columns and tables. When I check in a table initially, these transfer fine.
If I edit the table and add a new column somewhere in the middle (i.e., anything other than the last ordinal position) and give that column an extended property, SQL Source Control correctly identifies the new column. However, down in the bottom pane when it compares the database version with the source control version, it incorrectly flags each and every extended property in an ordinal position after my new column as having changed.
Can this be modified so that…
6 votes -
Support Database Projects Referenced as Same Database in SSDT
Currently, when comparing an SSDT project using SQL Compare, it only loads the base project. If the project references another project as the same database (the standard workaround to the circular reference problem), the objects in the referenced project will not be compared. This can lead to changes being missed and deployments failing.
It would be nice if SQL Compare could follow the reference back and include the objects from the referenced database in the compare as well.
14 votes -
Allow a pre and post scrip to run on SQL Data Compare
Sometimes I need to write scripts to run before and after a SQL Data Compare.
13 votes -
Performance: Use all available cores when "registering database"
The performance of the get and commit tabs is still very poor. AFTER querying the structure and content from the sql-server, which of course uses all cores to answer the query, only one core is used for the further comparison by SQL source control (shown as "registering database"). This step takes the longest amount of time, so optimizing SOC to use all cores for that operation should speed up the whole thing. Our developers have machines with 8 cores, so this is a huge waste of available ressources and time and thus money.
71 votes -
Embed Coments
You should consider adding tokens like the following:
--%version --%
--%modifications --%When you check out the latest version of a SQL Script, Source contral would replace a token in the script with the version history from the repository.
When the script is checked it additions made in the modifications token are grabbed and included in the comments box for check-in.In addition the modification comments could be formatted a little better either by discreet fields or by a masked format.
Make the message concise and informative. I use the following format:[bug/issue number] [Area of Focus] [Action completed]
Ticket:…
1 vote
- Don't see your idea?