Comments
Sort by recent activity
Thanks for your post.
I emailed you about this earlier, but I thought I would update the post in case anyone else finds the same problem.
This issue is a bug with SQL Data Generator 2.0 and has been logged with the internal tracking code SDG-972.
SQL Data Generator v1 doesn't have this problem, which can be downloaded from here / comments
Thanks for your post.
I emailed you about this earlier, but I thought I would update the post in case anyone else finds the same problem.
This issue is a bug with SQL Data Generator 2.0 and has bee...
Hi,
V3 has now been released. / comments
Hi,
V3 has now been released.
Thanks for your post.
This is actually a known issue with SQL Source Control, it's logged under the code SOC-2683.
We have already written a fix for this, which should be available in the full release of v3. / comments
Thanks for your post.
This is actually a known issue with SQL Source Control, it's logged under the code SOC-2683.
We have already written a fix for this, which should be available in the full rele...
Thanks for your post.
the best place to log feature suggestions is on our uservoice site.
this will be much more visible to the developers and users, and suggestions can be up-voted by users to make them more likely to be implemented.
We've only just created the site, so your idea will be one of the first. / comments
Thanks for your post.
the best place to log feature suggestions is on our uservoice site.
this will be much more visible to the developers and users, and suggestions can be up-voted by users to mak...
Thanks for your reply.
There isn't any plans for a new version of Multi-Script at this stage.
The reasoning behind having a 25 simultaneous database limit was because most users workstations will have between 1 and 4 cores and a finite network bandwidth. We thought it was safer to restrict the number of simultaneous executions rather then causing the machine to crash/run out of memory or use all the network bandwidth.
The 25 simultaneous connections still means there are 25 executed at once, so each time one finishes one of the remaining can start.
I hope this helps. / comments
Thanks for your reply.
There isn't any plans for a new version of Multi-Script at this stage.
The reasoning behind having a 25 simultaneous database limit was because most users workstations will h...
I'm afraid not. It looks like the upper limit is 25.
There isn't any development planned for Multi-Script in the near future, so it's likely to stay like this for a while.
Sorry I can't be of more help. / comments
I'm afraid not. It looks like the upper limit is 25.
There isn't any development planned for Multi-Script in the near future, so it's likely to stay like this for a while.
Sorry I can't be of more ...
Thanks for your post.
I couldn't find any error reports submitted with your email address, but I would try unlinking and relinking your database to the repository and see if that helps. / comments
Thanks for your post.
I couldn't find any error reports submitted with your email address, but I would try unlinking and relinking your database to the repository and see if that helps.
Thanks for your post.
There isn't a way to do it through SQL Source Control, but depending on your source control system, it might support allowing you to change the comments.
For example, here is a way to do it with subversion:
<http://stackoverflow.com/questions/692851/can-i-go-back-and-edit-comments-on-an-svn-checkin>
I hope this helps. / comments
Thanks for your post.
There isn't a way to do it through SQL Source Control, but depending on your source control system, it might support allowing you to change the comments.
For example, here is ...
Thanks for your post.
I might be wrong, but the behaviour of a left out join and a right outer join is different, so switching the type of join (and I presume also the order the tables) in the query wouldn't always return the same result.
However, we have a uservoice site for SQL Prompt feature suggestions, so you might get some interest on there. Here is the link: http://redgate.uservoice.com/forums/944 ... uggestions / comments
Thanks for your post.
I might be wrong, but the behaviour of a left out join and a right outer join is different, so switching the type of join (and I presume also the order the tables) in the quer...
Thanks for your post.
There isn't a command line or API for SQL Source Control, but as a workaround you could commit the working copy that SQL Source Control uses using a different client.
To find the working copy, press shift+right-click on the 'linked to path' on the setup tab. This folder contains all the changes, so you should be able to automate a commit of this folder. I haven't tested this before, so I can't guarantee there won't be problems.
The idea with SQL Source control is that the developer will commit the change when they're happy with the work, rather than a scheduled commit when the object might not be in a consistent state.
I hope this helps. / comments
Thanks for your post.
There isn't a command line or API for SQL Source Control, but as a workaround you could commit the working copy that SQL Source Control uses using a different client.
To find ...