Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.7K 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
- 317 Dynamics CRM
- 110 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 385 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
Auto shrink error
napoleon
Member Posts: 15
Hi everyone
Can anybody assist here I created a database which is SQL logins based and restored a backup on it.
But the problem that i was getting was the log file was growing in seconds. I ended up having to kill the restore and do it in a more bigger harddrive.
The autoshrink option was ticked and when i went to the directory to check on the log file , the log file is still huge.
The error that i'm getting when i go FILE > Database > Alter is
"You cannot enter '2147483648 KB ' in Integer. The cursor is in front of the invalid character.
If a screenshot is required to look at this error please e-mail me on this address : - bongani@ngo.co.za
Thanks
Can anybody assist here I created a database which is SQL logins based and restored a backup on it.
But the problem that i was getting was the log file was growing in seconds. I ended up having to kill the restore and do it in a more bigger harddrive.
The autoshrink option was ticked and when i went to the directory to check on the log file , the log file is still huge.
The error that i'm getting when i go FILE > Database > Alter is
"You cannot enter '2147483648 KB ' in Integer. The cursor is in front of the invalid character.
If a screenshot is required to look at this error please e-mail me on this address : - bongani@ngo.co.za
Thanks
As simple as it can be, that how I like it!
0
Comments
Shrinking the log only gets rid of unused space up to the file size that you set in your database setup. If your TL contains lots of transactions, then the log file needs to be as big as it needs to be to hold those transactions. So if you have 2GB of transactions in your log, then that file will need to be at least 2GB. If you set your log file to be 150MB, and it contains 10MB of transactions, then shrinking the file will only shrink it down to the 150MB. If you have a lot of unused file space in your log, you can set the file size to a smaller size and try again.
Open Enterprise Manager and expand the console root until you expose your database, and the select it. Then click on View, Taskpad. In there you can see a visual representation of the files, and how much of it is used.
What you can do to purge the TL is run a full SQL Server database backup (including a TL backup) and that will get rid of all committed transactions from the TL. Read Books Online (Start, All programs, MS SQL Server, Books Online) for information on how to run backups.
By the way, if you are talking about a development or test database, you should really set the recovery model to simple. This makes it so that the TL is only used for active transactions.
RIS Plus, LLC