Comments on: An Explicit DROP INDEX is Not Allowed On the Index, Msg 3723

By: Steve Ognibene

Steve Ognibene — Wed, 17 Jan 2024 19:16:30 +0000

I am thanking you 12 and a half years later. Much appreciated!

By: ThomasLaRock

ThomasLaRock — Mon, 21 Sep 2015 17:43:00 +0000

In reply to Phil Gardocki. Thanks! Glad you found the post helpful.

By: Phil Gardocki

Phil Gardocki — Mon, 21 Sep 2015 17:38:00 +0000

Thank you later? I’ll thank you now!

By: ThomasLaRock

ThomasLaRock — Tue, 03 Mar 2015 15:35:00 +0000

In reply to Guest.

Yes, I understand the needs for altering table schemas from time to time.

However, what the OP (Ajay) was asking about here is the SYSUSERINFO table, which I believe is a system table for MS Dynamics. That is what led to my comment asking why they would need to make alterations against that table, because I wanted to know more about what they were trying to accomplish with Dynamics.

If you can provide a use case for altering this table in Dynamics, let me know! I’m always happy to learn new things.

By: Guest

Guest — Tue, 03 Mar 2015 14:56:00 +0000

In reply to ThomasLaRock.

Various reasons…say you need to change the length of a field being used as a primary key – you have to drop the index first, then change the field, then recreate the constraint. If you think about it, there are many reasons one would need to do something like this from time to time.

By: ThomasLaRock

ThomasLaRock — Mon, 26 Jan 2015 14:15:00 +0000

In reply to Ajay. Um, I suppose you might be able to do so, but the real question I have is why would you need to drop an index against that table?

By: Ajay

Ajay — Thu, 22 Jan 2015 06:29:00 +0000

Can we apply the above workaround for SYSUSERINFO Table ??/