Initializing NOT NULL fields?

megawavez
Member Posts: 133
Hi,
We are doing a data migration and I'm looking into using SQL scripts to copy the data over from the old database to the new one. In looking at the table definitions, it looks like Navision does not provide default values for fields, so if I do a SELECT INTO from another database, I'll have to provide a value for every field in the destination database (ie list out each field and set to '' or 0).
Does anybody know of a way around this? Maybe some tool to automatically populate NOT NULL fields with '' or 0?
Anyway, probably can't be done, but just wanted to ask anyway.
Thanks,
M
We are doing a data migration and I'm looking into using SQL scripts to copy the data over from the old database to the new one. In looking at the table definitions, it looks like Navision does not provide default values for fields, so if I do a SELECT INTO from another database, I'll have to provide a value for every field in the destination database (ie list out each field and set to '' or 0).
Does anybody know of a way around this? Maybe some tool to automatically populate NOT NULL fields with '' or 0?
Anyway, probably can't be done, but just wanted to ask anyway.
Thanks,
M
0
Comments
-
You can use the "Maintain defaults" option in File-Database-Alter-Integration to create defaults for all fields. Else you need to enter empty string or zero into each field.
But, I hope that you know that not all data can be just "copied" from old DB into new one...0 -
Thanks, exactly what I'm looking for!
We'll definitely need to go back through the data, but this will greatly speed the migration process.0 -
megawavez wrote:Thanks, exactly what I'm looking for!
We'll definitely need to go back through the data, but this will greatly speed the migration process.
What version are you upgrading from/to.
You may find that the time you save in getting the data moved is completely wiped out by having to completely re-write the update routines outside of NAV. Unless of course you are in a tight conversionwindow, and must do it out side of Navision.
Good luck, and let us now how this progresses.David Singleton0 -
David Singleton wrote:megawavez wrote:Thanks, exactly what I'm looking for!
We'll definitely need to go back through the data, but this will greatly speed the migration process.
What version are you upgrading from/to.
You may find that the time you save in getting the data moved is completely wiped out by having to completely re-write the update routines outside of NAV. Unless of course you are in a tight conversionwindow, and must do it out side of Navision.
Good luck, and let us now how this progresses.
Upgrading from a heavily customized version of 2.6 (1400 modified objects) with it's own manufacturing module to Nav 5.0. I'm trying to get rid of as many customizations as possible.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions