Comments
Sort by recent activity
is there still no fix for this?- having downgraded back in October i've now started getting pop-up 'send error message' type dialogues and having updated to latest still getting the 'you haven't permissions to access the database' nonsense message. / comments
is there still no fix for this?- having downgraded back in October i've now started getting pop-up 'send error message' type dialogues and having updated to latest still getting the 'you haven't pe...
brad_bruce_01 said:
kalo said:
I'm getting the same error with version 7.4.7.16362. Azure not involved so not sure why it's saying it can't access the database. Has been working previously for a good while. Just through an error when I tried today, noticed there was an update available so installed that, after that now got the "SQL Source Control can't access this database" error. Tried unlinking control and then relinking but still get the same error.
Kalo, I reached out to Redgate support. They said the current version has a bug and provided me with the previous version that resolved my issue. I would recommend the same. Good luck!
Thanks - trouble is I updated to latest in this instance because i was already getting a different error, so haven't got time to go backwards at this point. Might need to if we have an internal release date prior to any fix though! / comments
brad_bruce_01 said:
kalo said:
I'm getting the same error with version 7.4.7.16362. Azure not involved so not sure why it's saying it can't access the database. Has been working previo...
This still seems to be an issue for me - have got 7.4.9 latest update. Any update on when this issue will be fixed please? / comments
This still seems to be an issue for me - have got 7.4.9 latest update. Any update on when this issue will be fixed please?
I'm getting the same error with version 7.4.7.16362. Azure not involved so not sure why it's saying it can't access the database. Has been working previously for a good while. Just through an error when I tried today, noticed there was an update available so installed that, after that now got the "SQL Source Control can't access this database" error. Tried unlinking control and then relinking but still get the same error. / comments
I'm getting the same error with version 7.4.7.16362. Azure not involved so not sure why it's saying it can't access the database. Has been working previously for a good while. Just through an error...
Slightly annoying that this isn't an option - at least thanks to this thread i know i'm not going crazy why I can't get my databases to show as identical ignoring this - and can't auto-script deployment but ignore this / comments
Slightly annoying that this isn't an option - at least thanks to this thread i know i'm not going crazy why I can't get my databases to show as identical ignoring this - and can't auto-script deplo...
Hi Jessica, I've got a support call open but no solution yet - so open to suggestions from forum users who may have encountered the same issue thanks. / comments
Hi Jessica, I've got a support call open but no solution yet - so open to suggestions from forum users who may have encountered the same issuethanks.
Thanks for your response: I will log a ticket. / comments
Thanks for your response: I will log a ticket.
Tianjiao_Li said:
Hi @kalo, As you can see this is an intended change made about 3 years ago, we would need to have sufficient evidence for changing this behaviour again. Can you please kindly post your suggestion on our user voice forum so that other people can vote for it?
I think you have misunderstood my last post : i wasn't asking for the behaviour to change, i was asking for the behaviour to work as i expected. I originally posted that i needed to be able to suppress the checkbox tick and have the app remember but was told that wasn't possible - even though the app had been behaving that way for me. But then found in the release notes that this was possible albeit having to hack the xml ourselves. In James' post from 2015 he says set the xml value to false. I did this but it still didn't work. I logged a support call and Sergio directed to me some documentation: https://documentation.red-gate.com/soc6/configuring/change-the-default-for-the-checkbox-on-the-dependencies-selection-screen which points out that has to be False not false : resetting the case-sensitive node in the UI options to this value then at least set the default checkbox state to OFF. So i think an upgrade along the way had removed the node i'd manually inserted into the xml file myself and therefore the behaviour i'd come to expect for the last 3 years had stopped working that way. It would probably be clearer if the xml didn't have to be doctored by the user manually but could be set in the options screen of the application itself, so i might log that request on user voice forum. thanks. / comments
Tianjiao_Li said:
Hi @kalo,As you can see this is an intended change made about 3 years ago, we would need to have sufficient evidence for changing this behaviour again. Can you please kindly...
I think this might be the feature which has disappeared at some point : so i've logged a support ticket [image] Trying James' advice below to add in the xmlnode, the file removes it when the app next updates the file. [image] / comments
I think this might be the feature which has disappeared at some point : so i've logged a support ticketTrying James' advice below to add in the xmlnode, the file removes it when the app next update...
Tianjiao_Li said:
Hi @kalo, As you can see this is an intended change made about 3 years ago, we would need to have sufficient evidence for changing this behaviour again. Can you please kindly post your suggestion on our user voice forum so that other people can vote for it?
I think you have misunderstood my last post : i wasn't asking for the behaviour to change, i was asking for the behaviour to work as i expected. I originally posted that i needed to be able to suppress the checkbox tick and have the app remember but was told that wasn't possible - even though the app had been behaving that way for me. But then found in the release notes that this was possible albeit having to hack the xml ourselves. In James' post from 2015 he says set the xml value to false. I did this but it still didn't work. I logged a support call and Sergio directed to me some documentation: https://documentation.red-gate.com/soc6/configuring/change-the-default-for-the-checkbox-on-the-dependencies-selection-screen which points out that has to be False not false : resetting the case-sensitive node in the UI options to this value then at least set the default checkbox state to OFF. So i think an upgrade along the way had removed the node i'd manually inserted into the xml file myself and therefore the behaviour i'd come to expect for the last 3 years had stopped working that way. It would probably be clearer if the xml didn't have to be doctored by the user manually but could be set in the options screen of the application itself, so i might log that request on user voice forum. thanks. / comments
Tianjiao_Li said:
Hi @kalo,As you can see this is an intended change made about 3 years ago, we would need to have sufficient evidence for changing this behaviour again. Can you please kindly...