Home | Contact Us | Log In | Help
HOME NEW LISTING MOST POPULAR HIGHEST RATED SCRIPTS ADD SCRIPT DOWNLOADS FORUM
Tutorials
  ASP.Net & C#
  ASP
  Perl and PHP
  Java Scripts
  C and C++
  Ajax Tutorials
  J2ee, J2Me, Java
  Python & Ruby Rail
  Crystal Report
  Sap
  CGI
  XML
  Cold Fusion & CFML
  HTML, DHTML & CSS
  Dreamweaver
  FLASH
  Photoshop/Web Designing
  Tools & Utilities
  Oracle/D2K
  Sql Server
  MySql
  Domain Name Registration
  Remotely Hosting
  Web/Server Application
  Hotel Marketing
  Internet and Law
   Search Engine Optimization/SEO
E-Commerce
Interview Questions
SQL Server 2
SQL Server 2005 Practical Troubleshooting

This is the definitive guide to troubleshooting the Microsoft SQL Server 2005 database engine, direct from the people who know it most intimately: the people who wrote it, designed it, and support it. SQL Server expert Ken Henderson, author of the best-selling Guru’s Guides to SQL Server, has assembled a “dream team” of SQL Server developers and support engineers to provide in-depth troubleshooting and diagnostic information that has never been documented before: information that would be impossible to get without access to Microsoft’s own source code. You’ll find comprehensive, in-depth chapters on

• Waiting and blocking
• Data corruption and recovery
• Memory
• Procedure cache issues
• Query processing
• Server crashes and other critical failures
• Service Broker
• SQLOS and scheduling
• tempdb
• Clustering

Using BACKUP and RESTORE in SQL Server -- Full Backups

In a typical installation SQL Server stores its data in two files. One has an MDF extension and stores the data itself and the other has an LDF extension and stores the transaction log. You can configure SQL Server to have multiple data files and multiple transaction log files if you'd like but that's beyond the scope of this article. When SQL Server processes a transaction it goes through the following steps:

  1. It writes what it's going to do to the transaction log.
  2. It makes the change to the data file. This change is typically made on the in-memory copy of that portion of the data file.
  3. It writes to the log that the transaction is committed.
  4. The CHECKPOINT process writes the portion data file associated with the transaction to disk. This might happen anywhere from seconds to minutes after the step above.
  5. It writes to the log that the transaction is "hardened".
Reporting Services Makes Server Support Easier

Welcome to the largest Microsoft SQL Server community on the web with 417,550 registered members! SQLServerCentral.com offers you thousands of SQL Server articles, FAQs, scripts, and forums to help your professional development as a DBA, developer or user of SQL Server. Whether Microsoft SQL Server 7.0, 2000 or 2005, we have the information you need to make you a better SQL Server user. Best of all, this is a completely free resource!

Reporting Services Makes Server Support Easier Reporting Services is one of the most widely used subsystems in SQL Server and there have been some very creative solutions invented by DBAs around the world. New author Carolyn Richardson is one of those, bringing us a implementation that tracks uptime and disk space for her SQL Servers

SQL Server Magazine

SQL Server Magazine Forums, SQL Server Magazine is the technical guide to managing, mining, building and developing SQL Server databases.

Are you looking for SQL tools to make your life easier? Then this forum is the place for you to discuss the wealth of free tools in the SQL Server marketplace and help you find them.

Looking for an answer? Search our Frequently Asked Questions first. If you have an answer to an often-asked question, please email it to forumfaqs@sqlmag.com and we'll add it to this section for everyone to see!

  Copyright 2000-2006 © SoloScript.com, All rights reserved.