Upgrade only some companies

Djou2424
Member Posts: 76
Now that we can't backup/restore only a few companies, is there a way to do an upgrade for some of the companies at one point and do the rest at a later date?
We have a client that we are upgrading to 2013R2 that has 133 companies.
We would like to be able to split the upgrade over 2 or 3 week-ends, doing half or a third of the company at a time.
Is it possible?
We have a client that we are upgrading to 2013R2 that has 133 companies.
We would like to be able to split the upgrade over 2 or 3 week-ends, doing half or a third of the company at a time.
Is it possible?
0
Comments
-
You can only do this as a separate database. Not on the same database.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
Have you considered turning this into a multi tenant solution?
http://msdn.microsoft.com/en-us/library/dn271673(v=nav.71).aspx
This is one area where a multi tenant solution could be useful - multiple company databases with one application database.
"Tenants and Companies
When you have upgraded your application and the data, you have a database that has the same number of companies as you had before the upgrade. In Microsoft Dynamics NAV 2013 R2, this database is considered a tenant. This does not mean that you have to turn your solution into a multitenant deployment. But it means that you can if you want to.
For example, your Microsoft Dynamics NAV deployment in the earlier version consisted of a database that has 20 companies. In other words, you support 20 companies that all share the same application functionality. In this example, the companies are separate companies that have nothing to do with each other except that they are supported by you in one database. In Microsoft Dynamics NAV 2013 R2, you can choose to extract the application-wide tables into a separate database and keep the data for all 20 companies in the original database. This becomes a single-tenant business data database. Then, you can choose to split the business data database into one for each company so that you run a truly multitenant environment. The application is stored separately in the application database, and you maintain application functionality centrally. When you modify the application, you make the changes available to one tenant at a time. As a result, if something goes wrong, all other tenants are not affected.
Compare this to earlier versions of Microsoft Dynamics NAV where a database could contain several companies. These companies could be related or not, but they would all use the same application and write to the same database. Also, when you modified the application, it would affect all companies immediately. So if something went wrong, all companies would be affected."David Machanick
http://mibuso.com/blogs/davidmachanick/0 -
The database has 133 companies, and they are all related with each other.
When we deploy a modification, we have to do it for every company at the same time.
The reasons why I ask the question are:
- Split the upgrade over 2 week-ends to reduce the down time for the employes
- So far we have been unable to upgrade from 2013 to 2013R2. Upgrading from 2009 to 2013 went fine, but we are getting some unexpected sql errors when we upgrade from 2013 to 2013R2. We are able to upgrade if we only keep a couples of companies in the database (we've tried 2, 10 and 15). So splitting the upgrade in multiple phases, a few companies at a time could have been a work around.0 -
This is what the multi tenant structure does.
You have one set of application code applied to all the databases.
You end up with a more manageable SQL Server because you have 133 companies spread out among multiple databases.
You should be able to split your companies in the old version into different databases, then upgrade them and merge them into your multi tenant solution - one common codebase for all 133 companies.David Machanick
http://mibuso.com/blogs/davidmachanick/0 -
But if we split them into multiple databases, this mean that if they have external software that read data from the SQL tables, those software will need to be modified as well to go read the data in different databases based on the companies they need the data from?
Same with customization that was done to go write data in multiple companies from 1 company.
I will go read more about multi-tenants but I doubt this is something that would be useful for that client.0 -
You can't go into multi-tenant solution until you upgrade to NAV2013 R2 first.
In order to do that, the only way he can do this is by having a old database and NAV2013R2 database and upgrade one company at a time.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0
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