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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 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
Options
How to decompress BLOB data from c# for a Navision 2009R2 DB
mheijkant
Member Posts: 14
Has anyone found out what kind of compression Navision uses on blobs in Navision versions from 2009R2 downwards.
Saw an article on it that's only applicable to 2013 and above
https://devch.wordpress.com/2014/01/21/ ... revisited/
In this article its explaned to do the following:
In the case of these metadata fields, the NAV Compressed Blob-Type magic number is 0x02457d5b (hex).
In order to use the standard .Net DeflateStream to Decompress,
just throw away those first four magic-number bytes and then process the rest of the stream with DeflateStream as usual.
So for Navision 2013 this works fine.
Looking at BLOB fields from within SQL, the NAV 2009R2 Compressed Blob-Type magic number is 0x01447C5A (hex).
But using the same decompression code with these "magic numbers" doesn't seem to work.
Searching for it for a while and it looks like its something of a company secret.
By the way, I dont want to change the navision blob compression property to No.
Who can help me solve this riddle.
Saw an article on it that's only applicable to 2013 and above
https://devch.wordpress.com/2014/01/21/ ... revisited/
In this article its explaned to do the following:
In the case of these metadata fields, the NAV Compressed Blob-Type magic number is 0x02457d5b (hex).
In order to use the standard .Net DeflateStream to Decompress,
just throw away those first four magic-number bytes and then process the rest of the stream with DeflateStream as usual.
So for Navision 2013 this works fine.
Looking at BLOB fields from within SQL, the NAV 2009R2 Compressed Blob-Type magic number is 0x01447C5A (hex).
But using the same decompression code with these "magic numbers" doesn't seem to work.
Searching for it for a while and it looks like its something of a company secret.
By the way, I dont want to change the navision blob compression property to No.
Who can help me solve this riddle.
0