Comments
Sort by recent activity
Unfortunately there is a bug that means that the random namespace doesn't work in SQL Data Generator with Python 2.7. You need to install Python 2.6 and then point SQL Data Generator to it.
This version works - https://www.python.org/download/releases/2.6.6/
Once you have installed it, open SQL Data Generator and from the Tools menu, choose Application Options and then you'll see a "Python libraries:" text box on the General tab. Add the path to the lib folder of your new Python install to this. For example, my text box now has this as the contents -
.;C:Program Files (x86)Red GateSQL Data Generator 3Lib;C:Program Files (x86)Red GateSQL Data Generator 3Dlls;C:Python26lib
Save the changes and this should get things working for you.
Let me know if you need any more assistance. / comments
Unfortunately there is a bug that means that the random namespace doesn't work in SQL Data Generator with Python 2.7. You need to install Python 2.6 and then point SQL Data Generator to it.
This ve...
Hi Andy,
You can only view revision numbers with the fully integrated source control systems, i.e. Subversion, TFS and Vault. Any source control systems that need a config file to access their command line will not return revision numbers.
If you right click on the database in SSMS there is an option "View history", where you can see the revision history. / comments
Hi Andy,
You can only view revision numbers with the fully integrated source control systems, i.e. Subversion, TFS and Vault. Any source control systems that need a config file to access their comm...
Hi Matthew,
There is currently no way to disable automatic mapping in SQL Compare. If you'd like to suggest the feature then please feel free to post it on our User Voice site.
Thanks. / comments
Hi Matthew,
There is currently no way to disable automatic mapping in SQL Compare. If you'd like to suggest the feature then please feel free to post it on our User Voice site.
Thanks.
Hi,
You're right that dealing with conflicts is going to be one of the key things that govern how switching is dealt with. I think switching is something we'd like to look at in the future although I don't have any timescales to give you I'm afraid.
An option that we currently suggest is creating a separate working database for each branch. That might make things a bit easier for you. / comments
Hi,
You're right that dealing with conflicts is going to be one of the key things that govern how switching is dealt with. I think switching is something we'd like to look at in the future although...
I see that you've already added this suggestion on our User Voice site, which is the best place to leave suggestions as we frequently monitor this site.
Thanks for the suggestion, they are always appreciated. / comments
I see that you've already added this suggestion on our User Voice site, which is the best place to leave suggestions as we frequently monitor this site.
Thanks for the suggestion, they are always a...
Hi,
Go into the Control Panel, go into Programs and Features, select SQL Lighthouse 1 and choose Uninstall. / comments
Hi,
Go into the Control Panel, go into Programs and Features, select SQL Lighthouse 1 and choose Uninstall.
Hi,
Would you be able to provide specific details of the error that you are experiencing? Are you able to send in an error report?
Thanks. / comments
Hi,
Would you be able to provide specific details of the error that you are experiencing? Are you able to send in an error report?
Thanks.
I felt my previous post wasn't adequate so I'm following up here.
The problem with cross-database dependencies is that the engine is only capable of deploying properly if there are one-way dependencies. For instance, if you want to deploy two databases then it would be successful if one depends on the other one. If they depend on each other then this will cause problems as whichever database the engine tries to deploy first will depend on objects that aren't there. At the moment the engine is not capable of resolving this. It's not ideal, but the way of sorting this out is to manually work out an order of deploying objects such that it won't cause dependency issues.
I hope this helps but if you'd like more information then please ask. / comments
I felt my previous post wasn't adequate so I'm following up here.
The problem with cross-database dependencies is that the engine is only capable of deploying properly if there are one-way dependen...
OK, I look forward to hearing the results [image] / comments
OK, I look forward to hearing the results
Would you be able to send me the create scripts for some of the problematic objects? If I can get a script for one of the objects in the main database and scripts for the things it references in the other database then that would help me replicate the behaviour you are experiencing.
Email them to support@red-gate.com and put #32849 in the subject line.
Thanks! / comments
Would you be able to send me the create scripts for some of the problematic objects? If I can get a script for one of the objects in the main database and scripts for the things it references in th...