Share
ReportI have question about dropping non-clustered index in D365 BC. will it affect the accuracy of the data?
Thank for your help
You’re offline. This is a read only version of the page.
25
I have question about dropping non-clustered index in D365 BC. will it affect the accuracy of the data?
Thank for your help
My approach would depend a little on what table you have been dropping indexes on.
If it is on a table in the base application you can recreate the index, but try to give it the same name as it had originally.
If it is in a customized table my approach would be to uninstall and then install the extension that the table is a part of.
Thank for responding,
The situation here is I already drop non-clustered index in system.
The only thing I care about that I must restore DB or just re-create non clustered index
If you want to drop a non clustered index in a Business Central database i would recommend you do it by changing the maintain on SQL property on the index instead of doing it directly on the SQL server.
Please see the doc in the link.
Does any one else who familiar with this, please give me some advice
Thank for your respond
Ok
Yes please follow the best advice from the Link I have shared and act accordingly, which is best for you DB, also I would recommend do the activity on Test DB first same replica of your source DB.
Thanks.
thank for your respond
Yes. my organization using on Premium version.
you mean I can re-create non-clustered index instead of restoring database, right?
Hi,
Are you using OnPrem version?
Rebuilding an index drops and re-creates the index. This removes fragmentation, reclaims disk space by compacting the pages based on the specified or existing fill factor setting, and reorders the index rows in contiguous pages.
Source : www.beyondtrust.com/.../reorganize-and-rebuild-indexes-in-database.htm
Thank for your responds.
After dropping non-clustered index. the query take more time to respond
Can I just easily re-create the index again depend on the previous structure instead of restore database
Hi Hoang_NguyenQuoc ,
Disabling a clustered index has additional effects. The data in the table still exists, but will be inaccessible for anything other than a drop or rebuild operation. All related nonclustered indexes and views are also unavailable. Foreign key constraints that reference the table are disabled. Queries against the table will fail.
Disabling a nonclustered index will deallocate the index pages – the space is freed in the database.
The biggest difference between disabling and dropping a nonclustered index is whether the index definition stays around.
To disable in index, issue an ALTER INDEX command.
Source : docs.microsoft.com/.../disble-enable-indexes-vs-drop-recreate-during-bulk.html
#1
Sohail Ahmed
2,655
#2
Mansi Soni
1,574
#3
YUN ZHU
1,453
Super User 2025 Season 1
All responses (
Answers (
