Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Group 4 Final


Published on

  • Be the first to comment

  • Be the first to like this

Group 4 Final

  1. 1. Group 4 Final ProjectSQL 2008 Enterprise Server X64 ByJohn Cocchiarella, Kerry Quam and John Stretch
  2. 2.  Processor Speed: Recommended 1.4 GHz or faster Processor Type X64 processor Memory –RAM Minimum 1GB Recommended 2.048 GB or more Maximum Operating System Maximum Hard Disk Minimum of 6 GB available Monitor Super VGA (800x600) or Higher Resolution
  3. 3. SQL Server Module Disk Space RequirementDatabase Engine and data files, 811MBReplication, Full-Text Search, andData Quality ServicesAnalysis Services and data files 345MBReporting Services and Report 304MBManagerIntegration Services 591MBClient Components (other than 1823MBSQL Server Books Onlinecomponents and IntegrationServices tools)SQL Server Books Online 200MB
  4. 4. Net Framework 3.5 Service Pack 1.Net Framework 4.0Windows PowerShellInternet Explorer 7.0 or later version for: Microsoft Management Console (MMC) SQL Server Data Tools (SSDT) Report Designer component of Reporting Services
  5. 5.  Windows Server 2008 R2 SP1 64-bit Datacenter Windows Server 2008 R2 SP1 64-bit Enterprise Windows Server 2008 R2 SP1 64-bit Standard Windows Server 2008 R2 SP1 64-bit Web Windows Server 2008 SP2 64-bit Datacenter Windows Server 2008 SP2 64-bit Enterprise Windows Server 2008 SP2 64-bit Standard Windows Server 2008 SP2 64-bit Web
  6. 6. Backups : Take regular full-database backups. Usethe BACKUP DATABASE command with theWITH CHECKSUM option to verify the back up.A daily full back up is advised, along withincremental backups every four hours.Retain the full-database backups for a minimumof 72 hours for full and incremental backups
  7. 7. There are two primary causes of data corruption:Physical - An alteration of data caused by hardware or hardware driversLogical – A data relationship becomes brokenTools to help identify data corruption:Turn on the “checksum” for your databasesRun DBCC CHECKDB on your databases as frequent as is practical
  8. 8. Over time, as indexes are subjected to data modifications,gaps in data on pages develop, and the logical ordering ofthe data no longer matches the physical ordering of thedata.How remove fragmentation from an index using SQL Server Management Studio:Use Sys.dm_db_index_physical_stats for fragmentation information.If fragmentation is >5% and < = 30% use ALTER INDEX REORGANIZEIf fragmentation is > = 30% use ALTER INDEX REBUILD
  9. 9. The End