Home
Login
Sign Up
Profile Options
Tools
Edit Profile
Manage all aspects of your profile here including demographics, emails, notification settings, etc...
Change Password
Begin the password change process
Email Subscriptions
Manage your opt-in/opt-out email subscriptions
View Profile
View your profile - what other's see
Sign-out
Sign out of this community
1-800-819-1190
Contact support line
Smart Connect
Connect with others and manage various member options
View QR Code
View your profile QR Code - Connect and or share your contact information
Tour Page
Take an interactive tour of this page
Knowledge Base
Visit the knowledge base for more info
Insights
Member reporting and analysis
Terms of Use
Cookies
Privacy Policy
Contact Us
Help
 
 

Site Menu

Forum | Message
Bringing Lawson On-premise. Converting from AIX/Windows environment with Oracle DB to Windows with MS SQL DB. Any Lawson customers have any experience with this? Looking for insight on how to roadmap this process and develop cost and schedule.
Travis Logsdon, PMP, LSSGB InforUsers CloudSuite Announcements
BC:

Question:

Article:

Bringing Lawson On-premise. Converting from AIX/Windows environment with Oracle DB to Windows with MS SQL DB. Any Lawson customers have any experience with this? Looking for insight on how to roadmap this process and develop cost and schedule.

Categorized as:

On-premise implementation
Database conversion

Delivered Read
On-premise implementation
Database conversion
2
527
Latest msg: There are differences between the ORACLE DB Characteristics and the SQL DB Characteristics that need to be accounted for. Like dates and integers, ma... from Kent Jacobson, on 11/20/2018

Comments (2) (Descending Chronological Order)
There are no comments at this time, be the first to comment

Kent Jacobson
BC:
There are differences between the ORACLE DB Characteristics and the SQL DB Characteristics that need to be accounted for. Like dates and integers, making this a not so simple task.

Using the internal Lawson utilities like expsysdb/impexp which creates a flat file from the source productline that can be used to import into the target productline. This requires you to have an operational Lawson Environment (LSF) with attached productlines at the exact same version level; one  Read more...attached to ORACLE and one attached to SQL. If you data is large, this can be a long running process and may jeopardize your desired down-time.

At ClearSky/TeamAbsolute, our developers have created what we call the MIGRATE.S3 which migrates Lawson data from one ORACLE to SQL outside of the Lawson environment. This is done at the data base layer resulting is high-speed migration with the target data base in Lawson ready format. Depending on who you are currently hosted by, this tool can make this migration pretty easy. Show less...
2
Darrin Michael
BC:
yep
1

Online