Null value in post processing operation

TRP

Hi RedGate Support

I am currently unable to get past the get changes operation in SC6. I have tried linking and unlinking the database but this hasn't helped.

I am struggling to find out exactly how to diagnose the problem based on the attached log file.

Any help will be appreciated.

Tom

Mike U

No worries at all. The only reason I mentioned a support ticket for this is that it's quite specific to your database schema. And I agree, from the sound of it SQL Source Control should have been able to handle having the table and schema dropped at the same time and figured out the dependency ordering correctly. But again, for us to fix some of these complex dependency ordering problems we do need access to your schema definitions.

A support ticket has already been raised for this problem, so someone from the support team should be in touch with you directly soon. If you ever do need to raise a support request, you can do that directly at https://productsupport.red-gate.com

TRP

Further to this I have uninstalled SC6 (and it has failed to reinstall), then installed it on another computer and am getting the same error again.

I have sent another error log via your feedback system. Can someone please look into this as the product is not functional at all at the moment.

Many thanks

Mike U

Looking at that log it looks like there's a problem with a full text index definition. Specifically, there's an ALTER FULLTEXT INDEX statement that references something (possibly the table, but more likely a specific column within the table) that doesn't exist. If you search your scripts folder for "ALTER FULLTEXT INDEX" you might be able to find the culprit.

If you need more help diagnosing the problem, then we'll need a copy of your scripts folder to figure out which objects are inconsistent - so that's probably best handled through a support ticket rather than on a public forum.

TRP

Hi Mike

The problem seems to have been because an unwanted table and corresponding schema was dropped at the same time. SourceControl worked fine once the schema was added back in. Then changes could be committed, the schema dropped again and that change could finally be committed.

I consider this a bug in so much as I expected SourceControl to figure out it needed to resolve the table drop first, then the schema. Do you agree or at least feel the error information could be more helpful?

Sorry I thought this was for raising a support ticket. As your products are so reliable I can't ever call raising a support request before. In future I'll find the right process for doing so!

Thanks

Tom

TRP

Thank you very much!