User profile for DanW564

Newer information for others still finding this discussion: Data Compare: https://documentation.red-gate.com/sdc/using-the-command-line/using-the-command-line-on-a-service-account-in-windows sqldatacompare /allUsers /activateSerial:123-456-789012-ABCD SQL Compare: https://documentation.red-gate.com/sc/using-the-command-line/using-the-command-line-on-a-service-account-in-windows sqlcompare /allUsers /activateSerial:123-456-789012-ABCD / comments

Newer information for others still finding this discussion:Data Compare: https://documentation.red-gate.com/sdc/using-the-command-line/using-the-command-line-on-a-service-account-in-windowssqldatac...

0 votes

way0utwest, thank you for your thoughtful response and your work on this over the years. I voted for and commented on item you mentioned. Re#1: I think I hear your concern. Essentially, I hear you saying that you need to guard against users blaming you for something going wrong because the tool didn't protect them from something they thought it would protect them from. I get that, but I'm also confident that it's possible to cause damage with any tool, and you can't completely protect us from ourselves. Here's a compromise idea that I would be thrilled about: What if the cache of identified items was used to quickly identify objects, and initially, only those objects were re-checked (database vs repo)? Then, this short list was displayed, but the full re-check was initiated. While the full re-check was running, allow for an option to stop/cancel the full re-check (such that we can't commit unless the full refresh is cancelled), but show some warning that the user has to acknowledge before the full re-check gets stopped (maybe even log it to protect yourselves...?). That way, when users complain that something broke because of a change someone else made that they were not aware of, at least they know, and you can remind them, that they intentionally disabled your safety net. If something like that was implemented, I'd have a new lease on the possibility of using SQL Source Control in my current job. With any source code repository (at least as I understand it), it's possible to commit a change that will have a conflict with a commit done by someone else. We have to do an Update (SVN) or Pull (Git) to see changes potentially done by someone else. Relative to that, I see cached list of recognized changes as analogous to my working copy folder (SVN) or local repository (Git), so I don't see trusting the cache to identify differences between the database an the linked repository to be all that big of deal. Wouldn't any repository warn of a conflict if someone committed a different change to the same object/file, or at least a change that couldn't be automatically merged? Re#3: I wasn't trying to ask for a filter by user, only by object type, or a way to commit a single object, based on the changes identified by the polling process. I tried yesterday to post a new idea to the uservoice site, but the post idea button appeared to not be working for me. I tried both Chrome and IE, but neither worked from what I could see. Either that, or there are several new ideas posted by me with no real content that I couldn't find with the search. / comments

way0utwest, thank you for your thoughtful response and your work on this over the years. I voted for and commented on item you mentioned.Re#1: I think I hear your concern. Essentially, I hear you s...

0 votes

Performance Improvement Wishlist

In a nutshell, I wish SQL Source Control (SSC) could isolate context of changes similar to the way TortoiseSVN does so for my working directory on my C:\ drive. Virtually all of my source control e...

2 followers 3 comments 0 votes

Rob C said: Thanks for the feedback Tim, that's really useful to know. I hope that the return of the old-style report will suffice in the mean time. Once SC-10194 has been taken care of, I think it will suffice nicely for the purpose that I am working on, which is very similar to what Tim_Cartright described above. Thank you for bringing that back! FWIW, I found a way to fix my broken HTML file. See https://forum.red-gate.com/discussion/comment/153003#Comment_153003 / comments

Rob C said: Thanks for the feedback Tim, that's really useful to know. I hope that the return of the old-style report will suffice in the mean time. Once SC-10194 has been taken care of, I t...

0 votes

I ran into this yesterday. The report file I generated with the UI for SQL Compare 13.4.6.7079 Professional displays fine. However, when I tried the new Classic setting from the command line, the H...

0 votes

How can we help you today?

DanW564

Activity overview