Comments
Sort by recent activity
After we do our restore from "Production" and run some schema scripts which cover items not in source control, we use SQL Compare.
Comparing "from" the Source Control latest version "to" the restored database and letting SQL Compare deploy the changes seems to clear everything up.
When we go to the SQL Source Control window in SSMS, it's "clean" (nothing on Commit Changes, nothing on Get Latest). / comments
After we do our restore from "Production" and run some schema scripts which cover items not in source control, we use SQL Compare.
Comparing "from" the Source Control latest version "to" the restor...
Thanks Pete.
One question: will all of this unlinking/re-linking cause an explosion of files in our local TFS workspaces?
One thing I noticed when I was evaluating SQL Source Control prior to our purchase of the product was that there seemed to be an inordinate number of local TFS workspaces created.
Thanks again,
Craig / comments
Thanks Pete.
One question: will all of this unlinking/re-linking cause an explosion of files in our local TFS workspaces?
One thing I noticed when I was evaluating SQL Source Control prior to our p...
The database being restored doesn't have any of the extended properties.
I had thought of this as a solution, so as part of the restore I went ahead and set the extended properties (SQLSourceControl Database Revision, SQLSourceControl Scripts Location, and SQLSourceControl Migration Scripts Location), setting the Revision value to the value of the revision when I did my initial commit.
This only seemed to make things worse, though. / comments
The database being restored doesn't have any of the extended properties.
I had thought of this as a solution, so as part of the restore I went ahead and set the extended properties (SQLSourceContro...
eddie davis wrote:
Hi,
The command line for this option is one of the following:
/Options:DisableSOCForLiveDBs
Or using the alias
/Options:dafld
Full list of the Command Line Options can be found HERE.
Many Thanks
Eddie
That option works great! Thanks! / comments
eddie davis wrote:
Hi,
The command line for this option is one of the following:
/Options:DisableSOCForLiveDBs
Or using the alias
/Options:dafld
Full list of the Command Line Options can be f...
mmoore wrote:
After looking further into this, I noticed that this only applies to the Extended Properties that are added by SQL Source Control. They are always added, which in my case is pointless on my customer's Sql Server.
I don't think that's the case. I check-boxed this option in the "Ignore" section and still had the SQL Source Control version number update appear in the deployment script.
I would LOVE LOVE LOVE to not have to manually edit my script every time I deploy to an environment that's not under SQL Source Control, especially since those environments aren't always updated to the LATEST in our repository (we selectively deploy objects to the target environment). / comments
mmoore wrote:
After looking further into this, I noticed that this only applies to the Extended Properties that are added by SQL Source Control. They are always added, which in my case is pointl...
I am definitely in the camp of wanting to specify SPECIFIC foreign key values. / comments
I am definitely in the camp of wanting to specify SPECIFIC foreign key values.