12.07.2015 Views

Solution Guide for Migrating Oracle on UNIX to SQL Server - Willy .Net

Solution Guide for Migrating Oracle on UNIX to SQL Server - Willy .Net

Solution Guide for Migrating Oracle on UNIX to SQL Server - Willy .Net

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<str<strong>on</strong>g>Soluti<strong>on</strong></str<strong>on</strong>g> <str<strong>on</strong>g>Guide</str<strong>on</strong>g> <str<strong>on</strong>g>for</str<strong>on</strong>g> <str<strong>on</strong>g>Migrating</str<strong>on</strong>g> <str<strong>on</strong>g>Oracle</str<strong>on</strong>g> <strong>on</strong> <strong>UNIX</strong> <strong>to</strong> <strong>SQL</strong> <strong>Server</strong> <strong>on</strong> Windows 357Capturing StatisticsSome of the points <strong>to</strong> be c<strong>on</strong>sidered <str<strong>on</strong>g>for</str<strong>on</strong>g> capturing statistics are:●●●●Types of data. The type of data being captured — qualitative or quantitative.Characte ristic. The statistic must be relevant <strong>to</strong> the test being per<str<strong>on</strong>g>for</str<strong>on</strong>g>med. It mustsuit the comparis<strong>on</strong>s being made or analysis <strong>to</strong> be per<str<strong>on</strong>g>for</str<strong>on</strong>g>med. CPU usagemeasurement is an example of a statistic that is relevant <strong>to</strong> testing.Unit of measurement. The unit of measurement would be dependent <strong>on</strong> themagnitude of the measured characteristic. An example is measuring andcomparing memory: the unit <strong>to</strong> be used is bytes or Mbytes.Frequency. The frequency of measurement of a statistic can be a critical decisi<strong>on</strong>.Too much data can be cumbersome and <strong>to</strong>o little could be harmful.Some examples of resources <strong>on</strong> which statistics can be captured are:● Memory usage of the system● Memory usage of the database● CPU usage● Disk I/O rate● Number of user c<strong>on</strong>necti<strong>on</strong>s <strong>to</strong> the database● Procedure cache usage● Number of transacti<strong>on</strong>s executed per sec<strong>on</strong>d● Data cache usage● <strong>Net</strong>work bandwidth usageComparing and Reporting ResultsTest results have <strong>on</strong>ly as much value as the inferences that can be drawn from them.Test results can have either a qualitative value or a quantitative value. In a developmentproj ect, the expected behavior of the soluti<strong>on</strong> is based solely <strong>on</strong> business requirements.For a migrati<strong>on</strong>, measurements from the existing soluti<strong>on</strong> <str<strong>on</strong>g>for</str<strong>on</strong>g>m the expected result.During the testing, the data from the migrated soluti<strong>on</strong> is compared with the expectedresults. Deviati<strong>on</strong>s from expected results cannot be c<strong>on</strong>strued as defects. As a result,analyzing and reporting results is a <strong>to</strong>pic of serious c<strong>on</strong>sequence. A thorough analysis ofthe results has <strong>to</strong> be made and c<strong>on</strong>clusi<strong>on</strong>s drawn based <strong>on</strong> several measurable andn<strong>on</strong>-measurable fac<strong>to</strong>rs (assumpti<strong>on</strong>s). The capabilities of the systems available <str<strong>on</strong>g>for</str<strong>on</strong>g>per<str<strong>on</strong>g>for</str<strong>on</strong>g>ming stabilizati<strong>on</strong> tests may be <strong>on</strong>e such fac<strong>to</strong>r.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!