Difference between backup from NAV and SQLserver

jaiverma2k2

What is differnece in backup taken from NAV front end and MSSQL back end.

I had restore a backup taken from both (SQL & NAV), i found the same. but i heard there is some difference, need to know what? please help

Regards,
Jai :?:

p_s_sundar

jaiverma2k2 wrote:

What is differnece in backup taken from NAV front end and MSSQL back end.

I had restore a backup taken from both (SQL & NAV), i found the same. but i heard there is some difference, need to know what? please help

Regards,
Jai :?:

If you know sql side (Server) you can use SQL Backup directly paste otherthan you can restore the Navision Backup.

jaiverma2k2

That mean there is no difference, i can use anyone of them.

garak

SQL -> u make a whole databasebackup with all datas and all objects. The creating and the restoring of these backup is fast, these backup can only be used with SQL. With these option u are very flexible because u can create some maint. backupjobs to create the backup (full, different, log) at worktime

Native -> u can make a whole backup, or only a databackup without Application objects (like forms, reports, and so on). The creating can be fast but the restorung can take some times (sometimes a whole day or two) if the database is very large and there are many datas and indexes. These Backup can only be used with native. U can use this for example, if u need a testdatabase on a single computer where no sql server is runnung, only the NAV Client is on this computer. With this backupoption, u create the backup, for example, at night, so that there are no locks for the user. but the native backup checks the datastrukture, these does the sql not do. So, the SQL is "stupid" vs. NAV backup

So read the THIS before.

jaiverma2k2

we have a nav5.0 running with SQL server, so should i go with SQL Server backup? (this backup can be schedule).

is there any scheduler which can be used in NAV (running of SQL server) for taking a backup?

which type of data structure it checks, if we take a backup through NAV

:?:

ara3n

Most of our clients with large sql db use sql backups only. As long as you don't mess with data directly on sql, Your sql back will work fine.

stryk

The difference is actually this:

A "native" C/SIDE Backup just exports the plain data and meta-data (Objects) - nothing else. No indexes, no SIFT, no SQL Views, no add. SQL Indexes, no Procedures, etc..
A SQL Server Backup exports all occupied Pages 1:1 - including all & everything.

Thus, when restoring a native Backup some SQL stuff could be missing, causing trouble. Secondly, the restore is quite time-consuming as all indexes & SIFT/VSIFT a recreated from the scratch.
With restoring a SQL Backup you get the database EXACTLY as it was before, the restore is much faster.

The only reason for using native Backups is IMHO to only export ONE company out of many, with SQL Backups this is tricky to accomplish.

Some claim that a native Backup uses less diskspace. True, it's just an "extract". But if diskspace is an issue you could use 3rd party software or SQL 2008 EE to use SQL backup compression, too.

Regards.
Jörg