Ases | Ases - An esoteric programming language | Interpreter library

You will need to deploy at least two ILB ASEs - one per zone. After that create and publish copies of your application onto each of the AZ deployed ASEs. You will additionally need to deploy a load balancing solution upstream of the AZ deployed ASEs so that traffic bound for an application is distributed across all instances of the ASEs.

This link and Autoscaling should help

You're assigning the subscription to the variable elements. Instead it should be the following

If you are using visual studio 2019 then you should be able to turn on C++17. This demo uses std::optional. Not sure how efficient it is, but it's convenient.

I have replaced host_name() in my table schema with asehostname() and my problem is solved. host_name() was returning the name of the machine executing the bcp job every time, rather than the ASE host where the data is coming from.

It is trying to convert something that throws a FormatException. If you are able to do so then do something like this

The critical thing with routes is they both need to be in the same replication system, meaning they must share the SAME primary rep server (known as the ID server) - this contains information about all the replication servers in the replication server setup, or domain as it's known. You can create many replication servers in a domain, but for them to be able to link together via routes they must all use the same ID server.

NOTE: You can't set them up separately and then link them later. When you set up RS2 you have say RS1 is the id server and put in all the required info into rs_init for RS1 as you run through the various rs_init menus to create RS2.

If that's been done already correctly then:

Firstly set up route between RS1 and RS2 (via a 'create route' command here) if you want data to flow in both directions at some point it makes sense to setup routes both ways between RS1 and RS2, as by definition a route is in one direction. This will mean you can set replication up between any of the three ASE instances.

NOTE: You need to check that the route is actually fully up and active (via admin who) - if not then you need to start looking through the rep server errorlogs as to why that's failing e.g. missing entry in interfaces file, login issue etc.

One routes are set-up you can create a subscription replication definition against the source database and a subscription at the target database when these are attached to different replication servers. This can be at the table-level or a database-level replication definition (MSA) depending on what your aim is.

As you're using an older version of SQL Server you have no access to STRING_SPLIT or STRING_AGG. The former, however, isn't particularly helpful here as Microsoft still haven't implemented ordinal positions into the function and it only supports a single character splitter.

I am going to instead use DelimitedSplit8k_LEAD which does support ordinal positions. Unfortunately, it too only supports a single character splitter, so I have replaced the double semi-colon (;;) delimiter with a pipe (|); as i assume that won't appear in your data.

2012 also doesn't have TRIM, so you'll need to use RTRIM and LTRIM to trim the values.

Finally, you can use the "old" FOR XML PATH method to "re-aggregate" the string:

Without a proper data sample and complete knowledge of your data, it's hard to know what's the cause of the error. But with newer versions of plotly you should be able to show plotly figures in Spyder with examples like the one below. Try that, see if it works, and tell us what you find out.

Version info:

Sounds like you need to be using an APPLY statement. Not sure if the join criteria on the APPLY statement is correct, but you should be able to extrapolate the logic. See if that will work with Sybase.