In my last post, I talked about how you can get 43%-67% faster backups. This time, I’m using that same SQL Server setup to discuss how throwing more CPU cores might help you check for corruption faster if you’ve already got modern fast storage.
2020-09-28
You want to check for corruption, but you don’t want to slow down your primary production server. In this post, I’m specifically talking about offloading the corruption checking process. I’m not talking about doing corruption checking on both the primary and other servers – that’s wonderful, and if you’re doing that, you should hug yourself. You’re doing a good job. Who’s a good dog? You are! Good dog.
2020-06-19
When mirroring was first released for Azure SQL Database, it used Change Data Capture...
By Steve Jones
One of the things I’ve tried hard to do in database development situations if...
By DataOnWheels
The T-SQL Tuesday topic this month comes James Serra. What career risks have you...
We have two "identical" instances of an ASP.NET web service (or so I have...
Comments posted to this topic are about the item OPENQUERY Flexibility
Comments posted to this topic are about the item A Full Shutdown
Which of these are valid OPENQUERY() uses?
See possible answers