Comments
Sort by recent activity
Hello,
We've opened a support ticket for this question as it will take some troubleshooting to figure out why the history is not showing up. I will be repsonding there right after this response, thanks. / comments
Hello,
We've opened a support ticket for this question as it will take some troubleshooting to figure out why the history is not showing up. I will be repsonding there right after this response, th...
Hello,
We've opened a ticket for this issue so we can troubleshoot further. I'll be responding to you through that ticket immediatly after this forum response, thanks. / comments
Hello,
We've opened a ticket for this issue so we can troubleshoot further. I'll be responding to you through that ticket immediatly after this forum response, thanks.
Hello,
We've opened a ticket for this issue so we can troubleshoot further. I'll be responding to you through that ticket immediatly after this forum response, thanks. / comments
Hello,
We've opened a ticket for this issue so we can troubleshoot further. I'll be responding to you through that ticket immediatly after this forum response, thanks.
Hello Warren,
I ran this by some of my colleagues and as far as we know it's not this advanced; SQL Data Generator is not able to populate one row based on another in the sense you mentioned mentions nor if you have State and StateAbbreviation it won't match them up (so you end with MI for California instead of Michigan). Perhaps there is a way to update it using your own script, but we're not sure exactly how that script would be. / comments
Hello Warren,
I ran this by some of my colleagues and as far as we know it's not this advanced; SQL Data Generator is not able to populate one row based on another in the sense you mentioned mentio...
Hello Warren,
Python code is not known to lockup unless there is an infinite loop or too much memory allocated. Since the issue is only happening with the find filter box and not if you don't touch it I would think this is a bug with that dialog box. I can't think of any workaround since it's maxing the CPU and I can't think of any way to split the script up where this bug wouldn't be run into.
Sorry there wasn't a solution for this bug. / comments
Hello Warren,
Python code is not known to lockup unless there is an infinite loop or too much memory allocated. Since the issue is only happening with the find filter box and not if you don't touch...
Hello,
Unfortunately there is no way to keep the order between deployments, there is no information passed from one running of SQL Compare to the next. If the objects stay the same the order should but as you've noticed if you add objects then it will change when incorporating those. / comments
Hello,
Unfortunately there is no way to keep the order between deployments, there is no information passed from one running of SQL Compare to the next. If the objects stay the same the order should...
Hello,
Looks like you were able to resolve the scaling issues by using the link in your post and fiddling with the scaling in Windows 10 per the support ticket conversation we had. Let us know if the issue comes back or persists.
I think with SQL Source Control we are somewhat stuck with the issue in SSMS since we are a plug-in there and not a separate window. Hopefully a permanent solution for SSMS gets released. / comments
Hello,
Looks like you were able to resolve the scaling issues by using the link in your post and fiddling with the scaling in Windows 10 per the support ticket conversation we had. Let us know if t...
Hello Dwaine,
Sorry for the issue you are having with SQL Data Compare. We've opened a support ticket for this issue so we can get to the bottom of why this is happening. I'll be responding through that for some follow up info we need to start troubleshooting, thanks. / comments
Hello Dwaine,
Sorry for the issue you are having with SQL Data Compare. We've opened a support ticket for this issue so we can get to the bottom of why this is happening. I'll be responding through...
Hello,
I have done some investigating and it seems that SQL Source Control doesn't cache credentials during a session and relies on SVN's session caching. So unlinking the DB, clearing any stored credentials in Windows in control panel/credential manager, then relinking with their user ID should clear the credentials.
We've opened up a feature request (SOC-6633) to have SQL Source Control be able to clear these out but it would probably take a reasonable amount of time to implement and thoroughly test. So for now unlinking and relinking should be a good workaround.
Let me know if this does not work, thanks. / comments
Hello,
I have done some investigating and it seems that SQL Source Control doesn't cache credentials during a session and relies on SVN's session caching. So unlinking the DB, clearing any stored c...
Hello,
Sorry for the confusion with out commit warning messages you are seeing in SQL Source Control. Below is a link to how SQL Source Control works behind the scenes and should answer most of these concerns. Committing changes would never affect the local DB just the repository, so for commits it would be the repository possibly loosing data. If doing a get latest then that is where changes can happen to the localDB and that local data could be lost. So if you check in a drop table with a create for the same table someone else who does a get latest with that same operation is at risk for losing data.
For drops and creates the data is always going to be at risk, alter statements are used by our engine whenever they can be but in some situations drop/create is all that can be figured out and that is where the warnings will appear. http://documentation.red-gate.com/displ ... the+scenes / comments
Hello,
Sorry for the confusion with out commit warning messages you are seeing in SQL Source Control. Below is a link to how SQL Source Control works behind the scenes and should answer most of the...