Comments
Sort by recent activity
Hi,
I'm afraid this is quite an old issue dating back to 2013, and occurred before we had any GIT support in the product. I can't say for sure (as I no longer work on the tool), but I would suspect what you're experiencing is a new/different bug.
If you submitted an error report with your email address, our support team should be able to look it up and see if this is a know issue and/or if there are any workarounds that would help.
You can log a request at https://redgatesupport.zendesk.com/home or send an email to support@red-gate.com.
Thanks,
Chris / comments
Hi,
I'm afraid this is quite an old issue dating back to 2013, and occurred before we had any GIT support in the product. I can't say for sure (as I no longer work on the tool), but I would suspect...
I've had confirmation that this issue should be addressed in the next release. I can't give an exact date, but it should be within about a month or so. / comments
I've had confirmation that this issue should be addressed in the next release. I can't give an exact date, but it should be within about a month or so.
Thanks for your post.
This appears to be a reproducible bug when relinking a database using the shared model. I've informed the development team and sent them some reproduction steps, so it should be something we can fix fairly quickly. Our internal reference for this is SOC-4566.
I think the only workaround I can suggest at this stage is either use the dedicated model when you link, or to take a copy of the database and then link to the new folder. You could use SQL Compare to copy the schema to a new blank database, or restore a backup.
I hope this helps.
Sorry for the inconvenience. / comments
Thanks for your post.
This appears to be a reproducible bug when relinking a database using the shared model. I've informed the development team and sent them some reproduction steps, so it should ...
I'm afraid this is a bug with the current version. The DropAndCreateInsteadOfAlter option doesn't seem to be observed from the command line when using source control data sources.
I've logged this as bug SC-6317. I'm not sure of an exact timeframe for the fix, but I would guess it's likely to be around July.
I couldn't find a workaround for this, apart from using the user interface where the option seems to behave correctly. / comments
I'm afraid this is a bug with the current version. The DropAndCreateInsteadOfAlter option doesn't seem to be observed from the command line when using source control data sources.
I've logged this ...
Thanks for your post.
The option DropAndCreateInsteadOfAlter will script drop/create statements in the script, but not for any changes covered by the migration script.
If you use a migration script, it is going to use that exact script to go between the revisions covered by the migration script, regardless of any options you set. A migration script is effectively overwriting any default behavior that would normally occur.
Do you know if this particular deployment is using a migration script? An easy way to tell would be by repeating the comparison in the SQL Compare UI.
The option will only affect the script for changes outside of the migration script.
I hope this makes sense. / comments
Thanks for your post.
The option DropAndCreateInsteadOfAlter will script drop/create statements in the script, but not for any changes covered by the migration script.
If you use a migration script...
I think I follow you now.
I've tested out your command and you appear to be right. It doesn't look to be observing the Drop/Create option from the command line.
If it's any consolation it works from the UI. I haven't tested calling a SQL Compare project file from the command line to see if that works any better.
I'll see if I can find a workaround for this, or at least log a bug for the development team to address.
I'll update you once I've taken a closer look. / comments
I think I follow you now.
I've tested out your command and you appear to be right. It doesn't look to be observing the Drop/Create option from the command line.
If it's any consolation it works fro...
Sorry for the delay.
We usually have a notification service running to alert the support team to any unanswered posts, but that went down temporarily just before Christmas and it looks like your post was affected.
It also looks like a spammer responded quite convincingly to your post with some completely unrelated advice, presumably taken from somewhere else on our forums. I'll delete that to prevent further confusion.
I hope you accept our apologies on both incidents.
With regards to your actual issue you're experiencing, I assume that you can connect to the collection through VS on the same machine as you're using SSMS. If that's ok, then I have seen this kind of thing happen when there is something wrong with the config file. Normally some whitespace causing the config to be ignored.
If you're still having a problem linking SQL Source Control to TFS preview, then could you email support@red-gate.com along with your config file and we'll try and troubleshoot the problem for you?
You might also like to try using SQL Connect instead, as this will enable you to work with TFS and your database from within VS, rather than SSMS.
Again, sorry for the slow response. / comments
Sorry for the delay.
We usually have a notification service running to alert the support team to any unanswered posts, but that went down temporarily just before Christmas and it looks like your po...
Thanks for you post and sorry for the delay.
Making manual modifications to the repository outside of SQL Source Control can sometimes cause the add-in to become a bit confused and behave strangely. It's not really serious and you can normally resolve it by unlinking and relinking the database to source control.
It's a bit of a pain needing to do this so we're looking for ways to make this process a bit simpler. We should really be able to handle these kind of conditions, but sometimes it can go wrong.
Can you replicate this problem? I didn't get the same issue when I followed your steps. After you completed the roll back, did you update your local database using 'get latest' before you attempted to commit another change? / comments
Thanks for you post and sorry for the delay.
Making manual modifications to the repository outside of SQL Source Control can sometimes cause the add-in to become a bit confused and behave strangely...
Thanks for your post.
This is actually a known issue. I believe you submitted a bug report when you hit this, so you should have been sent an email with the workaround. If you didn't get it, this was the gist of it:
The execption was caused becuase your current WriteToFileOptions.xml file is in a state that we cannot read.
You should be able to resolve this by deleting the file found at %localappdata%\Red Gate\SQL Compare\WriteToFileOptions.xml
The next time you run SQL Compare, it will write out a new WriteToFileOptions.xml in the correct format.
You may need to re-enter your custom folder layout in the usual place and save your default settings for this feature again to restore your default settings to your usual layout.
I hope this helps. / comments
Thanks for your post.
This is actually a known issue. I believe you submitted a bug report when you hit this, so you should have been sent an email with the workaround. If you didn't get it, this w...
Thanks for your post.
I think this is the expected behaviour unless I'm misunderstanding. The database scripts and the migration scripts are linked to different locations in the TFS project, so you'll get a changeset for each.
I'm not sure why the migration script isn't being picked up when you 'get latest'. Is the seconds database linked to the same scripts and migrations folder in TFS? / comments
Thanks for your post.
I think this is the expected behaviour unless I'm misunderstanding. The database scripts and the migration scripts are linked to different locations in the TFS project, so you...