May 20, 2009 at 2:53 pm
I am working on autamting our dataload process with SSIS pkgs and i have hundreds of sql scripts in the ETL process. How would i test all my scripts to check every rule in the script is working perfect.
Thanks
May 20, 2009 at 3:23 pm
Tara (5/20/2009)How would i test all my scripts to check every rule in the script is working perfect.
Carefully? 🙂
Welcome to the ancient art of building a testing environment.
You have to ensure you have a baseline that would allow you to repeat the testing process.
You have to ensure test data covers every single business rule -Business side would help with this.
You have to ensure you have a way to control code versions.
You have to ensure you have a way to measure if testing is going forward or backwards e.g. less or more problems as testing goes on.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.May 20, 2009 at 5:32 pm
Yes your test data on every part of the script to ensure it is met.
Better to test every line of code before it goes into production and ends up in a loop and causes the log file to grew and crash the entire system because you never tested a while loop ending.
May 21, 2009 at 10:23 am
I am looking for a tool that checks hundereds of rules in our scripts automatically and give us a reports for each test case. We do not have a testing team with us and so would like to depend on the bets tool which tests all our scripts and also do reporting.
May 21, 2009 at 12:22 pm
I not sure there is a tool that would go through your code i.e
for qty and pass in these values and see if is meet.
If qty > 0
begin
print 'you reached me so go update this'
end if
if qty = '0'
begin
print = 'you have nothing get out'
end if
The only thing i can think of is you know the logic and pass in the parameters and ensure each part of the code works.
At end of day you write for business purposes and these should be available as to what the code is supposed to do.
If you want to see if you application breaks when you have 100 users on it and check that the performance is good then you can get benchmark tools from quest.com
If you want to make sure your code is optimized then use tools like toad for quest or run execution plans in sql to see if using the write indexes.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply