July 25, 2019 at 7:04 am
Hi
We've enabled TDE on a databases that are replicated to DR. The SQL instance is on a VM and the whole VM is replicated at the block level.
When we tested the SQL instance at DR no writes would commit. As soon as we set encryption to off, on the databases, transactions started to commit.
Once the database had unencrypted we re-encrypted it again, and it carried on working.
Once TDE was enabled I thought you'd be able to read\write to the databases or not. Being able to read but not write doesn't fit in with my understanding of how TDE works. I'm going to do some tracing but has anyone come across a similar issue?
July 25, 2019 at 7:27 am
That is strange. If the blocks are all moved, that should mean your master db is moved, and with it the certificate needed for the encryption/decryption.
Off the top of my head, this doesn't really make sense. I assume this was a one time replication or is it constant? Once the far side is up, no commits to any db? Or just the TDE ones?
July 25, 2019 at 7:34 am
I have no idea what was going on, but I'm curious what error message did you get when writes did not commit?
[font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]
July 25, 2019 at 7:38 am
Hi Steve
Thanks for the reply,
I'm just doing some initial investigations, I'll post up some results in half an hour or so. This landed on my desk after being on leave yesterday!
Cheers
Alex
July 25, 2019 at 7:47 am
So far, no error at all.
I just updated a single record. Everything looked ok, but when I restarted SSMS and queried the table the update wasn;t there.
I'm just going to profiler it.
July 25, 2019 at 10:23 am
Looks like this may be an application\performance issue at the DR site.
Thanks for your interest.
Alex
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply