![]() ![]() all level 1 components of a level 0 assembly, all level 2 components of a level 1 assembly) The CheckDate eliminates any components that are no longer used in the product on this date.”įor me, although this gives a technical description of what is happening, I have to look in three different places to get the overview and it doesn't really explain how the procedure works and what it should and should not do. “Use recursive query to generate a multi-level Bill of Material (i.e. “Stored procedure using a recursive query to return a multi-level bill of material for the specified ProductID.”įinally we have a comment in the procedure itself: We then have three extended properties, the first is most useful for documenting the procedure: If we then look at the parameters we have StartProductID and CheckDate which help to describe how it is used. If we look at this in terms of documentation, if we start with the name “uspGetBillOfMaterials”, I guess usp means it is a stored procedure and it gets a bill of materials. If we take the first stored procedure in the AdventureWorks2012 database to see how it is documented, if we take the procedure definition, we get: One of the things I mentioned was that having a suite of unit tests helps to document the code and in this post I would like to demonstrate that. I recently had the chance honour to spend twenty minutes talking to Boris Hristov about testing with Sql Server for his Google Hangouts series, catch the video here ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |