There are various post on this forum addressing SQL2005 and its issues. I mainly had problems with security and windows logins. Here, in brief, are the steps I followed to make it work:
Before: SQL 2000, Navision Client v4 SP2 18.104.22.16811, Navision 3.70A database
After: SQL2005, Navision Client v4 SP2 4.02.23099, Navision 3.70A database
The above steps are just a summary and believe me I went through a lot of hardship to come to this conclusion. So some of you may have done it first time but others may still be trying to figure it out. Hopefully this helps. Seems pretty straight forward now that I read it
I tried the FBK but this is much slower (many hours to restore) and requires your Log file to be huge if you have a database thats bigger than 20gig. I found that SQL backup is far quicker.
However, I did not check the SIFT triggers. Are they compiled differently on SQL2005 or is it to do with the Client. Ideally I would not like to go the Navision backup/restore route purely because of the time that it takes. If I can survive by just turning MaintainSIFT off then On to recreate the triggers then I will be happys - unless of course simply compiling the object does the trick?