Comments
Sort by recent activity
We ran into this issue the entire day yesterday. We also did our own digging and found the exact same thing. We fixed it by specifying the previous (working) version number (as said above) and everything is back to the way it was. / comments
We ran into this issue the entire day yesterday. We also did our own digging and found the exact same thing. We fixed it by specifying the previous (working) version number (as said above) and ever...
This is from the SQL Monitor forum and it has been verified to be legit. https://forum.red-gate.com/discussion/84180/sql-monitor-security-vulnerability / comments
This is from the SQL Monitor forum and it has been verified to be legit. https://forum.red-gate.com/discussion/84180/sql-monitor-security-vulnerability
Co-workers are getting this and said the same thing. The links within the email look fishy. / comments
Co-workers are getting this and said the same thing. The links within the email look fishy.
We just modify a stored procedure and added comments in it. Clicking "Refresh" shows the waiting image with the spinning arrows. Clicking "Import and Generate Scripts" does not show any progress indicator even though it's doing background work. Oh, it is taking some time to generate even though it's 1 procedure and it was just comments added to it. The SCA version: 3.0.18249.1181 / comments
We just modify a stored procedure and added comments in it. Clicking "Refresh" shows the waiting image with the spinning arrows.Clicking "Import and Generate Scripts" does not show any progress ind...
Again, I don't mind the wait. It's just that there are no indicator that it is processing. We have confuse developers here thinking they may have not really click "Import & Generate Scripts", so they go and click again and this causes an error since since the first click is currently processing. / comments
Again, I don't mind the wait. It's just that there are no indicator that it is processing. We have confuse developers here thinking they may have not really click "Import & Generate Scripts", so th...
It was a bit difficult trying to understand but I believe I got what you're trying to say. I thought through it and other ways as well and it's best to include the stored procedure within the migration script (doing an exists check is nice as well). / comments
It was a bit difficult trying to understand but I believe I got what you're trying to say. I thought through it and other ways as well and it's best to include the stored procedure within the migra...
The same thing happened to me yesterday. Though I'm not sure if the cause is the same for the both of us. VS actually wrote a log of the error in the local temp directory. I was in a rush and decided to delete my git repository and re-clone it down and it work fine after that (I have no changes). / comments
The same thing happened to me yesterday. Though I'm not sure if the cause is the same for the both of us. VS actually wrote a log of the error in the local temp directory. I was in a rush and decid...
In order to "Import and generate script", Developer B has to "Refresh". But since Developer B already pull down changes from Developer A, the "Refresh" may blow up (depending on the type of change ... maybe a new column was added to a table and the stored procedure now query that column) which then prevent the "Import and generate script". How do one solve that? / comments
In order to "Import and generate script", Developer B has to "Refresh". But since Developer B already pull down changes from Developer A, the "Refresh" may blow up (depending on the type of change...
That's a lot of work to prevent the lost of work. A lot of time, you don't even know if someone else is touching the same objects that you're touching. There are now rules that everyone need to be cognizance of which I'm not a fan of. Even common scenario like this isn't even talk about in the help doc or this forum. There's got to be a way to do an "Import" and it determine that the object you are importing conflict with the object in the project which has not been deployed yet. I don't know what "Refresh" is doing, but if we can import without a refresh and write in the "detection" code. That would help a lot. / comments
That's a lot of work to prevent the lost of work. A lot of time, you don't even know if someone else is touching the same objects that you're touching. There are now rules that everyone need to be...
You can definitely ignore anything that's apart of a schema using filters. The "enable" cdc on the affected tables, if SCA is not already doing that for you, then you may have to manually write a migration scripts to do that. / comments
You can definitely ignore anything that's apart of a schema using filters. The "enable" cdc on the affected tables, if SCA is not already doing that for you, then you may have to manually write a ...