Comments
Sort by recent activity
first look seems great - thanks for the help! / comments
first look seems great - thanks for the help!
@DanC, so far so good - I've installed that this morning, and have not yet seen any recurrence of the problem. / comments
@DanC, so far so good - I've installed that this morning, and have not yet seen any recurrence of the problem.
@DanC, I do remember seeing that error message at one point, yes; I didn't specifically write down which version of step in the process I saw it at, though. If you can let me know where the log would be located, I can go take a look for you. EDIT: found the log, confirmed that the error you referenced is present. 7.2.35.13078 seems to be working okay ... I was able to use an older install file last night to get that installed, and haven't seen the error again. / comments
@DanC, I do remember seeing that error message at one point, yes; I didn't specifically write down which version of step in the process I saw it at, though. If you can let me know where the log wo...
Thanks @DanC. I'm still having an issue with 7.2.35 ... looking at the logs, the error being recorded says something like: ErrorCode: invalid_grant Microsoft.Identity.Client.MsalUiRequiredException: AADSTS50196: The server terminated an operation because it encountered a client request loop. / comments
Thanks @DanC. I'm still having an issue with 7.2.35 ... looking at the logs, the error being recorded says something like:ErrorCode: invalid_grantMicrosoft.Identity.Client.MsalUiRequiredException:...
note: I'm having that same problem, with SSMS 18.11.1 (and earlier with 18.10. something). I've tried Redgate SQL Source Control 7.3.10.14545, 7.3.22.15267, and a couple others with version numbers I haven't saved. I'm going to go back and try some earlier versions. / comments
note: I'm having that same problem, with SSMS 18.11.1 (and earlier with 18.10. something). I've tried Redgate SQL Source Control 7.3.10.14545, 7.3.22.15267, and a couple others with version numbers...
Kurt, thanks very much for the detailed response!!! Given that you've been able to confirm that the deadlock behavior would happen regardless, I am happy to let things lie as they are ... the tool, as usual, is doing its job well. Thanks again! / comments
Kurt, thanks very much for the detailed response!!! Given that you've been able to confirm that the deadlock behavior would happen regardless, I am happy to let things lie as they are ... the tool...
I appreciate the confirmation, Jessica. Is there a place we can go to request this feature, or a roadmap we can look at to help us predict when this feature might be available? Most other Redgate products have this connection so my hope is that this will arrive at some point! / comments
I appreciate the confirmation, Jessica. Is there a place we can go to request this feature, or a roadmap we can look at to help us predict when this feature might be available? Most other Redgate...
@Kendra_Little and @David Atkinson, thanks for your responses! I believe that clarifies the difference between what I was trying to have the option do and what the option was actually doing.
We were trying to satisfy a request from our data catalog team, who were attempting to import metadata from our source control repository into the Erwin product used to map dependencies between databases - they were having trouble tying definitions to the appropriate databases, and had hoped that a tweak to our source control commit options would give them the extra information they needed. I'll let them know that isn't an option.
Again, thanks for your responses!
/ comments
@Kendra_Little and @David Atkinson, thanks for your responses! I believe that clarifies the difference between what I was trying to have the option do and what the option was actually doing.
We w...
Thanks for the information! / comments
Thanks for the information!
Hi Sergio: sadly, my question is indeed describing a situation where I have stored procedures using three-part name references.
/ comments
Hi Sergio: sadly, my question is indeed describing a situation where I have stored procedures using three-part name references.