Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics RMS (Archived)

Moving Dynamics RMS 2.0 database from desktop to server

Posted on by 40

 Hi,

 

We are looking to acquire a server for our small operation. We currently have RMS on one of our desktop computers and the POS peripherals are on the same computer. When we upgraded our RMS software from 1.3 to 2.0 we had a lot of issues, so we just wanted some input, advice, comments, etc on what we might need to look for in acquiring the server, and what we would need to do to move the database to the server, while still having the peripherals on the client desktop.

Any input would be much appreciated.

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Re: Re: Moving Dynamics RMS 2.0 database from desktop to server

    The periferals shouldn't care that the back end database has moved, since they interface with the front end SO POS on the local machine. 

  • Reg James Profile Picture
    Reg James 40 on at
    Re: Re: Moving Dynamics RMS 2.0 database from desktop to server

     So essentially there is nothing to worry about since we can still use the setup we currently have while we sort out the server.  Anything to worry about regarding the peripherals (printer, barcode scanner, etc.)?

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Moving Dynamics RMS 2.0 database from desktop to server

    This is an oversimplified approach, but it can be this easy.

    1. on the existing computer, SO Admin - Daabase - Backup to a .bck file on a local drive
    2. copy the .bck file to the new computer
    3. install RMS with SQL or just any SQL server of your choice on the new machine
    4. create database on new computer and restore .bck file
    5. on existing computer, repoint SO Admin - File - Configure to open database on new computer

    I also like to run the following commands on the new computer after creating a new database:
    select name from sysfiles
    backup log <databasename> with truncate_only
    dbcc shrinkfile(<databasename>_log,2)
    alter database <databasename> set recovery simple
    alter database <databasename> set auto_close off

    There can be many reasons why this simple approach may need extra help to work,
    but you can always present those problems to the forum for solution,
    and you can still use your local database until you get the new one working.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans