Navision timestamp column issue

(0) Share

Report

Posted on by Community Member

Is it possible to remove default timestamp column from Navision 2016. We want to move data into azure using stretch database functionality but due to timestamp column limitation we are not able to do so. Is there any workaround for this timestamp column?

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Luc van Vugt on at

Like (0)

Report

The Timestamp field is used by NAV for versioning each record in a table. A such it's an essential part of NAV so don't touch it.

Some more info you can find by googling for "NAV Timestamp field versioning". F.e. https://dynamicsuser.net/nav/b/kriki/posts/timestamp-field-in-sql-and-nav2016.

Was this reply helpful? Yes No
Suggested answer

Suresh Kulla 50,245 Super User 2025 Season 2 on at

Like (0)

Report

As Luc mentioned it is a internal field used for versioning don't mess up with that field, what kind of workaround are you looking for ?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Due to this timestamp column I am not able to stretch the database to azure. So We want to change its datatype .I tried BigInteger in Nav 2016 but it is dependent on existing timestamp column. If it is there in the table I can apply stretch database solution of SQL 2016. So I wanted to remove it from tables.

Was this reply helpful? Yes No
Luc van Vugt on at

Like (0)

Report

Did you reference resources like this one https://msdn.microsoft.com/en-us/library/dn951458(v=nav.90).aspx?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks a lot Luc for your help. We have implemented the solution you suggested above in one of our database and that is working fine. This is a different problem. In SQL Server 2016 there is a new feature of Stretch database which archives historical database in azure database and returns it on demand. No programming required for that. We wanted to implement that feature in our Navision database. But this does feature does not support timestamp datatype. That is why we are not able to implement this great feature of SQL. So was looking for its work around. But it seems it does not have any solution..Please suggest. Thanks.

Was this reply helpful? Yes No
Suggested answer

dkatson 2,263 on at

Like (0)

Report

Did you asked Microsoft for that? I think this is general case.

How ever I have many NAV installations that works perfectly in Azure without any problems.

Was this reply helpful? Yes No