Explanation:Excessive casting of data typesit will only degrade performance. Match your data types to the source or destination and explicitly specify the necessary data type casting. 5. Point out the wrong statement :
A. Heap inserts are typically slower than using a clustered index
B. Use partitions and partition SWITCH command; i.e., load a work table that contains a single partition and SWITCH it in to the main table after you build the indexes and put the constraints on
C. Use the NOLOCK or TABLOCK hints to remove locking overhead
D. Use a commit size of <5000 to avoid lock escalation when inserting; note that in SQL Server 2008 you can now enable/disable lock escalation at the object level, but use this wisely
Answer:A
Explanation:Excessive casting of data typesit will only degrade performance. Match your data types to the source or destination and explicitly specify the necessary data type casting. 5. Point out the wrong statement :
A. Heap inserts are typically slower than using a clustered index B. Use partitions and partition SWITCH command; i.e., load a work table that contains a single partition and SWITCH it in to the main table after you build the indexes and put the constraints on C. Use the NOLOCK or TABLOCK hints to remove locking overhead D. Use a commit size of <5000 to avoid lock escalation when inserting; note that in SQL Server 2008 you can now enable/disable lock escalation at the object level, but use this wisely
Explanation:For using Heap inserts,you may want to drop indexes and rebuild if you are changing a large part of the destination table; you will want to test your inserts both by keeping indexes in place and by dropping all indexes and rebuilding to validate.[/expand] 6. Which of the following error message indicates that the package cannot run in SSIS ?