I have a problem when i want to restore database with sql server version. It's no problem when i restore with fdb version. Is there data range limitation in sql server?
Please help.
Thanx in advanced.
Values for datetime data types earlier than January 1, 1753 are not permitted in SQL Server. SQL Server rejects all values that do not fall within the range from 1753 to 9999.
Data type Range Accuracy
datetime January 1, 1753, through December 31, 9999 3.33 milliseconds
It is why the "migrate.fob" is used to check all date fields in the db when migrating from Native to SQL server. See the upgrade toolkit documentation for the Migration process...
You are? No, the backup you made is from Native DB, and now you are restoring it to the SQL... there is no chance to create such a date under SQL... And there is no NAV check for such a dates. It will allows you to post e.g. to 24.06.0001...
To enter a date < 1. Januar 1753 is not possible under SQL.
If you enter a date, for example 01.Dec.0030, the NAV client will show you an error.
Also in this case the native Server and der SQL Server works different.
Thats also the reason why in the Upgratetoolkit a batch exist for changing incompatible dates (migrate.fob).
you doesen't know from where your backup is?
mhm, if you have the SQL log activate, than you can find in the log is a database restored from a sql backup or is there only a database created and than there are many transactions after the creation (this could be a sign for a fbk).
But normaly you knwo from where the backup comes ....
Yes you are right, actually i receive the backup from other place, i just want to make sure that the backup comes from native or sql server. If the answer is no then it's fine.
But if we work with native and we have that such of transaction and we want to migrate to sql server......what should we do?
To migrate from native to sql read the manual on upgrade toolkit
Do you have search the forum?
Here a Quick step overview:
1) Download the upgrade toolkit
2) Read the migration documentation
3) Import the Migrate.fob
4) Run the objects from the migrate
5) Make native Backup
6) Create an Database with finsql -Client on SQL Server (read manual)
7) Import native Backup
8) now you have an SQL Server Database
9) Question: Database Login / Windowslogin
Databse -> (create Database user on SQL Server)
10) Create your maint. plans
these all test before on a TESTDATABASE and don't forgett a sql perfomance tuning (read post in subforum sql performance)
Answers
From Books online
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
If you enter a date, for example 01.Dec.0030, the NAV client will show you an error.
Also in this case the native Server and der SQL Server works different.
Thats also the reason why in the Upgratetoolkit a batch exist for changing incompatible dates (migrate.fob).
Next question is, how can I know that the backup is from Native or Sql Server?
Thanx again.
There is no way how to make difference between fbk from Native or SQL server...
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
mhm, if you have the SQL log activate, than you can find in the log is a database restored from a sql backup or is there only a database created and than there are many transactions after the creation (this could be a sign for a fbk).
But normaly you knwo from where the backup comes ....
Yes you are right, actually i receive the backup from other place, i just want to make sure that the backup comes from native or sql server. If the answer is no then it's fine.
But if we work with native and we have that such of transaction and we want to migrate to sql server......what should we do?
Do you have search the forum?
Here a Quick step overview:
1) Download the upgrade toolkit
2) Read the migration documentation
3) Import the Migrate.fob
4) Run the objects from the migrate
5) Make native Backup
6) Create an Database with finsql -Client on SQL Server (read manual)
7) Import native Backup
8) now you have an SQL Server Database
9) Question: Database Login / Windowslogin
Databse -> (create Database user on SQL Server)
10) Create your maint. plans
these all test before on a TESTDATABASE and don't forgett a sql perfomance tuning (read post in subforum sql performance)
Regards
Very helpful.