Create a New DB and Restore the Production DB
Comments
-
Why would you want to do this?There are no bugs - only undocumented features.0
-
Andwian wrote:...And I observed that the DB file size is smaller than the old one...
Where are you observing this? If we are talking a SQL restore, then the new DB will be the same size as the old one. With a NAV restore it will be whatever size you create the empty database.There are no bugs - only undocumented features.0 -
Maybe he means "Database Used" :-k
If my database is 60gb with 85% used - Delete & Restore it would then show ..say 80% used.
That's because all the keys have been recreated & everything is optimized.0 -
Savatage wrote:Maybe he means "Database Used" :-k
If my database is 60gb with 85% used - Delete & Restore it would then show ..say 80% used.
That's because all the keys have been recreated & everything is optimized.
But only if you do a NAV backup/restore. I think he's looking at the SQL backup file size. But then we're all just guessing.There are no bugs - only undocumented features.0 -
Sorry for not getting back earlier.
I mean the *.mdf, *.ndf, and *.ldf file size in the windows program file, or Database | Alter.
For the DB Used, I think it would be grow with time, so it is useless to see the DB used.
I think DB Size could be grow, and the DB used % will be less again and again.
Anyway, is it nice to do the routine creating a new DB and restoring for the Production DB?Regards,
Andwian0 -
I see no reason. Why are you thinking this might be something to do?There are no bugs - only undocumented features.0
-
If it's not broke don't fix it.David Singleton0
-
That makes no sense, why would you do that? your mdf file would grow anyway... and in performance perspective its even worse if sql needs to enlarge the mdf file regularly. in fact its better to have a large file and size increase should happen as few as possible.
If your ldf is too large then you do something wrong reagarding log file backup...
So having smaller files will not not result in a performance gain, it might even decrase your performance.
However doing regular maintanance jobs such as index reorg/rebuild is what you should do for performance.David Singleton wrote:If it's not broke don't fix it.0 -
To keep the database 'fresh', you put in place proper maintenance. Watch this to learn about essential database maintenance on SQL Server: http://www.youtube.com/watch?v=0KbZkKdyZps0
-
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