Navision 3.1 and Nav 2005

ccbryan63

Hi... I have a client running Nav SQL, version US 3.01.B (3.60). Two years ago the company upgraded to SQL Server 2005. We (my company and his) were not aware of compatibility issues between Nav 3.01 and SQL 2005, and in fact for the last two years we have not boticed any compatibility problems at all.

Suddenly, I am unable to modify or add tables in Navision. Using a developer license and a superuser ID, when I attempt to save a new or modified table, I get the message

"The following SQL Server error(s) occurred:

4628, "01000",[Microsoft][ODBC SQL Server Driver][SQL Server]The ALL permission is deprecated and maintained only
for compatibility. IT DOES NOT imply ALL permissions defined on the entity."

I have searched Mibuso, and have found the response that SQL 2005 is compliant only with Nav 4.0 and up. My questions are:

1. Why is it that after two years suddenly I can't add or modify tables? The obvious answer is, "something changed", but I didn't change anything!

2. The 'answer' to this problem is apparently that Nav 3.1 and SQL Server 2005 are not compatible. But is there any other possible recourse than to upgrade Navision (or degrade SQL)?

Thanks for your help...

Chandler

DenSter

I'm surprised that it has worked for such a long time. You can't make them compatible, so I only see two ways around this. First you could do a technical upgrade, and use the latest executables. This will cost you if you have not been paying for the maintenance fee. Second, you could start using SQL Server 2000. I don't know if it will work, but I'd say take a NAV backup, create a new database on SQL Server 2000 and restore the NAV backup in there, see if that will work.

bbrown

From SQL BOL

Granting ALL permission on objects and statements has been deprecated. When GRANT ALL is executed, the following occurs:

The command succeeds, but only permissions grantable in SQL Server 2000 are granted to the user.

You receive the following message: "The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity."

SQL Server 2005 provides additional permissions at various scopes that can be used to manage user permissions. For example, the CONTROL permission can be used to grant ownership-like permissions on an object.

ccbryan63

I figured out what changed: my company's developer license expired.

However, when I use our current license on the database in question, I find that while I can once again modify table structures, but I can no longer add tables, including those in the 50,000 range. And I can no longer add sumindex fields to keys. This makes sense since both adding tables and adding index keys involve creating tables in the SQL Database.

So while Attain 3.1/3.6 still 'works' with SQL 2005, "license creep" may force the issue (of support, anyway.)

David_Singleton

ccbryan63 wrote:

I figured out what changed: my company's developer license expired.

However, when I use our current license on the database in question, I find that while I can once again modify table structures, but I can no longer add tables, including those in the 50,000 range. And I can no longer add sumindex fields to keys. This makes sense since both adding tables and adding index keys involve creating tables in the SQL Database.

So while Attain 3.1/3.6 still 'works' with SQL 2005, "license creep" may force the issue (of support, anyway.)

Just get your developer license updated, that seems the simplest solution.