02.10.2006, 18:31 | #1 |
Участник
|
Adding index through SQL
Hello,
We have a very big table (close to 20 mil records now) and would like to add a new index there. Doing it through Axapta will take longer then if we would do it through SQL directly. Our operation is 24X7. Plan: 1. create that index on the table in a test environment, export the table. 2. create that index on that table directly in SQL on production environment ( using same naming convention) 3. import the project into Production environment. We hoped that Axapta will recognize that the index is already there and won't recreate it. Unfortunately, it didn't recoginze it and recreated it. Question. Is there a way to register that index with Axapta somehow, like for example, SQLDictionary table where all fields are saved? Is it possbile at all? I would appreciate any comments. Thanks, gb |
|
02.10.2006, 18:40 | #2 |
Участник
|
Axapta can not recognize, if it is own index. because while creating this index, axapta will always do re-create (because it is new)
I think not-re-create can be done only if you put whole application into to prod. BUT.. when this done - Synchronize always should be done (to be sure everything will work OK) |
|
02.10.2006, 18:48 | #3 |
Участник
|
I will try that. Synchronize is ok, because when you synchronize a table and there were no changes done to its structure including inexes, it won't rebuild the index. So, I guess the question is if it will accept that index as an existing one or will somehow realize that it was a change and will recreate it.
Thanks for the idea. Regards, gb |
|
03.10.2006, 01:55 | #4 |
Участник
|
Replacing the application folder and resynching the db drops that index and recreates it from scratch. It does basically the same way as simple import.
So the question remains. How does Axapta recognize that the index was added from SQL and not from Axapta. It almost looks like that there is some kind of info saved in a system table. Any suggestions are appreciated. Thanks, gb |
|
|
|