Settings and activity
43 results found
-
47 votes
In 2019, we launched Redgate Change Control, our migrations-based versioning tool, which has a way to Open a project that you get from version control. We’re working to merge these tools together and have 1 tool for versioning database changes. When we do this, we’re hoping to make sharing projects with others easier.
Please let me know if you have any questions about this. Thank you!
-
1 vote
An error occurred while saving the comment -
25 votes
An error occurred while saving the comment Unfortunately, there's no way to do this in SQL Source Control at the moment. If you use SQL Compare for deployment, then you could use "Table Mapping" when setting up the comparison project to map table names that differ across your environments. You could then filter out the synonyms in the deployment so that your dev synonym doesn't overwrite what your test synonym refers to. I would recommend saving projects for dev -> test and test -> prod so that you don't have to set this up each time.
-
1 vote
-
5 votes
In v2.2, which is expected to be released in the next few weeks, we’ve implemented Object Filtering, which allows you to specify which objects to inlcude/exclude for source control. Therefore, you could link a database and set up a filter so that only the tables/procedures your interested in for your project would be source controlled. Would this help?
You can get the v2.2 Release Candidate at http://www.red-gate.com/messageboard/viewtopic.php?t=13668 to try this out.An error occurred while saving the comment Hello Afroz,
Links are set up per window user per machine. So, the only way to do this currently would be if you logged in as 2 separate window users and linked the db for each user to a separate location and set up the filters for each link.
The other option is to use 2 separate machines that have SSMS. I'm not sure if you have a VM, but this would allow you to link the same database to different locations and again specify a filter for each.
I don't think either of these are ideal... I'm glad this won't be an issue with your non-legacy apps.
Another idea is to still comit all the database changes to the same repository and then do something on the repository side to just get the changes for one project or another.
Cheers!
Stephanie :-) -
4 votes
An error occurred while saving the comment Thanks for your suggestion! Good points. For now, you can use the options under the "Show" button to change the text size if needed.
-
38 votes
An error occurred while saving the comment This never worked, but is in our designs. I'll merge this suggestion with the existing suggestion and we'll keep this on our backlog.
-
15 votes
AdminRedgate Administrator
(Admin, Redgate)
shared this idea
·
-
7 votes
An error occurred while saving the comment Interesting. This sounds very similar to keywords in SVN... http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/805367-support-svn-id-keyword
-
4 votes
-
215 votesAdminRedgate Administrator
(Admin, Redgate)
shared this idea
·
-
12 votes
An error occurred while saving the comment Hi John,
Would it be possible to create a new user db and put stored procedures that are shared across teams there instead of the master? That way you could source control only the objects you cared about instead of all objects in the master db.
-
636 votes
Hi everyone. I have merged some User Voice items on this topic of “filtered” static data, as there was significant overlap. I want to share our current guidance on handling scenarios where you need to version a subset of the columns and/or rows in the table.
With SQL Source control, the best option at this point is to use a post-deployment script for this purpose.
SQL Source Control introduced pre- and post- scripts in v6.3.
A post-deployment script gives you a good amount of flexibility over exactly which rows or columns of data you want to include in your project. Example post-deployment scripts for static data are here: https://documentation.red-gate.com/soc7/common-tasks/working-with-pre-post-deployment-scripts/static-data
If you make heavy use of Static Data, we have stronger support for this in SQL Change Automation.
SQL Change Automation:
- Supports column filtered static data tables in the SCA plugin in SSMS
- Supports multiple post-deployment scripts, in case there is…
An error occurred while saving the comment I do not want to source control certain columns in my reference tables (e.g., update date/times since these are different on each server and get set by a DEFAULT).
-
4 votes
-
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…
-
189 votes
While SQL Source Control provides a way to view object history, it does require additional tooling to update your database to a specific version from history.
We currently have documentation on how this works here: https://documentation.red-gate.com/soc/common-tasks/update-to-a-revision-from-source-control
An error occurred while saving the comment Hello J.,
You're right. This is currently a feature of the SSMS Integration Pack and SQL Compare. It's something we could consider adding directly to SSC in a future release if there is enough demand.
Thanks!
An error occurred while saving the comment Workaround:
1) "Get" the tagged/labelled version or a specific revision of your schema to a folder using your source control system
2) Use SQL Compare Pro to compare and then synchronize this folder to your development databaseA free trial of SQL Compare Pro is available at http://www.red-gate.com/products/SQL_Compare.
AdminRedgate Administrator
(Admin, Redgate)
shared this idea
·
-
3 votes
I don’t understand… If someone else committed a drop of an object, then once you click the “Get Latest” button on the “Get Latest” tab, then it will drop if from the db.
-
Auto checkout from TFS on modify of sql object. and show the object as checked out in SQL Mgt Studio
76 votesSimilar to TFS checkout suggestion, http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/802123-tfs-exclusive-checkout-svn-lock. I guess the difference here is that it is an option to do the checkout automatically.
An error occurred while saving the comment The blue circle in the ObjExp just identifies local changes that have not been committed yet. v1 of SQL Source Control uses the edit-merge-commit model instead of the checkout-edit-checkin model. Keep voting here or http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/802123-tfs-exclusive-checkout-svn-lock if you need this feature.
-
2 votes
An error occurred while saving the comment This seems similar to this suggestion, choose subfolders in subversion - https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/986303-choose-subfolders-in-subversion.
-
12 votes
James Billings
responded
If MKS offers a command-line, you may be able to configure it with config files – see http://www.red-gate.com/supportcenter/Content?p=SQL%20Source%20Control&c=SQL_Source_Control/help/2.2/SSC_working_with_config_files.htm&toc=SQL_Source_Control/help/2.2/toc1432725.htm
An error occurred while saving the comment What is MKS?
If CA's SCM has a command line interface, then you can create your own configuration file for SQL Source Control to work with it. More information is at http://www.red-gate.com/supportcenter/content/SQL_Source_Control/help/3.0/SSC_working_with_config_files.