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
NAV 5.0 SQL vs. ODBC
OldNavDog
Member Posts: 88
Hi, Experts!
I have a NAV 5.0 SP1 SQL-based Installation running on a 64-bit Server 2008 R2 backend that I am trying to set-up the NAV ODBC Driver, but to no avail.
It seems like the Driver Setup gives lip-service to working with a Server-Based Database; but it really DOESN'T (???)
Everything goes fine on the Driver Install and launching (through WoW64) the 32-bit ODBC setup "Console".
BUT, when I try to create a System (or User) DSN to NAV, as soon as I place a Server Name into the appropriate Field, the "Database" Field becomes un-editable.
I have tried all manner of ways to "phrase" the "Server Name" (the SQL Server is not only in the same Domain, it is on the same physical Server). "servername" (only), "servername.local", "domain\servername", IP Address, you-name-it, I've probably tried it.
I have read that this is sometimes caused by a "Allow Remote Connections" Property not being set on the Database in SQL Server; but this is not one of the "Express" versions of SQL Server, so I don't think that even applies (nor can I find that Property in SQL Management Studio).
HELP!
I have a NAV 5.0 SP1 SQL-based Installation running on a 64-bit Server 2008 R2 backend that I am trying to set-up the NAV ODBC Driver, but to no avail.
It seems like the Driver Setup gives lip-service to working with a Server-Based Database; but it really DOESN'T (???)
Everything goes fine on the Driver Install and launching (through WoW64) the 32-bit ODBC setup "Console".
BUT, when I try to create a System (or User) DSN to NAV, as soon as I place a Server Name into the appropriate Field, the "Database" Field becomes un-editable.
I have tried all manner of ways to "phrase" the "Server Name" (the SQL Server is not only in the same Domain, it is on the same physical Server). "servername" (only), "servername.local", "domain\servername", IP Address, you-name-it, I've probably tried it.
I have read that this is sometimes caused by a "Allow Remote Connections" Property not being set on the Database in SQL Server; but this is not one of the "Express" versions of SQL Server, so I don't think that even applies (nor can I find that Property in SQL Management Studio).
HELP!
Experience is what you get, when you don't get what you want. --Anon.
0
Comments
if you are on SQL just use the ODBC that comes with it.
N/ODBC is for the native database
http://www.BiloBeauty.com
http://www.autismspeaks.org
But holy God! Why even HAVE (and discuss, however briefly) a "Server" field in the NODBC Driver???
Sigh.
One sentence left out of documentation == 10 wasted hours researching and experimenting...
:x
Thanks again, though. I can see where you would be right... :roll:
Because N/ODBC does work with a database server. Just not with SQL Server.
http://www.BiloBeauty.com
http://www.autismspeaks.org