Comments
Sort by recent activity
We're using a shared database model. Does it have any use in that environment?
Also, does the list of "recommended objects" include ones that are waiting to be committed and ones that haven't changed since the last commit? This seems to be the case, I just want to make sure. / comments
We're using a shared database model. Does it have any use in that environment?
Also, does the list of "recommended objects" include ones that are waiting to be committed and ones that haven't chan...
This is a big issue for us as well!! / comments
This is a big issue for us as well!!
Thank you, that change worked like a charm!
Is it possibly a bug that the version in that file is set to 2 rather than 3? / comments
Thank you, that change worked like a charm!
Is it possibly a bug that the version in that file is set to 2 rather than 3?
Hi,
Thanks for your reply. The change didn't work; I'm still getting the blue dot as soon as I click on the database in the object explorer and the SPIDs' IOs keep rising.
This is the current contents of my RedGate_SQLSourceControl_Engine_EngineOptions.xml file are: <?xml version="1.0" encoding="utf-16" standalone="yes"?>
<!---->
<EngineOptions type="EngineOptions" version="2">
<PollingEnabled>False</PollingEnabled>
</EngineOptions>
/ comments
Hi,
Thanks for your reply. The change didn't work; I'm still getting the blue dot as soon as I click on the database in the object explorer and the SPIDs' IOs keep rising.
This is the current cont...
Thank you! / comments
Thank you!
Thanks for the reply,
Is it possible to figure out a workaround/patch with you guys? We have a good number of seats. / comments
Thanks for the reply,
Is it possible to figure out a workaround/patch with you guys? We have a good number of seats.
Hello,
I'd tried this before without success.
I finally had a chance to try it again and still no success.
Here's what I did:
* Create TestTable in DatabaseA
* Commit DatabaseA..TestTable (to RepositoryA)
* Insert record into DatabaseA..TestTable
* Link static data on DatabaseA..TestTable
* Commit DatabaseA..TestTable data link (to RepositoryA)
* Create TestTable in DatabaseB
* Commit DatabaseB..TestTable (to RepositoryB)
* SVN check out RepositoryA to local drive
* SVN check out RepositoryB to local drive
* Manually copy RepositoryA > trunk > Data > dbo.TestTable_Data.sql to RepositoryB > trunk > Data
* SVN commit changes to RepositoryB
* Return to SSMS and refresh Commit Changes tab for DatabaseB
* Nothing showed up
Did I miss a step? Or do you have any other ideas?
Thanks! / comments
Hello,
I'd tried this before without success.
I finally had a chance to try it again and still no success.
Here's what I did:
* Create TestTable in DatabaseA
* Commit DatabaseA..TestTable (to Repo...
I second dbdmora's question.
Is there an estimated time of release for this version? / comments
I second dbdmora's question.
Is there an estimated time of release for this version?
Have you guys been able to fix the bug with v3.1 that caused the permission error for non-sysadmin users? / comments
Have you guys been able to fix the bug with v3.1 that caused the permission error for non-sysadmin users?
A feature to allow simple updates would be fantastic.
I'm getting around this limitation by creating views against the source tables that select only the columns I don't want to "update". I use the Table/View generator to populate those columns in the target and randomizing generators for the columns I want to "update". The only columns for which this doesn't work are those with a Foreign Key constraint and IDENTITY columns.
2 possible enhancements to address this, which would help my situation but possibly not the other posters', are:
1. For columns with FK constraints, default to the "Foreign Key" generator, but allow us to change it to a different one.
2. For IDENTITY columns, default to the "Server Assigned" generator, but allow us to change it to another integer-type generator with an option to SET IDENTITY_INSERT ON. / comments
A feature to allow simple updates would be fantastic.
I'm getting around this limitation by creating views against the source tables that select only the columns I don't want to "update". I use th...