My SQL Server Database is Corrupt - Now What?!
How do you recover from corruption if your organization doesn't have a disaster recovery handbook? And how can you prevent the same corruption from recurring?
How do you recover from corruption if your organization doesn't have a disaster recovery handbook? And how can you prevent the same corruption from recurring?
As a production Database Administrator, I do not want to give Developers direct access to the SQL Server Agent job log especially for servers in the DMZ. Another problem we have is that when there is a lot of log data for a job, the default job log doesn't contain the full log detail and that makes it harder to troubleshoot. Most of all, we are trying not to use a different code set for deployment based on the environment. Basically we want to use the same methods to deploy our jobs to Development, Test and Production.
Phil Factor on his renewed appreciation for the "customer-focused" culture of the Data Platform Group at Microsoft
There is likely still a lot of 32-bit software out there, even as the x86 platform appears to be dying away. Steve Jones notes that you'll likely be dealing with 32/64 bit issues in your career.
This articles shows a technique that generates and launches an SSIS package to update statistics in parallel.
The most critical task for all DBAs is to have a Backup and Recovery strategy that ensures, every day, that in the event of a disaster they can restore and recover any database, within acceptable limits for data loss and downtime. Even with all the required backups in place, it's easy to miss subtle failings in the overall plan that can, and eventually will, defeat your recovery plans.
This Friday Steve Jones takes a break from serious technical discussions. With the Oscar nominees announced there were lots of films left out of the awards. Are there some of these you'd recommend?
You can download a free eBook from SQLServerCentral and Red Gate software on the most important task a SQL Server DBA or developer needs to understand.
In February 2008, Microsoft announced a record-breaking data load using Microsoft® SQL Server® Integration Services (SSIS): 1 TB of data in less than 30 minutes. That data load, using SQL Server Integration Services, was 30% faster than the previous best time using a commercial ETL tool. This paper outlines what it took: the software, hardware, and configuration used. We will describe what we did to achieve that result, and offer suggestions for how to relate these techniques to typical scenarios. Even for customers who don't have needs quite like this benchmark, such efforts can teach a lot about getting optimal performance.
Today Steve Jones talks about the future of software development and how it might not require developers to know anything about servers.
By Steve Jones
At Redgate, we’re experimenting with how AI can help developers and DBAs become better...
I was messing around performing investigative work on a pod running SQL Server 2025...
By Steve Jones
Redgate recently released SQL Compare v16, which included a new feature to work with...
Comments posted to this topic are about the item What is Page Density
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Looking to confirm my understanding of these three products and how they can be...
In SQL Server, there is a concept of page density. This is determined by how much data is stored on each page. What is a page density of 90%?
See possible answers