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
- 266 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
Performance Copmarison SQL-FDB databases
emkpro
Member Posts: 47
Hi, I was wondering which database is better for navision,
also, what if I am working with huge databses. about tera bytes in size
canb SQL server support those ?
also, what if I am working with huge databses. about tera bytes in size
canb SQL server support those ?
//EMK\\
0
Comments
Each server have pro and cons. I think, that there was some discussion about it. Try search.
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
If you work with HUGE size of database, I suggest you to use MS.SQL 2000 Database.
Its size limitation is your overall harddisk capacity. Using Filegroups in SQL Server you aslo can put your database in several HDDs...
Hope this helps,
Jemmy
Keep in mind the following when you investigate SQL Database and Navision option.
1. SQL Server does very well with handling appropriately designed VLDBs.
2. Terabyte sizes would place you in that range of VLDB
3. As the size of the database grows, so will the probability that design limitation in the application or the application's database architecture will be encountered.
4. Navision, as an application was originally designed to work with their own database, therefore the investiment in Load Testing, Performance Optimization and overall architecture most likely has been placed into the product running on the smaller Proprietory database.
5. Navision is basicaly a Fat Client with the application logic, constraints and most validation rules in the application - so don't look to the database to allow you to adapt to growth in size or overhead to your processing.