Hi Darren

While it is technically possible at the database level in Microsoft SQL Server to change a column from INT to BIGINT, Sage CRM has not been tested with BIGINT, and therefore environments where such changes have been made fall outside of supported configurations.

BTW testing would be quite big as we would have to consider

• Mismatches between the database and CRM metadata
• Unexpected behaviour in the application layer (ASP pages, .NET components, APIs)
• Issues with joins, foreign keys, and integrations
• Potential problems during upgrades or patching

If you have logged a case, then ask the local support team to log it with us as an enhancement - we would need to understand the need to support a field type that has to support numbers larger than a couple of billion and into the quintillion range!

Hi Darren

While it is technically possible at the database level in Microsoft SQL Server to change a column from INT to BIGINT, Sage CRM has not been tested with BIGINT, and therefore environments where such changes have been made fall outside of supported configurations.

BTW testing would be quite big as we would have to consider

• Mismatches between the database and CRM metadata
• Unexpected behaviour in the application layer (ASP pages, .NET components, APIs)
• Issues with joins, foreign keys, and integrations
• Potential problems during upgrades or patching

If you have logged a case, then ask the local support team to log it with us as an enhancement - we would need to understand the need to support a field type that has to support numbers larger than a couple of billion and into the quintillion range!

The need to support BigInt is very close to home - Sage 200 - In the SLCustomerAccount table the master key (SLCustomerAccountID) is a BigInt field, a value that gets synchronised in integrations and we've come a cross a customer whose Sage 200 is now populating it with values bigger than a normal INT can handle. The integration in CRM is currently forced to store it in a nVarChar field - which is not ideal for database indexing etc. 

There we have out business case!  I will raise a development request.