When using a Geo Replicated Azure SQL Database Readable Secondary there are a few things to consider when it comes to performance tuning. Check out this episode of Data Exposed: MVP Edition as we discuss what you need to keep in mind with Microsoft’s Anna Hoffman, @AnalyticAnna.
-
-
Ever seen the below error? Until this week I hadn’t. So, I figured I’d take a little time and introduce it to those that had not. Error Description: Length of LOB data (65754) to be replicated exceeds configured maximum 65536. Use the stored procedure sp_configure to increase the configured maximum value for max text repl size option, which defaults to 65536. A configured value of -1 indicates no limit We ran into an issue with a customer this week, this error was flooding the error log. After a little digging I found it had to do with transactional replication (also applies to Change Data Capture) they had setup which included…
-
My life for the last 2 years has been a constant battle of putting out fires with system performance; finally user complaints have moved getting this resolved as my top priority. Let’s see how I tackled the problem… Symptoms: Very High Disk Latency as high as 300,000 milliseconds (ms) is not unusual Average: 900 – 15,000ms Memory Pressure Slow User Experience Problem: Bad hardware Over-provisioned VM Hosts (what happens on one VM effects the other) Old NetApp SAN No infrastructure budget for new hardware Challenge: Make the system viable with no hardware changes or tweaks Step 1: Brain Storming (in no particular order) Reduce I/O I can probably tune a ton…
