SQL Server Performance

Database Testing

Discussion in 'EditorsBlog' started by shanetasker, Dec 2, 2008.

  1. shanetasker New Member

    One of the challenges of working with databases is how to effectively test changes to them. For example, if the size of a data type is changed or a column is re-named, how do you go about testing all of the processes that potentially touch the column? I have come across all sorts of different approaches that teams use in order to try and test changes to the database. These have included everything from manual testing through to fully automated test harnesses.
    Many people have commented that Visual Studio Team System 2008 Database Edition (aka 'Data Dude') is a product not worth paying for. Especially when there are so many third party tools that perform many of the functions included with Data Dude at significantly lower price points. However, one area where Data Dude does excel is in the area of integrated and automating testing capabilities. It is great to see that the product team continues to develop and enhance the features that are available in Data Dude. A new GDR for Data Dude has been released which can be downloaded from here. Although this release contains some important new features, is the cost of Data Dude really worth it?
    - Peter Ward
  2. avantbond New Member

    A little birdy told me that MS is planning to roll Data Dude into the next version of VS TFS with some additional improvements.
  3. Anonymous New Member

    Pingback from sql server | Digg hot tags
  4. pward New Member

    Microsoft has announced (http://www.microsoft.com/presspass/press/2008/sep08/09-29VS10PR.mspx) that Visual Studio Team System (VSTS) 2010 will provide a unified VSTS Development and Database product.
  5. mfrancis New Member

    HiSQL Data Generator from Red Gate is a great value tool that can be used to fill databases with realistic test data in one click, or if you want to, customize the data.Check it out at http://www.red-gate.com/products/SQL_Data_Generator/index.htm
  6. matt.chatterley New Member

    We tend to achieve this via automated testing (NUnit) of DataLayer methods which encapsulate the database functionality - test fixture set up methods prepare the data (either in a few inline queries if simple, or loading bulk from XML if complex) - and then run through all the methods in their various negative and positive permutations.That said, this doesn't really solve the problem of creating the test data in the first place - even though we refine test data if issues arise from manual testing later on - essentially using it to prevent regressions - it is still easy to overlook complex interactions if extreme care is not taken!

Share This Page