Database conversion log file issue with SQL 2005

slowhandfan
Member Posts: 56
I have a customer running Nav 4.03 BL=23305 on SQL 2005. I need to upgrade them to 4.03 BL=25143 so their Windows 7 work stations can run fat client. It is a 57 gig navision database.
The SQL log file cannot be set to unrestricted growth. They have plenty of disk space, but I cannot change the log file max size beyone 2 gig (2,097,152) for love or money. If I change it, it just changes it back to this max size.
When you try to open the database with the upgraded client, he tells you he must convert the database(we expected that), and it fails part way through item ledger entry because the log file is full.
I have read the other threads, surfed the internet, logging is set to simple,etc etc....
Is there anyway to make SQL2005 accept a larger log file(ldf). We have 160 gigs to dedicate to it, but SQL 2005 will not accept anything larger than 2 gig.
Is there a fix that can be applied to SQL 2005, or a servioce pack maybe? Does anyone know a way out of this?
Are there any SQL 2005 options or is change to enterpise edition to 2008 the only way out?
Thanks in advance for you help........ 911
Scott (aka Slowhandfan)
The SQL log file cannot be set to unrestricted growth. They have plenty of disk space, but I cannot change the log file max size beyone 2 gig (2,097,152) for love or money. If I change it, it just changes it back to this max size.
When you try to open the database with the upgraded client, he tells you he must convert the database(we expected that), and it fails part way through item ledger entry because the log file is full.
I have read the other threads, surfed the internet, logging is set to simple,etc etc....
Is there anyway to make SQL2005 accept a larger log file(ldf). We have 160 gigs to dedicate to it, but SQL 2005 will not accept anything larger than 2 gig.
Is there a fix that can be applied to SQL 2005, or a servioce pack maybe? Does anyone know a way out of this?
Are there any SQL 2005 options or is change to enterpise edition to 2008 the only way out?
Thanks in advance for you help........ 911
Scott (aka Slowhandfan)
0
Comments
-
Not sure where your issue is, but SQL 2005 is not limited to a 2 GB log file size. Have you tried increasign the file from SQL Management Studio? Or T-SQL?There are no bugs - only undocumented features.0
-
-
Could the log-file be placed on a FAT32 partition? It has a 4gb filesize limit, but I don't know if it is related...Regards
Peter0
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