Comments
Sort by recent activity
Hi Tim,
Sorry you've been seeing this problem. I can reproduce your problem here and you are quite right that the issue seems to be creating the procedure before full text indexes have been added to referenced tables. I will add an issue to our internal bug tracking system about this. Immediately the only work-around for this I can see is to pre-populate your target database with either the full text tables or the stored procedure (interestingly SQL Server allows creating stored procedures that reference objects that don't exist - so I can run your create procedure script with none of the referenced tables). If you are using SQL Source Control then migrations scripts might be a way to do this.
Matthew Chandler
Software Developer on SQL Compare and SQL Data Compare / comments
Hi Tim,
Sorry you've been seeing this problem. I can reproduce your problem here and you are quite right that the issue seems to be creating the procedure before full text indexes have been added ...
Hi Dennis,
I think custom filters could help you here. If you click on "Custom filter rules..." in the left hand pane of your project you ought to be able to add a filter for stored procedures to:
Exclude if: Object name Begins with sp_MS
which I think should do what you are looking for.
I hope that's useful,
Matthew Chandler
Software Developer on SQL Compare and SQL Data Compare / comments
Hi Dennis,
I think custom filters could help you here. If you click on "Custom filter rules..." in the left hand pane of your project you ought to be able to add a filter for stored procedures to:...
Hi Jeff,
Thanks for your feedback. When deploying to scripts folders we would not normally rename files to add the schema part onto the filename, but I can see this would not help when we are adding new objects into the schema. Aside from manually renaming files I'm afraid I can't think of any good way to generate files in this format with SQL Compare at the moment.
Matthew Chandler
Software Developer on SQL Compare and SQL Data Compare / comments
Hi Jeff,
Thanks for your feedback. When deploying to scripts folders we would not normally rename files to add the schema part onto the filename, but I can see this would not help when we are addi...
Hi There,
Yes I can see your point - once we have decided which rows to update the WHERE clause seems redundant. I suppose there are cases where the target has changed that the where clause might have some use. Has this behaviour caused you any issues using SQL Data Compare?
Matthew Chandler
Software Developer on SQL Compare and SQL Data Compare / comments
Hi There,
Yes I can see your point - once we have decided which rows to update the WHERE clause seems redundant. I suppose there are cases where the target has changed that the where clause might ...
Hello,
Thank you for bringing this to our attention. We have shipped a new version of SQL Data Compare (12.0.26) with this bug fixed on our frequent releases channel, which can be installed from check for updates in the product. I hope this did not cause you too much inconvenience. Thanks again for getting in touch,
Matthew Chandler
Software Developer on SQL Compare and SQL Data Compare / comments
Hello,
Thank you for bringing this to our attention. We have shipped a new version of SQL Data Compare (12.0.26) with this bug fixed on our frequent releases channel, which can be installed from c...
Thanks for the feedback. As part of our most recent frequent updates release we are using a shorter date-time format in the project browser.
Matthew Chandler
Software Developer on SQL Compare and SQL Data Compare / comments
Thanks for the feedback. As part of our most recent frequent updates release we are using a shorter date-time format in the project browser.
Matthew Chandler
Software Developer on SQL Compare and ...
Hi Ed,
Apologies for not getting back to you sooner.
It should be possible to do what you have described in Data Compare. Under the "Tables & Views" section of the edit project dialog you can specify a custom comparison key (the leftmost column) from which you could use your foreign key column as the comparison key. From the right hand column its possible to exclude columns from the comparison - so the original primary key can be excluded from the comparison and deployment if desired.
I hope this helps with your issue
Matthew Chandler
Software Developer on SQL Compare and SQL Data Compare / comments
Hi Ed,
Apologies for not getting back to you sooner.
It should be possible to do what you have described in Data Compare. Under the "Tables & Views" section of the edit project dialog you can spec...
Hi there,
I'm sorry you've run into this error. This sounds like a bug in SQL Compare but its hard to know what's going wrong without more information. I suggest you get in touch with support@red-gate.com, as I hope they will be able to help you with this issue.
Matthew Chandler
Software Developer on SQL Compare and SQL Data Compare / comments
Hi there,
I'm sorry you've run into this error. This sounds like a bug in SQL Compare but its hard to know what's going wrong without more information. I suggest you get in touch with support@red...
I'm glad you sorted this out. Do let us know if you need any other help or information,
Matt Chandler / comments
I'm glad you sorted this out. Do let us know if you need any other help or information,
Matt Chandler
Hi There, sorry you've had trouble getting SQL Release set up.
You're right that static data ought to be included by default by SQL Release (and is only turned off if you use the IgnoreStaticData flag.)
Its not obvious to me right now why your static data isn't getting deployed as you'd expect. Something that would help me to debug the issue is if you could post the script you ran to generate the update (minus any sensitive data of course). Alternatively it could be useful if I could see the scripts folder you are updating from. If that is possible you can email me at dlmautomationsupport@red-gate.com
Kind Regards,
Matt Chandler
Test Engineer on the DLM Automation Suite team. / comments
Hi There, sorry you've had trouble getting SQL Release set up.
You're right that static data ought to be included by default by SQL Release (and is only turned off if you use the IgnoreStaticData f...