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
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
SQL Server and OLAP For Navision
Stefanie
Member Posts: 2
Normally, these version (SQL for Navision) allows to create the database in SQL Server 7.0,
after it's possible to create some OLAP cubes, but I never succeed in.
I explain my situation :
First, I had a problem with the TIMESTAMP field :
When I want to export my database from Navision (version 2.01)TO SQL For Navision (version
2.50).The database is correctly exported to SQL but a field Timestamp is created in all the table as a first key.
After, when I want to create a cube in OLAP Services, every link between the table is generated automatically between these fiels timestamp. My OLAP Cube is not valable
because these links are false. I'm stopped there.
Now with the new version of SQL For Navision, the Timestamp problem seems to be resolute.
But when I want to generate my cube, I have these message :
"it's impossible to open the Table CRONUS France SA of the database ....."
Have you got some informations about the way to create some cubes? Have you got these problems? If is the case, how do you resolve?
after it's possible to create some OLAP cubes, but I never succeed in.
I explain my situation :
First, I had a problem with the TIMESTAMP field :
When I want to export my database from Navision (version 2.01)TO SQL For Navision (version
2.50).The database is correctly exported to SQL but a field Timestamp is created in all the table as a first key.
After, when I want to create a cube in OLAP Services, every link between the table is generated automatically between these fiels timestamp. My OLAP Cube is not valable
because these links are false. I'm stopped there.
Now with the new version of SQL For Navision, the Timestamp problem seems to be resolute.
But when I want to generate my cube, I have these message :
"it's impossible to open the Table CRONUS France SA of the database ....."
Have you got some informations about the way to create some cubes? Have you got these problems? If is the case, how do you resolve?
0
Comments
I did same labs with OLAP Server and a C/SIDE database some months ago. One thing I discovered is that You have to create a table with dates structured in the way that the date tables in the same way as in example files shipped with MS OLAP Server.
You have to decide in what way to insert records in this table. Perhaps when You set up accounting periods?
After created the table it MSOLAP worked fine togehter with Navision on C/SIDE. We are now running on SQL Server but we have not Yet testet OLAP Server together with the Navision data in the SQL Server.
I don't know if that was an answer to Your question....
//Lars Westman
http://www.linkedin.com/in/larswestman