Add more digits to the file extension for file based replication

[JimDiaz]

I. 07/26 18:07:44. The maximum number of messages in the messaging system has been reached.

Why the limitation?

[Former Member]

Probably held over from the old 8.3 file naming convention of yesteryear.

[regdomaratzki]

SQL Remote only currently uses three characters in the extension for messages files for the FILE, FTP and HTTP message system, and we limit the characters to alpha-numeric character. Because of that, the maximum number of messages that one database can send to another database in the system is 36 + 36*36 + 36*36*36 = 47988. At the default message size of 50K, that allows for approximately 2GB of SQL statements to be pending in the message system.

If you reach the maximum number of messages, you will need to either increase the message size, or convince your remote databases to pick up messages more often.

[JimDiaz]

Yes, thanks but the limit I believe is 36 * 36 * 36 = 46,656

[Former Member]

We also did bump into that limitation one or two years ago. We did solve it by incrementing the message sizes,

[regdomaratzki]

36*36*36 is correct if SQL Remote only used three digit extensions, but SQL Remote will first use files with a single character extension (.0 -> .z), and then two character extensions as well (.00 -> .zz), so that's why we need to add another 36 + 36*36.