Corruption

External Article

Troubleshooting and Fixing SQL Server Page Level Corruption

  • Article

Corrupt SQL Server databases are the worst nightmare of any SQL Server professional. In any environment, from small business to enterprise, the compromise of integrity and availability of the data can constitute a business emergency. This is especially the case in those organizations reliant on an OLTP data model, for a high-volume website. SQL Server database corruption and disruption of the transaction processing system can cause business repercussions such as large financial losses, a drop in reputation or customer retention, or contractual SLA problems with the service provider, if not managed in-house.

2013-02-18

3,385 reads

Blogs

T-SQL Tuesday #199 Invitation: Back to on-prem?

By

It’s time for T-SQL Tuesday again! And we’re almost to number 200! T-SQL Tuesday...

Data Skew in Data Engineering: What It Is and How to Fix It

By

You kick off a distributed job expecting it to finish in minutes — but...

Error Deploying GraphQL in Fabric: dm_exec_describe_first_result_set

By

A while ago we suddenly had an error while trying to deploy one Fabric...

Read the latest Blogs

Forums

Secure Cached Plans

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Secure Cached Plans

Complex Data Processing with dbt Python Models: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Complex Data Processing with dbt...

Over or Under Provisioned

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Over or Under Provisioned

Visit the forum

Question of the Day

Secure Cached Plans

The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?

See possible answers