Howdy, Stranger!
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
- 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
- 305 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Setting up a linked server - looking for tips and tricks
Resender
Member Posts: 119
OK, I got to setup a linked server in the following environment
*Windows 7
*MS SQL Server 2008 R2
*MS Virtual PC
We got a Virtual PC running Windows XP, and on that XP (called VIRTUALXP-88...) we got Navision Attain 3.6 installed.
The fdb file containing our database is not located on the virtual machines virtual hard drive (no pun intended) but on a secondary partition of our physical machine.
We run Navision either as a virtual application or in the virtual machine itself depending on what we are working on.
On the physical machine running Windows 7 we now want to create a linked server from the SQL Server to the Navision Attain one.
I've used the following:
Linked Server:Nav
Provider: Microsoft OLE DB Provider for ODBC Drivers
Data Source: VIRTUALXP-88...
Provider String: UID & PWD
Location:
\name_of_our_database.fdb
Catalog:
When I try to create it it runs into error,
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "NAV".
OLE DB provider "MSDASQL" for linked server "NAV" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". (Microsoft SQL Server, Error: 7303)
There people I could ask it inhouse but their on leave for another week or 2 and I need to resolve this.
Thank you for any input
*Windows 7
*MS SQL Server 2008 R2
*MS Virtual PC
We got a Virtual PC running Windows XP, and on that XP (called VIRTUALXP-88...) we got Navision Attain 3.6 installed.
The fdb file containing our database is not located on the virtual machines virtual hard drive (no pun intended) but on a secondary partition of our physical machine.
We run Navision either as a virtual application or in the virtual machine itself depending on what we are working on.
On the physical machine running Windows 7 we now want to create a linked server from the SQL Server to the Navision Attain one.
I've used the following:
Linked Server:Nav
Provider: Microsoft OLE DB Provider for ODBC Drivers
Data Source: VIRTUALXP-88...
Provider String: UID & PWD
Location:
\name_of_our_database.fdbCatalog:
When I try to create it it runs into error,
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "NAV".
OLE DB provider "MSDASQL" for linked server "NAV" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". (Microsoft SQL Server, Error: 7303)
There people I could ask it inhouse but their on leave for another week or 2 and I need to resolve this.
Thank you for any input
0
Comments
If I run the same query through the linked server it takes hours with no result.
To do this I had in the Provider opstions for MSDASQL, which apparently Microsoft OLE DB Provider for ODBC Drivers, I had to check Nestled Queries,Level Zero Only and Support 'Like' operator. From what I found their is an advisement to turn off Allow Inprocess but I haven't noticed much difference.(Off course then again haven't done much with it)