Property cannot be updated or deleted
Andy_PS
Posts: 16
Property cannot be updated or deleted. Property 'SqlAssemblyFileLine' does not exist for 'dbo.up_CLR_RotaAppointmentTransfer'.
Had a search on the forums and the web in general and I can't see what would cause this :S
If you need aany more info then just ask
Comments
You may have encountered a known issue with SQL Compare. Can you check at SQL Compare is not trying to update an extended property on an object that it has rebuild? In this case the extended property will not exist on the object. It might be easier to dump the script out to file and execute it manually with a SQL editor to check this.
Regards,
Jonathan.
P.S.
Out of curiosity what task are you trying to solve with the SQL Toolkit?
-Project Manager
-Red Gate Software Ltd
It seems like a good way of updating any version to any version.
We take a snapshot of the latest database schema and then run the compare against that and the live database. It saves having to script all the changes by hand.
Is there any current work arounds?
If you aren't worried about extended properties there is an option to disable comparing and synchronising extended properties. If you do want extended properties to be synchronised then you will have to do a comparison and synchronisation in two passes, once with extended properties disabled to sync the objects and then again with extended properties enabled which should just then correctly sync the extended properties. Sorry, I know it is not great, but we are looking into a fix for this at the moment which will hopefully make it into the next release of SQL Compare.
Regards
Jonathan
-Project Manager
-Red Gate Software Ltd
I'll try the 2 pass approach, since it'll only be done during an update the extended time needed shouldn't be too much of a concern
Thanks, let us know how it goes or if you have any more problems.
Thanks,
Jonathan
-Project Manager
-Red Gate Software Ltd
Here's my final code
I could have put the fudge into the 'SynchroniseSchema' method to bring everything into a more oop style, but in this case I decided to keep the fudge separate so it's easy to see what needs changing when the issue is fixed.
Thanks for all your help You've been very speedy and hit the mark every time with the problems I've had