Saturday, July 3, 2010


Administrative Activities That Are Required For SQL Server

The practical behavior and acceptability of an application based on SQL Server depends on several administrative activities:
  1. Backing up your data regularly to minimize the possibility of losing important business data. You need to consider issues such as hardware failure (for example, a hard drive that fails) or external events such as a fire in the building that houses your database server(s).
  2. Verifying that data has backed up successfully. Storing backups in a remote location (or locations) ensures that no single disaster can destroy your business while you attempt to get SQL Server up and running again.
  3. Ensuring that you can restore backed up data. 
  4. Replicating data between business sites if it’s important that both sites have access to synchronized data.
  5. Selecting hardware that supports scalability or high performance; for example, hard-drive size and configuration, and clustering of SQL Server machines.
  6. Using database mirroring (introduced from SQL Server 2005) to allow rapid failover from a failing SQL Server machine to another SQL Server machine that has the database in the same state. That allows your application to continue on the other machine with little or no appearance of a problem to users or customers.
The database engine in SQL Server is designed to support robust, reliable processing of data. In addition, it’s designed to support configurations that ensure high availability and scalability. 

If you’re going to design database applications that support your business’s interaction with its customers, the database must be accessible when customers need it. It’s bad business to lose orders simply because the database isn’t available when your customer wants to place an order.


About bench3 -

Haja Peer Mohamed H, Software Engineer by profession, Author, Founder and CEO of "bench3" you can connect with me on Twitter , Facebook and also onGoogle+

Subscribe to this Blog via Email :