Jeff Moden (11/18/2016)
N_Muller (11/18/2016)
Jeff Moden (11/3/2016)
I don't know if you've ever read the following but it might give you some hints about why you might not want to drop the Clustered Index prior to loading your tables.[font="Arial Black"]https://technet.microsoft.com/en-us/library/dd425070(v=sql.100).aspx[/font]
I have a related, but slightly different problem. A C++ code writes data to database using OLE DB FastInsert and FastCommit. The process is similar:
1. truncate table
2. drop indexes
3. write data (C++ FastInsert and FastCommit)
4. recreate indexes
I tried changing from dropping and recreating the indexes, to disabling and rebuilding the indexes. Now the FastInsert fails. Is there a requirement for FastInsert that one cannot have indexes on the table?
If you disable the clustered index, you've disabled the table. 😉
Thanks. I just figured that out.