4

I have imported the certificate and the key and I have created a symmetric key however, whenever I try to decrypt the credit cards, it just returns NULL. If the symmetric key you are talking about is one you've manually created in the user database then you'll need to create it with the same initialization vector as the previous one by specifying a ...


2

Every write is performed on every machine, whether it is a Master or a Slave. The corollary to that is that there is a limit to write scaling with traditional Replication. Even Galera and Group Replication are just variants on Master(s) and Slave(s). Each server has all the data, and it is kept as up-to-date as is practical. Hence, Sharding is the only ...


1

It sounds like you'd benefit from using procedural replication for those stored procedures. That way, SQL Server will just run the procedures on the replicated instance rather than replicating all the DELETE and INSERT operations. I'll wager that will be much faster and will reduce latency in addition to fixing the issue you're seeing where the destination ...


1

The minimum for an HA setup is 3 nodes, geographically distributed. If you put all the nodes in a single data center, you are vulnerable to a datacenter crash. (They do happen.) If you use Master + Slave(s), failover is not well automated. See MHA as a possible alternative. With Galera cluster, you can write to all nodes, thereby helping minimize downtime....


1

Check out this Microsoft KB article: You receive an "Error 18482" error message when you try to make a remote procedure call (RPC) from one server to another in SQL Server Especially the very last part: You may receive this error message when installing replication because the installation process makes remote procedure calls between the servers ...


1

I have a data warehouse that multiple sources of data feed into. I generate a new PK, but bring in the original PK from the source along with it. With a lot of the feeds I also bring in a 'source key' that's typically an environment variable or something to identify the actual source, and then create a composite key to differentiate between original PKs that ...


1

converting my comment to answer ... Since you confirmed that the db compatiblity is 90 which is sql 2005 Run SELECT name, compatibility_level FROM sys.databases WHERE name = 'YOURDBName' and then you can use ALTER DATABASE [YOURDBName] SET compatibility_level = 110 -- 2012 version


1

With PostgreSQL logical replication, the table on the standby server (where the subscription is) is available for data modifications. This is different from physical replication, where the standby is a physical copy of the primary and cannot be modified directly. Perhaps your confusion originates there. While you can modify the table on the standby, it is ...


1

By default, CREATE SUBSCRIPTION will first copy all the existing data from the source tables. The idea is that you usually start with an empty destination database created with something like pg_restore -s. If you don't want to have the initial data copy, create the subscription like this: CREATE SUBSCRIPTION ... WITH (copy_data = false); See the ...


1

CREATE SUBSCRIPTION mysub CONNECTION 'dbname=testha host=192.168.150.210 user=postgres password=postgres port=5432' PUBLICATION mypub; What was the output of this command? You should have gotten something like either: NOTICE: created replication slot "mysub" on publisher CREATE SUBSCRIPTION Or ERROR: could not create replication slot "mysub": ERROR: ...


Only top voted, non community-wiki answers of a minimum length are eligible