Comments
Sort by recent activity
Thank you so much for including the stack track and the code for the function. We were able to replicate your issue. We are looking into a fix for this now. Our internal reference number is SOC-800. / comments
Thank you so much for including the stack track and the code for the function. We were able to replicate your issue. We are looking into a fix for this now. Our internal reference number is SOC-...
2 Things:
1) Could you please check for updates to make sure you have the latest version? To do this, please click Help > Check for Updates... near the Red Gate logo on the SQL Source Control tab. The latest version is 0.3.0.1, which was released on March 8th.
2) Could you please email SQLSourceControlSupport@red-gate.com with the file located at C:\Users\danny\AppData\Local\Red Gate\SQL Source Control 0\Transients-TFS\ae8a33f1-d80e-4c6b-a86f-1b9076626d12\Tables\dbo.E_Sold_Policies.sql? This way, we can try to reproduce it locally so we can provide a fix for you. Our internal reference number for this issue is SOC-802. / comments
2 Things:
1) Could you please check for updates to make sure you have the latest version? To do this, please click Help > Check for Updates... near the Red Gate logo on the SQL Source Control tab....
Hi Roman,
No problem. I'm glad you were able to find this on our Suggestion Forum. We are currently working on the Revert functionality. If this is important to you, you can comment/vote at http://redgate.uservoice.com/forums/390 ... ?ref=title
Thank you! / comments
Hi Roman,
No problem. I'm glad you were able to find this on our Suggestion Forum. We are currently working on the Revert functionality. If this is important to you, you can comment/vote at http...
One more thing that I wanted to mention... In this example, you want to revert/undo a dropped table. In a future SQL Source Control version, you will be able to do this, but it will only bring back the table's schema and not the data that was in the table. Does that make sense?
SQL Source Control is not a replacement for database backups. After reverting the schema, you could use our SQL Data Compare to synchronize the data in that table from a recent backup or from another dev/test/production db. Since it's a development db, you may not be concerned about the data anyways.
In a future version of SQL Source Control, we are considering giving users the option to also source control data. This would be useful for static/reference/lookup data that is part of the application and not really recommended for transactional data. If this data was in source control, then this should be revertable as well. This is a ways out right now... / comments
One more thing that I wanted to mention... In this example, you want to revert/undo a dropped table. In a future SQL Source Control version, you will be able to do this, but it will only bring ba...
SQL Source Control currently doesn't have the ability to ignore objects.
Please vote/comment on this suggestion at http://redgate.uservoice.com/forums/390 ... ?ref=title to help us prioritize future features.
The best thing to do now is:
1) Sort the Commit List by Object Name
2) Use your mouse and shift key to highlight all the objects that start with DYN*
3) Unclick on one of the rows, which will unselect all of the highlighted objects
4) Commit your other objects, which are still selected
If you only made one change, you could also use the checkbox in the column header to unselect all the objects in the commit list, and then only select the one object you want to commit.
You can also do this by right-clicking on the object in the Object Explorer and selecting Commit. This will bring you to the Commit tab with only the one object selected.
I hope these tips help for now... :-) / comments
SQL Source Control currently doesn't have the ability to ignore objects.
Please vote/comment on this suggestion athttp://redgate.uservoice.com/forums/390 ... ?ref=title to help us prioritize future...
If you are also looking for GIT Support, please vote/comment on our Suggestion Forum at http://redgate.uservoice.com/forums/390 ... ?ref=title. / comments
If you are also looking for GIT Support, please vote/comment on our Suggestion Forum at http://redgate.uservoice.com/forums/390 ... ?ref=title.
There are no plans to support Git at the moment. If this is something you need, please post a suggestion at http://redgate.uservoice.com/forums/390 ... ce-control. This suggestion currently doesn't exist.
We are looking at polls that describe source control systems popularity over time. SVN and TFS seem to be the most used right now and have been increasing in usage over the past 2 years. Git is on that poll, so we'll be looking at its popularity.
Btw, it's great to hear that you are hyped about SQL Source Control. We love hearing this type of stuff and are so glad that you are finding it useful in your environment! :-) Please continue to post problems to these Support Forums or post suggestions to our Suggestion Forum as you continue to evaluate SQL Source Control. / comments
There are no plans to support Git at the moment. If this is something you need, please post a suggestion at http://redgate.uservoice.com/forums/390 ... ce-control. This suggestion currently doesn...
Hi Justin,
Thanks for checking the svn:needs-lock properties. We're looking into other settings to counteract this. Our internal reference number is SOC-719 and you should be hearing from us soon. / comments
Hi Justin,
Thanks for checking the svn:needs-lock properties. We're looking into other settings to counteract this. Our internal reference number is SOC-719 and you should be hearing from us soon.
This issue was caused by a seperate SVN plug-in caused SVNSCC by Pushok Software. If you have this plug-in installed, use the following workaround:
To get SQL Source Control and SVNSCC to work together, we need to configure SVNSCC not to modify attributes on the check outs used by SQL Source Control. As far as I can tell, the best way to do this is:
1) Unlink all your SVN databases in SQL Source Control (Right click on each database, select 'Other SQL Source Control Tasks' then click 'Unlink database from source control.')
2) Close SSMS
2) Bring up a command prompt (Start+R, type in cmd and click ok)
3) Type or copy and paste in the line below changing <username> to be your windows login, and press enter
echo pushok::rwmon=skip-tree>"C:\Users\<username>\AppData\Local\Red Gate\.pushokprops"
4) Run the 'SSC RW Monitor' (under Start->All Programs->Pushok Software)
5) In the dialog that appears, click "Cleanup and Restart"
6) When it has finished processing, SQL Source Control should work (You will need to relink your databases) / comments
This issue was caused by a seperate SVN plug-in caused SVNSCC by Pushok Software. If you have this plug-in installed, use the following workaround:
To get SQL Source Control and SVNSCC to work tog...
SQL Source Control should NOT be locking your files. I think it might be a setting on your Subversion server. Do you have TortoiseSVN installed? If so:
1) Right click on C:\Users\justin.collazo\AppData\Local\Red Gate\SQL Source Control 0\WorkingBases\fc53bc1b-0e4b-4af9-9070-8aef7175a516\Tables\HumanResources.EmployeeDepartmentHistory.sql
and select Properties
2) Select the "Subversion" tab at the top
3) Click the "Properties..." button near the bottom
4) Is there a svn:needs-lock property? If so, remove it.
5) Click OK to close the SVN properties window
6) Click OK to close the file properties window
7) Right click again and commit the change to Subversion (this is just committing the change that a lock is not needed on that file)
Now, you should be able to commit the file from SQL Source Control with out getting this permission error. Please let us know if you still have any problems.
You'll want to talk to your SVN administrator about the settings on your SVN server and see if you can remove the svn:needs-lock on your area. This way, you won't have this permission problem happen again. You'll need to remove the needs-lock property from all your existing files. / comments
SQL Source Control should NOT be locking your files. I think it might be a setting on your Subversion server. Do you have TortoiseSVN installed? If so:
1) Right click on C:\Users\justin.collazo\...