-
The most important thing is to use the most recent build of your NAV version to make sure it is supported to run with SQL 2008. If you are just migrating a "normal" NAV database, then it is basically "detach DB 2000 - copy to SQL 2008 - attach DB 2008" - then adjust config (Compatibility...
-
The most important thing is to use the most recent build of your NAV version to make sure it is supported to run with SQL 2008. If you are just migrating a "normal" NAV database, then it is basically "detach DB 2000 - copy to SQL 2008 - attach DB 2008" - then adjust config (Compatibility...
-
I've a problem, who can help me? I've a SQLServer table sorted by a type code field that show the following records A A2 A3 B B2 C Why the same table called like a temporary table, containing the same record and ordered with the same key, show records ordered like the following? A B C A2 A3 B2...
-
Hi friends I have changed the back end from Nav native DB to SQL sever 2005 . I open the sql DB and check the flow fields in customer ledger ex:- Amount, Original Amt. (LCY), Remaining Amt. (LCY), Original Amt. (LCY) . there are not there where can I find them . how this fields are exsist . for the purpose...
-
We have 8 Citrix servers. 6 of these with 4.02 client with one of the later hotfixes. 4.03 client on the remaining 2 citrix servers because they are newer. It works. No issues so far, I know its not purist but I so far I have no reason to doubt mixing 4.02 & 4.03. I reckon I will schedul in the 5...
-
Can you mix clients like that OK? In any case, why not just put 5.00 executables now. If you are upgrading anyway, surely thats the best so you don't need to do it again later. if you are not ready to risk 5.00 then at least put 4.00 SP3 everywhere, and not just on some work stations.
-
Its what Microsoft advised me to do. Quite a long story and would be happy to discuss again. I have some other posts on this websitre from a while back relating to plan guides, also check http://www.mibuso.com/forum/viewtopic.php?t=16343&highlight=guide where it is also discussed. I am not a SQL...
-
3.7db, 4.02 clients (with some 4.03) & 4.03 stored procs installed, which I think is ok. I Am not going to upgrade the db to 4.03, going to jump straight to 5.0 later in the year. I will set it to 2005 compatibility for now. Thanks. But, I would still like to know if there are any experiences out...
-
[quote user="Nuno Maia"] David, During your error fix, were you able to run 3.70 with SQL 2005 ? [/quote] By the time I got it all working, I had already converted to 4.00SP3. But I don;t think there would be a problem with 3.70, and I will try that next time.
-
[quote user="Jörg Stryk"] Hi David! Once, I encountered similar problems; means that after a failed conversion of a database, I got the same error as you described. The problem is, that the column "securityoption" was added to $ndo$dbproperty with the first attepmt, after failure...