Comments
Sort by recent activity
Hi Michelle,
Thank you for your response, that's clear for me now, Unfortunately I am unable to test the behavior now, because I'm experiencing some problems with Data Generation with DLM. As far as they are solved I will test the behavior / comments
Hi Michelle,
Thank you for your response, that's clear for me now, Unfortunately I am unable to test the behavior now, because I'm experiencing some problems with Data Generation with DLM. As far ...
Hello,
Under "SQL Build Tfs add-on" I've meant DLM Automation VSTS Build and Release extensions
URL: http://www.red-gate.com/products/dlm/dlm-automation/add-ons
Thank you
Giorgi / comments
Hello,
Under "SQL Build Tfs add-on" I've meant DLM Automation VSTS Build and Release extensions
URL: http://www.red-gate.com/products/dlm/dlm-automation/add-ons
Thank you
Giorgi
Thank you Michael,
Giorgi / comments
Thank you Michael,
Giorgi
michaelwhittaker wrote: »
Hi @Giorgi, if you have a support and upgrades contract with us you can submit a ticket here. One of the team will be in touch shortly after you do that. Please try to give us as much information as possible as it will help us help you!
Hello @michaelwhittaker ,
I've already added the ticket three days ago ...
Ticket ID: 96358 / comments
michaelwhittaker wrote: »
Hi @Giorgi, if you have a support and upgrades contract with us you can submit a ticket here. One of the team will be in touch shortly after you do that. Please try to...
Hello, I have the same issue, can I also get the link for support ticket? / comments
Hello, I have the same issue, can I also get the link for support ticket?
Yes that solved my problem,
Sorry for late response,
Thank you,
/ comments
Yes that solved my problem,
Sorry for late response,
Thank you,
Hello Sam,
Unfortunately not, because:
If I compare one source control's two different revisions, I can set up it with SQL Compare Command line this way:
(I am using xml file to pass arguments)
<SourceControl1 />
<Revision1>HEAD</Revision1>
<SourceControl2 />
<Revision2>1525</Revision2>
<ScriptsFolderXML>SourceControlAddress 2160320.xml</ScriptsFolderXML>
where 1525 is some older Changeset number
but this approach will work for only one database (db repository) pointed in file "SourceControlAddress 2160320.xml" (in this case branch - db 2160320, that we are release fixes from)
but we also have development database, called Trunk and when major release approaches, we want to compare Trunk to the branch (db 2160320) and issue the change as deployment script,
and if I had something like ScriptsFolderXML1, ScriptsFolderXML2, for SQL Compare command line, I would configure it something like this:
<SourceControl1 />
<Revision1>HEAD</Revision1>
<SourceControl2 />
<Revision2>HEAD</Revision2>
<ScriptsFolderXML1>SourceControlAddress 2160320.xml</ScriptsFolderXML1>
<ScriptsFolderXML2>SourceControlAddress Trunk.xml</ScriptsFolderXML2>
The scenario is absolutely possible by SQL Compare UI,
but for automation reasons we need it to be supported by SQL Compare command line
Thank you, / comments
Hello Sam,
Unfortunately not, because:
If I compare one source control's two different revisions, I can set up it with SQL Compare Command line this way:
(I am using xml file to pass arguments)
<So...
Hello Sam,
We will consider the method described by you, but frankly, creating additional step it's not preferable option for us,
as we've automated the process
Thank you,
Giorgi Abashidze / comments
Hello Sam,
We will consider the method described by you, but frankly, creating additional step it's not preferable option for us,
as we've automated the process
Thank you,
Giorgi Abashidze
Hello Sergio,
I agree absolutely to timetrak_aw, Revision number is nice means to control at what point is production db.
But besides that, I tried to remove Revision extended property, but source control has done strange thing, after that, I saw all the old migration scripts in my "Get Latest" tab
So as I see our upgrade to SC 5 was something like half an upgrade, and some parts of logic in SC and SQL Compare think that they are working as old versions
Thank you / comments
Hello Sergio,
I agree absolutely to timetrak_aw, Revision number is nice means to control at what point is production db.
But besides that, I tried to remove Revision extended property, but source ...
As far as I've seen, there is a frequent update to 11.6.10.2352 version, I've updated and tested that version, but with same result:
At the end of the script there is a block with update of all of the 3 database extended properties
Thank you,
Giorgi / comments
As far as I've seen, there is a frequent update to 11.6.10.2352 version, I've updated and tested that version, but with same result:
At the end of the script there is a block with update of all of ...