I’ve read somewhere (I don’t remember where) that I can restore on SQLServer a native DB backup. Is that possible and if yes, How? Thanks, Alessandro
quote:
I’ve read somewhere (I don’t remember where) that I can restore on SQLServer a native DB backup. Is that possible and if yes, How? Thanks, Alessandro
Originally posted by a.cavalieri - 2005 Sep 02 : 11:27:35
It’s easy. Just create new database with finsql client and restore (with Navision client) fbk backup file. BostjanL
Technical that’s possible - but regarding to performance, this is not that easy (frankly spoken this is hell-on-earth) Please search the forum for “SQL Performance” and you’ll find plenty advice!
Yes, it’s so simply than backup-restore. BUT before that, You must use the upgrade toolkit to test your databse and to find any problem (bad dates, …) For performance, depending on hardware, Numbers users, database size, … I migrate to sql server 3 months ago WITHOUT problem
quote:
must use the upgrade toolkit
Not necessarily. You need the “Upgrade Toolkit” basically when moving from one version to another, e.g. from 2.60 to 3.70 … only in case of problems it could be useful. To just change the db engine, you could do it by Backup & Restore, but then you have to … … change locking mechanisms and orders … change filter statements … change keys and sift settings … change processes … implement general db maintenace plans … implement proper backup strategy (full/diff/trans) … implement index maintenance plans … implement statistic updates … monitor/change disk i/o … monitor/change cpu usage (affinities) … & more … Actually, after changing to SQL Server you need to monitor your system very careful to detect problems soon - and fix them! SQL Server is a “high end” database and requires much more attention than the native db …
Its important to realize that every implementation is different. Geofry did a conversion of a mid sized database, with a fairly decent sized server, and luck has it it seems to have gone quite smoothly. But from those posts, I am guesing that you have done approcimately 1 conversion [V] thats just not enough to base a technical opinion on. And its not just dependent on users adn database size, more important is what those users are doing. A 20 user system on SQL, where the 20 users are entering and posting large invoices with lot tracking, dimensions, and generating production orders, could be a killer for SQL, where in another situation, a 100 user system might be nothing. Yes there are cases when you can do a very straight forward SQL upgrade, but its crazy to bet on it. I think Joergen has done this more than once or twice, and I would be confident in takign his advise. Yes you can do a backup restore SQL conversion, but there is a lot more to getting that systme running properly.