Technical |
Posted by Tom Carpenter
Jul
28
2010
When you backup the SQL Server transaction log, the log is truncated by default. The space that has been consumed by transactions is freed once those transactions are backed up. Backing up the transaction log of a database throughout the day allows you to recover to the point of failure or any point in time. In addition, because databases that are set to full or bulk logged recovery models do not truncate the transaction log during full or differential backups, it may be essential to backup the transaction log periodically just to truncate the log.
If you allow the transaction log of a database to become completely filled, users will be denied write access to the database until you clear the transaction log. Scheduling regular backups of the transaction log can prevent this from happening. When the log is full, users may still execute read-only SELECT statements against the database. You can also prevent the transaction log from filling up by enabling autogrowth on the transaction log.
Just as you can backup the database using SQL Server Management Studio (SSMS), you can backup a transaction log in the graphical interface. Just be sure to select the Backup Type of Transaction Log. The T-SQL command for backing up the transaction log for the AdventureWorks database is as follows:
BACKUP LOG AdventureWorks To DISK='C:\BACKUPS\AWorksTlog.bak';
The preceding content excerpted from SQL Server 2008 Administration by Tom Carpenter.
Tweet This Post
News |
Posted by Tom Carpenter
Dec
23
2009
Microsoft has changed the edition structure for SQL Server 2008 R2 by adding two new editions: Datacenter and Parallel Data Warehouse. The Datacenter edition adds features for management improvement and support for more than 8 processors. The Parallel Data Warehouse edition supports much larger data stores and enhanced data warehouse functions. For more information about these new editions and the traditional editions and what they'll look like in SQL Server 2008 R2, visit this page:
http://www.microsoft.com/sqlserver/2008/en/us/R2-editions.aspx
Tweet This Post
OK. We’ve decided to change the title of my upcoming SQL Server 2008 book. Instead of DBA’s Guide to SQL Server 2008, we’re calling it Real World SQL Server 2008 Database Administration: Skills and Knowledge for MCITP Certification and Beyond.
The reason for the title change is simple. We are covering the objectives for 70-432 and 70-450 in the book and we want this to be clear; however, we also realize people want more than a certification prep book. In fact, this book includes several entire chapters that have nothing to do with the certification, but everything to do with effective SQL Server 2008 administration. Hopefully, the new title will help to clearly communicate the purpose of the book.
Tweet This Post
My new book, the DBA’s Guide to SQL Server 2008 is well under way. The SQL Server 2008 book should be available early next year (2010) and it will include coverage of SQL Server 2008 R2. The book is focused on helping DBA’s effectively implement and support SQL Server 2008 servers and databases. Unlike many books on the market, it does not attempt to be all things to all people. It is not a book for programmers. It is a book for DBA’s and network admins who must support SQL Servers. If you would like to see coverage of specific topics, feel free to comment here and I’ll make sure as many are included as possible; however, I can only include topics provided to me by the end of September.
Back to writing!
Tweet This Post
