SQL Server Performance Tuning
SQL Server Performance Tuning for SQL Server 2005, 2008, 2008 R2,2012
SQL Server Performance Tuning for SQL Server 2005, 2008, 2008 R2,2012
Blogs
Data Warehousing Workshop (3/4)
|
|
For Full blog , you may have a look at ::
http://www.sqlserverpath.org/2012/02/15/data-warehousing-workshop-34/
Categories: Data Warehousing , Database Developement, Reporting Service
Post a Comment
Oops!
The words you entered did not match the given text. Please try again.
15 Comments
For such large DBs even TB DBs containing BLOB ( Binary Large objects), I recommend heavily to follow the below :
? Apply appropriate schema partitioning for huge tables aligning with volume of data entity exists there currently and expected DB growth for the upcoming times..
? Also , don't forget to use alignment partitioning using collation form ( Align tables on their PKs and FKs that are used within join columns within relevant OLAP queries..
? Then try to apply Storage aligned concept (Aligning indexes of partitioned tables on the same partitioning schema used for the table itself to approach closely the most optimal IO +Parallel processing)
? Despite of that try to perform your best to distribute these partitioned file groups on separated disks ( If local storage is used ) or separated SAN LUNs configured in different RAID G .
? Moreover, rebuild index either with online of offline option or online option will take significant time that , thereby it recommended to use re-organize the leaf of indexes instead of Rebuild to save .n impacts.
? Also , don't to use archiving solution to control such huge entity , you may have a look at my blog for this regard http://www.sqlserver-performance-tuning.com/apps/blog/show/129271
73-data-warehousing-workshop-3-4-
Kindly let me know if you have any
? Apply appropriate schema partitioning for huge tables aligning with volume of data entity exists there currently and expected DB growth for the upcoming times..
? Also , don't forget to use alignment partitioning using collation form ( Align tables on their PKs and FKs that are used within join columns within relevant OLAP queries..
? Then try to apply Storage aligned concept (Aligning indexes of partitioned tables on the same partitioning schema used for the table itself to approach closely the most optimal IO +Parallel processing)
? Despite of that try to perform your best to distribute these partitioned file groups on separated disks ( If local storage is used ) or separated SAN LUNs configured in different RAID G .
? Moreover, rebuild index either with online of offline option or online option will take significant time that , thereby it recommended to use re-organize the leaf of indexes instead of Rebuild to save .n impacts.
? Also , don't to use archiving solution to control such huge entity , you may have a look at my blog for this regard http://www.sqlserver-performance-tuning.com/apps/blog/show/129271
73-data-warehousing-workshop-3-4-
Kindly let me know if you have any
Oops!
Oops, you forgot something.