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.
A procedure that generates point in time restore database & log commands for your databases.
There are several different ways of restricting access to SSIS packages and confidential information they contain. However, preventing unauthorized users from running or viewing the content of your code is not the only security measure that you should take into consideration.
Why is it so hard to build better software? Steve Jones looks at recent problem in iOS that seems silly.
In this article, we'll tackle the topic of monitoring disk space usage. By tracking how much is in use and how much is still available, over time we'll have the data we need for better capacity planning, and can ensure that a database won't ever run out of disk space.
This tip describes memory pressure issues that can arise from the RESOURCE_SEMAPHORE Waittype and how to find which query or transaction is causing the memory pressure.
By Arun Sirpal
Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...
By DataOnWheels
This is a blog that I am writing for future me and hopefully it’ll...
By Steve Jones
While wandering around the documentation looking for some Question of the Day topics, I...
Comments posted to this topic are about the item Pro SQL Server Internals
Comments posted to this topic are about the item SQL ART: Who's Blocking Who?...
Comments posted to this topic are about the item Running SQLCMD II
I run this command to start SQLCMD:
sqlcmd -S localhost -E -c "proceed"At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version 2> goWhat happens? See possible answers