Typical database size increase after moving across to SQL

JamieBrown
Member Posts: 107
Hi guys,
We’re contemplating converting our native db (3.7 running on 4.03 exe’s) to SQL and was wondering if / how much the size of the database will increase?
Our database is currently 190GB (150GB used).
I’m guessing there’s a whole host of factors that would affect the size (no. of keys, optimisation level etc…) but if there’s a general rule to follow or if anyone has any experience with this I’d appreciate any info.
Thanks
We’re contemplating converting our native db (3.7 running on 4.03 exe’s) to SQL and was wondering if / how much the size of the database will increase?
Our database is currently 190GB (150GB used).
I’m guessing there’s a whole host of factors that would affect the size (no. of keys, optimisation level etc…) but if there’s a general rule to follow or if anyone has any experience with this I’d appreciate any info.
Thanks
0
Comments
-
on average sql db is about twice as big as native.0
-
That's before tuning indexes. Database sizes can be reduced dramatically by tuning indexes.0
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