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
- 270 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
NAV 2013 R2 SQL ERROR ON MODIFY FIELD INDEX
MrMnavD
Member Posts: 3
I'm a computer science guy, on my company we already have installed dynamics nav 2013 r2 on the server. It works fine but, yesterday one of the programmers came with this bug. When we replicate it we found that it corrupts the entire database, and we have to restore it to an early point.
What he did was delete 3 fields on a table, a custom table, 50000, not a nav standard table, after he delete those fields he rename those to and finally change the index of the fields. What happens was a SQL error shown on the image below. This error corrupt the entire database and we have to restore it from a previous backup.
If anyone knows what happens here any help will be helpfull to solve this problem. We replicate it like i said. The SQL Server is 2008 r2 on a windows server 2008 r2
Sorry for my english :roll:
What he did was delete 3 fields on a table, a custom table, 50000, not a nav standard table, after he delete those fields he rename those to and finally change the index of the fields. What happens was a SQL error shown on the image below. This error corrupt the entire database and we have to restore it from a previous backup.
If anyone knows what happens here any help will be helpfull to solve this problem. We replicate it like i said. The SQL Server is 2008 r2 on a windows server 2008 r2
Sorry for my english :roll:
0
Comments
How is "Prevent data loss from table changes" parameter set?
Error:The new Name 'Transfer Blocked' is already in use as a column name and it will create an invalid duplicate.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
The 'Transfer Blocked' has an index and after delete the other fields we reindexed this field. And the error ocurrs.