You can always install the Server itself case insensitve as long as the Navision Database itself is case sensitve, any client after 3.60 can create the datebase with a different codepage from the one the server has as default. and if you are using an older version you can create the database elswhere with the correct codepage and then use detach/attach to install it on the other server.
But for the database itself, keep it case sensitve you get all kinds of errors if you dont.
We are wanting to make the Navision database case insensitive because we will be using a common database for our .Net web based application.
What types of errors do you get if the Navision database is case insensitive?
If we start a new Navision database with case insensitive, will we still have problems?
One problem you will have for sure is with the proprietary Navision 'Code' datatype, which is case sensitive. One of our customers had a corrupt database because they had entered data directly into the Navision SQL tables, and used lower case characters in Code type fields. Navision can't read lower case characters in Code type fields and it will shut down when it happens.
You can have the same problem with CODE fields in case sensitive databases.
What I would like to know is - providing we follow Navision data rules - is there any problem with a SQL Server database for Navision being case insensitive?
As far as I can see it should only affect SQL Server keys, joins, and where clauses.
Would filtering be affected by the database being case insensitive? Does Navision build SQL Server keys for filters?
Can you think of any time when you wanted to do a case sensitive filter on a text field? Usually with names, descriptions, cities, etc. youwould want a case insensitive filter.
I use 2 navision sql databases, case-insensitive, for more then 2 years (version 3.6 and 3.7). I've never found for these reason any problem in the application. I really prefer that way because filtering is easier (never even to think about the case).
The point that DenSter noticed about using lower case characters in code fields is true. Sql manager has no problem to look at the data in lower case, but the navision application will give an error. But this has nothing to do with the fact if you are using case-sensitive or not.
Comments
But for the database itself, keep it case sensitve you get all kinds of errors if you dont.
Sporri
What types of errors do you get if the Navision database is case insensitive?
If we start a new Navision database with case insensitive, will we still have problems?
http://mibuso.com/blogs/davidmachanick/
RIS Plus, LLC
What I would like to know is - providing we follow Navision data rules - is there any problem with a SQL Server database for Navision being case insensitive?
As far as I can see it should only affect SQL Server keys, joins, and where clauses.
http://mibuso.com/blogs/davidmachanick/
RIS Plus, LLC
Can you think of any time when you wanted to do a case sensitive filter on a text field? Usually with names, descriptions, cities, etc. youwould want a case insensitive filter.
http://mibuso.com/blogs/davidmachanick/
RIS Plus, LLC
I use 2 navision sql databases, case-insensitive, for more then 2 years (version 3.6 and 3.7). I've never found for these reason any problem in the application. I really prefer that way because filtering is easier (never even to think about the case).
The point that DenSter noticed about using lower case characters in code fields is true. Sql manager has no problem to look at the data in lower case, but the navision application will give an error. But this has nothing to do with the fact if you are using case-sensitive or not.
Francois
Consultant-Developper
http://www.CreaChain.com
http://mibuso.com/blogs/davidmachanick/