Database Version 105

FDickschat
Member Posts: 380
I came across a NAV 5 SP1 DB which has a database version no. 105 in ndo$dbproperty. The only ones in this area I know of are 93 (5.0 SP1), 95 (5.0 SP1 CU1) and then 120 (2009 RC1). Anyone knows what this is?
Maybe 5.0 SP1 CU2?
Maybe 5.0 SP1 CU2?
Frank Dickschat
FD Consulting
FD Consulting
0
Comments
-
FDickschat wrote:I came across a NAV 5 SP1 DB which has a database version no. 105 in ndo$dbproperty. The only ones in this area I know of are 93 (5.0 SP1), 95 (5.0 SP1 CU1) and then 120 (2009 RC1). Anyone knows what this is?
Maybe 5.0 SP1 CU2?
5.0 SP1 CU2 should be version 100. So I guess 105 is an update after CU2. Or more likely it is an early 2009 and someone did a manual down grade, but didn't do it properly. Having a higher version DB than the client is a bad thing, because Navision checks for lower versions to upgrade, but in many versions it does not care if its a newer DB version and allows you to run.David Singleton0 -
Hmm just checking
http://wiki.dynamicsbook.com/index.php? ... ers_in_NAV
120 was the first 2009 version. So really not sure what 105 is. Maybe a CTP version of 2009.David Singleton0 -
The customer runs a 5 SP1 executable on SQL2005. Will need to check which build this is.
Strangely opening this DB with a 2009 executable did not bring up the question whether you want to convert it but simply a SQL error that the column "enabledforserver" in ndo$dbproperty does not exist. So it seems the 2009 exe assumes (by the version no.?) that this is a 2009 DB.
David, do you know what the column "enabledforserver" is actually used for?Frank Dickschat
FD Consulting0 -
FDickschat wrote:The customer runs a 5 SP1 executable on SQL2005. Will need to check which build this is.
Strangely opening this DB with a 2009 executable did not bring up the question whether you want to convert it but simply a SQL error that the column "enabledforserver" in ndo$dbproperty does not exist. So it seems the 2009 exe assumes (by the version no.?) that this is a 2009 DB.
David, do you know what the column "enabledforserver" is actually used for?
Isn't that the flag to say that the SQL db is enabled for Nav middle tier (RTC) server?
So my guess would be that this came from a CTP version of 2009.
I recommend a Navision backup and restore into a clean DB. You can probably just change the db version to one lower than the EXE they are running, this can trigger a DB upgrade which in many cases will fix it, but isn't a guarantee. Dean McRae is probably the only person that would know for sure.David Singleton0 -
David Singleton wrote:Isn't that the flag to say that the SQL db is enabled for Nav middle tier (RTC) server?David Singleton wrote:So my guess would be that this came from a CTP version of 2009.Frank Dickschat
FD Consulting0
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