Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Full Text Indexes cause process to fail

I think the ordering of the build process needs to be addressed. When I get latest on a local machine it looks like stored procedures are being added before the full text indexes they reference. Currently I am having to de-select any referencing objects, apply the full text indexes and then re-select the objects to be applied. Is there any chance this can be addressed in a future patch?

75 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Mike Birkett shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Jamie Burns commented  ·   ·  Report

    It's been a few years now, and this is still an issue.

  • db_brad commented  ·   ·  Report

    This is a deal breaker for us. If this is not fixed soon or some type of workaround presented, we can't go with this tool. Would love to, this is by far my favorite option.

  • nathan commented  ·   ·  Report

    Make an update for this. indexing first and sprocs should be last.

  • Ian commented  ·   ·  Report

    I agree - why do the build in an order that is going to fail? If it's because they cant be done transactionally, then just do them at the start of the script and it it fails, abort the rest of the script.