Comments
Sort by recent activity
Thanks for your post.
SQL Source control isn't really designed to be used to deploy a structure to different environments, it's purely to help a team of developers work together and record their changes directly through SSMS.
If you need to move the structure somewhere else, e.g. production to development, then we would recommend that you use SQL Compare.
In your situation:
1) Use SQL Compare to deploy the schema from your current production database to your development environment.
2) Link the development database to SVN using SQL Source control
3) Work on the development database until you're ready to deploy the changes to production
4) Use SQL Compare to deploy the version in SVN to production (or any other environment).
SQL Compare and SQL Source Control work very well together for this kind of process. There is a bit of information on how SQL Compare is integrated in SSMS for this task here.
I hope this helps. / comments
Thanks for your post.
SQL Source control isn't really designed to be used to deploy a structure to different environments, it's purely to help a team of developers work together and record their ch...
Sorry for the delay.
We've seen this error pop up a couple of times in the past, and in each case it was related to syntax used in functions.
Would you be able to try relinking the database to the repository and see if the problem persists?
If you get the same problem, would you be able to zip up your working base folder and send it to support@redgate.com?
You can find the working base folder if you shift+right-click the 'linked to' path on the setup tab. If you include the reference F0054484 in the subject line, it will update the ticket we've opened for you. / comments
Sorry for the delay.
We've seen this error pop up a couple of times in the past, and in each case it was related to syntax used in functions.
Would you be able to try relinking the database to the ...
Thanks for your post.
Can you confirm the exact version of TFS you're using? I think I've found an error report you submitted on 15th Nov, but you seem to mention source safe in that report. / comments
Thanks for your post.
Can you confirm the exact version of TFS you're using? I think I've found an error report you submitted on 15th Nov, but you seem to mention source safe in that report.
Sorry for the delay.
The reason for having the option to not include dependencies is basically so users can choose that unselected objects are not brought back into the project under any circumstances.
If you need the tool to help bring any connected objects back into the project, then that's when the 'include dependencies' option should be used. If it's performing dangerous or undesirable actions, then that's the issue we need to look into.
A lot had changed in the tools dependency engine in the last few years, so you might find it reliable now. / comments
Sorry for the delay.
The reason for having the option to not include dependencies is basically so users can choose that unselected objects are not brought back into the project under any circumstan...
Thanks for your post.
Indexes/constraints aren't considered objects in their own right in SQL Compare, and are treated as part of the table object. This is probably why their dependencies are taken into account without using the 'include dependencies' option.
When you don't use the 'include dependencies' option, then only the objects selected for synchronization will be considered and any other unselected objects will not be brought back into the project.
Does it pick up the dependency to the stored procedure if you 'include dependencies'? / comments
Thanks for your post.
Indexes/constraints aren't considered objects in their own right in SQL Compare, and are treated as part of the table object. This is probably why their dependencies are taken...
Thanks for your post.
'Include Dependencies' is part of the 'default' options set. If you set the options explicitly using the /options switch, you can make sure you don't include this option.
I hope this helps. / comments
Thanks for your post.
'Include Dependencies' is part of the 'default' options set. If you set the options explicitly using the /options switch, you can make sure you don't include this option.
I ho...
I'm afraid you can't stop the images folder being created in the current version. / comments
I'm afraid you can't stop the images folder being created in the current version.
Thanks for your post.
There has indeed been a change in the behaviour. We now create the images folder with the report, so that users without an internet connection can open the report.
If the images folder can't be found, it's supposed to try our website, but this doesn't work due to bug SC-4867.
As a workaround, you can either change the location where we look for the images in the generated .html report, or through the xsl template (in 'Program Files') used to generate the report. The former will only affect that instance of the report, the latter will affect all subsequent reports.
The change you will need to make will be: function SetupImagesDir()
{
imagesdir = reportFileName + "_images\\";
}
to function SetupImagesDir()
{
imagesdir = "http://www.red-gate.com/scimages/";
}
I hope this helps. / comments
Thanks for your post.
There has indeed been a change in the behaviour. We now create the images folder with the report, so that users without an internet connection can open the report.
If the imag...
I don't really know when you can expect the fix. It's currently scheduled for v10, but a date for that hasn't been discussed yet.
The workaround worked ok when I tried it here before posting, so I'd be happy to take a look at your report and see if I can get it working without the images folder for you.
Feel free to send it to support@red-gate.com. Can you include the reference F0054217 in the subject line, so it will update the ticket we have open for you?
Regards,
Chris / comments
I don't really know when you can expect the fix. It's currently scheduled for v10, but a date for that hasn't been discussed yet.
The workaround worked ok when I tried it here before posting, so I'...
ah ok, that would be:
HKEY_CURRENT_USER\Software\Red Gate\SQL Tools\SmartAssemblyReportUsage
Thanks for the update. / comments
ah ok, that would be:
HKEY_CURRENT_USER\Software\Red Gate\SQL Tools\SmartAssemblyReportUsage
Thanks for the update.