Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 270 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
SQL Server database only had 1 x mdf
guardioo
Member Posts: 13
I had create the database in SQL server.
Unfortunately after few months of using it,
I only see having 1 x database.mdf
When i try to expand database and having 1 x database_2.ndf,
It doesnt allow me to create.
Do you guys have any idea on this?
Unfortunately after few months of using it,
I only see having 1 x database.mdf
When i try to expand database and having 1 x database_2.ndf,
It doesnt allow me to create.
Do you guys have any idea on this?
0
Comments
NAV databases are created from within the Classic Client, not Mgt studio.
Expanding databases works automatically for most installations. Extra files are only usefull in rare situations in very large implementation.
If you only see a mdf file than normaly the customer started off with a cronus database which for whatever reason only has an mdf file.
Not sure what you mean by this.
One thing I've noticed with NAV 2013, is that the W1 CRONUS has only the 1 data file (*.mdf) but the NAV version has both the (*.mdf) and the (*.ndf). Not that it matters.
Although they should.